Skip to main content

prhub

One GitHub poller for many coding agents.

CI OpenSSF Scorecard PyPI Python versions Codecov CodeRabbit reviews License: MIT

Coding agents (Claude Code, Codex, Cursor, …) spend a lot of their time waiting: for CI on the PR they just pushed, for a review, for a merge, for the deploy. Left alone, each one waits the same way, with its own polling loop:

gh pr checks 2814 --watch
until gh pr view 2814 --json state | grep -q MERGED; do sleep 30; done
gh run watch 123456

Every one of those loops spends the same budget: the 5,000 requests per hour of the one GitHub token they all share. With a dozen agents the budget is gone within the hour, and then every gh command fails for everyone, you included, until it resets. On the author's machine, a single agent's monitoring loop once made about 190 GraphQL calls a minute and emptied the shared budget in under half an hour.

prhub replaces all of those loops with one daemon per machine. Once a minute it reads every PR and commit anyone is waiting on in a single batched GraphQL request, and writes the state to local files. Agents block on those files with prhub wait, which never calls GitHub.

prhub wait api#2814 --until done                  # open, approved at the current head, CI green, mergeable
prhub wait api#2814 --until checks --timeout 1800 # CI finished, whatever the result
prhub wait acme/api@3a1e48e --until deployed      # this commit is live in production
prhub state https://github.com/acme/api/pull/42   # current state, instantly
prhub list --ready                                # your PRs that are ready to merge, right now
prhub status                                      # daemon health and the GitHub budget left

