pi-warden

# pi-warden

**Stop babysitting your coding agent.**

pi-warden supervises Pi while it works, catching risky actions, ignored rules, stuck loops, unverified "done" claims, security issues, runaway output, wasted context, and more.

Instead of interrupting you for every problem, Warden usually feeds the issue back to the agent so it can correct itself and keep going.



## Install

```bash
pi install npm:pi-warden
```

1. `/warden enable` to activate. Paste a key from [console.typesafe.ai](https://console.typesafe.ai) if you have one (hidden input, saved owner-only), or skip for offline-only mode.
2. `/warden test` to see one synthetic verdict.
3. Work as usual. Status line shows verdicts; `ctrl+shift+w` opens the trace sidebar.

Works without any key (offline guards: pattern list, runaway stop, sensitive-path notes, credential warnings). Requires Pi 0.85+, Node 22.19+.

## What Warden catches

| Guard | Watches | Does |
| --- | --- | --- |
| **Action** | `bash`, `write`, `edit` before run | Holds irreversible calls, records trace-only off-task findings |
| **Rules** | every `write` and `edit` | Judges against project Markdown rules, quotes the broken rule |
| **Slop** | code and replies | Names stubs, restating comments, dead code, hedging |
| **Stuck** | tool results | Repeated failures using the same strategy |
| **Done-check** | final message | "Done" claims with no test/build/lint behind them |
| **Security** | code and output | Hardcoded secrets, injection risks |
| **Runaway** | reply stream | Stops replies that begin repeating themselves |
| **Subagent triage** | async child reports | Keeps noisy background work from waking the parent |

## How intervention works

1. **Read-only? Skip.** `git status`, `ls`, `read` means no request and no trace entry.
2. **Known-d