Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.242 ·

Hook events are tagged by where they could run

Each hook event is now labelled by where it should run: locally, deferred, low value or container-internal.

Under the hood Internal Changes
JSON All of v2.1.242
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
HooksArea: what it touches
Internal ChangesKind: in v2.1.242,
What probably matters to youSection of the release
What

A new table labels each hook event with where it belongs: session start, session end and notification hooks run locally; permission requests are deferred; setup, compaction, teammate-idle, task and elicitation hooks are marked low value; and config, worktree, instructions, directory, file-change and message-display events are marked internal to the container.

Details
  • The table is classification data with no user-facing surface, and reads as triage for which events a separate hooks worker would be handed.
  • No flag or code path was observed acting on the labels in this build.
Evidence

container_internal

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.242 →

Feedback