Editors want to drive your agent, scripts want predictable exit codes, and admins want the skip-permissions flag to respect their rules. This week’s releases touch all three. The CLI can now act as an ACP server for your editor, remote-agent sessions get more complete, and the permission and timeout behavior changes in ways that can affect existing setups.
Week 45 (November 4-7, 2026) brought versions 1.5.0 to 1.5.3: four releases and 60 changelog entries. Below are the changes that matter for daily work, followed by the smaller fixes and a short list of things to check.
Use agy as the agent inside your editor
What it is. agy acp runs the CLI as an Agent Client Protocol (ACP) server over stdio. An editor that speaks ACP can start it and use it as its agent. The command appears in agy --help as of 1.5.0.
What the editor can do. Prompts can carry images and embedded file context. You can steer a running turn by sending another prompt instead of waiting for it to finish. Sessions have three modes: default, accept-edits and plan. Each session keeps its own model and thinking level, so two sessions in the same editor do not share settings.
Resuming sessions. session/resume restores a session without replaying its history. For long conversations this means the editor gets the session back without receiving every earlier message again.
Signing in without a browser. agy acp --login handles Google sign-in from a terminal. It is meant for editors connected over SSH or on machines with no browser, which was the awkward case for any server-style mode.
Models. In 1.5.1, agy acp started offering every model available to your account to every ACP client. Before that, only a fixed list of editors saw models other than Gemini. If your editor was not on that list, check its model picker again.
What to check. The changelog describes the protocol features, not per-editor setup. Whether your editor exposes the three session modes or the steering behavior depends on its ACP client, so test those first.
Changes for everyday work
Remote agents from the terminal. --remote-agent runs the session’s conversations on remote agents instead of your machine. --project selects a remote project by ID or name. Without it, conversations open in your default remote project. In these sessions @-mention completion searches the remote agent’s files. Artifacts that cannot be shown in the terminal get an Open in browser link. The header shows remote workspace instead of your local directory, and the / menu no longer offers skills from your local machine. The Remote tab in /config shows the conversation’s own permission preset when it has one.
Cloud plugin skills in remote sessions. As of 1.5.2, skills from the cloud plugins you connected with /plugin appear in --remote-agent sessions. You can find them in the / menu, type them at the start of a message, or list them with /skills, where they are grouped by plugin under Remote agent skills. /skills reload lists them again.
Local projects. In a local session, /projects now lists your projects with the current one marked. You can create a project from a name and a set of folders, given as absolute, ~ or workspace-relative paths. You can also rename a project or change its folders. Switching to a project adds its folders to the workspace and starts a new conversation, so switching is not a free context hop.
Sign-in for partner plugin MCP servers. Installing a partner plugin from /plugin now shows a Connect <plugin> screen for each of its MCP servers, which opens the sign-in page. Esc skips it. In the Installed tab, a plugin that still needs sign-in carries a ⚠ needs sign-in marker and a Sign-in: row. Partner plugins also display a third-party developer tools notice at the end of the Discover list, in the plugin details, and after agy plugin install or /plugin install.
Skip-permissions is less absolute. Since 1.5.2, --dangerously-skip-permissions no longer auto-approves commands on the built-in list of protected commands. Those go through the usual checks, while every other command still runs without asking. If you use the flag in scripts, expect new prompts or denials for that subset.
Enterprise review wins over auto-approval. When your Gemini Enterprise administrator requires review of terminal commands or file access outside the workspace, --dangerously-skip-permissions and plugin agents set to auto-allow no longer approve them. Headless runs deny such requests instead.
A narrower outside-workspace prompt. The prompt for a file outside the workspace now reads Allow access to this file?. You can always allow or deny that one path, either for the conversation or in settings.json. Previously the choice turned on access to everything outside the workspace, so the new scope is much smaller.
Headless runs wait for background tasks. Without --print-timeout, agy -p now waits for background tasks to finish. It used to stop them after a hidden 30-minute limit and exit with success. When --print-timeout does cut a turn short, the run exits with code 3, prints an AGY_ERROR line naming the terminated tasks, and writes a [agy] print timeout after ... line to stderr. A CI job that relied on the old silent success after 30 minutes will now behave differently, so check how your wrapper handles exit code 3.
Technical notes
Subagents and side questions.
- Subagent model. The rows above the prompt and
/agentsnow show the model next to each subagent name. The status line JSON gets amodelfield too (1.5.3). /btwwith tools. Side questions can call tools, shown live in the card with aCalled N toolssummary. Calls that need permission are denied (1.5.0).
Plugins and hooks.
- Hook environment. Hook commands that come from a plugin get
PLUGIN_ROOTandPLUGIN_DATA. They point to the plugin’s folder and its persistent data folder, so a hook can use bundled files and keep state between runs.agy plugin validateno longer warns that these variables are unset for hooks (1.5.3). - Model name in hooks. Hooks now receive the actual model name when a custom model is in use (1.5.3).
sidecar.jsontemplates. They get a built-in${HOME}variable forworkspaceUrisandaccessGrants(1.5.0).- Sign-in reminder. The CLI shows
⚠ The <plugin> plugin needs you to sign in. Open /plugin to sign in.when a plugin needs sign-in (1.5.3).
Permissions and modes. Auto mode asks less often about safe commands that run outside the sandbox, such as package installs and restorable file removals (1.5.0).
Files and platforms.
- Non-UTF-8 text. File tools can read UTF-16 and legacy code-page files. BOM and UTF-16 encoding are preserved on write, and PowerShell scripts get a UTF-8 BOM (1.5.3).
- Windows. Agent commands run with Python in UTF-8 mode and UTF-8 PowerShell output, and CRLF file edits no longer fail (1.5.1).
- macOS. Option-key shortcuts such as
alt+mwork out of the box. SetAGY_CLI_MAC_OPTION_AS_ALT=0to revert (1.5.2).
Remote sessions. Files up to 20 MiB load in full (1.5.3). PDFs, binaries and files over 8 MB are uploaded to remote projects (1.5.2).
Speed and background requests. The agent moves on within about 1 second after a command exits while a background process holds output open, down from 5 seconds (1.5.1). agy -p no longer makes a background request to generate a conversation title (1.5.2).
What to take away
Terminal user.
- Try
/projectsto group folders you often open together. - If you work on a Mac with Option-key shortcuts, check that
alt+mand similar combinations now behave as expected. SetAGY_CLI_MAC_OPTION_AS_ALT=0if you preferred the old behavior. - Expect more prompts when you use
--dangerously-skip-permissionswith commands on the protected list.
User of parallel sessions.
- Point an ACP-capable editor at
agy acpand see whether per-session model and thinking level suit your split of work. - Try
--remote-agentwith--projectfor sessions that should run away from your machine, then look at/skillsfor theRemote agent skillsgroup. - Use the model shown next to subagents in
/agentsto confirm what each one runs on.
Admin of integrations and company deployments.
- Review scripts that call
agy -p. Runs without--print-timeoutnow wait for background tasks, and a--print-timeoutcut-off exits with code3. - Check how automation that uses
--dangerously-skip-permissionsor auto-allow plugin agents behaves under your Gemini Enterprise review settings. Headless runs now deny what requires review. - Walk through a partner plugin install to see the
Connect <plugin>sign-in screens and the third-party developer tools notice. If your plugin hooks need files or state, look atPLUGIN_ROOTandPLUGIN_DATA.
Sources: Antigravity CLI changelog, versions 1.5.0 to 1.5.3 (November 4-7, 2026), and the Antigravity CLI documentation. Features and behavior may change in later releases, so check the current documentation before you rely on details here.
