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 is cut short now fail instead of hanging

Hooks now wait for their output to finish after exiting, and fail with an "output incomplete" message if it was cut off

You'll notice Bug Fixes
JSON All of v2.1.285
You'll noticeTier: how much it should matter to you
3Useful: 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

A hook is a command you set up to run automatically at certain points while Claude Code works, such as before a tool runs. Claude Code reads what the hook prints. It used to wait until the hook's output channels closed. It now waits for the hook process to exit and then gives the output a moment to finish arriving.

If the output was cut off before it ended, the hook now fails. The message says the output is incomplete, that its output was cut before the end on this machine, and suggests a retry. For hooks on events that are able to block an action, this failure blocks the action. The handling of exit code 2, the code a hook uses to block, also takes cut-off output into account.

Why

A hook that starts a background program which keeps the output channel open should no longer leave Claude Code waiting forever. The trade-off is that a hook whose output is truncated now counts as a failure, and on blocking events that stops the action.

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 clear exactly when Claude Code decides a hook's output was cut off.

See this entry in the whole of v2.1.285 →

Feedback