{"version":"2.1.285","anchor":"windows-cloud-session-hook-approvals-get-two-new-prompts","canonical_anchor":"windows-cloud-session-hook-approvals-get-two-new-prompts","heading":"Windows asks for approval when it can't check a hook for a cloud session","tier":"notice","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/windows-cloud-session-hook-approvals-get-two-new-prompts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Windows asks for approval when it can't check a hook for a cloud session\n\nOn Windows, Claude Code has two new reasons to ask before running a cloud session command that one of your hooks cannot vet\n\n**Unclear.** It is not clear whether these new approval prompts are behind a flag.\n\n**What**\n\nA hook is a command you set up to run automatically at certain points, for example to check a command before it runs. A cloud session is a Claude Code session that runs on a remote machine and syncs your project. When a cloud session wants to run a command and Claude Code on a Windows computer cannot confirm that one of your local hooks lies outside the synced project, it now asks for your approval. There are two new explanations for why:\n\n- On Windows, Claude cannot yet confirm that the program behind the hook lies outside the synced project.\n\n- Claude cannot confirm that the folder the hook would start in lies outside the synced project.\n\nBefore this, the only explanations were that the hook's script was inside the project, that it could not be read, or that it was a model hook.\n\n**Why**\n\nThe cloud session can rewrite files in the synced project, so a hook stored there cannot be trusted to check its own commands. On Windows, commands that a local hook would normally have vetted now stop and ask you instead of running unchecked.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}