{"version":"2.1.295","anchor":"editwrite-tool-permission-logging-gains-timing-fields","canonical_anchor":"editwrite-tool-permission-logging-gains-timing-fields","heading":"Usage data for rejected tool uses now includes timing","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/editwrite-tool-permission-logging-gains-timing-fields","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Usage data for rejected tool uses now includes timing\n\nWhen a tool use is rejected, Claude Code's usage data now records how long hooks and the permission decision took\n\n**What**\n\nA tool use is one action Claude takes, such as editing a file or running a command. When one is rejected, Claude Code already records a usage-data event. That event now also records two durations:\n\n- How long the hooks (your own scripts set to run before a tool is used) took\n\n- How long the permission decision took\n\n**Why**\n\nThis only adds measurements to usage data. It does not change what Claude can do or what you see.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}