Across our customers, Macroscope auto-approves 40% of PRs, so your team reviews only what actually needs a human. Approvability gives the +1 on the low-risk changes and escalates anything risky.
Start with $100 in free usage. Usage-based pricing, no seat fees.
of pull requests are auto-approved across Macroscope customers.
That is review time your team gets back, every week.
Every PR clears three hurdles before Macroscope posts a real GitHub approval. If any one fails, it goes to a human.
A dedicated agent reads the diff, traces the call graph through your codebase, and classifies the change by type, scope, complexity, and runtime impact against your policy.
Macroscope's bug-finding review must come back clean. A safe-looking refactor with a real bug still needs a human, so any medium-or-higher issue blocks the approval.
Optionally require that authors only auto-approve files they own, read straight from your CODEOWNERS. Off by default, one flag to turn on.
Macroscope approves only the changes where the intent is obvious and the blast radius is small. Everything else defers to a human.
Drop a markdown file in your repo and Macroscope reads it like a senior engineer reads a team handbook. Your rules win over the defaults, every time.
Let Macroscope approve the routine PRs so your team spends its review time on the changes that actually need it.
$100 in free usage to start. No seat fees.
Approvability is an AI code review check that evaluates whether a pull request is safe enough to auto-approve without a human reviewer. It classifies the PR by change type, evaluates the author's track record, traces runtime impact through your codebase, and checks for correctness issues. When a PR clears every hurdle, Macroscope posts a real GitHub APPROVE review. The default policy is intentionally conservative.
By default: documentation updates, unit and integration tests, code behind a disabled feature flag, simple self-contained changes like copy edits and additive API fields, straightforward bug fixes (a missing null check, an off-by-one, an inverted conditional), mechanical renames and file moves, and minor CI tweaks. These are the PRs where a human reviewer adds essentially zero value.
Anything with blast radius beyond the diff: breaking schema changes, significant runtime behavior changes, gating logic like feature flags and permission checks, major refactors, production and infrastructure changes, and anything touching security, authentication, billing, or sensitive data. The rule is simple: if Macroscope has any doubt about scope or side effects, it defers to a human.
Yes. Add a .macroscope/approvability.md file at the root of your repo with your team's policy written in plain English. Macroscope reads it like a senior engineer reads a team handbook and treats it as the highest-priority guideline, overriding defaults when the two conflict. Tighten rules for sensitive paths, allowlist low-risk directories, or set custom conditions for specific folders.
Every Approvability decision is a GitHub Check Run with a verdict and reasoning, giving you a permanent audit trail. Combined with explicit, customer-controlled eligibility criteria, conservative defaults that escalate sensitive paths, and instant human override, Approvability is built to enforce whatever bar your compliance framework sets. Teams under stricter frameworks can restrict it to specific repos or disable it entirely.
No. It is a triage layer on top of code review, not a replacement. A human still reviews any PR that fails the eligibility, correctness, or ownership hurdles, and a human keeps final merge authority. The goal is to make sure every human review is a review the PR actually needed, not a 30-second rubber stamp that pulled someone out of deep work for half an hour.
Approvability is off by default. Install Macroscope and it starts posting 'Would Approve' verdicts on qualifying PRs without approving anything, so you can validate the default policy for a week. Add a .macroscope/approvability.md file if you want to adjust it, then flip approval on for the workspace or repo. From there, qualifying PRs are auto-approved with a real GitHub APPROVE review. Setup takes under five minutes.
Join teams building with Macroscope to catch more bugs and merge PRs faster than ever. Simple usage-based pricing. No seat fees, no surprises.
