Evidence record / antigravity

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-13-antigravity-gemini-enterprise-gained-administrator-enabled-claude-5-5-while-its-linux-sandbox-descript

Gemini Enterprise gained administrator-enabled Claude 5.5, while its Linux sandbox description conflicts with the CLI sandbox page. The Enterprise page added Claude Opus 5.5 and Sonnet 5.5 as administrator opt-in, billed by token, with CLI identifiers claude-opus-5-5-<level> and claude-sonnet-5-5-<level>. Levels are low, medium (default), high and max; --effort needs agy 1.2.11 or later. The page advises CLI users to enable --sandbox=true and calls the Linux mechanism bubblewrap, while the CLI sandbox page says namespaces. The verifier found no real bwrap or nsjail string in the 1.3.4 Linux binary; this does not prove which runtime boundary is enforced.

Channel: docs-only; Enterprise account configuration and model service. Half: both. Date: 2026-10-09..2026-10-10 (documentation change).

Operator consequence: An Enterprise team can select Claude within the Google harness after administrator approval and with a separate token bill; it must configure that account before switching jobs. Pin a documented model identifier and thinking level and check agy models under the actual project. Do not choose a Linux isolation policy from the conflicting mechanism names: a vendor correction or a runtime probe of mounts, network and denied paths would settle the boundary.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-antigravity-gemini-enterprise-gained-administrator-enabled-claude-5-5-while-its-linux-sandbox-descript

Profile citations

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact