Antigravity CLI adds session controls

Listen to this article

Antigravity CLI 1.2.14 adds immediate messages and a Linux remote fallback. Google dates its release entry September 30.

The terminal application brings Antigravity’s agent capabilities into a command line workflow, including file editing, tools and conversation history. This update gives people supervising those sessions more control over when a correction reaches the agent.

Choose when a follow up reaches the agent

Queued Messages offers Send Immediately to interrupt the current turn. The default Queue option waits until that turn ends.

Google’s configuration guide explains that the settings panel saves selections to a JSON file. Users can reach it with either the config or settings slash command. Some launch flags take precedence over persistent settings for the current session.

That choice matters when an agent is already partway through a task. A correction to the wrong file or an outdated requirement may need attention immediately. A separate request can wait until the current work is finished. Keeping those intentions distinct gives the person supervising the session a clearer way to intervene.

For a task that needs to stop altogether, Google’s interaction guide still documents the Escape key as a way to cancel an active turn. It also supports composing longer instructions across multiple lines before submitting them.

Remote Linux sessions get a fallback

Without a systemd user service manager, the CLI starts its remote daemon as a background process. This fallback neither restarts after a crash nor launches at boot.

The Remote Control guide describes two existing approaches. An interactive connection lasts with its terminal session. A background daemon provides a separate remote instance. Both let users reach work on their own machine through a browser signed into the same Google account.

A container can therefore be a more practical place to run a remotely supervised session, but its lifecycle still needs attention. Anyone planning unattended work should check what happens when that process exits. The release’s explicit fallback warning is important when reading broader documentation about persistent services.

Scripts need a valid object schema

Invalid output schemas fail at startup with exit code 1. Text, missing files and schemas without an object root are rejected. Releases roll out gradually.

The headless execution guide explains how scripts can capture a completed JSON response or consume streaming events. Its structured output example uses an object schema. The same guide still lists primitive type names as accepted input, so the newer versioned release notes are the relevant guidance for this changed behavior.

Teams using the CLI in automation should check their schema inputs before upgrading, then run a small task through the normal success and error paths. ByteForward has not independently tested these changes.

Featured image is an original AI generated conceptual editorial illustration.