Antigravity
Antigravity CLI (agy) is Google’s terminal agent, which replaced Gemini CLI for personal accounts. If the machine has agy installed and used at least once, its sessions show up in the dashboard next to Claude Code’s and Codex’s, with the Antigravity badge. Fleetly reads the conversations Antigravity writes to ~/.gemini/antigravity-cli and never reads its sign-in.
What you can do
- See the sessions, the title Antigravity gives each one, the state (working, your turn, open in a terminal), the conversation and the commands it ran.
- Send a message to an Antigravity session. Each message resumes the conversation on the same machine, and the reply shows up live.
- Start a new session: in +, pick Antigravity and, if you like, the model (the list comes from your account: Gemini, Claude and GPT-OSS).
- Use the queue: the message is delivered when the session finishes what it is doing.
- Approve from the dashboard and your phone, like with Claude: in sessions Fleetly starts, every command and edit that needs permission becomes a request, and Accept automatically approves everything while it is on. The building policy applies too. See Approvals.
- Hand a conversation off from one agent to another: in the message box’s +, Hand off to Antigravity (or, in an Antigravity session, Hand off to Claude or Hand off to Codex). For Antigravity, the machine’s Claude Code or Codex writes the summary.
Roles and teams
In Edit roles, pick Antigravity as the role’s agent. A team can mix all three agents: Claude Code writes, Antigravity reviews, Codex tests, in any order. Work moves from one seat to the next along the arrows, as between Claude and Codex. See Agent teams.
| In the role | In Antigravity |
|---|---|
| Prompt | Goes in as the session’s rules (an AGENTS.md for this role only). |
| Skills | Each one becomes a SKILL.md for this role only. |
| Model | One from your account’s list, or Antigravity’s default. |
| Forbidden | Actually refused by Fleetly, action by action: editing files, running commands or git push. |
The team runs sessions in Auto mode: commands that change something ask for approval in the dashboard and on your phone. So the team doesn’t stop and wait, turn on Accept automatically or forbid commands in the role.
Permission modes
In sessions Fleetly drives:
| In the dashboard | In Antigravity |
|---|---|
| Ask for approval | Every command and edit asks for approval in the dashboard and on your phone. Reads go through. |
| Can edit files | Edits without asking; commands still ask for approval. |
| Auto | Edits without asking and runs read-only commands right away (git status, git diff, ls, cat, grep). The same goes for reads chained with && (cd folder && git status && git diff). Other commands ask for approval, and so does anything with ;, |, > or $. |
| Plan only | Antigravity’s own planning mode: reads and plans, changes nothing. |
With no answer in 15 minutes, the request is denied. Fleetly never uses the mode that skips Antigravity’s permissions, and it changes nothing in sessions you open in a terminal.
Subagents
When an Antigravity conversation opens others (subagents), they show up inside it, like Claude Code’s subagents: in Details, what each one got and did, and their usage adds to the conversation’s.
Sessions open in a terminal: when agy asks "Run this command?", the session shows up in the dashboard as waiting for you, with the command, and the notice reaches your phone (you still answer in the terminal). For the building policy to apply to them and, with away mode, for requests to wait for the dashboard and your phone, accept the Antigravity hook when installing the collector (fleetly-collector hooks, or --so agy): it writes the fleetly entry to ~/.gemini/config/hooks.json, with a backup (in the Fleetly app, it is the Política e celular no Antigravity do terminal step; to remove it, fleetly-collector hooks --tirar agy). When Fleetly has nothing to decide, agy does what it always did: it asks in the terminal what it asks and lets through what is already allowed. On Windows, the dashboard sees from Antigravity’s index which sessions are working.
What isn’t possible yet
- Sending a message to a session open in a terminal (interactive
agy): the dashboard refuses, so two processes don’t write to the same conversation. Reply in the terminal or closeagythere.
The estimated cost uses Gemini 3.8 Flash API pricing and Anthropic’s for the Claude models; GPT-OSS has no price. If you use Antigravity with your Google account, you don’t pay per token.
Didn’t find what you were looking for? Write to admin@fleetly.tools.