Pi Auto Reviewer

Run pi install npm:pi-auto-reviewer, or copy auto-reviewer.ts, review-tool.ts, jev-decisions.ts, and reviewer-cost.ts into ~/.pi/agent/extensions/pi-auto-reviewer/, a trusted project's .pi/extensions/, or load one session with pi -e ./auto-reviewer.ts. All four files must sit side by side.

Tier 1 runs immediately (ls, grep, git status); tier 2 is refused immediately (rm -rf /, sudo, chmod 777); tier 3 goes to the configured reviewer (git push --force, git reset --hard, recursive deletes).

Set PI_REVIEWER_BACKEND=jev with the provider and model, for example openrouter with typesafe/jev-1.13, or typesafe with jev-latest and a TYPESAFE_API_KEY. Other compatible APIs take a provider ID, model, and full endpoint, with an optional apiKeyEnv.

The command, detected risky behaviors, compact excerpts of the conversation, recent shell commands, git state, project docs, and OS information. The reviewer then decides ALLOW or BLOCK, and Jev's reason is a fixed description of that choice rather than a generated explanation.

Interactive mode prompts you to decide manually; non-interactive mode (pi -p or JSON mode) blocks the command. Jev failures log the error message rather than provider error bodies, and the 60-second deadline applies per attempt.

Fifteen behaviors feed the reviewer prompt: force-push, branch-delete, worktree-remove, hard-reset, git-clean, recursive-delete, privilege-escalation, broad-chmod, fork-bomb, disk-destructive, system-shutdown, remote-shell, and the three Windows equivalents.

No. Tiers 1 and 2 are unchanged; Jev only reviews tier-3 commands, using the same rules and context. It validates the choice, confidence, and probability distribution, and there is no additional confidence threshold beyond the existing deadline, retry, and fallback.