{"version":"2.1.292","anchor":"bash-telemetry-adds-zsh-nomatch-error-background-shells-for","canonical_anchor":"bash-telemetry-adds-zsh-nomatch-error-background-shells-for","heading":"Bash usage data records zsh 'no matches found' errors","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/bash-telemetry-adds-zsh-nomatch-error-background-shells-for","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Bash usage data records zsh 'no matches found' errors\n\nUsage data for each Bash command now notes zsh 'no matches found' errors, and main-session background commands can be flagged like subagent ones\n\n**Unclear.** What the flag on a main-session background command changes, and when it applies, is not known.\n\n**What**\n\nThe usage data Claude Code records each time its Bash tool (the tool Claude uses to run terminal commands) runs a command now includes `zsh_nomatch_error`. It notes when the zsh shell failed with \"no matches found\", which happens when a pattern such as `*.txt` matches no files.\n\nSeparately, a Bash command sent to the background can now be flagged for the main session, not just for some helper agents, when a further check allows it.\n\n**Why**\n\nThe new field shows Anthropic how often zsh pattern errors happen. Running commands works the same way.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}