@badliveware/pi-pr-upstream-status
Show upstream pull request status for the current branch in Pi.
Package details
Install @badliveware/pi-pr-upstream-status from npm and Pi will load the resources declared by the package manifest.
$ pi install npm:@badliveware/pi-pr-upstream-status- Package
@badliveware/pi-pr-upstream-status- Version
0.2.0- Published
- May 1, 2026
- Downloads
- 226/mo · 226/wk
- Author
- doz3r
- License
- MIT
- Types
- extension
- Size
- 51.8 KB
- Dependencies
- 0 dependencies · 1 peer
Pi manifest JSON
{
"extensions": [
"./index.ts"
]
}Security note
Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.
README
pi-pr-upstream-status
Shows the open GitHub pull request for the current branch in Pi and can prompt the agent when new PR feedback or failing CI needs attention.
Use it when you work on branches with upstream PRs and want review comments, check status, and CI failures visible without leaving Pi.
Install
pi install npm:@badliveware/pi-pr-upstream-status
Requirements
- A Git checkout with a GitHub remote.
- Optional:
GH_TOKENorGITHUB_TOKENfor private repositories, higher rate limits, unresolved review-thread filtering, and richer CI details. - Optional: GitHub CLI (
gh) as an additional private-repo auth fallback.
Without a token, public-repo lookups still work with anonymous GitHub API limits. Some review-thread and CI-log details may be unavailable.
What it shows
The extension adds a compact footer status with:
- check result:
✅,❌,⏳, or• - comment count such as
💬3 - PR link such as
#123when supported by the terminal
It also emits pr-upstream:state for footer frameworks or other extensions that want structured PR status.
Quick use
/pr-status
/pr-status refresh
/pr-autosolve off
Auto-solve is on by default. Turn it off if you only want passive status:
/pr-autosolve off
How it works
The extension detects the current branch, finds the matching open GitHub PR, refreshes status periodically, and updates Pi's footer/status primitives.
When auto-solve is enabled, it can fetch new issue comments, unresolved review-thread comments, and failing CI context. If the agent is busy, the work is kept pending and shown in a user-only card with brief comment/check status. When Pi is idle and allowed to proceed, it queues a structured auto-solve message that gives the agent a turn to verify the feedback, fix relevant issues, run validation, and summarize what happened.
Guardrails prevent automatic auto-solve from notifying the agent immediately in fresh sessions, before checks complete, or when an older Pi process is already active in the same workspace. /pr-autosolve now runs a one-shot solve even when auto-solve is off or checks are still running; CI failure context is included once failures are available.
Commands
| Command | What it does |
|---|---|
/pr-status |
Show current PR status. |
/pr-status refresh |
Refresh now. |
/pr-status on |
Enable the periodic watcher. |
/pr-status off |
Disable the periodic watcher. |
/pr-autosolve |
Show auto-solve status and config path. |
/pr-autosolve on |
Enable auto-solve and persist the choice. |
/pr-autosolve off |
Disable auto-solve and persist the choice. |
/pr-autosolve now |
Run a one-shot solve for current feedback and available CI failures, even when auto-solve is off or checks are still running. |
Auto-solve settings persist to:
~/.pi/agent/pr-upstream-status.json
Event payload
The extension emits:
pr-upstream:state
Payload includes the current branch, PR number/title/url, comment count, check state, head SHA, base repo, and auto-solve state.
Auto-solve prompts are delivered as Pi custom messages with:
pr-upstream:auto-solve
The message content contains the actionable instructions and summarized PR/CI context for the agent; structured details include the PR identity and feedback/CI counts for rendering or debugging.