Pi-Rogue

Explicit advisory help for sharper Pi sessions. Pi-Rogue adds one bounded Advisor and a read-only Advisor Board to a Pi session. Normal work stays normal: Pi-Rogue does not make model calls, rewrite prompts, switch models, dispatch workers, or run background loops unless you explicitly ask for advice.

pi install npm:@fiale-plus/pi-rogue

One public package. One install. Explicit commands only.

Supported host: Pi >=0.80.6 <0.81.0 on Node.js >=22.19.0.

What it provides

• Advisor — one-shot senior engineering advice through an explicit command or tool call.
• Advisor Board — bounded, read-only specialist and Head-of-Board calls over a compact session ledger.
• Core — shared filesystem, storage, text, and safety helpers used by the bundled extension.

The Board has five static specialist lenses:

Role	Focus
reviewer	Scope, correctness, regressions, tests, and maintainability
security	Secrets, trust boundaries, command/file safety, and authorization
architecture	Ownership, coupling, lifecycle, and API/state design
debugger	Reproduction, root cause, edge cases, and verification
reliability-perf	Hangs, retries, resource growth, repeated work, and concurrency

Specialists are read/search-only and suggest-only by default. They can return findings and recommendations, never edits or commands. Head-of-Board is an explicit, bounded, read-only synthesis call; it cannot dispatch a specialist or mutate the workspace.

Quick start

/pi-rogue status
/pi-rogue closeout start implement the requested change
/pi-rogue closeout record success
/pi-rogue closeout export
/pi-rogue-advisor <question>
/pi-rogue-advisor settings
/pi-rogue-advisor model list
/pi-rogue-advisor board watch status
/pi-rogue-advisor board watch intervene
/pi-rogue-advisor board watch head on
/pi-rogue-advisor board specialist ask reviewer inspect the proposed change for regressions
/pi-rogue-advisor board head ask what decision is safest before merging

The advisor tool is also explicit: invoke it when you want advice, rather than relying on lifecycle hooks. /pi-rogue status|help|doctor|closeout ... and /pi-rogue-advisor status|settings|model|board ... are the only command roots registered by the package. Closeout is local, explicit, bounded evidence bookkeeping; it never claims success without the user's status command.

Model map and bounds

Advisor model selection is separate from Pi's active model. The user-visible configuration has this shape:

{
  "models": {
    "advisor": null,
    "specialist": null,
    "head": null
  },
  "board": {
    "specialists": "suggest",
    "maxSpecialistCalls": 3,
    "specialistMaxTokens": 900,
    "headMaxTokens": 1200
  }
}

null selects one authenticated compatible text model using the bounded preference for that role. /pi-rogue-advisor model list [advisor|specialist|head] shows available candidates, role recommendations, and declared reasoning/context/cost facts without making an LLM call. The explainable policy is quality-balanced Advisor, efficient specialists, and reasoning/context-oriented Head—not a universal quality ranking. An explicit <provider>/<model> value overrides discovery and is warned about if unavailable. Resolution attempts the configured model and at most one preferred fallback—never an unbounded provider loop. Model selection never changes Pi's global active model.

The main Pi model is separate and Pi-owned. Pi-Rogue never changes it. For a cheap/fast default, start Pi with an authenticated registry entry such as pi --model openrouter/deepseek/deepseek-v4-flash. Equivalent provider IDs may be available (opencode-go/deepseek-v4-flash, ollama-cloud/deepseek-v4-flash); Pi's /list-models output is authoritative for the current host. DeepSeek's official pricing page currently lists V4 Flash as an efficiency-oriented option; prices, limits, availability, and provider markups change, so verify them before budgeting. Treat Luna/Kimi high-end variants as quality/escalation choices rather than assuming they are cheaper. The active model is shown by /pi-rogue-advisor status.

Explicit-only safety boundary

Normal session lifecycle events do not call models. The deterministic Board watcher runs in shadow mode by default to record compact risks without model calls. intervene mode explicitly queues a visible, non-binding next-turn suggestion; it does not trigger a turn, switch models, or mutate anything. Head escalation is separately off by default and can be enabled with /pi-rogue-advisor board watch head on. Pi-Rogue has no automatic review, model switching, prompt rewriting, or worker mutation. Explicit Advisor, specialist, and Head calls remain bounded and fail closed.

Package and development

@fiale-plus/pi-rogue is the canonical single public artifact. It bundles @fiale-plus/pi-core and the internal @fiale-plus/pi-rogue-advisor package; direct Advisor releases remain paused and are not a separate user install path.

npm install
npm run check
npm test
npm run test:packed-min-node

Learn more

• Canonical package README — install scope, model map, and command surface.
• Advisor README — explicit calls, Board roles, and safety limits.
• Advisor Board taxonomy — static roles and permission boundaries.
• Advisor Board replay PoC — bounded ledger/replay evidence model.
• Release guide — canonical pi-rogue-<semver> release process and legacy tombstones.