Repository navigation
Commit 3d3c4fe
feat(models): roll out Gemini 3.8 Flash across Antigravity, Google, and the sidecar (#3286)
* docs(devlog): Gemini 3.8 Flash rollout roadmap (260903_gemini_38_rollout wp0)
Diff-level roadmap for rolling Gemini 3.8 Flash across every surface that
currently names 3.6/3.7.
Two findings shape the plan, both first-hand rather than inherited from the
3.7 unit:
- Google documents 3.7 Flash as "remains fully supported", and a live CCA
fetchAvailableModels call returns 3.5, 3.6, 3.7 and 3.8 together. So this
is an ADDITIVE rollout with a default move, not the hard replacement the
3.6 to 3.7 migration performed.
- CCA publishes gemini-3.8-flash-{low,medium,high} and no -tiered row, so 3.8
is structurally 3.6-shaped: it belongs in ANTIGRAVITY_EFFORT_WIRE_MAP, not
in the single-wire thinkingLevel map 3.7 uses.
Three adversarial audit rounds (independent gpt-5.6-sol reviewer at high
effort) took this from FAIL to PASS. The two most valuable findings were
confirmed against the live backend: the Claude SDK identity paragraph 429s on
3.8 exactly as on 3.7, so that strip guard must widen before 3.8 becomes the
default; and static vs discovered effort resolution returned different request
bodies for the same input.
Docs only. No runtime change in this commit.
* feat(antigravity): expose Gemini 3.8 Flash with its suffix effort ladder
Google shipped Gemini 3.8 Flash on 2026-09-02 and CCA already returns it
ranked first in the Recommended sort, but discovery published it as three
uncollapsed rows with no effort ladder at all.
Additive, not a replacement. The 3.6 generation vanished from CCA the moment
3.7 shipped, which is why RETIRED_FLASH_TIERS exists. 3.8 did not do that:
Google documents 3.7 Flash as remaining fully supported, and a live
fetchAvailableModels call returns 3.8, 3.7 and 3.6 together. So 3.7 stays
picker-visible and every retirement mapping is left where it is.
3.8 tiers ride SUFFIX wire ids, unlike the single -tiered id 3.7 uses, so it
is registered through ANTIGRAVITY_EFFORT_WIRE_MAP. Two consequences, each
proven against the backend rather than assumed:
- The suffix is the sole tier carrier. CCA accepts a -low wire id paired with
a HIGH thinking level and returns 200, so a contradictory pair would run at
an unknowable tier. ANTIGRAVITY_SUFFIX_TIER_MODELS suppresses the redundant
level and makes static resolution byte-identical to the discovery path,
which never emitted one. That divergence also swallowed clamped efforts:
max/xhigh/ultra resolved differently before and after discovery ran.
- The Claude SDK identity paragraph 429s on 3.8 exactly as on 3.7. The strip
guard was an equality check on one model id; with 3.8 becoming the default
it would have returned RESOURCE_EXHAUSTED for every Claude-Agent-shaped
request while looking like a quota problem. Membership is now canonicalized
so raw suffix selectors from a partial ladder are covered too.
GEMINI_FLASH_WIRE_ID is renamed GEMINI_RETIRED_FLASH_TARGET_WIRE_ID: it holds
the 3.7 redirect target, and after 3.8 became current the old name pointed
readers at the wrong model.
Verification: bun run typecheck, plus focused
tests/google-antigravity-wire.test.ts, gemini-37-flash-migration.test.ts,
google-adapter.test.ts, provider-registry-parity.test.ts - 166 pass, 0 fail.
* feat(models): price and publish Gemini 3.8 Flash metadata
Adds the google/gemini-3.8-flash source record (regenerated, never hand-
edited) and the Antigravity + direct Google price rows.
The source record deliberately omits `cost`. Bundled generated metadata is
consulted before the expected-price overlay and returns status "verified", so
copying the adjacent 3.6 record - which does carry a cost block - would make
the Antigravity row unreachable and report CCA spend as a verified price.
Google publishes Developer API prices; it does not publish that Cloud Code
Assist charges them. The overlay is verified-derived for exactly that reason:
the number is proven, the claim that Antigravity bills it is inferred.
GEMINI_38_FLASH is its own constant despite matching 3.7 today, so a later
re-verification of one cannot silently move the other.
Nothing is retired here. Reconciliation refreshes capability records from the
registry, so an existing user picks up 3.8 on the next start, and a user who
deliberately chose 3.7 keeps it - Google still serves that model. The new
reconcile case asserts that preservation directly; the pre-existing 3.5 case
only exercised the opposite branch, where a retired default gets healed.
Verification: bun run typecheck, plus focused usage-cost, model-metadata-sync,
oauth-provider-reconcile and gemini-37-flash-migration - 137 pass, 0 fail.
* feat(models): carry Gemini 3.8 Flash to the remaining surfaces
Direct Google, the free-provider directory, the Gemini web-search sidecar
default, a preemptive Cursor seed, and the sidecar docs row.
The direct Google ladder omits `minimal` even though its 3.5/3.6/3.7
neighbours list it: Google documents `minimal` as a validation error for this
generation. defaultModel stays gemini-3.5-flash - adding a model elsewhere
must not silently move an existing API-key user's default.
The free-directory Gemini row gets a row-specific lastVerified rather than a
bumped shared constant, which would have stamped a 2026-09-03 check onto every
other provider row that nobody re-checked.
The Cursor seed follows the documented glm-5.3 precedent: Cursor has not
announced 3.8, and the static catalog is intersected with the live roster, so
the entry stays invisible until Cursor lists it.
Left alone deliberately: GEMINI_DIRECT_WIRE_RENAMES gains no 3.8 entry,
because no source anywhere proves a gemini-3.8-flash-tiered id exists, and the
providers.md rename example keeps naming 3.7 for the same reason.
Verification: bun run typecheck, plus 15 focused test files - 753 pass, 1 fail.
The failure is pre-existing and unrelated: 'Antigravity live model discovery
uses the CCA agent list' leaks a credential across files and fails on the
clean tree too, while passing when that file runs alone.
* fix(antigravity): strip the rejected paragraph by routed generation, not selector
The maintainer review found a hole three audit rounds missed, and a live probe
confirmed it: a saved gemini-3.6-flash selection does not call 3.6. Rule 0
redirects it onto gemini-3.7-flash-tiered, which rejects the Claude Agent SDK
identity paragraph with a 429 that reads as quota exhaustion.
The guard keyed on the selector through canonicalAntigravityUsageModel, which
covers the collapsed base and the raw suffix rows. It cannot cover retired ids,
because those deliberately keep their OWN identity for usage accounting - that
is the rule protecting historical spend from being relabelled. Two individually
correct mechanisms combined into a gap, and every saved 3.6/3.5 config would
have kept 429ing after this rollout.
Judging the routed wire id closes it, and naming a wire spelling once now covers
every selector that can reach that generation rather than requiring the set to
enumerate selectors that redirect into it. The old test asserting a 3.6
selection KEEPS the paragraph was asserting the bug; it is replaced by one
proving the strip, plus a real control on claude-sonnet-4-6 - a model with no
recorded rejection, where the paragraph is literally true.
Also folds the review's second point: the direct google 3.7 row no longer
advertises `minimal`. Google documents it as a validation error for that
generation, which is the same evidence 3.8 relies on, and the line was already
being edited here. 3.5 and 3.6 keep theirs - their pages still list it.
Verification: bun run typecheck, plus 12 focused test files - 681 pass, 0 fail.
---------
Co-authored-by: jun <[email protected]>1 parent fd324dc commit 3d3c4fe
33 files changed
Lines changed: 1658 additions & 42 deletions
File tree
- devlog/_plan/260903_gemini_38_rollout
- docs-site/src/content/docs/guides
- scripts
- src
- adapters
- cursor
- generated
- providers
- usage
- web-search
- tests
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
| 45 | + | |
| 46 | + | |
| 47 | + | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
| 53 | + | |
| 54 | + | |
| 55 | + | |
| 56 | + | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
| 61 | + | |
| 62 | + | |
| 63 | + | |
| 64 | + | |
| 65 | + | |
| 66 | + | |
| 67 | + | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
| 45 | + | |
| 46 | + | |
| 47 | + | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
| 53 | + | |
| 54 | + | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
| 45 | + | |
| 46 | + | |
| 47 | + | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
| 53 | + | |
| 54 | + | |
| 55 | + | |
| 56 | + | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
| 61 | + | |
| 62 | + | |
0 commit comments