Keep up with PRs.
Understand what ships.
Find the PRs that need attention, understand how the changes fit together, and dig into the code where it matters.
Gnosis brings your review queue, diffs, checks, and AI explanations into one place, and tells you when a PR needs you.
brew tap oddur/gnosis && brew install --cask gnosis Free and open source. Uses your local Claude Code or Codex, with your existing subscription or API billing.
Enlarge
Know when a PR needs you
Gnosis watches your review requests and your own PRs while it runs. When one needs you, it tells you once and opens the PR at the right tab.
- Notifications
- On the desktop when Gnosis is in the background, in the app when it isn’t. One per event: review requested, approved, changes requested, checks failed, ready to merge, and explanation ready. A notification never writes to GitHub.
- Menu bar panel macOS
- Click the Gnosis icon to see what needs you, grouped as To review, To fix, and Ready. Open a PR with a click, or with the arrow keys and Return. The number on the icon and the Dock counts new PRs that need you.
- Open in Gnosis
-
gnosis://links open a PR in Gnosis at a chosen tab. Use Copy Gnosis link in a PR’s actions to share one. An Open in Gnosis extension for Chrome, Edge, and Firefox adds a button to GitHub PR pages. It is coming to the browser stores.
Reviewing in Gnosis
Inspect changes, follow discussions, and see what blocks a merge. These are screenshots of the app using a sample repository.
Review a stack or an individual PR
See PRs in dependency order. Review each contribution, or compare the final stack against its base. Move into a single PR without losing your place.
- Stack and PR overviews
- Combined or per-PR changes
- Separate explanations for each scope
Enlarge
Browse changes and commits
Read the code without generating an explanation. Scroll through changed files, inspect one commit, and keep GitHub discussions beside the lines they refer to.
- Split or unified diffs
- Hide generated files, tests, and extensions
- Mark files or folders viewed
Enlarge
Rendered Markdown diffs
Switch from Markdown source to a rendered preview. See additions and removals in the document, with unchanged sections folded away until you need them.
- Source and preview
- Changes highlighted in context
- Tables, links, and code blocks
Enlarge
Chat about selected code
Select lines in a diff or ask about an explanation. Chat uses that context, so you can follow a question through without copying code into another tool.
- Questions about files or topics
- Your selected model and effort
- Saved conversations
Enlarge
Inspect and re-run checks
See which checks need attention, inspect job steps and logs, and jump from an annotation to the code. Re-run failed or cancelled jobs from Gnosis.
- Failing checks up front
- Job steps, timings, and logs
- PR and stack merge blockers
Enlarge
Resolve conflicts and restack
Preparing conflicts takes about 3 seconds on a large repository, down from about 50. For each conflict, keep the PR’s change, main’s change, or both, with undo. Review the result before you push, then prepare dependent PRs for restacking.
- One next step per file, with shortcuts
- Suggestions from Mergiraf or your AI tool
- Your resolutions shown apart from main’s changes
Enlarge
Illustrated explanations
When a diff needs more context, generate an explanation for the PR or stack. Gnosis groups the change into topics, with diagrams and notes beside the code.
Step through how a change works, then return to the lines it explains. Generation starts when you ask for it.
Enlarge
Explanations use Claude Code or Codex. You review the code and decide what to submit.
Try the illustrated example
This sample shows how a diagram can explain a subtle change: adding await keeps a concurrency
slot occupied until the work finishes.
Example: a missing await breaks the concurrency limit
Illustrative stack Select a PR
#120 Add a concurrency limit Foundation
One slot means one active command
acquire() waits until the slot is free. Holding that slot must cover the entire worker operation.
const queue = new Semaphore(1);const slot = await queue.acquire();// Hold the slot while work runs.slot.release();
Back to the app screenshot #121 Hold the slot until the worker finishes Builds on #120
A starts; B is waiting A owns the only slot. Its worker operation is still pending.
Why return await matters here
Both versions return a promise. Only return await keeps finally from releasing the slot before the worker finishes.
Concurrency limit: 1 active command
Before · without await
1 activeAfter · with await
1 activeasync function dispatch(command) { const slot = await queue.acquire(); try {Removed: return worker.run(command);Added: return await worker.run(command); } finally { slot.release(); }}
Without await, the returned promise stays pending, but finally runs
immediately.
#122 Test that a second command waits Builds on #121
Test the overlap, not just the result
Let A stay pending, then submit B. B must not start until A settles. Also test rejection: finally must still release the slot.
const a = dispatch(commandA);const b = dispatch(commandB);await worker.waitForStart("A");await flushMicrotasks();expect(worker.started).toEqual(["A"]);worker.finish("A");await worker.waitForStart("B");expect(worker.started).toEqual(["A", "B"]);worker.finish("B");await Promise.all([a, b]);
Back to the app screenshot Also included
- Saved filters
-
Save views by repository, author, labels, read status, briefing status, merge conflicts, or target
branch—including patterns such as
release/*. - Mute, star, and repository settings
- Mute PRs, star the ones to revisit, and set repository rules for Dependabot, inactivity, and automatic briefings.
- Local search with ⌘K
- Search locally available PRs, files, and saved explanations. Use recent destinations to get back to a review.
- GitHub comments and reviews
- Read GitHub threads inline. Draft comments with a Markdown preview, then submit them with your review decision.
- Images, SVGs, and Git LFS
- Compare images and SVGs, recognize moved files, and download Git LFS resources when you need to inspect them.
- Loaded before you click
- When you open a PR, Gnosis loads its changes, checks, and comments in the background, with fewer GitHub requests. Viewed-file progress and saved explanations stay in a local cache.
Uses your local coding agent
Gnosis runs Claude Code or Codex CLI on your machine, using the login you already have. AI usage goes through your existing subscription or API billing. There’s no Gnosis subscription.
Read the setup guideConnect GitHub
Choose which repositories to watch. Set filters and briefing preferences per repository.
Choose your models
Use Claude, Codex, or both. Pick separate models and effort levels for explanations and briefings.
Use a local clone if you have one
Link a repository to its local clone in Settings. Gnosis can read Git data from it.
Gnosis runs on your computer. AI requests send code and context to your selected provider under your account.
Install Gnosis
Download the app or use Homebrew. Later updates install from the app with Restart now.