# Macro Community Forum: Where Users Get Support in 2024

> Find Macro community support in 2024 via GitHub Discussions, Issues, and Slack integrations. Get help directly from the macro-inc/macro team.

- Repository: [Macro/macro](https://github.com/macro-inc/macro)
- Tags: community-engagement
- Published: 2026-08-14

---

**Macro does not operate a dedicated public forum; official community interaction happens through GitHub Discussions, GitHub Issues, and built-in Slack-style messaging integrations.**

The open-source **Macro** project—hosted at `macro-inc/macro`—takes a code-first approach to user support. Rather than maintaining a standalone community forum, the project channels all public discussion through native GitHub features and internal workspace tools. This article examines every community touchpoint found in the source code, shows you exactly where to ask questions, and explains how Macro's architecture anticipates forum-style interactions.

## Where to Find Macro Community Support

### GitHub Discussions and Issues

According to the repository structure and project documentation, **GitHub Discussions** and **Issues** serve as the primary community venues:

- **GitHub Issues** (`https://github.com/macro-inc/macro/issues`) — bug reports, feature requests, and technical problems
- **GitHub Discussions** (`https://github.com/macro-inc/macro/discussions`) — Q&A, ideas, and general community conversation

These channels are actively monitored by maintainers. No separate forum URL exists in any analyzed source file.

### Slack-Style Workspace Integration

The Macro codebase includes a **Model Context Protocol (MCP) integration for Slack**, indicating built-in support for channel-based messaging. This integration appears in:

```json
// crates/mcp_client/src/domain/provider_registry/slack/manifest.json
{
  "name": "macro-slack",
  "description": "The Macro : Slack MCP integration will allow users to effortlessly use slack communication in the macro workspace.",
  "long_description": "The macro workspace provides a chat client that can act on user requests..."
}

```

This manifest defines a **Slack-like channel service** within the Macro workspace. However, the source code does not reference a **public** Slack workspace or external community chat—this integration appears designed for private team communication rather than open community access.

## Forum-Style Features in Macro's UI

The project's documentation explicitly acknowledges forum-style interaction patterns. In `apps/docs/switch-to-macro.mdx`, a feature comparison table lists:

```markdown
| Inline thread replies (forum‑style reading) | X | ✓ |

```

This indicates Macro's **thread reply system** supports forum-style reading workflows. The UI anticipates discussion-thread patterns, but the underlying community infrastructure remains GitHub-based rather than operating an independent forum platform.

## Key Files for Community Interaction

| File | Purpose | Community Relevance |
|------|---------|-------------------|
| [`README.md`](https://github.com/macro-inc/macro/blob/main/README.md) | Project overview and quick-start | Entry point for new users |
| [`CONTRIBUTING.md`](https://github.com/macro-inc/macro/blob/main/CONTRIBUTING.md) | Contribution guidelines | Community participation rules |
| `.github/ISSUE_TEMPLATE/` | Issue templates | Structured bug reports and feature requests |
| [`crates/mcp_client/src/domain/provider_registry/slack/manifest.json`](https://github.com/macro-inc/macro/blob/main/crates/mcp_client/src/domain/provider_registry/slack/manifest.json) | Slack MCP integration | Internal messaging architecture |
| `apps/docs/switch-to-macro.mdx` | Migration and feature guide | Documents forum-style UI capabilities |

## How to Get Help as a Macro User

Follow this sequence for fastest community support:

1. **Search existing discussions first** — Check GitHub Discussions for similar questions
2. **Open a Discussion** — For how-to questions, configuration help, or general conversation
3. **File an Issue** — For confirmed bugs, crashes, or concrete feature requests with reproducible steps
4. **Review documentation** — Consult `apps/docs/` for usage patterns and migration guides

No registration beyond a GitHub account is required. The maintainers respond to both Issues and Discussions, making this the authoritative community channel.

## Summary

- **No dedicated forum exists** for Macro users in the public codebase
- **GitHub Discussions and Issues** serve as the official community platform
- **Slack MCP integration** provides internal team messaging, not public community chat
- **Forum-style thread UI** is built into Macro's interface but backed by GitHub for community use
- **All community paths** require only a standard GitHub account

## Frequently Asked Questions

### How do I ask a question about using Macro?

Open a **GitHub Discussion** at `github.com/macro-inc/macro/discussions`. Choose the Q&A category and provide your Macro version, operating system, and a clear description of what you're trying to accomplish. Maintainers and community members monitor this channel regularly.

### Is there a public Slack workspace for Macro users?

No. While the source code contains a **Slack MCP integration** ([`crates/mcp_client/src/domain/provider_registry/slack/manifest.json`](https://github.com/macro-inc/macro/blob/main/crates/mcp_client/src/domain/provider_registry/slack/manifest.json)), this supports private workspace messaging rather than a public community Slack. All public community interaction occurs through GitHub.

### What should I use for bug reports versus general questions?

Use **GitHub Issues** for bug reports with reproducible steps, crash logs, or specific feature requests. Use **GitHub Discussions** for "how do I," "best practices," or open-ended questions. This separation helps maintainers prioritize engineering work while keeping community conversation accessible.

### Does Macro plan to launch a dedicated forum?

The source code analysis reveals **no evidence** of planned forum infrastructure. The project architecture—using GitHub-native tools and internal Slack-style messaging—suggests the maintainers intentionally consolidate community activity on GitHub for transparency and searchability.