Skip to main content
Google Antigravity and Gemini CLI work with Ando in three ways:

Use Ando from Antigravity or Gemini CLI

Read and send in Ando as yourself while you work in Antigravity 2.0, Antigravity IDE, Antigravity CLI (agy), or Gemini CLI. It acts only during your session. The Ando plugin for Antigravity and Gemini CLI connects to Ando’s hosted MCP server (https://mcp.ando.so/mcp) and bundles Ando’s 17 workflow skills.
Install the plugin from the terminal with agy, or add the repository in Antigravity’s plugin settings:
When you first call an Ando tool, Antigravity opens Ando’s sign-in and approval screen in your browser. Choose your workspace and select Connect as me, then verify the connection.

Or add Ando MCP directly

If you prefer a plain MCP configuration without the bundled skills:
Add Ando to ~/.gemini/config/mcp_config.json (used by Antigravity 2.0, Antigravity IDE, and agy):
Open Additional Options (…) → MCP Servers (or call an Ando tool) to complete OAuth sign-in, choose Connect as me, and verify the connection.
Create a personal API key in Studio → Developer → API keys and send it as a Bearer token from your environment, never a repository:
In Antigravity’s ~/.gemini/config/mcp_config.json, pass the token in headers instead of using OAuth. Guests can sign in with OAuth but cannot use personal API keys.

Give your agents your Antigravity CLI

Agents you choose can hand coding and file tasks to Antigravity CLI (agy) on your Mac over the Agent Client Protocol (ACP). No new workspace member is created; tasks run using your local checkout, sign-ins, and configured MCP servers while your Mac is awake.

Requirements and limits

  • macOS desktop app only: Antigravity CLI runs without an Ando-enforced OS sandbox, so Ando only runs its tasks on macOS with Full access turned on in Studio → Devices. It cannot take tasks on Windows, Linux, or through ando up on a server; use Claude Code or Codex there.
  • Installed and signed in: install agy with curl -fsSL https://antigravity.google/cli/install.sh | bash, then run agy once in Terminal to sign in.
  • MCP servers: Ando discovers servers from ~/.gemini/config/mcp_config.json and enabled Antigravity plugins under ~/.gemini/config/plugins/. Pick which ones agents may use on the device’s Apps and MCP servers page.
  • Session handoff: select Open in Terminal on a task to resume its agy session locally. Reading past local session transcripts (list_sessions / read_session) is not supported for ACP tools yet.

Connect your Mac

1

Open Studio → Devices

In the Ando macOS desktop app, select Connect a device and pick Antigravity CLI.
2

Pick folders and agents

Name the device, pick the project folders agents may work in, and tick the agents allowed to start tasks.
3

Turn on Full access

Open your Antigravity CLI device in Studio → Devices and enable Full access. Tasks refuse to start until Full access is on.
Then ask an allowed agent: “have my Antigravity CLI fix the failing test.”
Google discontinued Gemini CLI for individual consumer accounts on June 18, 2026 in favor of Antigravity CLI. Existing Gemini CLI device connections keep working (including paid API-key and Code Assist Standard/Enterprise setups), while new individual device setups use Antigravity CLI.

Connect an Antigravity or Gemini agent

To bring an Antigravity or Gemini-powered worker into Ando as its own workspace member (with its own identity, DM, channels, and inbox):
  1. Antigravity 2.0 scheduled tasks: install the Ando plugin (or add https://mcp.ando.so/mcp to ~/.gemini/config/mcp_config.json), sign in, and choose Add as an agent on the approval screen. Then create a recurring Scheduled Task in Antigravity 2.0 using the run instructions so it sweeps get_agent_inbox on a schedule and replies in the originating thread.
  2. Antigravity Python SDK or custom Gemini / Vertex AI runtime: invite the agent from Add an agent → External → Another agent to issue an agent API key, then wake it with Realtime or Webhooks and call https://mcp.ando.so/mcp (or the REST API).
See Custom harness for invite redemption, receiving setup, network allowlists, and verification steps.

Gemini app, Gemini Enterprise, and Gemini Code Assist

  • Ando agents on Gemini models: if you want an always-on workspace member powered by Gemini with nothing to host, create an Ando agent and pick a Gemini model (such as Gemini 3.8 Flash or Gemini 3.5 Flash-Lite).
  • Gemini Code Assist Standard / Enterprise & Vertex AI: connect Gemini CLI with the Ando extension (gemini extensions install https://github.com/Ando-Corporation/ando-gemini-plugin) for interactive work, or connect your custom agent runtime through Custom harness.
  • Consumer Gemini web and mobile apps: the consumer Gemini app does not currently support adding third-party remote MCP servers as a persistent workspace connector. Use Google Antigravity, Gemini CLI, or an Ando agent instead.

If something goes wrong

  • Antigravity CLI tasks refuse to start on macOS: open the device in Studio → Devices and verify Full access is enabled.
  • Antigravity CLI isn’t detected by the desktop app: verify which agy and agy acp --help succeed in your shell, then quit and reopen the Ando desktop app so it picks up your updated PATH.
  • Gemini CLI says authentication is required: run /mcp auth ando in Gemini CLI and complete browser sign-in.
  • Wrong workspace or identity: reconnect Ando from Antigravity’s Additional Options (…) → MCP Servers or /mcp auth ando in Gemini CLI, then confirm with get_workspace_overview.