{"version":"2.1.273","anchor":"per-tool-cpu-accounting-now-split-by-phase-via-a-dedicated-f","canonical_anchor":"per-tool-cpu-accounting-now-split-by-phase-via-a-dedicated-f","heading":"Per-tool CPU accounting now split by phase via a dedicated file","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/per-tool-cpu-accounting-now-split-by-phase-via-a-dedicated-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Per-tool CPU accounting now split by phase via a dedicated file\n\nClaude Code now tracks CPU usage per phase for individual shell tool calls\n\n**What**\n\nClaude Code has a new helper that computes a file path used to track CPU usage broken down by phase for shell tool calls, skipping session IDs that look like sub-paths or start with \"cc-\". This is used to log a `tengu_tool_cpu_by_phase` telemetry event, and it fails gracefully with a fallback message if the tracking file can't be created.\n\n**Why**\n\nThis gives more detailed CPU usage data for shell commands, broken down by phase, which can help diagnose performance issues in specific stages of command execution.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}