{"version":"2.1.283","anchor":"bridge-now-reports-refused-tool-host-work-to-the-server","canonical_anchor":"bridge-now-reports-refused-tool-host-work-to-the-server","heading":"Cloud sessions are told when a device refuses to run their tools","tier":"internal","area":"Remote Tools","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/bridge-now-reports-refused-tool-host-work-to-the-server","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Cloud sessions are told when a device refuses to run their tools\n\nWhen a local machine refuses to run tools for a cloud session, Claude Code sends the server a short refusal notice with a reason code\n\n**Unclear.** The refusal report was already present in the previous build, and which part of it differs in this release is unclear.\n\n**What**\n\nA cloud session can hand work to a local machine, which then acts as the tool host: the machine that runs the session's tool calls. When that machine refuses the work, Claude Code sends the server a refusal notice. The notice carries the ID of the refused work and a reason code.\n\nThe notice is sent once, with a 5 second timeout. If it fails, Claude Code does not wait for an answer and does not retry it. It is not sent in these cases:\n\n- you use Claude through a provider other than Anthropic\n\n- Claude Code is in essential-traffic mode, where it keeps network calls to the minimum\n\n- the `allow_remote_control` policy is off\n\n**Why**\n\nThe cloud side finds out straight away why a device would not host its tools, instead of waiting until the request times out.\n\n- Area: Remote Tools\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}