An "act first" Bash behaviour reads an environment variable but has no default, so it stays off.
named in this entry, found in this entry's text
First cited
1
The earliest release whose published evidence quoted CLAUDE_CODE_GORSE_PLOVER was v2.1.246, 25 Aug 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
ReleaseDateThe span that was quoted
v2.1.24625 Aug 2026e.bashActFirstEnabled ??= dt(_.CLAUDE_CODE_GORSE_PLOVER, Kd, void 0)
Presence across releases
1
BuildsHow manyDatesReading
v2.1.218 – v2.1.30980 builds22 Jul 2026 → 22 Oct 2026 ◆in the build
Build by build
80
One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
v2.1.29914 Oct 2026·presentverdict: present · bool
v2.1.30014 Oct 2026·presentverdict: present · bool
v2.1.30115 Oct 2026·presentverdict: present · bool
v2.1.30216 Oct 2026·presentverdict: present · bool
v2.1.30318 Oct 2026·presentverdict: present · bool
v2.1.30419 Oct 2026·presentverdict: present · bool
v2.1.30520 Oct 2026·presentverdict: present · bool
v2.1.30621 Oct 2026·presentverdict: present · bool
v2.1.30721 Oct 2026·presentverdict: present · bool
v2.1.30822 Oct 2026·presentverdict: present · bool
v2.1.30922 Oct 2026·presentverdict: present · bool
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the environment variable does. All environment variables.