{"version":"2.1.302","anchor":"bash-cpu-cgroup-setup-hardened","canonical_anchor":"bash-cpu-cgroup-setup-hardened","heading":"Safer setup for measuring the CPU used by Bash commands","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/bash-cpu-cgroup-setup-hardened","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Safer setup for measuring the CPU used by Bash commands\n\nSetup for measuring Bash command CPU on Linux now rejects `..` in paths, keeps colons when parsing, and says what is lost if it fails\n\n**What**\n\nClaude Code can measure how much processor time commands run through its Bash tool use, using a Linux feature that groups processes so their resource use can be counted. The setup for this has been tightened:\n\n- A group path containing `..` (a step up to a parent folder) is now rejected.\n\n- Paths that contain colons are now read correctly instead of being cut at the colon.\n\n- If setup fails, the log now says Bash-tool CPU will not be measured separately, and nothing else changes.\n\n**Why**\n\nThis closes a path risk and fixes a parsing bug in usage measurement. If the measurement cannot be set up, your commands still run as normal.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}