Trust & safety
Is it safe to let AI agents change my codebase?
Yes — because agents never hold the keys. CatWrangler runs version control server-side, where every write passes through gates: load the right context, write in an isolated line of work, then validate before merge. Incoherent or broken change is refused, never landed.
The honest worry about AI agents touching a codebase is that one will move fast, miss context, and quietly break something. CatWrangler answers that structurally: the write path is gated, and the gates are not optional.
The write path is gated; reading stays open
Exploring and reading the codebase is wide open — that is how agents get up to speed fast. The discipline only kicks in on the write path, and it runs in three steps every change has to pass.
An agent can't skip a step or route around it, because the gates run server-side and the agent never holds the keys to the write path. The system enforces the order; the agent just builds.
- Load context first: describe the change in plain language and get exactly the right files, functions, and the decisions behind them — no grepping the whole repo, no guessing.
- Isolate the write: every agent automatically gets its own line of work. The shared trunk is never written directly, so nothing in progress can corrupt what everyone else depends on.
- Validate before merge: on submit, the change must actually cover the decision it claims, and it has to build and pass tests before it can land. Incoherent or broken change never merges.
Hosted, so the keys stay out of reach
CatWrangler is a hosted service with one isolated server per customer — nothing to install or self-host. Credentials and the write path are structurally out of agents' reach. An agent can't bypass the gates because it never holds the keys.
That is the difference between hoping an agent behaves and knowing it can't land a change that doesn't pass. And if a change ever does need pulling back, a bad deploy rolls back automatically — your codebase isn't left in a broken state.
“This is exactly the gate doing its job — per protocol I stopped instead of working around it.”
Related questions
Can an agent skip the gates if it's in a hurry?
No. The gates run server-side and the agent never holds the keys to the write path, so there is no path around them. The order is enforced by the system, not by the agent's good behavior.
What happens when a change is broken or doesn't match its stated intent?
It's refused at the validation gate. A change must cover the decision it claims and must build and pass tests before it can merge, so incoherent or broken work never lands on the shared trunk.
Keep reading
Vibe-Engineering
Many agents. One codebase. Zero collisions.
Point your agents at CatWrangler and build — the discipline runs underneath.