Agents · Codex

OpenAI Codex for teams, without collisions

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

Codex on a team

Codex edits through patches, often several files at once, which makes a silent overwrite of a teammate's change harder to spot in review. 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. Codex gets a team brief with each prompt, heads-ups about teammates' changes, and the rest of the team's agents see what Codex is changing.

What Lanes installs for Codex

Lanes writes .codex/hooks.json in the repository. Codex reports every file edit as apply_patch, so the hook reads the files from the patch's *** Update File: lines, takes a lease on each and queues behind a teammate's agent when needed, then commits and publishes after the patch is applied. The prompt hook adds the team brief.

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 codex 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 Codex:

codex 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 Codex

• Codex runs repository hooks only after each person trusts them: run /hooks in Codex once and approve the Lanes entries.
• Codex loads .codex/hooks.json once the project's .codex/ layer is trusted.
• lanes approve <id> --run --agent codex runs an approved request with your own Codex, in its read-only sandbox for read-only requests.

Status

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

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