{"version":"2.1.287","anchor":"cloud-hook-staging-failure-message-now-mentions-claude-code","canonical_anchor":"cloud-hook-staging-failure-message-now-mentions-claude-code","heading":"Cloud hook error now tells you how to fix it with CLAUDE_CODE_TMPDIR","tier":"notice","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/cloud-hook-staging-failure-message-now-mentions-claude-code","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Cloud hook error now tells you how to fix it with `CLAUDE_CODE_TMPDIR`\n\nWhen a cloud session cannot store a verified hook copy safely, the error now explains what is blocked and suggests setting `CLAUDE_CODE_TMPDIR`\n\n**What**\n\nA hook is a command of yours that Claude Code runs at a set moment. A `PreToolUse` hook runs before a tool call, meaning an action Claude takes such as running a command, and it can block that call. When you start a cloud session with `claude --cloud`, Claude Code keeps a verified copy of such a hook somewhere the session itself cannot change.\n\nIf it cannot do that, the error message used to say only that the machine had no private place to keep a verified copy. The message now says:\n\n- a verified copy could not be saved outside the session's write access\n\n- the tool calls that hook matches are blocked\n\n- you can set `CLAUDE_CODE_TMPDIR` to a folder the session cannot write to and restart `claude --cloud`\n\n**Why**\n\nThe old message stated the problem but gave no way out. The new one tells you what is being blocked and what to change to fix it.\n\n- Area: Hooks\n- Names: `CLAUDE_CODE_TMPDIR`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}