Review pull requests
without leaving your work.
Macro brings your GitHub pull requests into your inbox — @mentionable anywhere, comments synced both ways, and notifications that actually work.
Login fired initSession() from both the session-token createEffect and onMount, so every login double-POSTed /auth and could start duplicate backfills. Make the per-method handlers the sole init owner. Show more
Clean fix. Confirmed the double POST is gone in the preview. Filed PRJ-204 for the backfill follow-up.
Preview: fix-auth-double-init.preview.macro.com
MKMary can you review fix(auth): stop double session init before the release?
Looks good — let's ship after the preview check goes green.
Looks good — let's ship after the preview check goes green.
MMacro what's left before we can ship the auth fix?
Almost there — here's the state:
- #4109 is approved by MKMary and all 14 checks pass.
- It closes PRJ-204 on merge.
- Last blocker: the backfill discussed in #eng-reviews is now resolved.
Open source under the AGPLv3 — read it, self-host it, make it yours.
Star on GitHubPRs, where the rest of your work lives.
GitHub hosts your code. Macro puts your pull requests next to your email, chat, tasks, and agents — and keeps everything in sync.
Questions, answered
How do I connect GitHub to Macro?
Install the Macro GitHub app on the org or repos you want, and your pull requests start flowing into Macro — in your inbox, searchable, and @mentionable everywhere. There's nothing to export and nothing to keep in sync by hand.
Do comments really sync both ways?
Yes. A comment you write on a PR in Macro is posted to GitHub, and comments made on GitHub show up on the same thread in Macro. Reviews, approvals, and check status come across too, so the conversation stays in one place no matter where your teammates are.
Why are Macro notifications better than GitHub’s?
GitHub notifications are noisy and easy to miss. In Macro, a review request or an @mention on a PR lands in the same inbox as your email and messages, with reliable push and unread state — so the things that actually need you don't get buried.
Can I @mention a PR in a doc or message?
Anywhere. PRs are blocks like everything else in Macro — @mention one in a channel, a document, a task, or a CRM record and it becomes a live link with status, diff, and checks inline. Open it from there without hunting through GitHub.
How do tasks link to pull requests?
Link a Macro task to a PR and they stay in step — the task shows the PR's status and checks, and merging the PR can close the task. You get the issue-to-PR tracking you'd use a separate tool for, in the same place as the rest of your work.
Can agents use my pull requests?
Yes — your PRs become part of Macro's unified, team-level memory, so agents can read them as context. Ask "what's left before we ship the auth fix?" and the agent reads the open PRs, reviews, checks, and related threads to answer.
Is it faster than reviewing on GitHub?
That's the point. Review is keyboard-first and sub-100ms — jump between PRs, open diffs, comment, and approve without waiting on page loads. The whole interface is built for speed, like the rest of Macro.
Bring your PRs home.
Connect your account in 30 seconds and review pull requests next to your email, messages, tasks, and agents.