{"version":"2.1.280","anchor":"windows-shell-name-hint-no-longer-hardcodes-the-powershellb","canonical_anchor":"windows-shell-name-hint-no-longer-hardcodes-the-powershellb","heading":"Windows shell-name hint no longer hardcodes the PowerShell\/Bash tradeoff wording","tier":"internal","area":"Windows","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/windows-shell-name-hint-no-longer-hardcodes-the-powershellb","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Windows shell-name hint no longer hardcodes the PowerShell\/Bash tradeoff wording\n\nThe Windows shell hint text pointing out PowerShell vs Bash syntax differences is now built from a separate string\n\n**Unclear.** The finding does not say whether the wording or behavior of the hint actually changed for users, only how it is assembled internally.\n\n**What**\n\nOn Windows, Claude Code shows a hint about which shell is active, including a note that PowerShell is the primary shell but that each shell (PowerShell, Bash, etc.) takes its own command syntax. That explanatory text is now pulled from its own string constant and a different helper function, rather than being written directly into the hint code.\n\n**Why**\n\nThis is an internal restructuring with no described change in what the hint says or when it appears.\n\n- Area: Windows\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}