Agents · Amp

Amp for teams, without collisions

In shortRun lanes init --agents amp in your repository and commit the result. Lanes writes .amp/plugins/lanes.ts so that every Amp edit is committed as you and published to a shared branch, after waiting for any teammate editing the same file. Add lanes mcp to Amp 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

Amp on a team

Amp is built for long autonomous threads. A long thread is also a long window in which a teammate's agent can change the code under it. 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. Amp gets a team brief with each prompt, heads-ups about teammates' changes, and the rest of the team's agents see what Amp is changing.

What Lanes installs for Amp

Lanes installs a plugin in .amp/plugins/lanes.ts that coordinates each edit, waiting for a teammate's edit of the same file and then publishing, and adds the team brief to each 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.

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 amp 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 Amp:

amp mcp add lanes -- node "/path/to/lanes.cjs" mcp

5. 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 Amp

• Run plugins: reload in a running Amp after lanes init.

Status

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

Mixed teams work: one person can use Amp 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