{"version":"2.1.323","anchor":"bash-tool-slow-command-hint-rules-can-require-cpu-time-and","canonical_anchor":"bash-tool-slow-command-hint-rules-can-require-cpu-time-and","heading":"Slow-command notes on shell commands can now depend on CPU time","tier":"notice","area":"Bash Tool","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/bash-tool-slow-command-hint-rules-can-require-cpu-time-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Slow-command notes on shell commands can now depend on CPU time\n\nRules that add a note to slow shell commands can now require a minimum CPU time, quote CPU seconds, and be skipped when the output has a marker\n\n**Unclear.** It is not clear where these rules come from or whether any are active by default.\n\n**What**\n\nWhen Claude runs a shell command through the Bash tool (the tool Claude uses to run commands in your terminal), Claude Code can attach a short note to the result if the command was slow. The rules that decide when a note is added can now do more:\n\n- `minCpuSeconds`: the rule only matches when the command used at least this much CPU time, meaning time the processor actually spent working rather than time spent waiting.\n\n- `unlessOutputHas`: the rule is skipped when the command's output contains the marker `[python-cpu-note]`.\n\n- `{seconds}` and `{cpu_seconds}`: placeholders the note text can use to quote the elapsed time and the CPU time. Any other use of curly braces in the note text is rejected.\n\nA rule that uses `{cpu_seconds}` or `minCpuSeconds` only matches when CPU usage figures are available for the command. Before, rules could only look at elapsed time, whether the command failed, and the kind of command, and the note text was fixed.\n\nSeparately, the Bash tool's own description in this release adds `.claude\/settings.local.json` to the examples of files Claude should not commit because they may contain secrets.\n\n**Why**\n\nA note that quotes CPU seconds lets Claude tell a command that is busy computing apart from one that is only waiting, for example on the network. The output marker lets a command that already reports its own CPU use avoid getting a second, duplicate note.\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}