{"version":"2.1.288","anchor":"device-hook-staging-reworked-to-try-private-fallback-folders","canonical_anchor":"device-hook-staging-reworked-to-try-private-fallback-folders","heading":"Hook copies are now stored in private folders before the shared temp folder","tier":"internal","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/device-hook-staging-reworked-to-try-private-fallback-folders","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Hook copies are now stored in private folders before the shared temp folder\n\nClaude Code now keeps verified hook copies in folders other users cannot write to, using the shared temp folder only as a last resort\n\n**Unclear.** This may only apply when hook forwarding is turned on.\n\n**What**\n\nHooks are scripts you set up to run automatically at certain points while Claude Code works. Claude Code keeps verified copies of them in a staging folder before running them.\n\nIt now tries folders that other users on the same machine cannot write to first, and uses the shared temp folder only if none of those work. Previously the temp folder was tried first, and the private folders were used only when the temp folder was shared.\n\nOther changes to how the copies are stored:\n\n- A private folder that fails is abandoned, and Claude Code goes back to the earlier order.\n\n- Leftover empty folders are now cleaned up.\n\n- A failed write is retried.\n\n**Why**\n\nA folder that anyone can write to lets another user on the machine swap a hook copy for something else. Trying private folders first narrows that risk, which matters most for cloud sessions.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}