{"version":"2.1.293","anchor":"cloud-sessions-deny-permissionrequest-hooks-that-cant-run","canonical_anchor":"cloud-sessions-deny-permissionrequest-hooks-that-cant-run","heading":"Cloud sessions deny permission requests when a PermissionRequest hook can't run","tier":"notice","area":"Hooks","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/cloud-sessions-deny-permissionrequest-hooks-that-cant-run","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Cloud sessions deny permission requests when a PermissionRequest hook can't run\n\nIn cloud sessions, a `PermissionRequest` hook that is a command, script, HTTP or MCP tool hook now causes the request to be denied\n\n**What**\n\nHooks are actions you configure to run automatically at set points. A `PermissionRequest` hook runs when a tool call (an action Claude wants to take) needs a permission decision.\n\nIn cloud sessions, Claude Code does not run command, script, HTTP or MCP tool hooks, because those would run on the shared server the session uses. If a `PermissionRequest` hook is one of those types, the permission request is now denied, with a message saying the hook can't run in this cloud session.\n\n**Why**\n\nA hook that was meant to decide on permissions is not quietly skipped in a way that lets the action through. If you rely on these hooks, expect such requests to be refused in cloud sessions.\n\n- Area: Hooks\n- Names: `PermissionRequest`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}