Unclear What makes a session diskless, and so whether your hooks are affected.
What
A 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:
- Command and script hooks: not run
- HTTP hooks: not sent
mcp_toolhooks: not called, with a message startingMCP tool hook not run:and a reason
Each 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.
Why
This is a safety backstop. Even if a hook slips past the earlier filtering, it cannot run in a session that has no disk.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What makes a session diskless, and so whether your hooks are affected.