{"version":"2.1.269","anchor":"serve-only-control-only-cloud-client-now-reacts-to-being","canonical_anchor":"serve-only-control-only-cloud-client-now-reacts-to-being","heading":"Serve-only cloud clients now detect and report being unlinked","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/serve-only-control-only-cloud-client-now-reacts-to-being","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Serve-only cloud clients now detect and report being unlinked\n\nA headless client acting only as a tool host for a cloud session now notices when it's unlinked and ends with a dedicated tool_host_ended reason\n\n**What**\n\n- The headless cloud client, when running in \"serve-only\" mode (meaning this computer is just acting as a tool host for a cloud session rather than driving it), now reacts to being unlinked mid-session: it handles a `tool_host_ended` message from the server and also periodically rechecks whether it's still linked, ending its connection if not.\n\n- Its session-end reasons now include a distinct `tool_host_ended` value, separate from existing reasons like `disconnected`, `rejected_options`, `open_failed`, and `output_failed`, with its own exit message. This new reason only fires for serve-only (control-only) clients.\n\n**Why**\n\nWithout this, a serve-only helper client could keep running even after the cloud session it was serving had ended or unlinked it, instead of shutting down promptly with a clear reason.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}