{"version":"2.1.287","anchor":"device-hooks-private-run-folder-and-away-handling","canonical_anchor":"device-hooks-private-run-folder-and-away-handling","heading":"Hooks a cloud session runs on your machine now start in a private folder","tier":"notice","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/device-hooks-private-run-folder-and-away-handling","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Hooks a cloud session runs on your machine now start in a private folder\n\nCommand hooks sent from a cloud session to your machine now run in a private folder or are refused if there is none\n\n**What**\n\nA hook is a command that Claude Code runs on its own at set points in a session. A cloud session can send a command hook to your own machine to run there.\n\nWhen such a hook has not opted in with `cloudOptIn`, Claude Code now handles it this way:\n\n- If the folder it would start in is unmarked and private, the hook runs in a private folder set up just for that run.\n\n- If no such folder is available, the hook is refused with a message saying the machine has no private folder to start it in.\n\nThe hook's answers are now sent back through a separate path, unless your device is reported as away.\n\n**Why**\n\nThis gives tighter control over where hooks from the cloud can run on your computer.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}