Unclear It is not stated what makes Claude Code treat a hook as having run elsewhere, so it is unclear which setups this affects.
What
Hooks are your own commands that Claude Code runs at set moments, such as before a tool is used. When Claude Code collects what those hooks printed, it already left out output that:
- failed
- was blocked
- was empty
It now also leaves out output from any hook marked as having run elsewhere, meaning on another machine. Output from elicitation hooks (hooks that run when a connected tool asks you for input) that ran elsewhere is now passed through a separate conversion step.
Why
When a hook has run on another machine, its output would otherwise be added to the conversation a second time. Leaving it out stops Claude from seeing the same hook output twice.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not stated what makes Claude Code treat a hook as having run elsewhere, so it is unclear which setups this affects.