{"version":"2.1.293","anchor":"bash-identity-check-for-app-identifier-shell-lines-behind-t","canonical_anchor":"bash-identity-check-for-app-identifier-shell-lines-behind-t","heading":"New check on whether shell commands name settings files, switched off by default","tier":"soon","area":"Bash","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/bash-identity-check-for-app-identifier-shell-lines-behind-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### New check on whether shell commands name settings files, switched off by default\n\nA new, switched-off check tells shell commands that only name app identifiers apart from ones that name settings files\n\n**Unclear.** Which shell commands this check applies to is not explained.\n\n**What**\n\nClaude Code has a new check for shell command lines that decides whether a line names one of Claude Code's settings files. It does two things:\n\n- It recognises lines that only name app identifiers, such as `xcrun simctl`, `defaults` or `open -b` with a bundle ID ending in `.claude`, so they are not counted as naming a settings file.\n\n- It checks whether a command names a settings file either by its path or by its inode (the unique number a file has on disk).\n\nIf the check itself fails with an error, the line is treated as naming a settings file. The check is off unless it is switched on remotely.\n\n**Why**\n\nIt appears to be part of the rules for shell lines supplied from elsewhere, and it is being rolled out quietly.\n\n- Flag `tengu_violin_arching`: Not enough to say (read for one account on one subscription tier against v2.1.293; this account: off, anonymous baseline: on, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Flag `tengu_violin_ebony`: Not enough to say (read for one account on one subscription tier against v2.1.293; this account: off, anonymous baseline: on, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Bash\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}