Skip to content

Google Antigravity 1.5.3

Released · Google

Security fixChanges skills and plugins

What the release notes say

  • Added each subagent's model 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.
  • Added the PLUGIN_ROOT and PLUGIN_DATA environment variables to 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.
  • Changed the error shown when Vertex AI reports that the selected model does not exist or that your Google Cloud project cannot use it, which now reads The requested model was not found, or your project does not have access to it. instead of the raw API error.
  • Improved the plugin sign-in screen in /plugin, which now indents the sign-in link like the surrounding text and sets it apart with a blank line, no longer underlines trailing blank space in wrapped links, and uses the plugin's display name from plugin.json, such as Canva instead of canva.
  • Improved agy plugin validate so the category field in plugin.json is accepted instead of reported as an unknown field, with a warning only when it is not a non-empty string.
  • Improved auto-generated conversation titles, which now keep abbreviations and acronyms from your request as written instead of guessing what they stand for.
  • Fixed agy plugin uninstall, agy plugin enable, agy plugin disable, and uninstalling from /plugin failing for plugins installed as symbolic links, such as plugins installed from Antigravity, or for plugins whose names contain spaces or symbols such as c++-tools, and agy plugin list shows symlinked plugins again.
  • Fixed agent turns failing with http2: timeout awaiting response headers when the model took more than 60 seconds to start responding, which are now retried.
  • Fixed every model request failing with a 404 error when an enterprise model gateway URL ended in /v1beta, even though the model list loaded; a trailing /v1beta in the gateway URL is now ignored.
  • Fixed the agent's requests to sign in to a plugin being dropped from the conversation, so when a plugin needs a sign-in the CLI now shows a line such as ⚠ The <plugin> plugin needs you to sign in. Open /plugin to sign in.
  • Fixed the agent's file tools mishandling text that is not UTF-8, 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 (.ps1, .psm1, .psd1) with non-ASCII text are written with a UTF-8 byte order mark so Windows PowerShell 5.1 reads them correctly.
  • Fixed a message sent during a turn with the Send Immediately queued-messages mode briefly disappearing from the conversation and reappearing when it arrived just as the turn ended.
  • Fixed hooks receiving a placeholder or empty model name when the session uses a custom model, so hooks now get the name of the model actually in use.
  • Fixed files larger than the remote read limit being silently cut off in --remote-agent sessions, which now load in full up to 20 MiB and report an error above that instead of showing partial content.
  • Fixed agy acp sessions exiting before the agent backend finished shutting down when the client closed the connection, which could interrupt saving conversation data.
  • Fixed a security issue where a command run in the terminal sandbox could change environment state later loaded by persistent terminal commands run outside the sandbox, and hardened persistent terminal IDs against path traversal.
  • Fixed garbled characters in tool-call summaries when the CLI shortens file paths that contain non-ASCII characters.
  • Fixed paths that share a prefix with your home directory, such as /home/alice when your home is /home/al, showing with a mangled ~ prefix in the /context file list and the keybindings reset hint.