{"version":"2.1.248","anchor":"served-tools-report-their-state-and-a-reason-when-they-are-n","canonical_anchor":"served-tools-report-their-state-and-a-reason-when-they-are-n","heading":"Served tools report their state, and a reason when they are not served","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/served-tools-report-their-state-and-a-reason-when-they-are-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Served tools report their state, and a reason when they are not served\n\nDebug logs now name why Claude Code's tools were not handed to the host.\n\n**What**\n\nClaude Code can now hand its tools to the host over the session channel, announcing on attach, on reconnect and when a worker starts. When that does not happen a debug line names the reason: `not_bound`, `not_served`, `not_announced` or `serving_off`.\n\n**Details**\n\n- The line is `[servedTools] not served over the session channel: ` followed by one of those four reasons.\n- Notices sent along with the announcement are truncated at a sentence or dash boundary first.\n\n**Evidence**\n\n`[servedTools] not served over the session channel: `\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}