Tasks built for human-
agent collaboration.
A fast, keyboard-first tracker in the same workspace as your email, chat, and docs — so the work that starts in a thread never gets stranded in a separate tool, and agents can pick up tasks and close them.
Built in the open.
Read the code, file issues, and help shape where goes. Star us on GitHub.
“Tasks shouldn't be another app you check. They should live where the work already happens.”
The workflow you know, where the work lives.
Linear made tasks fast and keyboard-first. Macro keeps that and folds them into the same app as your email, channels, docs, and agents.
Questions, answered
How is Macro Tasks different from Linear?
In building Macro Tasks we were heavily inspired by Linear: status, priority, assignee, keyboard-first, and a GitHub integration that moves a task through “In Progress,” “In Review,” and “Done” as you branch, open a PR, and merge. The difference is that Macro Tasks live in the same app as your email, channels, and docs — so you can turn a message into a task in one click, and non-engineers see the work without a separate seat in a separate tool.
Can I migrate my issues from Linear?
Most teams just recreate their open work — finished issues rarely justify carrying over. If you do want history, connect Linear under Settings → Connectors and ask an agent to bring your open issues across. You can also keep Linear connected via MCP so agents can still reference it during a gradual cutover.
Does the GitHub integration really update status for me?
Yes. Copy a branch name from a task and the task moves itself: it goes to In Progress when you branch, In Review when you open the PR, and Done when it merges. The task records which pull request is associated with it, so status updates itself instead of waiting on standup. See the GitHub integration docs.
Aren’t tasks just another app to check?
That’s exactly what we wanted to avoid. Tasks share one inbox with your email and messages, you can @mention a task in any doc or channel, and creating one from an email or message takes a single click. They’re kept deliberately light — status, priority, and assignee by default — so there’s nothing to check that the work doesn’t already surface.
Can I add custom fields like story points or effort?
Yes. Fields are minimal by default, but you can add custom properties — story points, effort, due date, dependencies, recipients, and more — from the Add a property menu when you want them. We advise keeping it light, but the power is there when a team needs it.
Can agents work on tasks?
Assign a task to an agent the same way you’d assign it to a teammate. It does the work, opens a PR, and reports back in the task itself. Because every task feeds the shared context your agents read, they always know what the rest of the team is doing.
Is Macro open source?
Yes — fully open source under the AGPLv3 (as of May 31 2026), not “open core.” To build on Macro under a different license, contact licensing@macro.com.
Close the loop.
It takes 30 seconds to connect your account and bring tasks, email, messages, docs, and agents into one shared memory.