All guides

Copilot CLI and Antigravity

SimpleEdit runs five agent CLIs: Claude Code, Codex, OpenCode, GitHub Copilot CLI and Google’s Antigravity CLI (agy). Copilot and Antigravity run their own terminal UI, like the others, and use the login and settings you already have. They get the app’s sessions, threads, workflows, consults, headless reviews, search and usage. Fork is the one surface they lack.

Before you start

1. Start a session

  1. Right-click ✦ Agent (or press ⌘T for the default provider).
  2. Select New Copilot session or New Antigravity session. Models you added show in the picker too, and Settings → Default Model sets the default.
  3. Type your prompt in the CLI’s own terminal, in the session’s worktree.

The dot next to the session is the CLI’s own state: working, waiting on you, idle or an error. See Getting started for the dots.

A workflow can use either provider for its workers and reviewers.

2. Answer the folder trust dialog

In a folder the CLI has not trusted yet, the session stops at the CLI’s own trust dialog. Copilot asks for permission; Antigravity asks “Trust this folder?”. Answer in the terminal. SimpleEdit shows the session as waiting and never answers for you.

Antigravity remembers a trusted folder, so its next launch there goes straight to idle. Copilot’s hooks fire before it asks, so the session is ready to report its state while the dialog waits for you.

3. What works

4. Fork is missing

Neither CLI has a fork command that SimpleEdit can call. Both fork only inside their own terminal. The sidebar’s Fork action is hidden for these sessions.

To branch the work, use Hand off…. It starts a fresh session with a short summary. See Getting started.

5. What Antigravity writes

Antigravity is the one provider with a global entry. SimpleEdit adds a single simpleedit-bridge entry to ~/.gemini/config/mcp_config.json, and keeps every other server in the file. The entry holds no path, port or token: each session passes those in its environment, including that build’s own bridge path. So the installed app and a dev build never rewrite each other’s entry, and a session always runs the bridge of the build that started it.

Outside SimpleEdit the entry does nothing. The variable it needs is unset, so its command exits at once: no node process, and no tools or instructions from SimpleEdit. Antigravity’s /mcp panel lists the entry as disconnected, which is expected.

Uninstalling SimpleEdit leaves the inert entry. agy mcp remove simpleedit-bridge deletes it.

The rest is temporary or Antigravity’s own: hooks live in a session temp folder that is deleted when the session ends, and Antigravity caches the bridge’s tool list under ~/.gemini/antigravity-cli/mcp/.

Copilot has no global entry. It loads SimpleEdit’s MCP server from a per-launch config file, also named simpleedit-bridge so it doesn’t clash with a server you called simpleedit, and SimpleEdit writes nothing to ~/.copilot; the hooks and MCP config are passed per launch, not saved.

6. Usage

Copilot bills in AI credits, or in premium requests on legacy billing; the pill’s tooltip shows whichever is non-zero. Mail delivered at the end of a turn makes the CLI take another turn, and Copilot bills that like a prompt. Waking an idle agent costs a turn the same way.

Antigravity reports tokens only, with no dollar figure and no machine-readable quota. For plan usage, use agy’s own /usage.