Run Antigravity CLI in MXterm: install, move from Gemini CLI and a split pane for tests

The short version

1. Install it from Google's instructions.

2. Open your project folder in MXterm and open a terminal pane.

3. Run agy in the pane, then split the pane for a shell.

If you came from Gemini CLI

Google's Gemini CLI README says: "Free individual access and Google AI Pro / Ultra (Google One) moved to Antigravity CLI on June 18, 2026." The same notice says Gemini CLI is designed for Gemini Code Assist Standard / Enterprise licenses and Code Assist for GitHub on Google Cloud, so check how it applies to your account on that page (github.com/google-gemini/gemini-cli, read 31 October 2026).

Google's migration page says it "preserves backward compatibility with the core developer-experience constructs popularized by Gemini CLI." It documents agy plugin import gemini for moving your Gemini CLI extensions, says workspace skills move from .gemini/skills/ to .agents/skills/, and says some themes or overlays "might not be supported" (antigravity.google/docs/cli/gcli-migration, read 31 October 2026). This page does not say Gemini CLI was discontinued for everyone.

Install it

Google describes it as "a keyboard-first terminal client that runs Antigravity workflows in local shells, remote cloud environments, and SSH sessions" (antigravity.google/docs/overview?tab=cli, read 31 October 2026).

The macOS install is a one-line install script; the default binary location is ~/.local/bin/agy, and agy --version checks the install. The first launch walks you through a color scheme, a rendering mode (Alt-Screen or Inline) and workspace trust (antigravity.google/docs/getting-started?tab=cli, read 31 October 2026).

Check Google's pages on the day you install; commands change. MXterm does not install agents; you install it yourself.

Step 1: open a pane and run agy

Open MXterm on your project folder and open a terminal pane; it is a real shell. Run agy there.

Google gives ~/.local/bin/agy as the default binary location, so if your shell cannot find agy, check that folder is on your PATH.

Step 2: sign in and give it a task

Google's authentication page says: "If no saved session is found: The CLI automatically launches your local default web browser." Over SSH the page says: "The CLI detects the SSH environment and prints a unique, secure authorization URL." It also documents signing in with a Gemini API key (antigravity.google/docs/install?tab=cli, read 31 October 2026).

After sign-in, type the task as you would in any terminal. MXterm does not sign you in.

Step 3: a shell beside it

Use the split buttons in the pane header (Split Right and Split Down) to put a plain shell next to it for your tests. Split panes run real shells.

Run your test command in the shell pane, and keep the CLI in the pane beside it.

Next to other agents

It can run in a pane beside Claude Code or Codex in the same workspace.

See Claude Code in MXterm, the guide to running Claude Code and Codex side by side in split panes and isolating agents with git worktrees. To keep agents in one room, see the Control Room. Our list of AI coding agents in 2026 gives the vendors' own descriptions of each one.

When a plain terminal is enough

For a task with this CLI, a plain terminal is enough once it is installed and you are signed in.

MXterm helps when agents or tasks run in parallel and you want them in one window. To try it, use the download page.