Version 2.1.220

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.

• 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.

tengu_auto_mode_beta_latch

The permission classifier used by auto mode attaches a beta descriptor to its API requests, where the previous build sent none. Both classifier stages now carry it.

• Registers WA("auto_mode_classifier", "auto-mode-classifier-2026-07-16") and adds it to the frozen known-betas list, so it is also reachable through the header lookup map.
• In 2.1.219 the classifier's request builder was a stub that unconditionally returned an empty extraBetas array; it now returns this beta.
• Gated on provider being "firstParty" and the base URL being api.anthropic.com. Suppressed by CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETAS or hipaa mode, in which case the list stays empty.

auto-mode-classifier-2026-07-16

A new predicate detects sessions where Claude Code has no entitlement data at all, and the Opus lineup walk used for refusal fallback filters Opus 5 out in that state.

• isEntitlementOverlayUnavailable returns true when the provider is first-party, an OAuth token is stored, the profile scope is absent, no Anthropic API key is set, and the cached model-access list is empty.
• A helper combines that predicate with a canonical-name check against "claude-opus-5"; the candidate scan becomes .find((n) => N1e(lo(n)) && !u2c(n) && r(n)), and a sibling helper substitutes "claude-opus-4-8" in its place.
• No remote flag is involved. It is driven purely by runtime auth and cache state, so a first-party OAuth session with an empty entitlement cache will not auto-pick Opus 5 as a fallback target.

isEntitlementOverlayUnavailable

The refusal and model-fallback picker gained a normalization step that rewrites any model whose canonical id is "claude-opus-5" to "claude-opus-4-8" before it is used as a fallback target. A refusal that used to fall back to Claude Opus 5 on affected setups now falls back to Claude Opus 4.8.

• The first-party branch went from if (!rm()) return s2c("claude-opus-4-8"); let r = EE(); in 2.1.219 to if (!rm()) return l2c(c2c); let r = d2c(EE());, where c2c is the constant "claude-opus-4-8" and d2c performs the mapping.
• The next-fallback-model resolver applies the same mapping: l2c(rm() ? r.id : s2c(r.id), "exact") becomes f2c(rm() ? d2c(r.id) : l2c(r.id), "exact").
• The non-exact candidate scan skips the same models: Gji().find((n) => N1e(lo(n)) && !u2c(n) && r(n)) versus the old Uji().find((n) => N1e(lo(n)) && r(n)).
• The gate is a runtime condition, not a remote flag. The substitution only applies when the helper body Hn() === "firstParty" && zA() && !bH() && eZ() === null && ZJt().length === 0 holds, the same predicate the build reports elsewhere as entitlement_blind. Otherwise behaviour is unchanged.

claude-opus-4-8

The build-time constant block embedded throughout the bundle carries a new version, timestamp and commit hash, rethreaded through roughly 55 call sites.

• VERSION 2.1.219 -> 2.1.220, with a new BUILD_TIME of 2026-07-24T22:17:45Z and a new GIT_SHA.
• Surfaces in the /status version line, the bug-report template's Environment Info, the claude-code/<version> user agent, update-check output (Current version: ), telemetry and analytics payloads, and the npm install/view commands targeting @anthropic-ai/claude-code.
• The BUILD_REF_NAME suffix helper still returns the empty string, and the JOSE compactDecrypt calls in the OIDC JWE path were re-minified with no behaviour change.

VERSION: "2.1.220", BUILD_TIME: "2026-07-24T22:17:45Z"

The warn-level log emitted when the auto-mode classifier's beta is rejected changes from "the bare retry succeeded" to "the retry without it succeeded".

• Log text only, the surrounding logic is unchanged.
• The branch is currently unreachable because the latch it belongs to is keyed on a null constant.

beta rejected (HTTP 400) and the retry without it succeeded

Several unrelated areas were reflowed or had their module-init closures renamed, with no semantic difference found in any of them.

• Method-chain reflows in JWT verification, PEM fingerprinting via createHash("sha1") and createHash("sha256"), MCP server-config mapping, the SDK set_model control request, QR-code rendering and several string-splitting sites.
• Renamed module-init closures for the test and typecheck command regexes and for the git worktree path constants /worktrees/ and config.worktree.lock.

failed to validate JWT signature

The inlined build constants appearing in around 40 user-visible and log strings were re-stamped, with no surrounding logic touched.

• VERSION 2.1.219 -> 2.1.220, BUILD_TIME 2026-07-24T03:24:19Z -> 2026-07-24T22:17:45Z, GIT_SHA 7006c4c3acac98e554d3997baeda6a7fa4d1ff7c -> 4073f59596e272f39393db4f96abc5f4b10eff21.
• Affected strings include version output, claude update messages, user agents, doctor output and daemon logs.

GIT_SHA: "4073f59596e272f39393db4f96abc5f4b10eff21"

A large group of apparently new and removed code is pure bundler renaming, with prompt wording unchanged from 2.1.219.

• Covers the code-review phase prompts including "## Phase 2 \u2014 Verify (1-vote, 3-state)", "## Phase 3 \u2014 Sweep for gaps" and the Artifact publishing block.
• Also covers the /simplify 4-agent and single-pass prompts, the "# Saving skills" system prompt variants, the background-session shipping policy text, the workflow status strings and the credential file paths.
• Only the surrounding minified identifiers and the interpolated tool and skill symbols differ. No user-visible behaviour change.

## Phase 3 \u2014 Sweep for gaps