How it works

                 ┌──────────────── one machine ────────────────┐
  GitHub API ◄── │ prhub daemon ──► ~/.local/state/prhub/*.json │ ◄── prhub wait / state / list
  (1 batched     │   every 60 s                                 │     (any number of agents,
   query/min)    └──────────────────────────────────────────────┘      no API calls)
  • Discovery. Every few minutes the daemon runs one search for your open PRs (is:pr is:open author:@me, or your own query), so agents don't have to register anything.
  • Polling. Every minute, one GraphQL request reads every tracked PR (40 per request) and every watched commit, together with each repo's recent deployments. With 30 to 40 open PRs that costs about 1 point per poll on the author's machine, roughly 60 to 120 points an hour, however many agents are waiting.
  • Waiting. prhub wait tracks whatever it is asked about, nudges the daemon for an early poll (at most one every 15 s), then reads local files until the condition holds. Only data fetched after the wait started is judged, so a stale file never ends a wait.
  • Backing off. Below 1,000 points left the daemon slows to every 3 minutes, below 300 to every 10, and when GitHub rate-limits it, it waits for the reset. During a rate limit prhub status says PAUSED, and waits keep waiting rather than failing, so agents don't fall back to polling by hand against the same exhausted limit.

Install

Requires Python 3.11+ and the GitHub CLI, logged in (gh auth login). prhub reads the token from gh auth token on every poll, never stores it, and has no other dependencies.

uv tool install prhub            # or: pipx install prhub
prhub install-launchd            # macOS: run the daemon at login
prhub install-systemd            # Linux: run it as a systemd user service
prhub status                     # "daemon: healthy" within a minute

To try it without installing a service, run prhub daemon in a terminal. Uninstall: on macOS, launchctl bootout gui/$(id -u)/dev.prhub.daemon and delete ~/Library/LaunchAgents/dev.prhub.daemon.plist; on Linux, systemctl --user disable --now prhub and delete ~/.config/systemd/user/prhub.service.

Pull requests

prhub wait <pr> --until <condition>[,<condition>…] returns as soon as any one condition holds.

condition met when
done open, not a draft, CI SUCCESS, merge state CLEAN (configurable), and an APPROVED review of the current head that is newer than the head commit
green the CI rollup is SUCCESS
checks CI finished, whatever the result
merged the PR was merged
closed the PR was merged or closed
review a new review arrived after the wait started
change anything relevant changed: state, draft, CI, review, merge state, head commit

done deliberately does not trust GitHub's reviewDecision alone: it stays APPROVED after a new push unless the repository dismisses stale reviews, and a force-push with an unchanged patch relabels an old review onto the new head. prhub state marks such a PR review=APPROVED(stale: no approval of this head).

When CI goes red, state and wait also print the names of the failing checks.

Commits: CI and deploys

The same daemon watches commits, in any repository, so agents stop polling gh run watch and the Actions API.

prhub wait acme/api@3a1e48e --until green                      # every CI run on the commit passed
prhub wait api@3a1e48e --until green --workflow deploy         # only runs whose name contains "deploy"
prhub wait https://github.com/acme/api/commit/3a1e48e --until deployed --env production
prhub state @3a1e48e                                           # a commit of the clone you are in
condition met when
checks every run on the commit finished, whatever the result
green every run passed (exits 3 as soon as one fails)
deployed the commit is live in --env (default production, or any)
change anything about the commit's runs or deploys changed

It works the same whatever a repository's workflow names, default branch or release style:

  • CI is every check suite that ran something on the commit. Suites from apps that never start a run (they sit QUEUED forever) and cron-triggered runs (they attach to whatever the branch head is) are left out. A run cancelled because a newer run of the same workflow replaced it is not a failure.
  • Deployed reads GitHub Deployments, plus commit statuses named like deployed/<env>. A successful deploy of a later commit counts when that commit contains yours (asked once per new deployment through the compare API), so nightly releases, batched deploys and a cancelled deploy followed by a newer one all answer correctly. If a repository records no Deployments, use --until green --workflow <name of its deploy workflow>.

A commit stays tracked for 6 hours after the last state or wait that asked about it.

Naming things

you type means
https://github.com/acme/api/pull/42, acme/api#42 a PR
42 PR 42 of the clone in the current directory
api #42, api#42 a PR, by repo name or nickname (see below)
https://github.com/acme/api/commit/3a1e48e, acme/api@3a1e48e a commit (7 to 40 hex characters)
api@3a1e48e, @3a1e48e a commit, by nickname, or in the current clone

Nicknames come from [aliases] in the config, and from the names of the git clones found under clone_roots.

Exit codes

0 the condition was met · 1 timed out · 2 bad arguments, or no such commit · 3 the condition can never be met (the PR closed; for a commit, a run failed under green or its deploy failed) · 4 the daemon is not running.

Agent setup

Tell your agents. Add something like this to your agents' instructions (CLAUDE.md, AGENTS.md, …); a longer version is in docs/agents.md:

## Waiting on GitHub: use prhub, never poll
Every agent on this machine shares one GitHub token. To wait for a PR, CI or a deploy, run
`prhub wait <pr or owner/repo@sha> --until <condition>` (in the background if you need to keep working), and use
`prhub state <pr>` or `prhub list --ready` for the current state. These read local files and cost nothing.
Never loop over `gh pr checks`, `gh pr view`, `gh run watch` or `gh api` with `sleep`.
If `prhub status` says PAUSED, that is a GitHub rate limit: keep waiting, don't poll by hand.

Enforce it (Claude Code). prhub hook claude is a PreToolUse hook that refuses gh pr checks --watch, gh run watch, watch … gh … and shell loops that sleep around gh pr, gh run or gh api, and tells the agent which prhub wait to use instead. One-off reads and every write pass through untouched, and the hook stands aside entirely when the daemon is not healthy. Add it to ~/.claude/settings.json:

{ "hooks": { "PreToolUse": [ { "matcher": "Bash",
    "hooks": [ { "type": "command", "command": "prhub hook claude", "timeout": 5 } ] } ] } }

Put PRHUB_ALLOW=1 anywhere in a command to let one loop through on purpose.

Configuration

~/.config/prhub/config.toml (override the path with PRHUB_CONFIG). Every key is optional:

search = "is:pr is:open author:@me org:acme"  # what the daemon discovers by itself
interval = 60                                 # seconds between polls
discover_every = 180                          # seconds between discovery searches
clone_roots = ["~/code"]                      # clones under here become repo nicknames

[aliases]
api = "acme/api"                              # nickname -> owner/repo, or the name of a local clone
web = "acme/web-app"

[done]
merge_states = ["CLEAN", "HAS_HOOKS"]         # merge states that count as mergeable for `done`

Any PR or commit an agent waits on is tracked automatically, even if the search would not find it (someone else's PR, another organization). Closed PRs drop out an hour after they close.

Files

Everything lives in ~/.local/state/prhub (override with PRHUB_HOME):

path what
prs/<owner>__<repo>__<n>.json one record per PR: a summary plus the raw GraphQL fields
commits/<owner>__<repo>__<sha>.json one record per watched commit
watch.json, commit-watch.json what agents asked to track, and who asked (PRHUB_CALLER, else a tmux or Herdr pane id)
events.jsonl every state change, one JSON line each
daemon.json, daemon.log daemon health, the GitHub budget left, and the log

Other tools can read these too. A dashboard, a merge queue or a status bar can use them without calling GitHub.

Limits

  • github.com only for now; GitHub Enterprise Server is not supported.
  • One daemon per machine and per GitHub token. Agents on other machines need their own daemon.
  • The state is up to one poll interval old (60 s by default). prhub state --fresh asks for a poll first.
  • done checks the review decision, CI and merge state that GitHub reports. If your merge rules need more (a specific reviewer, resolved threads), check those before merging.

Contributing

Bug reports and pull requests are welcome: see CONTRIBUTING.md. Report security issues privately, as described in SECURITY.md.

License

MIT

Metadata

Release files for prhub 0.1.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 prhub 0.1.0
File Size Uploaded
prhub-0.1.0.tar.gz 29.8 kB Details

Built distribution (wheel)

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

Total release size: 58.6 kB

Release files / prhub-0.1.0.tar.gz

Download URL prhub-0.1.0.tar.gz
Size 29.8 kB
Tags Source
SHA-256 checksum
How to use checksums
eec6abf4cd49543b83fe425e7a9280add1a83f71d903f294b7601f2d472edd33
BLAKE2b-256 checksum
How to use checksums
cd3a1ed6ba23357dca52d2d9a8fa2e2521c158c629ac47ead87b339fcd07fed7
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 11, 2026.

Transparency log

Release files / prhub-0.1.0-py3-none-any.whl

Download URL prhub-0.1.0-py3-none-any.whl
Size 28.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c12ec96b54a08dedb6ce5902dd37ba835bb23f1bfe4ae9199f496940a037836e
BLAKE2b-256 checksum
How to use checksums
62a6e23f0b1bce7571103dc7efc87e7413e29a4091b2fdcca0ef96c0eca15bb9
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 11, 2026.

Transparency log

Release history Release notifications | RSS feed

0.2.1

6 release files

0.2.0

4 release files

0.1.6

2 release files

0.1.5

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

This release

0.1.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