Claude Code v2.1.246 · 25 Aug 2026
Clearer reason when an administrator has blocked plugin hooks
When managed settings block plugin hooks, the message now says that explicitly.
You'll notice Tier: how much it should matter to you
2 Useful: my rating, 1 to 5
1 Signal: worth watching, 1 to 5
Hooks Area: what it touches
Improvements Kind: in v2.1.246, 25 Aug 26
Improvements Section of the release
What
When plugin hook modules are refused because managed settings only permit hooks from enterprise-managed sources, the message now says so explicitly instead of reusing a generic reason.
Evidence
an admin stood the guard down (safe mode / managed allowManagedHooksOnly)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.246 →
25 Aug 2026 · 429 entries, this one is #235.
45 199 37 148
Open the release →
Names in this entry
cli --bare Minimal mode: skip auto-discovery of hooks, skills, custom commands, subagents, installed plugins, MCP servers, auto memory, and CLAUDE.md so scripted calls start faster. Skills in a directory you pass with --add-dir still load. Claude has access to Bash, file read, and file edit tools. Sets CLAUDE_CODE_SIMPLEbare mode
setting disableAllHooks Turn off hooks , a custom status line , and a custom @ file suggestion
setting allowManagedHooksOnly Run only the hooks your organization deploys
Is this right?
0 0 Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
← Previous · 234 of 429
Clearer warning when a saved hooks answer cannot be reused in a cloud session
You'll notice Hooks
In v2.1.246 Improvements release-page order
Next → · 236 of 429
Prompt banner is drawn without a gradient
You'll notice Terminal UI
