Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Antigravity CLI 1.5.3: subagent models, sandbox fix

Written November 9, 2026

Antigravity CLI 1.5.3 (Nov 7) shows the subagent model in rows and /agents, adds PLUGIN_ROOT/PLUGIN_DATA, and fixes a sandbox escape.

What changed

Antigravity CLI 1.5.3, released November 7, 2026, is a small release with one security fix that matters more than the features. The release notes list it plainly, and the rest of the release is visibility and plugin-hook work.

The sandbox fix. A command run in the terminal sandbox could change environment state that persistent terminal commands run outside the sandbox later loaded. That is fixed in 1.5.3, and persistent terminal IDs are hardened against path traversal. The fix is in the release; it is not a live flaw to work around, and it is not a reason to stop using the sandbox — it is a reason to update.

Subagent models are visible at a glance. Each subagent's model now appears next to its name in the subagent rows above the prompt and in /agents, hidden on narrow terminals, with the full model and effort in a subagent's detail view, and a model field on each subagents entry in the status line JSON. /agents now shows a single Tip: Press enter on a subagent to view details. line instead of repeating [view details] on every row. If you run subagents on different models, you can now see which one is doing what without opening each one.

Plugin hooks get their own paths. The PLUGIN_ROOT and PLUGIN_DATA environment variables are now set on hook commands that come from a plugin, pointing to the plugin's folder and its persistent data folder, so plugin hooks can use files bundled with the plugin and keep state between runs. agy plugin validate no longer warns that these variables are not set for hooks.

Other fixes worth knowing

Plugin management for symlinked installs is fixed: agy plugin uninstall, enable, and disable — and uninstalling from /plugin — no longer fail for plugins installed as symbolic links, such as plugins installed from Antigravity, or for plugin names containing spaces or symbols such as c++-tools. agy plugin list shows symlinked plugins again.

Two failure modes are fixed that used to look like the model was at fault. Agent turns no longer fail with an http2: timeout awaiting response headers error when the model takes more than 60 seconds to start responding; they are retried. And every model request no longer fails with a 404 when an enterprise model gateway URL ends in /v1beta — a trailing /v1beta in the gateway URL is now ignored, even though the model list loaded fine.

File handling improves for non-UTF-8 text, mostly on Windows: reading a UTF-16 or legacy code-page file now returns its text instead of treating it as binary, edits keep a file's UTF-8 byte order mark or UTF-16 encoding, and PowerShell scripts with non-ASCII text are written with a UTF-8 byte order mark so Windows PowerShell 5.1 reads them correctly. In --remote-agent sessions, files larger than the remote read limit are no longer silently cut off; they load in full up to 20 MiB and report an error above that instead of showing partial content. Hooks also now receive the name of the model actually in use when the session uses a custom model, instead of a placeholder or an empty name.

For context, 1.5.2 (November 6) added plugin skills in remote-agent sessions and stopped --dangerously-skip-permissions from auto-approving protected commands in headless runs. That change is covered on its own page; 1.5.3 does not repeat it.

Verdict

Update for the sandbox fix alone — a sandboxed command reaching state outside the sandbox is the one line that matters. The subagent model display is the change you will notice daily, and the plugin-hook paths are the change plugin authors will build on.

Steps

  1. Update to 1.5.3. Check with agy --version. If you run the sandbox, the fix only applies once you are on 1.5.3.
  2. Look at /agents. Each subagent row now shows its model. If a subagent is running a model you did not expect, that is now visible before the turn finishes, not after.
  3. Use the hook paths if you write plugins. A hook can read bundled files through PLUGIN_ROOT and keep state between runs through PLUGIN_DATA, instead of hard-coding paths.
  4. Retry the symlinked-plugin operations that failed. Uninstall, enable, and disable now work for symlinked plugins and for names with spaces or symbols.

What can go wrong

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Antigravity 1.5.2 tightens headless permissions · Vet an Antigravity plugin before the one-click install: what the bundle can do, and what Google does not check · Claude Code hardens its sandbox ahead of Nov 10