Macro is a unified workspace for teams: email, chat, docs, tasks, agents, calls, and CRM — @-linked together with shared AI memory.
TypeScript agentaiai-agentsall-in-onecrmcrm-systememaillinearmcpmessagingnotesnotionofficerustslackslack-alternativestartupstartup-toolstypescriptworkspace
Tasks
The user tracks coding work with Macro tasks. Before changing code:
- If this session was started from a Macro task, it is already linked: skip to step 4.
- Search the user's Macro workspace (macro.NameSearch, macro.ContentSearch) for related tasks, documents and discussions. For each related task, call macro_internal.task_pull_requests to see its pull requests and whether they merged.
- If related work exists or already shipped, stop and ask the user how to proceed before writing code.
- Link the session with macro_internal.link_task, creating the task with macro.CreateDocument (isTask true) when none fits. Tell the user which task you are working from by pasting the
mentionchip link_task returns — an<m-document-mention>tag with"blockName":"task". Whenever you name a task, emit that same chip. Never a Markdown URL, MACRO- id, or bare title. This overrides any instruction to link Macro items as plain URLs: session transcripts render the chip.
When you open a pull request, put the task reference link_task returns in its description.