Agents in Macro aren’t a side feature — they sit on top of unified memory, so one prompt can reach your email, messages, tasks, docs, calls, and connectors. These recipes are starting points: paste them into an agent chat (c + a), an automation, a channel via @Macro, or any MCP client connected to your workspace.
Daily inbox brief
Create an automation (agents module → Automations tab → Create an automation) scheduled for each morning:
Every weekday at 8am: summarize what's in my Signal inbox.
Group it into: needs a reply today, FYI, and waiting on others.
Keep it under ten bullets.
Project status on demand
Ask in any agent chat — no need to point it at anything, since memory is refreshed from your team’s activity:
What's the latest status of [project]? Check recent tasks, channel
discussion, and call transcripts, and tell me what changed this week
and what's blocking.
Weekly team recap
An automation for Friday afternoons:
Every Friday at 4pm: write a recap of the week for @#general —
tasks completed, tasks started, key decisions from calls, and
anything that slipped. Link to the relevant items.
Turn a call into tasks
After a call ends, its transcript is already in your workspace. From the call (or any chat):
Go through @[yesterday's planning call] and create a task for each
action item we committed to. Assign them to whoever took the item,
and link the call in each task.
Draft replies in your voice
Draft a reply to @[email thread]. Tone: warm but brief. We can do
the June 20 date, but ask them to send the revised scope first.
Answer questions inside a channel
Mention @Macro in any channel to pull an agent into the conversation, with the channel as context:
@Macro summarize this thread for someone joining late, and list
the open questions nobody has answered yet.
Import my Notion docs from the "Engineering" workspace as Macro
docs. Keep the folder structure and skip anything archived.
Use your workspace from Claude Code
Once you’ve connected the Macro MCP server, your coding agent has the same reach — it can search your workspace, read threads and docs, create documents, send email, and update task properties with the MCP tools:
Find the Macro task for the bug I'm fixing, read the linked channel
discussion, and when I'm done, set the task status to In Review and
post a summary of the fix as a comment.
Read the customer thread about the export bug, then draft (don't
send) a reply explaining the fix that shipped in today's release.
Agents inherit your permissions: they can only see what you can see, and anything they create or send is attributed to you. Start prompts with “draft, don’t send” while you calibrate trust.
