Get an API key

Docs · Guides

Emergency stop

Stop every agent in a workspace at once: no sends, no identity tokens, no scheduled mail, while reads keep working. One click or one API call.

Pausing one inbox stops one agent. The emergency stop is the switch for the whole workspace, for the moment you don’t yet know which agent is misbehaving: a reply loop, wrong recipients, a leaked key. It covers Homingbox inboxes and Shakehand identities alike.

#Stop

Owners press Stop every agent under Settings (with an optional reason). An agent or a script can also pull it, with an API key that has the workspace:emergency permission (only the Full access preset has it):

curl
curl -X POST https://api.agentboxd.com/v1/emergency-stop \
  -H "Authorization: Bearer $AGENTBOXD_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "reason": "support-bot is replying in a loop" }'

Stopping a stopped workspace changes nothing. The workspace gets a workspace.stopped event (the audit record: when, why and who, a person or an API key), every owner gets an email, and so do your people on call, even during quiet hours.

#What stops

  • Every send from every inbox: POST …/send, replies, sending a draft, SMTP submission. They answer 423 workspace_stopped (SMTP: 550 5.7.1 workspace_stopped, permanent, so clients don’t retry for days and send on resume).
  • Scheduled drafts stay scheduled; nothing fails. After the resume, those still due go out within a minute.
  • Sign in with Agentboxd identity tokens: minting answers 423 workspace_stopped; apps redeeming a code get invalid_grant.
  • The claim queue hands out nothing (paused: true).
  • Hosted MCP connections keep working for reading; tools that send return the error with a note that a person must resume.

#What keeps working

Reading mail, threads and contacts with any key or connected app; receiving mail; webhooks, the event stream and categorisation. The people handling the incident need to see what arrives. Mail that was already handed to the outbound queue before the stop may still leave. Inboxes you paused one by one stay paused after the resume.

#Resume

Only a workspace owner can resume, from the red banner on every dashboard page or from Settings. There is deliberately no API call for it: a key that may be compromised can stop the workspace, never restart it. The workspace gets workspace.resumed and the owners get an email.