Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.248 ·

PostToolUse hooks receive how long the tool took

PostToolUse hooks now get duration_ms, the tool's own run time excluding prompts and hooks.

Use it now Notable Improvements
JSON All of v2.1.248
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
HooksArea: what it touches
ImprovementsKind: in v2.1.248,
What probably matters to youSection of the release
What

The data passed to a PostToolUse hook now includes an optional duration_ms, the tool's own execution time. It excludes time spent on permission prompts and on other hooks, so it reflects the tool rather than the wait around it.

Evidence

Tool execution time in milliseconds. Excludes permission-prompt and hook time.

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundleduration_ms
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since A small documentation edit on Customize your status line touched a line naming duration_ms after this was published. | `cost.total_duration_ms` | Total wall-clock time the session has been running, in milliseconds. Accumulates across resumes and doesn't include time while the session isn't running | statusline see the edit
Confirmed since Anthropic's documentation has since written up duration_ms, on Monitoring. | `interaction.duration_ms` | Wall-clock duration of the turn | | monitoring-usage see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up duration_ms, on Monitoring.

See this entry in the whole of v2.1.248 →

Feedback