{"version":"2.1.318","anchor":"shell-cpu-time-proc-read-failure-logging","canonical_anchor":"shell-cpu-time-proc-read-failure-logging","heading":"Failed reads of shell command CPU time are logged and reported differently","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/shell-cpu-time-proc-read-failure-logging","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Failed reads of shell command CPU time are logged and reported differently\n\nWhen Claude Code cannot read a shell command's CPU time from \/proc, it now always logs it and reports unexpected errors\n\n**What**\n\nOn Linux, Claude Code reads \/proc, a system folder with live process details, to find how much CPU time a shell command's processes used for its usage data. When that read fails, Claude Code now always writes the debug message saying the CPU time was left out. It also reports the error unless it is one of two expected kinds.\n\nBefore, the message was written only for file system errors other than running out of open files, and other errors were reported instead.\n\n**Why**\n\nThis affects only diagnostics. The shell command itself runs the same either way.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}