Google Antigravity CLI 1.2.14

Changelog: Queued messages configuration, systemd-free remote-control, faster conversation loading, and cursor and file handling fixes

Adds a configurable Queued Messages option in /config, supports running remote-control on Linux systems without systemd, accelerates resuming long conversation transcripts, factors attachments into automatic thread titles, hardens --json-schema validation, and fixes unicode cursor drift, special file hangs, and corrupted transcript step recovery.

Improvements(6)

• Added the Queued Messages option to /config: keep the default Queue to hold follow-up messages until the current turn ends, or choose Send Immediately to interrupt the agent with them; it can also be set with "queuedMessages": "send-immediately" in settings.json, which was previously ignored.
• Improved remote-control start on Linux machines without a systemd user service manager, such as most containers: instead of failing, it now starts the daemon as a background process and warns that it will not restart after a crash or start at boot; remote-control status shows its PID and remote-control stop shuts it down.
• Improved loading long conversations: resuming a conversation with thousands of steps is noticeably faster because the CLI no longer scans every step up front.
• Improved automatically generated conversation titles to take images and files attached to your first message into account, so screenshot- or file-driven requests get specific titles and messages with only attachments get a title too.
• Improved the sign-in error shown to accounts blocked for a Terms of Service violation, which now includes a link to submit an appeal.
• Changed --json-schema to reject plain text, bare type names such as string, and missing schema files instead of silently treating them as a string schema; these inputs, and any schema whose root is not "type": "object", now fail at startup with an error and exit code 1.

Fixes(3)

• Fixed the prompt cursor drifting away from the end of the text after emoji such as ⚠️ or 👩‍💻, or scripts with combining marks such as Devanagari and Thai, especially inside tmux, and fixed prompt wrapping splitting such characters across two lines.
• Fixed the agent hanging when it tried to view a pipe, socket, or device file, and a conversation getting stuck with INVALID_ARGUMENT errors after the agent viewed a truncated MP4, MOV, or M4A recording; both are now rejected up front with a clear message.
• Fixed resuming a conversation whose history had a missing step, for example after a crash or an interrupted write, hiding the most recent steps and letting new messages overwrite them.

<h3 class="