{"version":"2.1.307","anchor":"cloud-device-forwarding-not-ready-reason-and-a-softer-fo","canonical_anchor":"cloud-device-forwarding-not-ready-reason-and-a-softer-fo","heading":"Cloud sessions say device forwarding is off 'for now' while it is not ready yet","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/cloud-device-forwarding-not-ready-reason-and-a-softer-fo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Cloud sessions say device forwarding is off 'for now' while it is not ready yet\n\nA new not_ready reason lets cloud sessions tell Claude it cannot reach your computer yet, instead of saying forwarding is off\n\n**What**\n\nIn cloud sessions, Claude Code can forward some tools to run on your own computer. When that is unavailable, Claude is given a notice explaining why. There is now a new reason for that notice:\n\n- `not_ready` joins the existing reasons `disabled_switch_off` and `disabled_flag_off`. It covers the case where the session has not yet been able to check whether tools can run on your computer.\n\n- For this reason the notice uses the softer `forwarding_off_for_now` wording instead of `forwarding_off`. Claude is told it cannot reach your computer yet and that starting a new session may help.\n\n- Before building the notice, Claude Code now first tries to attach the tool host (the part on your computer that runs the forwarded tools).\n\n**Why**\n\nClaude can now explain the situation more accurately while things are still starting up, rather than telling you forwarding is switched off when it simply is not ready.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}