Skip to content

armgit / macro

Public Imported from GitHub
0

Macro is a unified workspace for teams: email, chat, docs, tasks, agents, calls, and CRM — @-linked together with shared AI memory.

docs: Agents rewrite, Unified Tagging page, and CRM/Tasks copy edits (#5383)

juliawestae6683324487
diff --git a/apps/docs/product/agents.mdx b/apps/docs/product/agents.mdx
index f3a004225d..8c26536fbb 100644
--- a/apps/docs/product/agents.mdx
+++ b/apps/docs/product/agents.mdx
@@ -75,7 +75,7 @@ Agents can run on a schedule. An automation is a saved prompt that runs on its o
### Choosing a model
-A model picker sits in the chat input. You choose a model per chat, so you can reach for a stronger one on a hard question and stay fast on everyday ones. Your choice is remembered for that chat and carried forward when you start a new one from the composer.
+A model picker sits in the chat input. You can choose a model per chat depending on how difficult you deem the question. Your choice is remembered for that chat and carried forward when you start a new one from the composer.
Without a Macro Pro account you can only use Haiku, the fast model. More capable models are available once you upgrade.
@@ -85,7 +85,7 @@ Without a Macro Pro account you can only use Haiku, the fast model. More capable
### MCP setup
-Your agents' reach isn't locked inside Macro. The same tools are exposed over Macro's MCP server, so external clients like Claude Code, Codex, and Cursor can work with your workspace directly. Connect once by going to **Settings → MCP server** (authorize with your Macro account — MCP access is included on every plan, Free included), or point a client at the endpoint below. Once connected, your coding agents can search your workspace, read threads and docs, create documents, send email, and update task properties without leaving your editor.
+Macro's MCP server lets AI clients like Claude Code, Codex, and Cursor work with your workspace directly. Connect once by going to **Settings → MCP server** (authorize with your Macro account — MCP access is included on every plan, Free included), or point a client at the endpoint below.
```text
https://mcp-server.macro.com/mcp
diff --git a/apps/docs/product/crm.mdx b/apps/docs/product/crm.mdx
index 3b4e3f53b1..d45d0fd81c 100644
--- a/apps/docs/product/crm.mdx
+++ b/apps/docs/product/crm.mdx
@@ -12,17 +12,13 @@ description: "Contact and company records built automatically from your team's e
CRM is rolling out now. If you don't see the **Customers** view in your workspace yet, it hasn't reached your account.
</Note>
-Most CRMs die because nobody fills them in. Macro's CRM builds itself: because your team's email already flows through Macro, contact and company records are created and kept up to date automatically as you work. You don't have to run an importer or type in fields.
-
-### A CRM that lives where you work
-
-The primary benefit of "Macro CRM" is that it's not even a separate CRM: it seamlessly brings the features you need into your existing team collaboration space.
+Macro's CRM builds itself: because your team's email already flows through Macro, contact and company records are created and kept up to date automatically as you work. You don't have to run an importer or type in fields.
<Note>
You can also work with our CRM through Macro's MCP server. To connect it, go to **Settings → MCP server**.
</Note>
-### Deeply tied into your email client
+### Tied into your email client
Macro CRM is deeply integrated with the Macro Mail client. It works with your existing email. Most CRMs, like Salesforce, have a limited Gmail/Outlook integration.
@@ -94,13 +90,11 @@ Use the **Group** and **Filter** controls in the toolbar to reshape the table, o
### Records build themselves
-When someone on your team emails an external contact, Macro creates a contact record for them and groups contacts into companies by email domain (everyone `@acme.com` rolls up to one Acme record). Each contact tracks its first and last interaction, so you can see the full history of a relationship at a glance. Generic tool and vendor domains (the SaaS notification emails every company gets) are filtered out so the CRM stays focused on your actual customers.
-
-New companies are enriched automatically with public data: name, description, logo, website, industry, headcount, funding, location, and social links land on the record without anyone touching it.
+When someone on your team emails an external contact, Macro creates a contact record for them and groups contacts into companies by email domain (everyone `@acme.com` rolls up to one Acme record). Each contact tracks its first and last interaction, so you can see the full history of a relationship at a glance. Generic tool and vendor domains are filtered out.
### Team sharing
-CRM is a team feature, and it's where Macro's email auto-sharing lives. When **Email Sync** is on for a company, your team's email threads with that company become visible to teammates in the CRM, so nobody has to forward a thread just to share context. Turning it off for a company keeps the record but makes its threads private to their participants.
+CRM is best used as a team feature, and it's where Macro's email auto-sharing lives. When **Email Sync** is on for a company, your team's email threads with that company become visible to teammates in the CRM, so nobody has to forward a thread just to share context. Turning it off for a company keeps the record but makes its threads private to their participants.
Team admins can also **hide** a company or contact entirely, which removes it (and its threads) from the team's view. Members see visible records; admins and owners can edit records, toggle Email Sync, and manage hidden ones.
diff --git a/apps/docs/product/tagging.mdx b/apps/docs/product/tagging.mdx
index 63da435ea8..f5d5d626f2 100644
--- a/apps/docs/product/tagging.mdx
+++ b/apps/docs/product/tagging.mdx
@@ -24,7 +24,7 @@ The same tags apply across:
## Creating and applying tags
-The fastest way is inline. Type `#` in a document to open the tag menu, then pick an existing tag or create a new one. Tags render inline as colored pills, and clicking a pill shows everything else carrying it.
+Type `#` in a document to open the tag menu, then pick an existing tag or create a new one. Tags render inline as colored pills, and clicking a pill shows everything else carrying it.
Everywhere else, use the tag panel in the properties window. Select one of your existing tags or start typing to create a new one.
@@ -66,7 +66,7 @@ Every tag has a color from a fixed palette:
## Filtering and search
-Tags turn a pile of items into a lightweight database. In any block, go to **Filter → Tags** to show only the items carrying a tag. To filter across your entire workspace at once, use the same **Tags** chip in the filter menu of [search](/product/search#filtering-by-tags). Select two or more tags and a match-mode toggle appears:
+In any block, go to **Filter → Tags** to show only the items carrying a tag. To filter across your entire workspace at once, use the same **Tags** chip in the filter menu of [search](/product/search#filtering-by-tags). Select two or more tags and a match-mode toggle appears:
- **Any** — items that have any of the selected tags (the default)
- **All** — items that have every selected tag, for example everything tagged both `marketing` and `q3-launch`
@@ -91,4 +91,4 @@ Curate the full set from **Settings → Tags**, which lists your **Personal** an
## Tagging with agents
-Tell your local model (Claude Code, Cursor) connected to the [MCP server](/AI/mcp/overview) "tag this thread `marketing`" or "make a `q3-launch` tag and add it to these tasks," and it handles the rest without you leaving your editor.
+Tell your AI client (Claude Code, Cursor) connected to the [MCP server](/AI/mcp/overview) "tag this thread `marketing`" or "make a `q3-launch` tag and add it to these tasks," and it handles the rest without you leaving your editor.
diff --git a/apps/docs/product/tasks.mdx b/apps/docs/product/tasks.mdx
index db1f292a8c..dac0f33e5f 100644
--- a/apps/docs/product/tasks.mdx
+++ b/apps/docs/product/tasks.mdx
@@ -6,7 +6,7 @@ description: "Track work with priorities, statuses, and linked context."
<iframe src="https://www.youtube.com/embed/gxJquVXRX5A" title="YouTube video player" frameborder="0" className="w-full aspect-video rounded-xl" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen />
-Macro Tasks start private and lightweight but scale seamlessly onto a team, where tasks you create are auto-shared with members. They're @mentionable anywhere in Macro as live, up-to-date pills, sync bidirectionally with GitHub PRs to move status automatically, and are fully accessible to AI clients like Claude Code and Cursor via Macro's MCP server.
+Macro Tasks start lightweight enough for a single user but scale easily onto a team, where tasks you create are auto-shared with members. They're @mentionable anywhere in Macro as live, up-to-date pills, sync bidirectionally with GitHub PRs to move status automatically, and are fully accessible to AI clients via Macro's MCP server.
> To create a new task use shortcut <kbd>c</kbd> \+ <kbd>t</kbd>
@@ -60,10 +60,10 @@ Macro's MCP server lets AI clients like Claude Code, Codex, and Cursor work with
**MCP for tasks uses**
-- **Create a task** — `CreateDocument` with `isTask: true`.
-- **Find your tasks** — `ListEntities` returns tasks as documents with subtype `task`; you can filter by status, assignee, or priority. Asking your client for "my tasks," "tasks assigned to me," or "what I completed yesterday" runs against Macro rather than an external tracker.
-- **Read a task** — `ReadContent` / `ReadMetadata` for the body and details.
-- **Update a task** — `SetEntityProperty` sets status, priority, assignees, due date, parent/subtasks, and story points; `GetEntityProperties` shows the current values.
+- **Create a task**
+- **Find your tasks**
+- **Read a task**
+- **Update a task**
### @mentioning