{"version":"2.1.280","anchor":"served-tools-session-channel-reannounces-after-reconnect-for","canonical_anchor":"served-tools-session-channel-reannounces-after-reconnect-for","heading":"Served-tools session channel reannounces after reconnect for control-only channels","tier":"internal","area":"Remote Tools","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/served-tools-session-channel-reannounces-after-reconnect-for","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Served-tools session channel reannounces after reconnect for control-only channels\n\nClaude Code now re-announces available tools after a reconnect on control-only session channels\n\n**What**\n\nClaude Code keeps a per-session channel that announces which tools are available to a \"worker\" process. For channels marked control-only, the channel now notices when the worker disappears, and when it comes back online (`onWorkerLive`), it triggers a `reconnected` reannounce of the available tools. This is on top of the existing reannounce that already happened when the connection stream itself reconnected.\n\n**Why**\n\nWithout this, a control-only channel whose worker dropped and came back could end up with a stale or missing record of which tools were available. Reannouncing on worker reconnect keeps that list accurate.\n\n- Area: Remote Tools\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}