Agents · Cursor

Cursor for teams, without collisions

In shortRun lanes init --agents cursor in your repository and commit the result. Lanes writes .cursor/hooks.json so that every Cursor edit is committed as you and published to a shared branch right after it is made. Add lanes mcp to Cursor 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

Cursor on a team

Cursor makes fast, wide edits. When a teammate's agent is changing the same code, nothing in Cursor tells it so. 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. Cursor gets teammates' changes published to the shared branch, and the rest of the team's agents see what Cursor is changing.

What Lanes installs for Cursor

Lanes writes .cursor/hooks.json with an afterFileEdit hook. Each Cursor edit is committed and published to lanes/main right after it is made, so teammates' agents see it and get heads-ups about it. Cursor has no hook that can wait before an edit without also deciding its permission, so Lanes cannot queue a Cursor edit behind a teammate's.

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 cursor 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 Cursor:

Add this to ~/.cursor/mcp.json:

{ "mcpServers": { "lanes": { "type": "stdio", "command": "node", "args": ["/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 Cursor

• Add lanes mcp to Cursor so the agent can ask for the team brief and check a file before it edits it. That is how Cursor gets the shared context.
• The Claude Code hooks in .claude/settings.json stay inert inside Cursor.
• The VS Code extension installs in Cursor from the .vsix file: Extensions, the ... menu, Install from VSIX.

Status

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

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