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.259 ·

prompt.context dispatch hook point

Computed prompt context blocks are forwarded through a registered prompt.context handler when one exists, alongside a session-bound extension point.

Nothing to try yet In Development
JSON All of v2.1.259
Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Plugin HooksArea: what it touches
In DevelopmentKind: in v2.1.259,
What probably matters to youSection of the release

A new dispatch path forwards computed prompt.context blocks through a registered handler, via zc.hasModuleHandlers("prompt.context") and eS("prompt.context", ...), if one exists, falling back to the untouched blocks otherwise. Related definitions x0e = kj("session.start") and tst = () => rb.whenSessionBound(y0e) point to a session-bound extension point.

Read from
Names in the bundleprompt.contextsession.start
What the documentation says
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 session.start, on Use the mods API. Work that outlives one event, such as checking on something once a minute, runs on a timer you start from `session.start`. A hook itself runs for one event and has a [time limit](/docs/en/plugins/mods/reference#limits) on its own execution… plugins/mods/api 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 session.start, on Use the mods API.

See this entry in the whole of v2.1.259 →

Feedback