Stop an agent instantly
What you get: a way to halt an agent that is doing the wrong thing, right now, enforced by the server, so the agent cannot talk its way past it.
1. Look before you pull
Section titled “1. Look before you pull”# is anything halted?quox safety statusorg_id 01KKNKH398KKEWB36JXRYR70QHdefcon GREENkillSwitches []# what would happen if this agent tried to act right now?quox safety gate commanderqblocked noescalate nodefcon GREENagentHalted noreason -# the audit trail is for admins only, and the server says soquox safety historyError: Request failed with status 403Status: 403 Admin access requiredgate shows the verdict a dispatcher gets for that agent: whether it is blocked, whether it must escalate to a human, and why.
2. Stop one agent
Section titled “2. Stop one agent”quox safety estop deploy-agent --reason "touching the wrong hosts"# check it tookquox safety gate deploy-agent# when you have looked into itquox safety release deploy-agentOnly a human admin can stop or release an agent; the server enforces that, whatever the client says. An agent cannot release its own kill switch.
3. Turn the dial for everything
Section titled “3. Turn the dial for everything”DEFCON sets the whole install’s posture, from GREEN (normal) through BLUE, AMBER and ORANGE (escalate) to RED (full halt):
quox safety defcon AMBER --reason "unexpected outbound traffic, investigating"quox safety defcon GREEN --reason "cleared"What just happened
Section titled “What just happened”The kill switch and the dial are checked by the server before every agent action, not by the agent. Each change carries your reason and lands in the append-only audit trail that quox safety history shows to admins.
Check it yourself
Section titled “Check it yourself”After a stop, quox safety status lists the agent under killSwitches, and quox safety gate <agent> reports the agent as halted.
quox safety release <agent> for one agent; quox safety defcon GREEN for the install.