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
- Copilot CLI 1.0.112 or newer. Install it and sign in the way you do outside SimpleEdit. Copilot updates itself, so its version can move without you; SimpleEdit checks it before it starts a session.
- Antigravity CLI 1.5.12 or newer. The command is
agy. Install it and sign in the same way;agy updateupdates it. - Both run with your own home folder:
~/.copilotfor Copilot,~/.geminifor Antigravity. Your settings, plugins, MCP servers, saved approvals and trusted folders apply. SimpleEdit does not sign you in, and Antigravity never starts a browser login. - Because the CLIs keep their own history, your sessions appear there too. Antigravity lists them in its conversation list. Copilot syncs them to GitHub when your Copilot settings say so; SimpleEdit’s headless runs turn that sync off, so those do not sync.
- If the binary is missing or older than the minimum, SimpleEdit says so and does not start the session.
1. Start a session
- Right-click ✦ Agent (or press ⌘T for the default provider).
- Select New Copilot session or New Antigravity session. Models you added show in the picker too, and Settings → Default Model sets the default.
- 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
- Threads and mail. Comment on lines as usual. A message reaches the agent when its turn ends, or as a typed prompt when it is idle.
- Resume. Sessions survive a restart; select Resume. Copilot gets its session id at launch. Antigravity learns it on the first turn, so a session restored before its first turn starts fresh, with nothing lost.
- Workflows. A workflow can run its workers and reviewers on either provider, and each has its own Workers at once row in Settings → Workflows. See Running a Workflow.
- Companions and consults. Review Room and post companions run with your own settings and saved approvals. A consult runs read-only: write and shell tools are refused, and the consulted model can still read the code.
- Screen PRs, Deep review and the rest. The headless runs work, including Screen PRs, Deep review, the tour, What’s new and round match.
- Session search. Their sessions are part of the project’s past sessions, like the others.
- Usage. The pill shows tokens for both. Copilot also shows AI credits, or premium requests on legacy billing. Neither reports a dollar figure, so there is no ≈ $ estimate as for Claude.
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.