Antigravity CLI 1.2.0 Adds Remote Control OS Service Support
Antigravity CLI 1.2.0 introduces background daemon controls via OS service managers, improved half-page scrolling, and bug fixes for MCP and filters.
Antigravity CLI 1.2.0 introduces background daemon controls and OS service registration.
- Antigravity CLI 1.2.0 introduces remote-control subcommands to register the tool as an OS background service that persists across logouts and reboots.
- New flag options allow users to define custom machine labels or restrict the daemon's scope to an active user session.
- The release refines terminal navigation, introduces distinct error messages for content filters, and resolves MCP plugin startup issues.
Background Daemon Integration with OS Service Managers
The release of Antigravity CLI version 1.2.0 adds dedicated subcommands designed to keep the CLI daemon running persistently on host systems. By registering directly with the host operating system's native service manager, the command-line client can maintain active remote connectivity even if a user logs out or the system reboots.
According to developer Shengzhe on X, the utility now exposes three primary subcommands for managing this persistent connection:
remote-control start: Registers and starts the background service.remote-control status: Queries the operational state of the background daemon.remote-control stop: Ceases daemon execution and deregisters the service.
The update includes two configuration flags for starting the service. Using the --name <label> flag, operators can assign a recognizable name to the machine within the Remote Control instance directory. Alternatively, passing the --session argument limits the daemon service lifecycle solely to the active login session rather than preserving persistence across complete system reboots.
Terminal UI and Scrolling Enhancements
In addition to daemon process management, Antigravity CLI 1.2.0 includes navigation adjustments across terminal views. Half-page scrolling behavior has been reworked for all scrollable views, including alternate screen mode (altscreen), diff viewers, and read-only detail panels.
In previous releases, key commands such as Ctrl+D could unintentionally trigger an exit prompt when an operator attempted to scroll through read-only panels. Version 1.2.0 corrects this behavior to ensure smooth document navigation. Furthermore, the release assigns Shift+Up and Shift+Down as default keybindings for half-page scrolling (bound internally to navigation.half_page_up and navigation.half_page_down), which users can customize in their key configurations.
Model Response Handling and Content Safety
Version 1.2.0 improves how the CLI surfaces model errors related to moderation. Previously, when inputs or generated completions were blocked by content safety filters, the CLI often exhibited ambiguous behavior. The client would either fail with a generic "no candidate found" error, exit the turn silently without returning output, or continually re-try sending the rejected prompt.
The updated release handles blocked responses explicitly. When an input or output violates content policies, the application stops retrying and reports an explicit content-filter stop reason in the terminal output, clarifying why the process was interrupted.
MCP Plugin Stability and Latency Reductions
The release notes also detail a number of architectural bug fixes regarding Model Context Protocol (MCP) integrations and file monitoring:
- Plugin MCP Initialization: MCP servers bundled within globally installed plugins previously failed to initialize on CLI startup or failed to refresh running states when plugins were toggled. Version 1.2.0 resolves these lifecycle issues.
- Schema Validation: Third-party MCP server tools that omit the
additionalPropertiesfield in their input schemas no longer fail schema validation checks. - Filesystem Overhead: The CLI eliminated unnecessary filesystem customization discovery walks that had been executing prior to every user message, even when no slash command was provided. Removing these redundant checks reduces latency before agent responses begin.
- Scratch Directory Watchers: Temporary files written to the agent's
scratch/directory no longer trigger recursive filesystem watchers, preventing unnecessary noise from cluttering artifact review panels and checkpoints.
System Compatibility and Session Fixes
Platform-specific issues on macOS were also addressed in version 1.2.0. The team resolved an issue where the macOS remote-control background service prematurely stopped after launching under the system service manager. In addition, the start and stop subcommands now reliably clean up legacy installer-script background services.
Other general maintenance fixes include removing extraneous ERROR: logging before google.Init prefixes from cli.log output, resolving an issue where Remote Control settings appeared unavailable when billing ran through paid Google Cloud projects, and fixing an "unknown step type" error that prevented users from resuming older conversation threads.
Enjoyed this?
Get more posts like this delivered to your inbox.
