{"version":"2.1.281","anchor":"cloud-hook-forwarding-accepts-non-posix-absolute-paths-wind","canonical_anchor":"cloud-hook-forwarding-accepts-non-posix-absolute-paths-wind","heading":"Cloud hook forwarding accepts non-POSIX absolute paths (Windows)","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/cloud-hook-forwarding-accepts-non-posix-absolute-paths-wind","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Cloud hook forwarding accepts non-POSIX absolute paths (Windows)\n\nLocal hooks can now be offered to a cloud session when their folders use Windows-style absolute paths\n\n**What**\n\nHooks are commands you set up to run automatically at certain moments while Claude Code works. Claude Code can offer the hooks on your computer to a cloud session, meaning a session that runs on a remote machine instead of yours.\n\nBefore offering them, it checks that certain folders are given as full paths. That check used to accept only paths starting with `\/`, which is how paths look on macOS and Linux. It now accepts any full path, including Windows paths such as ones starting with a drive letter. When the check still fails, the message now reads: \"Hooks stay on this machine: its launch, config or sync directory is not an absolute path this version can place, so none are offered to the cloud session.\"\n\n**Why**\n\nOn Windows, local hooks were never offered to cloud sessions because their paths failed the old check. They can now be offered."}