{"version":"2.1.290","anchor":"remote-tools-announce-waits-for-the-worker-to-start","canonical_anchor":"remote-tools-announce-waits-for-the-worker-to-start","heading":"Remote sessions now wait for the worker to start before announcing tools","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/remote-tools-announce-waits-for-the-worker-to-start","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Remote sessions now wait for the worker to start before announcing tools\n\nWhen announcing its tools to a remote session, Claude Code now waits for the remote worker to start and records why a wait failed\n\n**Unclear.** Whether this waiting applies to every remote session or only some is not clear.\n\n**What**\n\nWhen Claude Code tells a remote session which tools are available, it now waits for the worker, the process running that session, to start first. Previously it did not wait. It also records how long it waited and, when the wait fails, the reason, for example that the message was lost or that the worker was replaced.\n\n**Why**\n\nWaiting for the worker should make it more likely that a remote session actually receives the list of tools it can use.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}