Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.220entry #1

Claude Code v2.1.220 ·

Classifier beta-rejection latch still keys off a null placeholder

The automatic retry that would drop a rejected classifier beta can never trigger in this build.

Nothing to try yet Notable In Development
JSON All of v2.1.220
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
PermissionsArea: what it touches
In DevelopmentKind: in v2.1.220,
What probably matters to youSection of the release

The drop-on-400 latch for the auto-mode classifier beta is keyed on a constant that is null, so the branch and its telemetry are unreachable.

What

The path that drops a classifier beta after an HTTP 400 followed by a successful bare retry is keyed on a beta constant that is null in both builds, so it never fires.

Details
  • The latch bails out early when the constant is null, and the constant is declared as null in 2.1.219 and 2.1.220 alike.
  • The newly-sent auto-mode-classifier beta therefore has no automatic drop-on-400 path in this build.
  • The telemetry it would emit, tengu_auto_mode_beta_latch and permission_auto_mode_classifier, is present but unreachable.
Evidence

tengu_auto_mode_beta_latch

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.220 →

Feedback