{"version":"2.1.111","anchor":"powershell-tool-now-feature-flagged-on-windows","canonical_anchor":"powershell-tool-now-feature-flagged-on-windows","heading":"PowerShell Tool Now Feature-Flagged on Windows","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.111\/e\/powershell-tool-now-feature-flagged-on-windows","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.111","markdown":"### PowerShell Tool Now Feature-Flagged on Windows\n\nThe PowerShell tool on Windows is now controlled by the `tengu_cobalt_ridge` feature flag instead of being always enabled. Non-Windows platforms continue to respect the `CLAUDE_CODE_USE_POWERSHELL_TOOL` environment variable. This allows server-side rollout control of the PowerShell tool experience.\n\n**Evidence**\n\nFeature flag in `ly6()` at line ~250722 (search for `\"tengu_cobalt_ridge\"`)\n\n- Flag `tengu_cobalt_ridge`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.111; this account: on, anonymous baseline: on, compiled default: no gate table built for this version) 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."}