Playbooks · Coding tasks
Antigravity CLI 1.5.8: Hydrogen and Carbon arrive
Written November 15, 2026
Antigravity CLI 1.5.8 landed November 13: Gemini 4 Hydrogen and Carbon in the picker, click-to-expand in full screen, and security fixes.
Version 1.5.8, dated November 13, 2026 in Google's Antigravity changelog, is a model and polish release on top of 1.5.7's default change. It adds two Gemini 4 models to the picker, makes full screen output clickable, reports context window usage to ACP editors, tightens gateway controls, and ships 22 fixes, including security fixes closing bypasses in the sandbox and Windows allow rules. Nothing here changes the Auto default from 1.5.7.
Two new models in the picker
The 1.5.8 changelog entry adds Gemini 4 Hydrogen in four effort levels — Low, Medium, High, and XHigh — and Gemini 4 Carbon in three: Low, Medium, and High. How you sign in decides which ones you see. With a GEMINI_API_KEY, both models appear in /model and --model. With Application Default Credentials (AGY_ADC_AUTH), Hydrogen appears in the same four levels. Through an enterprise model gateway, Hydrogen is supported as well.
Click to expand in full screen
Full screen (altscreen) rendering gains click-to-expand. Clicking a tool group, a thought, a prompt's attached images, or multi-line command output now expands or collapses just that item. Until now the keyboard route was Ctrl+O; the mouse now does the same job one item at a time, which makes long tool output easier to skim. The default Rendering Mode is unchanged, so this only affects sessions already using full screen mode.
ACP context, gateway controls, faster remote starts
agy acp sessions now send context window usage updates, so editors such as JetBrains AI Chat can show how much of the context window a conversation is using. The value is sent at session start or reload, after each model call, and after a model or thinking level change.
Two admin settings arrive. gateway.routeWebFetch stops web page reads from going around an enterprise model gateway by disabling URL reading unless a proxy.address is configured, and featureControls.remoteControlEnabled lets an organization turn off Remote Control. With a gateway, web pages are now fetched directly from your machine, through proxy.address when set, instead of through Google's fetch service.
The first message of a --remote-agent conversation no longer waits for its remote environment to start or resume. The CLI prepares the environment as soon as the session knows its remote project, again after /new or switching projects, and starts a resumed conversation's idle environment in the background on --continue or --conversation=<id>.
Security fixes that close real bypasses
The terminal sandbox's network proxy could be bypassed with percent-encoded slashes (%2F), backslashes, or .. segments in a URL path, getting around rules limiting where credentials are sent or which Git and API paths are allowed. Every way of reading the path is now checked, and the cleaned-up path is the one sent upstream.
On Windows, always-allow rules could be bypassed when the shell was cmd, powershell.exe, pwsh.exe, or a full path to one of them. PowerShell and Command Prompt commands now always need an exact match, because their quoting rules differ from POSIX shells: a command with hidden extra statements, such as git status '&& del secret.txt', could otherwise be approved by a rule meant only for git status.
Two enforcement gaps close alongside. Permission rules for MCP tools were ignored for tools loaded up front and for the /browser subagent's Chrome DevTools tools; those tools now ask or are blocked according to your rules. And /plugin, agy plugin, and headless -p runs now honour an organization's plugin controls: when an administrator disables plugins or the marketplace, installs fail, while listing, disabling, and uninstalling still work.
More fixes worth knowing
- Windows hooks. Hook commands containing double quotes no longer fail and get silently skipped, which could leave a blocking hook unenforced.
- BOM files. Files saved with a UTF-8 byte order mark, as Windows PowerShell and Notepad produce, are no longer silently ignored:
settings.json,hooks.json, and custom agent and rule files now load. - Shell hangs.
!shell commands that wrote a lot to stderr no longer hang; they finish and show stdout and stderr in order. - Stale connections. Model requests retry on a fresh connection when a connection goes stale, and slow responses no longer time out after 60 seconds when admin settings configure a proxy or custom CA.
- MCP sign-ins. Remote MCP servers using OAuth without a client secret no longer sign you out at token expiry; refreshes now send the client ID the server requires.
- Side questions.
/btwand/helpno longer fail with a stream timeout after five minutes; they run until they finish or you press Esc.
Limits
- Model availability depends on the sign-in path. Carbon is listed for the
GEMINI_API_KEYroute; the Application Default Credentials route lists Hydrogen. - Click-to-expand is a full screen feature. The default Rendering Mode is unchanged.
- Version 1.5.8 does not revisit the 1.5.7 default. Sessions with no saved mode still start in Auto where Auto is available.
Related playbooks
- Antigravity CLI 1.5.3: subagent models, sandbox fix
- Antigravity CLI 1.5.4: ACP Auto mode
- Antigravity CLI 1.5.5: swarms in preview
- Antigravity CLI 1.5.7: Auto becomes the default
Sources
- Changelog — Google Antigravity Docs — the Antigravity CLI v1.5.8 entry dated November 13, 2026: Hydrogen and Carbon, click-to-expand, ACP updates, admin settings, and all 22 fixes.
Back to: Coding playbooks hub · Also: Antigravity CLI 1.5.7: Auto becomes the default · Antigravity CLI 1.5.5: swarms in preview · Also: Antigravity removes free Claude models Nov 18