{"version":"2.1.281","anchor":"new-serve-tools-refusal-reasons-about-windows-shell-profil","canonical_anchor":"new-serve-tools-refusal-reasons-about-windows-shell-profil","heading":"New 'serve tools' refusal reasons about Windows shell-profile directories","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/new-serve-tools-refusal-reasons-about-windows-shell-profil","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### New 'serve tools' refusal reasons about Windows shell-profile directories\n\nTwo new messages explain why a Windows computer's tools are not yet offered to cloud sessions\n\n**What**\n\nClaude Code can make the tools on your computer available to cloud sessions, which run on remote machines. There are two new explanations for when it does not:\n\n- The location of the shell profile, the file your command line reads when it starts, is still being worked out.\n\n- Windows did not report where the Documents folder is. The message says the next start tries again.\n\n**Why**\n\nOn Windows, you now get a specific reason when your tools are not offered, and you know that restarting will try again."}