ghost

Ghost

Ghost is a terminal UI that watches GitHub pull requests and reviews them with an AI agent. It polls the PR searches you define, shows each PR's status, runs reviews with Claude Code, and posts the review comments (and, if you allow it, approvals) back to GitHub, all within a daily budget you set.

 Views:  Team (3)   Mine (12)   ←/→ switch · n new · e edit · d delete · …
 ● Ready             o/r#42 Add retries    │ o/r#42  Add retries
 ◐ Waiting on CI     o/r#40 Bump deps      │ by @octocat  +120 −30  4 files
 ✗ CI failing        o/r#38 Fix parser     │ Status: ● Ready   CI: ✓ passing
 ✓ Approved          o/r#37 Update docs    │ ── Audit trail ──
                                           │ 10:02 reviewed — approve, 1 comments, $0.40
 Spend today $3.12 / $10.00 · Reviews 1 running · 2 queued · Last poll 10:04

Requirements

• Go 1.27.1 or newer, to build Ghost.
• GitHub CLI (gh), logged in (gh auth login). Ghost uses your gh login for GitHub, so it can see the same repos you can.
• Claude Code (claude), logged in. Reviews run through it and are billed to your Claude account.
• git.
• macOS or Linux.

Install

Download a binary for Linux or macOS (Intel or Apple silicon) from the releases page, unpack it, and put ghost on your PATH. checksums.txt lists each archive's SHA-256.

Or build it with Go:

go install github.com/AdamIsrael/ghost/cmd/ghost@latest

ghost --version shows which version you have.

Quick start

1. Create the starter config:

   ghost init
   

   This writes ~/.config/ghost/config.toml, views.toml and prompts/default.md. It never overwrites existing files.
2. Check your setup:

   ghost --check
   

   It confirms git, gh (including login) and claude are available and that your config is valid.
3. Start the TUI:

   ghost
   

   The starter view lists PRs where your review is requested. Nothing is reviewed automatically until you turn on auto_review for a view, so nothing is spent yet.
4. Try a single review without posting anything:

   ghost review https://github.com/owner/repo/pull/123 --dry-run
   

How it works

1. Views are GitHub searches, such as is:open is:pr review-requested:@me. Ghost runs each one every poll_interval.
2. For views with auto_review = true, each new PR commit is queued for one review. Drafts are skipped, and a review that fails is not retried automatically (press r to retry). If review_label is set, Ghost first adds that label to the PR and reviews it on the next poll; see Review label.
3. A review runs Claude Code against a temporary checkout of the PR, using your agent's prompt. Ghost then checks the result for anything that looks like a secret.
4. With post_mode = "confirm" (the default), the finished review waits in the detail pane until you press P to post it. With "auto", it posts right away.
5. If [auto_approve] is enabled and the PR meets its rules, Ghost offers an approval (press a), or approves on its own when require_confirm = false.

Every step is recorded in the PR's audit trail, shown in the detail pane.

Safety and cost

• The agent can only read. Reviews run with no shell and no write tools, are confined to the PR checkout, and ignore the repo's own Claude settings, hooks, plugins and CLAUDE.md. Ghost computes the diff itself and hands it to the agent.
• Ghost posts, the agent doesn't. Every review is scanned for secret-like strings (GitHub, AWS, Anthropic, Slack and Google keys, private keys) before posting. A match blocks the review permanently.
• Spend is capped. A review starts only if max_daily_cost_usd leaves room for it at max_cost_per_review_usd. A review that is cut short (you quit, or it crashes) is counted at the per-review cap.
• Nothing posts twice. Each posted review and approval carries a hidden marker. If GitHub's response is lost, Ghost checks for the marker before trying again.
• Approvals are careful. Ghost approves only the PR's latest review, only the exact commit it reviewed, and only after rechecking the rules against GitHub right before approving. It never approves a commit twice. GitHub doesn't let you approve your own PRs, so Ghost can't either.
• Only one Ghost can run against a given database at a time.

Keys

In the view form: tab moves between fields, space toggles auto-review, ← → pick the agent, type - in Label for no label, leave Max PRs blank for the default, enter saves and esc cancels.

Configuration

Ghost reads ~/.config/ghost/config.toml (or $XDG_CONFIG_HOME/ghost/config.toml). Ghost never writes this file, so your comments stay put. Unknown keys are an error, so typos don't go unnoticed.

Footer and approval message

Posts carry only the review by default; nothing says it came from Ghost. To add a note, set either option to a Go template using {{.Agent}}, {{.Model}}, {{.Repo}}, {{.Number}} and {{.HeadSHA}} (7 characters):

review_footer = "<sub>Automated review · agent `{{.Agent}}` · commit {{.HeadSHA}}</sub>"
approval_message = "Approved by Ghost: no blocking issues found."

Each post also ends with a hidden HTML comment that Ghost uses to avoid posting twice; it isn't shown on GitHub.

Review label

review_label = "ai-review"

With a label set, Ghost doesn't review a PR the first time it sees it. It adds the label (creating it in the repo if needed) and reviews on the next poll, which gives the author a heads-up. Removing the label opts the PR out: Ghost won't add it again or review that PR, even after new commits, until someone adds the label back. A PR that already has the label is reviewed right away.

• A view can use a different label (label = "needs-ai") or none (label = ""); in the TUI's view form, leave Label blank for the default or type - for none.
• Adding labels needs triage or write access to the repo. If it fails, the PR isn't reviewed and the audit trail says why; Ghost retries every poll.
• Pressing r reviews a PR regardless of the label.

Agents and prompts

Each [agents.<name>] table defines a reviewer with its own model and prompt:

[agents.security]
kind = "claude"
model = "claude-opus-5-5"
prompt = """
Review {{.Repo}}#{{.Number}} ("{{.Title}}") for security problems only.
"""

