Macro

Turn separate work surfaces into one bidirectionally linked context graph

Macro keeps Email, Messages, Tasks, Docs, Canvas, and CRM as purpose-built surfaces while placing them on the same backend and bidirectional graph. A task created from a customer email can retain its source relationship, and mentioning a company record in chat creates a link that can later be followed back from the CRM record. Markdown-compatible documents use CRDT-based collaboration and can @link emails, tasks, messages, companies, contacts, and other workspace objects. The core idea is to preserve relationships between the original contexts rather than copying summaries from one system into another.

Sources: [1]

Build team-level memory from operational activity and expose it to internal or external agents

Macro's agent layer synthesizes team conversations, DMs, sent and received email, and task activity into team-level memory rather than learning only from AI chat history. That memory is stored in Markdown and can be used by Macro's own model picker or exposed through MCP to external agents such as Claude Code and Codex. The project also aims for broad MCP coverage of actions available in the UI, so agents can move beyond retrieval into work such as drafting email, creating tasks, and editing documents.

Sources: [1][2]

For small teams whose context is fragmented across Slack, Notion, issue trackers, email, and CRM

Macro fits startups and small teams that spend significant effort reconstructing the latest state of work across separate communication and productivity systems. It is particularly relevant when a customer email should lead to a task, then a pull request, while preserving an auditable chain back to why the work exists, or when sales and engineering context should be available to the same AI agent. It is less compelling as a minimal single-purpose tool and more compelling when a team is willing to consolidate a substantial portion of its operating context into one system.

Sources: [1][2]

Self-hosting is possible, but the hosted product is still the primary path and external service dependencies remain

Macro is fully open source under AGPLv3 and can be self-hosted, but its FAQ says self-hosting was not the primary focus as of June 2026. The hosted service includes approved integrations for the iOS app, Google Mail, and GitHub, while a self-hosted deployment may need to maintain licenses or configuration for dependencies such as LiveKit, FusionAuth, and PostHog, or disable the related functionality.

Email support is currently centered on Gmail and Google Workspace, and Macro is an email client rather than an email server. AGPLv3 is a strong copyleft license: modified network services and derivative works may carry source-sharing obligations. Macro explicitly directs users who want to build closed-source or under an incompatible license to obtain a separate license.

Sources: [2][3]