Skip to main content

DiffButler

A terminal dashboard for human-directed AI code reviews on GitHub.

Keep track of what each pull request needs next: AI review, your review, or author changes. Start an AI review, discuss its findings in the agent's own session, and finish your review in the browser.

DiffButler dashboard showing pull requests and the next review action

Install

Install uv and Git. From a local checkout of this repository, run:

uv tool install --python 3.14 .

uv manages Python and dependencies in an isolated environment. No virtual environment activation is needed. If diffbutler is not on your PATH, run uv tool update-shell and restart your shell.

Install and sign in to Codex CLI or Claude Code before requesting AI reviews. The native presets support Codex CLI or Claude Code on Linux and macOS without version checks. Reviews use your normal agent settings, including model and reasoning effort, with background permission and output overrides. New conversations remain in the agent’s own history after DiffButler cleans up its workspaces; existing private sessions retain their original home for resume. See supported agents and validation for details.

Use

Use authenticated GitHub access, including for public repositories. If you already use gh auth login, export its token before launching DiffButler:

export GITHUB_TOKEN="$(gh auth token)"

Alternatively, create a fine-grained personal access token for the repositories you want to review with Pull requests: Read-only permission, and set it as GITHUB_TOKEN. Anonymous access is a last resort for public repositories; its low API quota makes it unsuitable for regular polling. See the authentication guide for host/account selection, HTTPS versus SSH Git setup, and token permissions.

From the GitHub repository you want to review, launch:

diffbutler

First-run setup detects the local repository, looks up your GitHub username using the selected token, asks for your preferred agent, and saves your choices. If username detection is unavailable, setup asks for it. Choose the recommended token access for public repositories; private repositories require it. Setup asks for the token's environment variable name and validates access. It never saves the token. New configs silently enable both Codex and Claude when found in PATH; setup asks only which detected agent should be the default. Missing agents get commented-out entries you can enable after installation. Later launches reuse your configuration.

The dashboard shows active reviews, including followed PRs whose GitHub review requests have disappeared after you posted feedback. Waiting-for-author reviews stay visible across refreshes and restarts. If an approved PR receives new commits, it reappears as done+ at the end of the queue without starting another AI review. Authenticated polling slows when API quota is scarce and speeds back up when it recovers, accounting for refresh cost and time until the quota resets.

Select a PR with the arrow keys, then work through the review:

  1. Optionally press n to change the current configured AI reviewer for all PRs. Press r to start a background AI review. Reviews start only when you request them. The agent is instructed to read the PR description, discussion, and earlier review threads and replies before reviewing the local code, reporting any unavailable context. DiffButler caches full Git history and reviews changes from the PR merge base to its head, excluding unrelated changes made later on the target branch.
  2. A successful review shows approve only when the AI explicitly reports no findings; otherwise it shows check. Press Enter to read the results, or c to resume the saved agent conversation. If the agent exits normally but DiffButler cannot parse its output, the task also shows check; use c to inspect the saved conversation or L for captured output. Changing reviewers leaves that conversation available through c; pressing r starts a new run with the current reviewer and replaces the current review details. Ask questions and explicitly tell the agent which comments to post, if any.
  3. Exit the agent to return to the dashboard, which refreshes activity from GitHub. Press w if you are waiting for author changes, or o to review in your browser.
  4. After approving on GitHub, press m to mark the task complete locally. DiffButler also detects your approval, closure, or merge and cleans up owned session resources while retaining review history.

Space performs the selected PR's next action: start a review, discuss findings, or open the browser. An AI review never counts as your approval. Background analysis uses the agent's native permission controls and read-only review instructions; source sent to the agent may go to its model provider.

  • /: Filter the queue.
  • a: Toggle monitoring all open PRs in configured repositories.
  • b: Browse accessible PRs and follow one.
  • R: Refresh from GitHub.
  • k: Stop the selected PR's review and reset its local tracking and owned resources. It disappears until a forge refresh rediscovers it; review history is retained.
  • h: View completed review history.
  • ?: Show all keyboard shortcuts.
  • q: Quit.

See the dashboard guide for all actions and configuration guide for settings.

Your own PRs are hidden from the review queue by default, including direct and team requests. Set include_own_prs = true in [ui] to review them, such as PRs an agent created using your account. PRs assigned to you are also hidden by default, even when you are requested directly or through a team. Set include_assigned_prs = true in [ui] to include them.

Reset

Close running DiffButler sessions, then run:

diffbutler reset

DiffButler refuses a second command or dashboard using the same data home, including reset, while another instance is running. Its instance lock releases on process exit; a leftover PID file does not block startup. See the locking details before handling Git lock files or resetting after a crash.

After confirmation, this permanently removes DiffButler's standard configuration, data, and state directories, including review history, saved sessions, and diagnostic logs. Custom files outside those directories are preserved. Use diffbutler reset --force to skip confirmation. Run diffbutler again to repeat first-run setup.

Contributing

See CONTRIBUTING.md for development setup and checks.

License

MIT.

Metadata

Release files for diffbutler 0.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for diffbutler 0.5.0
File Size Uploaded
diffbutler-0.5.0.tar.gz 127.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for diffbutler 0.5.0
File Interpreter ABI Platform
diffbutler-0.5.0-py3-none-any.whl Python 3 none any Details

Total release size: 300.2 kB

Release files / diffbutler-0.5.0.tar.gz

Download URL diffbutler-0.5.0.tar.gz
Size 127.6 kB
Tags Source
SHA-256 checksum
How to use checksums
3301e69f52736254a487e5880545d6528d57462fc6df2615e9357cb30ba37bf6
BLAKE2b-256 checksum
How to use checksums
d8830a5cc16ffe94a251d9da77aecffae22b7f82048662124a69f40e1ac3e3cf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.

Transparency log

Release files / diffbutler-0.5.0-py3-none-any.whl

Download URL diffbutler-0.5.0-py3-none-any.whl
Size 172.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
df728ca8361cecdb532f7bf9ddaed3bed0d61dadf15279f0e87cf900b65fc4d2
BLAKE2b-256 checksum
How to use checksums
4e4555c3e08c8262984de13c07c905420ecb2fae45300818bbec94502132931f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.

Transparency log

Release history Release notifications | RSS feed

0.5.2

2 release files

This release

0.5.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page