Pruse
Pull requests, tasks and parallel agents · on your Mac
Every pull request from all your repositories on one board, and a diff that keeps up with your keyboard. Investigate with Claude Code, turn what it finds into a plan you edit, and hand it back step by step, each in its own worktree. It never runs anyone else's code.
Free & local · Apple Silicon · Works with the gh login you already have. No account, no telemetry.
1213export async deliver (event:WebhookEvent ) {14const key =idempotencyKey (event)14for (let i =0 ; i <3 ; i++) {15for (const delayof backoff ({ max:5 })) {15const res =await post (event.url, event.body)16const res =await post (event.url, event.body, { headers: {'Idempotency-Key': key } })17if (res.status ===409 )return 'duplicate'18if (res.ok)return 'delivered'19await sleep (delay)}
2021throw new DeliveryError (event.id)}
3132test ('a 409 counts as delivered once',async () => {server.33reply (409 )34expect (await deliver (event)).toBe ('duplicate')})
Review
Open Pruse and see what needs you across all your repositories — as cards that say, in a sentence, where each PR stands. Filter, hide drafts, or arrange them on your own board: columns you name, cards you drag, kept on your Mac.
A private briefing before you dive in: what the PR does, where to start, the spots worth a close look — and, on a re-review, which open threads look addressed and which don't. It prepares you; the verdict stays yours.
Virtualized, syntax-highlighted, unified or side by side, whitespace hidden if you like — and images shown before and after. Move with j k, jump files with n p, mark viewed with v and glide to the next file, comment with c.
Comments stay local until you submit. If the author pushes meanwhile, Pruse finds your lines again by content and moves them.
Description, checks, reviews and threads in one calm column — outdated threads right where they were said. Reply, resolve, and jump from any thread to its line.
Merge, squash or rebase from the Conversation tab. Pruse tells GitHub exactly which commit you looked at — if someone pushed after you, the merge is refused instead of shipping code nobody reviewed.
Re-review
Submitting a review pins the exact commit you saw. When the author pushes again — even a rebase — Pruse shows Changed since your review and diffs just that.
The commit you reviewed is pinned in your clone, so rewriting the branch can't make it disappear.
Your old changes are replayed onto the new base first. What the base brought in stays out of your way.
Files you already ticked keep their check — unless their content actually changed.
Parallel work
Give Claude Code a task in its own worktree, keep reviewing, and come back when it needs you. Ask it to put its plan into Pruse: edit the steps beside the chat, start each one, and watch it tick them off. Its changes land in a live diff; committing stays yours.
New ones go next to your existing ones — .claude/worktrees/ if you use claude -w. Your checkout hooks run as usual.
Its own tools and your settings. Manual, Accept edits, Plan or Auto; plans shown in full before you approve. Paste screenshots, keep typing while it works (messages queue), and resume any session. Your plan's 5-hour and weekly limits sit in the title bar.
Scripts from every folder of a monorepo, saved commands, Run all. Logs and the real port for each; running a script in one worktree moves it off the others.
Discard with Undo, stash & switch branches, amend or undo only what isn't pushed, hooks shown live as they run. Commit messages and PR descriptions follow your repo's template and rules.
Type / for your repo's commands and skills, Claude Code's own and your plugins' — with their arguments.
A rail with every repository you work in — your own labels and colors, badges for agents, reviews and running servers. ⌘1–⌘9, or ⌘K for any repo, worktree or PR. Local repos without GitHub work too.
An agent needs you or finished, a dev server crashed, a review is requested, news on your PR. On your Mac — and on your phone through ntfy when you're away.
Your own shell in every worktree — colors, nvim with its icons, anything interactive. Several per worktree, and they keep running while you look elsewhere.
Tasks
Write down what needs doing — or have Claude put its plan here — link what comes after what, and give a task to Claude Code in a new branch and worktree, or let the next one start by itself once you've checked the last.
Drag between To do, In progress, In review and Done. The order is your priority.
“Do this after that.” Cards show what they wait for; nothing is picked for you.
Where it runs, the branch, the mode and the first message — /commands too. Start now, or by itself when the one before is reviewed or its agent is done.
Working, needs you or finished, steps ticked off as Claude goes, the branch and what changed — straight from its worktree.
Principles
Pull request checkouts are untrusted: there, the agent can only read and search, and Pruse runs nothing — enforced from outside, in layers. In your own worktrees, Claude Code works as you know it, and asks before every change unless you choose a mode that doesn't.
The session is created with Read, Grep and Glob. There's no shell, no editor, no web fetch to misuse.
No project settings, hooks, instructions or MCP servers — a malicious PR can't configure the agent that reads it.
Anything that isn't a read inside the checkout is denied — and shown to you, so you see what it tried.
Pruse advertises no terminal and no file writing to the agent. There's nothing to ask for.
gh loginFrom the terminal
$ Opening acme/payments#482 in Pruse… $ pruse inbox REVIEW REQUESTED #482 Idempotent retries for webhooks maya +214 −37 #479 Split ledger writes by tenant theo +88 −12 $ pruse diff # your own uncommitted changes
Free, for Apple Silicon Macs. Signed and notarized by Apple. Everything runs on your machine.
Download Pruse.zipUnzip and drag Pruse.app into Applications.
Optional: the pruse command, to open any repo or PR from your terminal.
ln -sf /Applications/Pruse.app/Contents/Resources/app/bin/pruse ~/.local/bin/pruseNeeds git. For pull requests, the GitHub CLI, logged in (gh auth login) — local repositories work without it. Claude Code is optional — without it, Pruse is simply a great diff.
Should a
409still record the attempt? Otherwise the dashboard shows it as never sent.