{"version":"2.1.259","anchor":"remote-tool-serving-gets-an-emergency-off-switch","canonical_anchor":"remote-tool-serving-gets-an-emergency-off-switch","heading":"Remote tool serving gets an emergency off switch","tier":"notice","area":"Remote Tools","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/remote-tool-serving-gets-an-emergency-off-switch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### Remote tool serving gets an emergency off switch\n\nWhen remote tool serving is muted by the emergency switch, served-call requests are answered empty with an explanatory reason.\n\nMCP and device hooks now check `e.isMuted?.()` before answering a served-call request. When muted, the request is silently answered empty and logged as 'serving is switched off (emergency switch)', with a corresponding UI reason string explaining that remote tool serving was turned off by Anthropic via the emergency switch.\n\nWhen this emergency switch is off, the client-facing message now says that any command a cloud session was running on the local machine was cancelled and Claude was told it may have partially run, rather than just stating that no new commands will run. A second, hooks-specific pair of messages mirrors this for plugins, confirming that hooks offered to cloud sessions are likewise suspended and resumed by the same remote emergency switch.\n\n- Area: Remote Tools\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}