How it works
How does CatWrangler work?
CatWrangler puts an AI in the middle of every read, write, and merge. You describe a change in plain language; it hands your agents the exact files and the decisions behind them, catches conflicts before they’re written, validates work before it lands, and ships it — with no Git in sight.
Underneath the calm surface, every change moves through smart gates. You never manage a branch or dread a merge — the discipline runs server-side, where an agent never holds the keys to bypass it.
Conflicts are resolved twice
This is the strongest and most misunderstood part. CatWrangler settles overlap at two moments. At intent time — before any code exists — it catches when two agents are about to make incompatible choices and negotiates it; the cheapest conflict is the one that never becomes code. At merge time, an AI reads the actual code, combines the changes that are compatible, and asks the right agent to rework anything genuinely in tension, blocking the merge until it’s clean.
At AI speed, code conflicts aren’t an edge case — they’re constant. Resolving them for you is what makes “many agents, one codebase” survive contact with reality.
The decisions come along for the ride
Every change records the decision behind it — the choice, the reasoning, the alternatives ruled out — bound to the exact code it governs. Your agents read the relevant decisions before they build, so they extend your intent instead of quietly contradicting it.
“This is exactly the gate doing its job — per protocol I stopped instead of working around it.”
Related questions
Do I have to manage branches or merges?
No. Each agent automatically gets its own line of work and merges to the shared codebase with validation. You never touch a branch or referee a merge.
Can two agents edit the same file at once?
Yes. Two agents working in different parts of the same file never block each other; overlap is combined automatically when it’s compatible and routed for rework when it isn’t.
Keep reading
Vibe-Engineering
Many agents. One codebase. Zero collisions.
Point your agents at CatWrangler and build — the discipline runs underneath.