Developer preview · Linux (X11)
The kill switch
The kill switch ends every session at once.
How it is triggered
- The host app sends one revoke message for all sessions on its private control channel, which is separate from the agent's MCP channel.
- The driver also revokes everything when that channel closes or when it receives the stop signal.
What happens
- Every session ends, including a call that is already running.
- Revocation is final for the life of the driver process: to continue, the host starts a new driver and you consent again.
- If the driver cannot report back to the host, it still stops its sessions instead of waiting.
See also Consent and the driver contract.