Google Antigravity integration

Run Gemini through Antigravity, then inspect the result.

Flame runs Gemini as a coding agent through Google Antigravity while keeping projects, worktrees, terminals, testing, Git, and review in one desktop workspace.

The developer problem

An asynchronous agent run still needs a place to be reviewed.

Agentic development creates work that can continue while you move on: a task may be running in another repository, waiting for approval, or ready for a diff review. Managing that state across CLIs and separate editor windows is the real operational problem.

Flame treats Antigravity as one runtime in an agent queue. You can see its work in the same place as Claude Code and Codex tasks, then move from completed work to tests and review without recreating the project context.

Try it on a real task

What Antigravity enables in Flame

Connect

Install Google's official Antigravity CLI explicitly, authenticate with Google, then select the runtime in Flame.

Example task

Give Gemini a failing parser test and ask for a minimal repair in a separate branch checkout.

Inspect the result

Follow the task transcript and tool activity, rerun the test, and compare the repaired parser against the original diff.

What to expect

This is the Antigravity agent runtime. A Gemini API connection is a separate provider path; native managed worker teams are unavailable here.

A connected workflow

From Antigravity task to a reviewed change

  1. 01

    Choose the task and project

    Start a Gemini task through Antigravity in the repository where the work belongs, with scoped permissions and an explicit landing policy.

  2. 02

    Protect active work

    Choose a separate branch and Git worktree when the task should not share your current checkout.

  3. 03

    Monitor asynchronous work

    Agents Manager keeps status, tool calls, duration, tokens, and terminal output visible while you work on another task.

  4. 04

    Bring it back to review

    Inspect the diff and merge preview in Flame, run the relevant verification, and decide how the completed branch lands.

How it works in Flame

What using Antigravity in Flame looks like

01

Trace a failing test through the Gemini task

Start with a reproducible test failure, choose the owning project and Antigravity runtime, then follow the agent’s tool activity and inspect the changed implementation beside the test output.

02

Keep agent work isolated

Optional Git worktrees let a Gemini task modify a separate checkout while your current branch stays untouched.

03

Avoid a single-provider workflow

Flame supports Gemini via Antigravity, Claude Code, and Codex as distinct full coding-agent runtimes. Pick the provider at the task level.

04

Review results next to the code

Task monitoring ends in Git review, not an opaque transcript. Inspect changed files and use the merge preview before the branch is landed.

FAQ

Antigravity integration questions

Use Antigravity with Flame.

Download Flame to keep implementation, verification, review, and the final Git decision in one workspace.

Free to use on macOS, Windows, and Linux.