Passing both --no-publish and --publish-report now errors before the run starts.
named in this entry, found in this entry's text
First cited
4
The earliest release whose published evidence quoted --no-publish was v2.1.224, 7 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.2247 Aug 2026--no-publish and --publish-report are contradictory - pass at most one.
v2.1.2247 Aug 2026Error: --no-publish and --publish-report are contradictory
v2.1.2247 Aug 2026Error: --no-publish and --publish-report are contradictory - pass at most one.
v2.1.23314 Aug 2026· keep local next time with --no-publish
Presence across releases
1
BuildsHow manyDatesReading
v2.1.224 – v2.1.30873 builds7 Aug 2026 → 22 Oct 2026 ◆in the build
Build by build
73
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.
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 CLI flag does. All CLI flags.
