Follow Discord
Sweep 29 Sep 2026 · 18:10Z Build v2.1.285 506 read Stable v2.1.280 Latest v2.1.285 Next v2.1.285 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.285 ·

Hooks whose output was cut off are no longer trusted

When a hook's output stream closes early, Claude Code no longer reads it as a verdict or reports the hook's script as missing

Group of 2 You'll notice Bug Fixes
JSON All of v2.1.285
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
HooksArea: what it touches
Bug FixesKind: in v2.1.285,
Bug FixesSection of the release

What

Hooks are your own scripts or commands that Claude Code runs at set moments, such as when Claude stops or before a tool runs. Claude Code reads what a hook prints to decide what to do next. It now checks whether the hook's stdio (the input and output streams it uses to talk to Claude Code) closed before the end of the stream:

  • A hook's output is no longer read as a clean verdict if its stdio closed before end-of-stream. Part of the output may have been lost, and Claude Code says it is "refusing to read the partial capture as a verdict". This matters most for hooks that grant permissions or add context to the conversation.
  • The check that decides a Stop hook or similar hook's script is missing no longer fires when stdio was incomplete or closed without an end (stdioClosedWithoutEnd). Before, it looked only at empty normal output and a "no such file" or "can't open" message in the error output.

Why

A cut-off answer from a hook can no longer be mistaken for a permission decision. You should also see fewer false reports that a hook's script is missing.

See this entry in the whole of v2.1.285 →

Feedback