Rules your AI agent can’t ignore.It’s 1 a.m. Do you know what your agent is doing?
Decide what every AI agent may do, enforce it from outside the agent, and keep a record of what each agent did.
It deleted the database. Then it said sorry. You deserve more than a sorry.
Supported by


claude is waiting for youWants to read
Allow onceDeny./confidential/plan.mdfix-billing-bugRunning
Protected: 2 moves blocked
- Read
src/billing.pyAllowed - Edit
src/billing.pyAllowed - Upload to
pastebin.comBlocked - Write
~/.bashrcBlocked - Run
pytestAllowed
Supported by


Meet Tego.
Write your rules once. Tego stops the move, not the work. Point at a step to see it.
- 1 Declare Set rules before the agent runs: which data it can read, which systems it can change, which services it can call.
- 2 Enforce Tego refuses what the rules rule out, whatever model or vendor the agent uses.
- 3 Record Each run is recorded with the rule that applied, so you can check what each agent did.
- 4 Decide When a rule says ask first, a person answers and can make the answer a rule. The loop goes back to Declare.
It’s 1 a.m. Do you know what your agent is doing?This already happened.
Real agent incidents, with sources.
Read more on the blogA cleanup trap deleted a home folder
Strict rules refuse key steps
The npm worm that planted AI agent hooks
Strict rules refuse key steps
An agent deleted production in nine seconds
Strict rules refuse key steps
Try it on your machine today.
Free and open source. Linux today; Mac and Windows through a small Linux VM.
curl -fsSL https://github.com/Attention-Span-AI/Tego/releases/latest/download/install.sh | sh