{"version":"2.1.282","anchor":"new-windows-remote-tool-serving-off-reasons","canonical_anchor":"new-windows-remote-tool-serving-off-reasons","heading":"Clearer reasons when a Windows computer can't offer its tools to a cloud session","tier":"notice","area":"Windows","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/new-windows-remote-tool-serving-off-reasons","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Clearer reasons when a Windows computer can't offer its tools to a cloud session\n\nTwo new messages explain why a Windows computer's tools aren't offered to a cloud session, and the profile-folder message names more folders\n\n**What**\n\nClaude Code can offer this computer's tools to a Claude session running in the cloud. When it cannot, it gives a reason. Two new reasons cover Windows:\n\n- The list of mounted Windows drives (`\/proc\/self\/mounts`) could not be read.\n\n- Trusted devices are required, but the connection to the device cannot check a device's proof.\n\nThe existing message about unreadable profile folders now names AppData, the Start Menu and Documents, where it named only Documents.\n\n**Why**\n\nYou get a clearer explanation when this computer's tools are not made available to a cloud session.\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}