hello from the mobile build. going to use this all day and see what breaks
Macro for GitHub
GitHub, wired intoyour workspace.
Review requests and PR comments land in your inbox.
Link a PR to a task and it updates itself.
Keep the invited team through sign-up
What changed
New teammates who accept an invite now stay in the invited team through sign-up. Existing accounts switch to that team after they sign in.
Fixes LAUNCH-42.
Testing
- New account from an invite link
- Existing account from an invite link
- Expired invite still shows the error page
A sample inbox. Open a review request to read the PR.
Never miss a review.
Review requests, comments, and mentions on your pull requests land in Home. Right next to your messages, tasks, and email.
GitHub notifications are easy to ignore, which is how a PR sits for two days waiting on a one-line review. Macro puts review requests, comments on your PRs, and mentions in the same inbox as everything else, so code review isn’t one more place to check. Press E when you’re done, same as everything else.
Paste a PR, see its status.
Pull request links turn into pills in docs and messages. Hover one to see checks, comments, and the size of the change.
Paste a pull request into a channel or a doc and Macro shows it with its status: open, merged, or closed. Hover it for the repo, the title, the line counts, and whether checks passed. No more “is this merged yet?” in the channel.
Tasks and PRs, linked both ways.
Put the task ID in a branch or PR title and the PR shows up on the task. Opening it moves the task to In Review. Merging it marks it done.
- New accounts land in the invited team
- Existing accounts switch teams
- Regression tests for both paths
This is the part our engineers like most. The task shows its pull request, the pull request links back to the task, and nobody updates status by hand. Opening the PR moves the task to In Review, merging marks it Completed, and closing it without merging puts it back in Not Started.
Coding agents in your channels.
Hand a bug to Cursor or Claude Code right from the conversation. The agent works on the branch and comes back with a pull request.
Most bugs start as a message. In Macro, you can @mention Cursor or Claude Code in that same thread and hand it off. The agent works on the branch, reports back in the channel, and the PR shows up linked to the task, ready for review.
Questions about Macro and GitHub
Your code and CI stay on GitHub. Macro handles the parts your team talks about.
Frequently asked questions
Is this a GitHub replacement?
No. Your code, reviews, and CI stay on GitHub. Macro brings the parts your team talks about into the workspace: notifications, PR status, and the link between a pull request and its task.
What shows up in my inbox?
Review requests, comments and reviews on your pull requests, mentions, and status changes on PRs you’re part of.
How do pull requests link to tasks?
Put the task ID in the branch name, PR title, or PR description. Macro links them and moves the task as the PR opens, merges, or closes. More on tasks in Macro.
Can I review code in Macro?
You can read the PR description and the review discussion in Macro. For the diff and approvals, Open on GitHub takes you there.
Which coding agents work with Macro?
You can mention Cursor, Claude Code, and Codex in channels, and connect any MCP client to your workspace. See agents in Macro.
Is there a free plan?
Yes. See pricing for current limits.
Read our Privacy Policy or visit the Trust Center.

If the invite has expired this still falls through to the personal workspace. Can we keep the error page for that case?
Good catch. Expired invites go to the error page again, and there’s a test for it now.
Bugbot reviewed this pull request and found no new issues.