PR review
you’ll want
to do.
Today, PR review means juggling five tabs and a context-hunting expedition. AgentBase pulls them into one calm workspace — and a garden that grows the more you review. Reviewing stops feeling like a chore.
Ask me anything about this PR — I've already read it.
From open to reviewed
Three small moments that turn
“I’ll get to it” into “already done.”
What happens between a PR opening and the reviewer hitting approve — minute by minute, with AgentBase pulling the strings.
@lila — PR #2847 ready for you.
PR opens
Slack pings the right reviewer.
Not a generic GitHub notification that gets ignored — a Slack message with the intent, the scope, the core logic that changed, and an estimated read time. The reviewer skims it in five seconds and knows exactly what they're walking into.
11 export async function middleware(req) {12− const session = await fetchSession(req)12+ const session = readSession(req.headers)13+ if (!session) return redirect('/signin')14+ if (!await rateLimit(session.id)) return rateLimited()
Reviewer reads
The reasoning is already pinned to the diff.
They open the PR. The author's reasoning — pulled from their Claude Code session and linked tickets — sits right next to the lines it explains. Tried, Chose, Ruled out. No more 'wait, why?' interrogations.
fetchSession with the header read?47 callers across the repo — all migrated in this PR. No orphans. The pattern matches a similar move you shipped in March (#2611 · session middleware refactor).
Reviewer asks
Sprig answers without anyone pulling the branch.
Whatever the reviewer wants to dig into — what's the blast radius, where else is this called, did we ship something like this before — Sprig already has the full PR, the codebase, and the team's review patterns loaded. Answer in the same panel, citations included.
Before · After
Five tools open at once.
Now one calm page.
GitHub for the diff. Slack for the thread. Your AI for context. Blame view for history. The ticket for the why. AgentBase pulls them into one page so reviewing a PR stops feeling like a tab-juggling expedition.
Before · five open tabs
readSession called?What you’ll feel
Sprig wilts when PRs sit.
He blooms when you don’t let them.
A small creature whose mood is your inbox — and that turns out to be the smallest visible reason a chore becomes a ritual.
Try it
Move auth check to edge middleware
3 files · 2 packages · about 4 minutes to read.
What this is
A creature whose mood is your inbox. Honest, ambient, ignorable.
Bigger than you
The shared garden grows when the team clears the queue together.
Privacy posture
We see what your reviewer would see — and not much else.
Letting a tool watch how you build PRs is a real ask. Here's exactly what we keep, what we don't, and how to leave at any time.
What we see
Only when you open a PR: the conversation you had with your AI about that change, plus the basics of the PR (repo, branch, commit). That's it. We don't watch you while you code, and we don't read anything else on your laptop.
Secrets scrubbed before saving
Your transcript runs through a scrubber before it ever lands in our database. API keys, tokens, passwords, private keys — all caught and replaced with [REDACTED] automatically. Even if you accidentally pasted one in, we never store it.
What stays on your machine
Your full conversation history with your AI. Your git history. Anything you haven't pushed. We only ever see the small slice tied to a PR you've opened — and only after you've installed AgentBase yourself.
[skip-intent]in the PR description and we'll leave that one alone. Take the marker out and we're back. Want to leave entirely? One command — npx useagentbase@latest uninstall — and you're out, locally and on our end.The gardeners
Built by engineers who’ve shipped
code review at scale.
We've spent years inside the review surfaces of the most demanding engineering orgs in the world — and watched every one of them grind under AI-generated PR volume. AgentBase is the review layer we wanted to use ourselves.