🐙 pi-prs

A Pi extension that owns GitHub pull request state for your session: watch PRs, surface review feedback, and show footer widgets — without blocking the interactive session.

Features

• /pr watch with explicit target — watch any PR by full URL, PR number, or owner/repo#number, independent of the checked-out branch. No more being pinned to the current branch's PR.
• pr_watch LLM tool — subagents cannot run slash commands, so the routing session gets the same watch as an LLM-callable tool. The orchestrator reports a PR URL, the router calls pr_watch, and zero-token polling takes over.
• Zero-token HITL — watch a PR targeting main from a project root. The extension polls GitHub in the background every 30s and wakes Pi on approval or new feedback. A human click on GitHub becomes an agent turn with no blocking and no reply needed.
• Repo-qualified resolution — a full https://.../pull/N URL resolves the PR from any directory, so a multi-project session rooted at /workspace can follow a release PR it isn't checked out on.
• Review feedback steering — unresolved review threads and new comments are sent to pi as steering messages so it can act on them.
• Footer widgets — with pi-fancy-footer, publishes PR number, unresolved review threads, and CI status.
• Self-contained — no runtime dependencies; review bodies used as GitHub provides them.

Requirements

• Pi (@earendil-works/pi-coding-agent), Node >= 24
• GitHub CLI, authenticated with gh auth login

Installation

pi install npm:@vectorfield/pi-prs

Usage

Watch the pull request for the current branch:

/pr watch

Watch an explicit pull request (independent of the checked-out branch):

/pr watch https://github.com/OWNER/REPO/pull/123
/pr watch #123            # resolves the PR in the repo at the session cwd
/pr watch OWNER/REPO#123

Stop watching:

/pr unwatch

The extension sends unresolved review feedback to pi, then checks GitHub every 30 seconds for new comments and reviews. New external feedback starts an agent turn so pi can address it. Watching stops automatically when the PR closes or merges.

#number and owner/repo#number forms resolve against the repository at the session cwd (like current-branch mode). A full https://.../pull/N URL is repo-qualified and works from any directory — this is what makes release-PR watching from a project root possible.

Example: zero-token approval gating

1. A worker opens a PR against main and a reviewer passes it; the orchestrator reports the PR URL.
2. The routing session starts the watch with the pr_watch tool ({ action: "watch", url }) and finishes the turn.
3. The extension polls in the background. When a human approves (or comments), Pi is woken automatically with the feedback.
4. On approval, the flow merges the PR; on requested changes, it relays the feedback without merging.

pr_watch LLM tool

Slash commands run only on the interactive session, which a detached subagent cannot reach. For flows driven by Telegram or delegated agents, pr_watch exposes the same watch as a tool:

{
  "action": "watch",   // or "unwatch"
  "url": "https://github.com/OWNER/REPO/pull/123"
}

Use it only from the main routing session — the wake steers that session back into the flow.

Extension API

pi-prs is the only extension that should poll GitHub in a session. Other extensions consume its state from the event bus instead of shelling out to gh:

import { createPiPrClient } from "@vectorfield/pi-prs/api";

export default function (pi) {
  const client = createPiPrClient(pi);
  client.onState((state) => {
    // state.pullRequest?.ci, .unresolvedThreadCount, .isDraft, …
  });
  client.onFeedback((event) => {
    // event.feedback: new review findings
  });
}

Publishing a pi-pr:feedback event yourself sends those findings to pi as a steering message.

Attribution

pi-prs is a maintained fork of the original pi-prs by Matthias Vallentin. It keeps the MIT license and the original copyright notice; see LICENSE. This fork adds explicit PR URL/number targeting and the pr_watch LLM tool, and is published as @vectorfield/pi-prs.

License

MIT