I built an emergency STOP for the two autonomous AI engineering teams working on Headroom. Turns out, defining what "stopped" actually means is surprisingly difficult.
The agents pick up issues, write code, run tests and prepare releases while I'm doing other things. That's the point. I want them to work independently without having to supervise every decision.
But agents make wrong assumptions. They can work on conflicting changes, keep iterating without making progress, or proceed with something that should have required my approval. Ordinary engineering problems, just happening with considerably less human intervention.
We already have shared context, scoped responsibilities, quality gates and release controls. The emergency STOP is the last line of defense, not a replacement for any of those.
It can block new tool calls and prevent deployments. But work that's already running doesn't magically disappear, and not every remote session can be controlled or verified.
So Mission Control doesn't simply tell me everything has stopped. It distinguishes between STOPPED, PARTIALLY STOPPED and NOT CONFIRMED.
I don't want a reassuring green indicator when I can't prove what's actually happening.
The point of building autonomous engineering teams isn't to remove myself from the equation. It's to give them room to work without losing control of the outcome.