Claude Code v1.0.41 · 2 Jul 2025
Enhanced Hook System with Per-Command Timeouts
Entry Kind: in v1.0.41, 02 Jul 25
Changes Section of the release
The hook execution system now supports individual timeout configurations for each command within a hook. Previously, all commands shared a single global timeout, but now each command can specify its own timeout value.
Usage Example: When configuring hooks, you can now specify a timeout for individual commands:
{
"hook_event_name": "pre-commit",
"commands": [
{
"command": "npm test",
"timeout": 30 // 30 seconds timeout
},
{
"command": "npm run lint",
"timeout": 10 // 10 seconds timeout
}
]
}
How sure we are
One source agrees One thing we can check says the same as this entry.
Anthropic's release notes agree Hooks: Added "hook_event_name" to hook input
See this entry in the whole of v1.0.41 →
Anthropic's note
Upstream's own release notes for v1.0.41 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.
Hooks: Added "hook_event_name" to hook input
Is this right?
0
0
Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
← Previous · 1 of 7
In v1.0.41 Changes release-page order
Next → · 3 of 7
New SubagentStop Hook Event