DSCODE 0.7.45

DSCODE 0.7.45

The Antigravity provider supports Gemini 4 Argon, selecting its reasoning with the thinking level the model requires.

Gemini 4 Argon through Antigravity

Google released Gemini 4 Argon on 2026-10-13 and made it available in Antigravity for Google AI Ultra and eligible Gemini Enterprise accounts. Two things kept it out of DSCODE. The catalog is gated by client version: an Ultra account's fetchAvailableModels returned no Argon to the antigravity/cli/1.2.4 identity DSCODE sent, and returned gemini-4-argon-low, -medium and -high to antigravity/cli/1.2.9. And the provider sent every Gemini route a thinkingBudget, which Google's model card says Argon rejects with HTTP 400.

DSCODE now identifies as Antigravity CLI 1.2.9, reporting the host's real operating system and architecture, for discovery and generation alike. Gemini 4 and later routes send thinkingConfig: { includeThoughts: true, thinkingLevel } with LOW, MEDIUM or HIGH from /effort; Gemini 3.x routes keep their existing budgets unchanged. Argon is in the fallback catalog exactly as the service listed it: per-level runtime models with enum labels MODEL_PLACEHOLDER_M419, M418 and M417, a 1,048,576-token context, 65,536 output tokens and medium as the default level, matching Google's default. Discovered per-level variants are grouped under Gemini 4 Argon and offer only the advertised levels; as with other per-level families, an effort change switches runtime model and earlier tool rounds replay as historical text. Should the service instead list one unsuffixed Gemini 4 runtime model, it serves all three levels and keeps signed history across effort changes. Other Gemini 4 identifiers, such as the allowlisted Cyber Permissive variant, appear as separate models with the same level handling. Service-reported token limits still take precedence.

Behaviour stops there. The newer identity reuses the 1.2.4 build number, which the service accepted; only the darwin/arm64 form was checked against the live catalog. Argon is not the default model, and DSCODE neither grants nor checks entitlement; an account without access receives Google's error. Argon's long-decode output beyond 65,536 tokens, explicit context caching and the context-size options seen in the Antigravity application are not exposed. Argon ignores custom sampling temperature.

Verification

node --test tests/antigravity.test.mjs passed all 28 cases, including a new case covering the fallback entry, all three levels without thinkingBudget, the live per-level catalog shape, single-runtime discovery, service token limits, the client identity and unchanged Gemini 3.8 budgets. npm run test:unit passed all 1,237 unit/component cases; node scripts/check-docs.mjs reported clean, npm run lint passed and make version-check confirmed v0.7.45 matches the manifest. The full npm run check gate, native integration and release CI were not run inside this session. A read-only diagnostic against a Google AI Ultra account on 2026-10-13 confirmed the version gate and the three Argon routes above. Live Argon generation was not yet exercised, and real Google discovery and generation have no automated case.