Antigravity
Run Google's Antigravity CLI (agy) as a Scape harness: install it, sign in with Google, pick it per session or as an Argus manager or child, and what it can't do yet.
Antigravity is Google's coding agent CLI, agy. Scape runs it as one of its nine harnesses, next to Claude Code, Codex and the rest, on your own Google account.
Install agy
Install the CLI with Google's installer:
curl -fsSL https://antigravity.google/cli/install.sh | bashIt lands in ~/.local/bin/agy. Scape finds it there even if your shell's PATH doesn't include it. Google's getting started guide has the details.
Sign in
Run agy once in any terminal and sign in with Google in the browser. agy keeps the sign-in in your macOS Keychain, and there is no separate login command.
To use a Gemini API key instead, set "modelProvider": "gemini" in ~/.gemini/antigravity-cli/settings.json and export GEMINI_API_KEY from your shell's startup file (such as ~/.zshrc), where Scape reads your environment; an export typed into one terminal doesn't reach Scape. The setting alone isn't enough: with it on and the key unset, agy won't start, and Scape greys out Antigravity in the picker until the key is there.
Pick Antigravity in Scape
- One session: press Cmd+N, choose Agent session, then Antigravity.
- Every new session: Settings → Agents → Default agent.
- Model and effort: wherever Scape offers a model (an Argus mission's header, a playbook's agent step), type any id
agy modelslists, such asgemini-4-argon-high. Effort islow,medium,high,xhighormax, depending on the model; agy refuses a level the model doesn't have, and some models ignore effort. - Custom command: Settings → Agents → Antigravity takes a path or extra launch arguments. Scape supplies the prompt and the conversation, so leave out
-p,--prompt,-i,--prompt-interactive,-c,--conversationand--.
The session card shows the model agy is using a few seconds after the tab starts, before you send anything.
How Scape talks to agy
The first time you open an Antigravity tab, Scape adds a plugin named scape to Antigravity, at ~/.gemini/config/plugins/scape/. It gives Antigravity tabs Scape's MCP tools and lets Scape see when the agent is working. Scape never edits your own agy settings, MCP config or hooks.
The Antigravity desktop app reads the same folder, so it sees the plugin too; outside Scape the plugin does nothing. To take it out, use Remove Scape's plugin from Antigravity in Settings → Agents. The next Antigravity tab adds it back.
Starting prompts come in two turns
agy loads Scape's tools a few seconds after it starts, and fixes each turn's tools when the turn begins. So a session that starts with a prompt (one you seed, a scape open --prompt, an Argus brief) runs in two turns:
- A short warm-up turn that agy answers with one word.
- Your real prompt, sent once agy has Scape's tools.
Argus children are briefed the same way. A child's brief is its second turn, so the child has Scape's tools, including message_parent, from its first real step. An Antigravity Argus manager gets its kickoff as its second turn too, and Scape holds that manager's other messages until the kickoff has landed.
Trusting the folder
The first time agy runs in a folder it asks "Do you trust the contents of this project?" Scape never answers that for you: typing into it would answer the question and lose the prompt. So Scape sends the starting prompt by itself only when it can confirm agy trusts the folder. Until then (including when it can't tell either way), the tab holds the prompt with a banner:
- Answer the question in the tab, and the prompt goes in.
- Or press Send starting prompt once you can see no question is up.
agy trusts folders by their exact path, so a new worktree asks again even when its parent repo is trusted.
What works
| Capability | Antigravity |
|---|---|
| MCP tools | Yes |
| Session resume | Yes |
| Spectator mode | Yes |
| Argus manager or child | Yes |
| Playbook agent steps | Yes |
| Watchdog (auto-answer) | No |
| Remote SSH sessions | No |
| Remote Control | No |
In a playbook, Antigravity runs without a tab. A tool agy refused to use fails the step with the tool's name. If agy's permission settings denied it, allow it under permissions.allow in those settings.
Known limits
- Waiting for your approval shows as working. agy doesn't tell Scape when it stops to ask before running a command, so the card keeps saying working. Look at the tab.
- Messages wait while a tool call is open. Pressing Return while agy asks for approval would approve the command, so Scape holds messages for the session until the tool call finishes. If you cancel a tool call with Esc, messages keep waiting until you type in the tab.
- Default account only. Antigravity runs on the Google account
agyis signed in to. Account profiles can't add a second one yet, and a project or Argus pinned to anything but "default" won't start an Antigravity session (it says why). - Antigravity's own question tool is off while you're Away. With Away on, agy's
ask_questiontool is turned off, so the agent can't stop the session to ask you something you won't see. It can still post a question to your Attention Inbox. - The plugin is shared. Because agy's config folder is shared with the Antigravity app, Scape's plugin shows up there too (where it does nothing).