architecture
Stet sits between your AI tools and your repo.
Context flows out to every AI tool. Every AI change flows back through one gate before it can merge.
Your AI tools
- Claude Code
- Cursor
- Codex
- Any agent
Stet gate
- Charter
- Locked behaviours
- Scope guard
- Decision log
Your repo
- GitHub
- main branch
- CI
Read path — context to the tools
The charter, decision log and locked specs are served to any tool that asks, over MCP or a synced AGENTS.md file in the repo.
charter · decisions · locked specs → MCP → claude code, cursor, codex
Write path — the change to the repo
Every change runs the locked checks and the scope guard. A pass merges; a break is blocked with the reason and a fix prompt for the agent.
ai diff → stet gate → pass / blocked → github, ci
Security.
Runs on your machine
Stet is a local CLI. No account, no telemetry. Your code never leaves your laptop. The only network call is the optional Linear ticket fetch, which sends just the ticket ID.
Open source
MIT licensed. Read every line on GitHub before you run it.
Your repo stays yours
Stet only writes .stet/, AGENTS.md and CLAUDE.md. Remove them any time.
try it now
Ten minutes to your first locked feature.
Free and open source. Run it in any project folder; it detects your stack and writes your AI rulebook.