An "act first" Bash behaviour reads an environment variable but has no default, so it stays off.
A Bash "act first" mode reads CLAUDE_CODE_GORSE_PLOVER and stays undefined with nothing set.
What's wrong with this entry?
A 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.
- Resolved once and cached for the process.
- Nothing else in this build supplies a value, so it is decided entirely by the environment variable or remote config.
e.bashActFirstEnabled ??= dt(_.CLAUDE_CODE_GORSE_PLOVER, Kd, void 0)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.