Docs

Lanes documentation

In shortStart with the install steps below, then use the CLI reference for every command and the MCP reference to give your agents the team tools. Each agent has its own setup page.

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

Install

Lanes needs Node.js 22.18 or newer and git on your PATH. The folder you set up must be a git repository.

git clone https://github.com/mfmatozza/lanes
cd lanes && npm ci && npm run build

Everything after that is node dist/lanes.cjs <command>. The examples on this site write it as lanes, so it helps to add an alias:

alias lanes="node /path/to/lanes/dist/lanes.cjs"

The VS Code extension carries the same file. Download lanes-0.3.0.vsix from the GitHub release and install it with code --install-extension lanes-0.3.0.vsix. A Marketplace listing is the next step.

Set up a repository

cd your-repo
lanes init --agents claude,codex
lanes team on
git push

init installs the hooks for each agent you name and commits them. team on writes .lanes/team.json, which turns on the shared brief and heads-ups. Push both so teammates get them.

Run a team server

Working alone, there is nothing to start: the first agent session starts a local server. For a team, one person runs:

lanes server --host 0.0.0.0
lanes invite bea

invite prints a lanes join command with a personal token for Bea. She runs it once on her machine. With --github <login>, she signs in with GitHub instead.

Check it works

lanes doctor

One line per check: Node, git, the hooks in this repository, team context, the server and your token, and Claude Code. A failed check says what to do next.

Reference