{"version":"2.1.246","anchor":"bash-act-first-switch-present-but-unset","canonical_anchor":"bash-act-first-switch-present-but-unset","heading":"Bash \"act first\" switch present but unset","tier":"soon","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/bash-act-first-switch-present-but-unset","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Bash \"act first\" switch present but unset\n\nAn \"act first\" Bash behaviour reads an environment variable but has no default, so it stays off.\n\n**What**\n\nA new setting controls an \"act first\" behaviour for Bash commands, read from `CLAUDE_CODE_GORSE_PLOVER`. It has no built-in default, so with the variable unset and no server-provided value it stays undefined and the behaviour is off.\n\n**Details**\n\n- Resolved once and cached for the process.\n- Nothing else in this build supplies a value, so it is decided entirely by the environment variable or remote config.\n\n**Evidence**\n\n`e.bashActFirstEnabled ??= dt(_.CLAUDE_CODE_GORSE_PLOVER, Kd, void 0)`\n\n- Area: Permissions\n- Names: `CLAUDE_CODE_GORSE_PLOVER`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}