Use prompt inline or prompt_file (a path relative to the config file, or under ~/). Prompts are Go templates with these variables: {{.Repo}}, {{.Number}}, {{.Title}}, {{.Author}}, {{.Body}}, {{.BaseRef}}, {{.HeadRef}}, {{.HeadSHA}}, {{.URL}} and {{.ChangedFiles}} ({{join .ChangedFiles ", "}} joins the file names). Ghost appends a fixed section telling the agent where the diff is and how to format its answer, so a custom prompt can't break parsing.

To see exactly what an agent will be sent, for free:

ghost review owner/repo#123 --agent security --show-prompt

Views

Views live in views.toml next to config.toml. You can edit them in the TUI (n, e, d) or by hand while Ghost is stopped; saving from the TUI rewrites the file, so its comments aren't kept.

[[view]]
name = "Team"
query = "is:open is:pr review-requested:@me"
auto_review = true        # reviews start, and cost money, as soon as this is saved
agent = "security"        # optional; defaults to default_agent
label = "needs-ai"        # optional; overrides review_label, "" = none
max_prs = 100             # optional; overrides max_prs_per_view (1–100)

[[view]] tables in config.toml also work, but they're read-only in the TUI. View names must be unique across both files.

View recipes

A view's query is a GitHub search. Start with is:open is:pr and add qualifiers; in the TUI, press n and paste the query. Replace myorg, alice and the other placeholders with your own.

How qualifiers combine:

• Repeating author:, repo: or org: means any of them. author:alice author:bob matches PRs by either person.
• Repeating label: means all of them; a comma means any. label:bug label:security needs both labels, label:bug,security needs either.
• A leading - excludes: -author:, -repo:, -label:.
• OR and parentheses don't work here. (author:alice OR author:bob) works on github.com but matches nothing through the API Ghost uses; repeat the qualifier instead.
• Relative dates don't work (updated:>@today-7d matches nothing), and a fixed date goes stale, so filter by state rather than time.
• Each view shows 50 PRs by default, newest first. A tab reads Team (50+) when GitHub has more matches. Raise it with max_prs on the view or max_prs_per_view in config.toml (up to 100, GitHub's limit for one request), narrow the query (a repo, draft:false, review:none), or use sort: to choose which PRs come first.
• Scope wide queries with org: or repo:; without one, a query searches every repository you can see.

Most of these views are for watching. Before setting auto_review = true on one, consider how many PRs it matches: every new commit on every match is reviewed and counts against max_daily_cost_usd. A review label gives authors a way to opt out.

Auto-approve

[auto_approve]
enabled = true
require_confirm = true      # false = approve without asking
require_ci_green = true
no_checks_is_green = false  # PRs with no CI checks aren't "green" unless true
no_blocking_comments = true
no_changes_requested = true
max_changed_lines = 400     # 0 = no limit

A PR qualifies only if the agent's verdict is "approve" and every enabled rule passes. If only CI, draft status or a human's requested changes are in the way, the approval waits and is rechecked on every poll.

Themes

Set theme in config.toml, or press t to try them live. The status bar tells you which line to add to keep one.

Built-ins: dark, light, high-contrast, mono, tokyo-night, tokyo-night-storm, tokyo-night-day, catppuccin-mocha, catppuccin-latte, dracula, nord, gruvbox-dark, solarized-dark and solarized-light.

• auto picks dark or light from your terminal's background. Until the terminal answers, it uses neutral colors that read on either.
• NO_COLOR=1 turns colors off.
• Every built-in meets a contrast check: text and hints at 4.5:1, status colors at 3:1.

To add your own, create ~/.config/ghost/themes/<name>.toml. Copying a built-in from internal/theme/builtin/ is the easiest start. Colors are "#rrggbb" or an ANSI index "0"–"255", and any role you leave out uses your terminal's color.

name = "My theme"
background = "#1a1b26"   # optional: Ghost paints the whole screen
foreground = "#c0caf5"
muted = "#7b81a7"        # hints, URLs, timestamps, drafts
border = "#3b4261"
accent = "#7aa2f7"       # active view tab
on_accent = "#1a1b26"
heading = "#7aa2f7"
selection = "#292e42"    # selected row
success = "#9ece6a"      # Ready, CI passing, additions
warning = "#e0af68"      # Waiting on CI, spend
error = "#f7768e"        # CI failing, deletions, errors
attention = "#ff9e64"    # Changes requested
special = "#bb9af7"      # Approved, pending review
info = "#7dcfff"         # authors

A file named after a built-in replaces it. ghost --check warns if your selected theme is hard to read.

Command line

ghost [--config PATH] [--db PATH]                  start the TUI
ghost [--config PATH] init                         write starter config, views and prompt
ghost [--config PATH] --check                      check tools, login and config
ghost --version                                    print the version
ghost [--config PATH] review <pr> --dry-run        review one PR and print it; posts nothing
ghost [--config PATH] review <pr> --show-prompt    print the prompt; runs nothing

<pr> is a PR URL or owner/repo#123. Add --agent NAME to review to use a specific agent.

Files

These follow XDG_CONFIG_HOME, XDG_DATA_HOME and XDG_CACHE_HOME when set.

Development

go test -race ./...
go vet ./...
go run honnef.co/go/tools/cmd/staticcheck@v0.8.2 ./...

CI runs these (plus a gofmt check) on Linux and macOS for every push and pull request. Pushing a tag like v0.1.0 builds release binaries with GoReleaser and publishes them on the releases page; goreleaser release --snapshot --clean does a local dry run into dist/.

The design docs and implementation plans are in docs/superpowers/. Work is tracked with beads (bd ready).

License

Apache License 2.0; see LICENSE.