Pi Warden
A Pi extension watches tool calls and agent progress for safety and completion problems.
A Pi extension watches tool calls and agent progress for safety and completion problems.
Before a guarded tool call, pi-warden builds state from the user task, a redacted action summary, recent conversation, and optionally the task spine, plan, project rules, pattern hits, and other enabled context. Jev returns typed Noul probabilities for questions such as irreversibility and off-task status, plus a Choice for scope; local thresholds and policy combine those answers with offline pattern checks to allow, warn, steer, or hold the call. In steer mode, the result goes back to the agent as tool feedback.
Would this guarded action have a hard-to-undo effect?
User task, redacted guarded action, recent conversation, and any enabled plan, project rules, and pattern hits.
How does this guarded action relate to the active task and earlier context?
User task, redacted guarded action, recent conversation, and any enabled plan, project rules, and pattern hits.
Skip read-only calls and run deterministic local pattern checks; retain pattern hits as request evidence in evidence mode.
Send the redacted task/action/context state and ask independent Noul questions for irreversibility and other judgments, plus a Choice question for task scope.
Convert Jev answers to a verdict using configured thresholds, together with pattern and authorization results.
In steer mode, block a held call and return corrective guidance to the agent; otherwise warn, ask for confirmation, or advise according to mode.
It combines local pattern detection with contextual Jev judgments and turns most findings into guidance the agent can act on. Its documented real-session example records a held database-reset call and an `irreversible` answer of 0.85.