Lanes
GitHub

Agents · Antigravity

Google Antigravity for teams, without collisions

In shortRun lanes init --agents antigravity in your repository and commit the result. Lanes writes .agents/hooks.json so that every Antigravity edit is committed as you and published to a shared branch, after waiting for any teammate editing the same file. Add lanes mcp to Antigravity so its agent can read the team brief and check a file before touching it.

Updated 2026-11-12 · Lanes 0.3.0 · Source on GitHub

Antigravity on a team

Antigravity runs agents across editor, terminal and browser. When teammates use it on one codebase, their agents still cannot see each other. When two people's agents work in the same repository, one can overwrite the other's change in a shared file, or write new code against a function the other is renaming. Git shows the damage later, at merge time, after both agents have finished.

Lanes connects every agent on the team to one coordination server. Antigravity gets heads-ups about teammates' changes, and the rest of the team's agents see what Antigravity is changing.

What Lanes installs for Antigravity

Lanes writes .agents/hooks.json. Each Antigravity edit waits for a teammate's edit of the same file, then goes ahead and is published. Antigravity's prompt-time hook carries no prompt text, so it cannot add the team brief at the prompt.

The file is committed with lanes init, so every teammate gets it when they pull. lanes off removes only the Lanes entries and leaves your own settings alone.

WhatAntigravity with Lanes
Edits wait for a teammate's edit of the same fileYes
Each edit committed as you and published to lanes/mainYes
Team brief added to each promptNo, use the MCP tool team_brief
Heads-up before reading a teammate's fileNo
Check at the end of a turnNo
MCP team toolsYes

Set it up

  1. Get Lanes: git clone https://github.com/mfmatozza/lanes && cd lanes && npm ci && npm run build. The commands below write lanes for node /path/to/lanes/dist/lanes.cjs.
  2. In your repository, run lanes init --agents antigravity and push the commit it makes.
  3. Turn on shared context once per repository: lanes team on, then commit .lanes/team.json.
  4. Add the MCP server to Antigravity:

Add this to ~/.gemini/config/mcp_config.json, or /mcp in agy:

{ "mcpServers": { "lanes": { "command": "node", "args": ["/path/to/lanes.cjs", "mcp"] } } }
  1. Check the machine with lanes doctor.

Working alone, the first session starts a local Lanes server. For a team, one person runs lanes server --host 0.0.0.0 and invites the others with lanes invite <name>.

Things to know about Antigravity

  • For the brief, add lanes mcp: the agent can then call team_brief at the start of a task.

Status

Built from Antigravity's published documentation and covered by Lanes' automated tests. It has not yet been run against the real Antigravity. Issues and reports are welcome.

Mixed teams work: one person can use Antigravity while teammates use Claude Code, Codex or Cursor. Every agent reports to the same server, so the brief and the heads-up name each teammate's task whatever agent they run.

Questions

Are Antigravity's edits queued?

Yes. Each edit waits for a teammate's edit of the same file, then goes ahead.

Why no brief at the prompt?

Antigravity's prompt-time hook does not carry the prompt text, so Lanes adds context through the MCP server instead.

Where does the MCP config go?

~/.gemini/config/mcp_config.json, or use /mcp inside agy.