Trust layer for IDE agents
Govern the session.
Not the model.
Your IDE agent builds. zer0dev frames Intent, stays lean while it works, and Audits the change before “done.” No source upload. No second coder.
Session loop
Select a step · Builder writes · Governor steers
zer0dev
Governor frames the session
Preflight.
Name the change and lock a small review scope before tools run.
Trace
01 / 03
- ›Load a short Boot map
- ›Name the change
- ›Lock a small review scope
- ›Extra skills wait until needed
View host trace
- ›GET /api/boot · thin index
- ›intent → feature.change
- ›scope → micro · css + a11y
- ›skills deferred until needed
The gap
Rules and PR bots miss the live session.
Everything else reacts too early or too late. The middle is where sprawl happens — and where a governor belongs.
01
Rules files.
Static lists. Easy to ignore mid-task. Drift the moment the repo changes.
02
PR review bots.
Catch bugs after the PR exists. Too late to stop a session that already sprawled.
03
Second agents.
Another model in the loop. You already have a builder — you need a governor.
Roles
Keep the builder.
Add the governor.
One writes. One frames and reviews. Neither replaces the other.
01
Builder.
Cursor · Claude · Copilot
Writes code in the IDE you already use.
02
Governor.
zer0dev
Frames intent, pulls lean context, closes a Done Gate on the change.
What you install
A thin client.
Law stays on the host.
Boot is a short fetch map — not a megaprompt in the repo. When doctrine updates, the next session pulls it. The host never needs your source.
01
Sign in
Magic link. One project key, shown once.
02
Install
Pick a session context. Paste Boot into Cursor, Claude, or Copilot.
03
Govern
Preflight before tools. Scoped audit before “done.” Law stays live on the host.
Opens Sign in. Then Boot → Install into your IDE.