{"version":"2.1.281","anchor":"cloud-device-hooks-claude-code-shell-prefix-and-writable-ro","canonical_anchor":"cloud-device-hooks-claude-code-shell-prefix-and-writable-ro","heading":"Cloud device hooks: CLAUDE_CODE_SHELL_PREFIX and writable-root checks now understand Windows paths","tier":"notice","area":"Windows","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/cloud-device-hooks-claude-code-shell-prefix-and-writable-ro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Cloud device hooks: CLAUDE_CODE_SHELL_PREFIX and writable-root checks now understand Windows paths\n\nChecks on CLAUDE_CODE_SHELL_PREFIX for cloud device hooks now understand Windows paths\n\n**What**\n\n`CLAUDE_CODE_SHELL_PREFIX` is an environment variable that puts a command in front of shell commands Claude Code runs. Hooks marked to run on your device for a cloud session are checked before they use it, and those checks now handle Windows paths:\n\n- Drive paths like `C:\\...`, backslashes, and drive-letter lists of paths are recognised.\n\n- Drive-relative paths like `C:foo` and unquoted backslashes are treated as impossible to verify.\n\n- The check of folders the command may write to now includes Windows folders, and on Windows any folder it cannot place makes it fall back to the cautious choice.\n\nWhen the check fails, those hooks run without the prefix. Folder comparisons also split on either kind of slash on Windows.\n\n**Why**\n\nOn Windows, the decision about whether your prefix can safely be used for cloud device hooks is now based on correctly read paths, and anything unclear leads to the hooks running without it.\n\n- Area: Windows\n- Names: `CLAUDE_CODE_SHELL_PREFIX`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}