pi-intercom-review-pair

Pair developer and reviewer Pi sessions for an issue through pi-intercom.

Packages

Package details

extension

Install pi-intercom-review-pair from npm and Pi will load the resources declared by the package manifest.

$ pi install npm:pi-intercom-review-pair
Package
pi-intercom-review-pair
Version
1.3.0
Published
Sep 15, 2026
Downloads
462/mo · 95/wk
Author
brunoorsolon
License
unknown
Types
extension
Size
26.2 KB
Dependencies
0 dependencies · 2 peers
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 intercom review pair

A Pi extension that pairs two already-running sessions as developer and reviewer without copying intercom UUIDs.

Install

Install both packages, then restart Pi:

pi install npm:pi-intercom
pi install npm:pi-intercom-review-pair

No sandbox environment variables are required. If PI_INTERCOM_SCOPE_ID is configured, normal pi-intercom scope isolation still applies; otherwise the extension can discover any connected session that also has review-pair loaded.

Use

From the session that should become the developer, run:

/pair-review 999 billing

Omit the issue number to enter it interactively. Omit the project name to enter it interactively; leave that prompt blank to use a random common word. The invoking session is always the developer. If exactly one other review-pair session is live, it becomes the reviewer automatically; otherwise the command asks you to select the reviewer by session name, working directory, model, status, and ID.

After confirmation, the command assigns these names:

<project>-<issue>
<project>-<issue>-review

Both targets receive self-contained role instructions. The developer asks the exact reviewer session to inspect a committed candidate, verifies findings, repairs valid ones, and repeats until the reviewer explicitly returns No findings. or requests a human decision.

Process markers

Both role prompts end with a non-typable marker owned by this extension:

⟦pi-intercom-review-pair:developer⟧
⟦pi-intercom-review-pair:reviewer⟧

processMarker(role) in src/core.ts produces them, so the exact characters should be matched through that function rather than retyped. The extension assigns the marker no meaning; a routing layer can match it in an injected prompt to run repository-specific process, for example loading a work-issue or review skill.

Development

npm test

The three-session RPC smoke requires an already-running broker and a local pi-intercom entry point. It refuses to start another broker:

PI_INTERCOM_EXTENSION=/path/to/pi-intercom/index.ts npm run test:rpc

Both smokes load extensions with --extension/-e; no installation is required. The fake provider fixture uses the local Pi installation to avoid network model calls.