pi-warden
Supervise a Pi coding agent with project-rule and action judgments.
What Jev decides
Whether a proposed action breaks a rule or raises risk, and whether progress or a completion claim is supported.
pi-warden checks proposed writes, project rules, repeated failures, and unverified completion claims, then usually steers the agent to correct itself.
- Jev role
- Assess context-dependent agent actions and work quality for Warden policy.
- Input
- The proposed action or result, relevant project rules, and recent agent context.
- Output
- Typed risk and quality judgments consumed by Warden policy.
- Decision frequency
- At eligible writes, tool results, and completion checks when judgments are enabled.
- Fallback
- Local pattern guards continue without a model key; policy can steer or hold actions.
How it works
Overview
pi-warden is a Pi extension that combines local guards with optional model judgments. It checks tool actions before they run, compares edits with project rules, notices repeated failures, and challenges unsupported done claims. Most findings are fed back to the agent; irreversible actions can be held.
Offline guards work without a key. Jev-backed judgments require enabling Warden and a TypeSafe key; the optional capability conscience is beta and off by default. The model gives a judgment, while configured policy determines the intervention.
- Language
- TypeScript
- License
- MIT
- Author
- DevMortimer
Sources
Related projects
Jev Review
A code-review pipeline assembled from small typed judgments instead of one long reviewer prompt.
What Jev decides
What is risky, which files and evidence matter, what could fail, how severe it is, and who should review it.
Distill
Route coding-agent work, reasoning effort, and context retention through bounded Jev decisions.
What Jev decides
Which configured model and effort should handle a call, what evidence deserves attention, whether another attempt is useful, and what context should be retained.
jev-model-router
Route Claude Code model tiers and reasoning effort with one parallel Jev classification.
What Jev decides
Which fast, balanced, or deep tier fits the work, how much reasoning it needs, and whether production risk requires escalation.