{"version":"2.1.293","anchor":"commandscript-and-http-hooks-refuse-to-run-in-diskless-sess","canonical_anchor":"commandscript-and-http-hooks-refuse-to-run-in-diskless-sess","heading":"Command, HTTP and MCP tool hooks no longer run in diskless sessions","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/commandscript-and-http-hooks-refuse-to-run-in-diskless-sess","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Command, HTTP and MCP tool hooks no longer run in diskless sessions\n\nIn a diskless session, command, script, HTTP and `mcp_tool` hooks are now held back and not run, and an error is logged\n\n**Unclear.** What makes a session diskless, and so whether your hooks are affected.\n\n**What**\n\nA hook is a command or action you configure to run automatically at set points while Claude Code works. In a diskless session, a session with no disk to work on, these hooks are now held back instead of run:\n\n- Command and script hooks: not run\n\n- HTTP hooks: not sent\n\n- `mcp_tool` hooks: not called, with a message starting `MCP tool hook not run:` and a reason\n\nEach returns a result marked as withheld, and Claude Code logs an error saying the hook should have been filtered out earlier. The list of hooks that come only from managed settings, the ones set by an administrator, is now filtered as well.\n\n**Why**\n\nThis is a safety backstop. Even if a hook slips past the earlier filtering, it cannot run in a session that has no disk.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}