Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.260 ·

PreModelSwitch/PostModelSwitch hook-load failures now give more actionable errors

Failed model-switch hook loads now give a specific, actionable error message.

You'll notice Improvements
JSON All of v2.1.260
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
ImprovementsKind: in v2.1.260,
ImprovementsSection of the release

When plugin-delivered PreModelSwitch hooks can't be loaded, the block reason is now a specific message explaining why, and notes that switching models again will re-check the hooks. PostModelSwitch hook-load failures similarly now include the underlying reason inline, instead of a generic message saying plugin hooks could not be loaded.

Read from
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up PostModelSwitch, on Hooks reference. | SessionStart, SubagentStart, PostModelSwitch | Context only | `hookSpecificOutput.additionalContext` adds context for Claude. SessionStart also accepts [`initialUserMessage`, `watchPaths`, `sessionTitle`, and `reloadSkills`](#sessionstar… hooks see the edit
Confirmed since Anthropic's documentation has since written up PreModelSwitch, on Hooks reference. | PreModelSwitch | `hookSpecificOutput` or top-level `decision` | `permissionDecision` (allow/deny/ask), `permissionDecisionReason`. `decision: "block"` also [cancels the switch](#premodelswitch-decision-control) | hooks see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up PreModelSwitch, on Hooks reference.

See this entry in the whole of v2.1.260 →

Feedback