Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.317 ·

Plain output from some background hooks can now become start-of-session context

Some background hooks that print plain text and succeed now have that text passed to Claude as context when a session starts

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

Unclear It is not stated which hooks have this behaviour turned on, or whether you can turn it on for your own.

What

Hooks are actions that Claude Code runs automatically at set points. Async hooks run in the background without making Claude Code wait. Some async hooks can now have their plain printed output passed to Claude when a session starts or resumes, as extra context for the SessionStart event.

This happens when all of these are true:

  • The hook has this behaviour turned on.
  • The hook finishes without an error.
  • Its output is plain text, not JSON (a structured data format).
  • It gives no other answer.

Long output is shortened, with a note saying '[The hook printed more than is shown here.]'.

Separately, when a hook callback fails, Claude Code now shows a warning. If the hook's onFailure setting is "block", the failure counts as a block.

Why

What Claude knows at the start of a session can now include text printed by these hooks. Keep that output short and relevant.

Read from
Names in the bundleSessionStart
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not stated which hooks have this behaviour turned on, or whether you can turn it on for your own.

See this entry in the whole of v2.1.317 →

Feedback