Agents · Qwen Code
Qwen Code for teams, without collisions
In shortRun lanes init --agents qwen in your repository and commit the result. Lanes writes .qwen/settings.json so that every Qwen Code edit is committed as you and published to a shared branch, after waiting for any teammate editing the same file. Add lanes mcp to Qwen Code so its agent can read the team brief and check a file before touching it.
Qwen Code on a team
Qwen Code is a terminal agent like Claude Code and Gemini CLI, and has the same blind spot: it cannot see a teammate's agent. 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. Qwen Code gets a team brief with each prompt, heads-ups about teammates' changes, and the rest of the team's agents see what Qwen Code is changing.
What Lanes installs for Qwen Code
Lanes adds its hooks to .qwen/settings.json with the same coordination as Claude Code, on Qwen Code's write_file and edit tools.
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.
| What | Qwen Code with Lanes |
|---|---|
| Edits wait for a teammate's edit of the same file | Yes |
Each edit committed as you and published to lanes/main | Yes |
| Team brief added to each prompt | Yes |
| Heads-up before reading a teammate's file | No |
| Check at the end of a turn | No |
| MCP team tools | Yes |
Set it up
- Get Lanes:
git clone https://github.com/mfmatozza/lanes && cd lanes && npm ci && npm run build. The commands below writelanesfornode /path/to/lanes/dist/lanes.cjs. - In your repository, run
lanes init --agents qwenand push the commit it makes. - Turn on shared context once per repository:
lanes team on, then commit.lanes/team.json. - Add the MCP server to Qwen Code:
qwen mcp add -s user -t stdio lanes node "/path/to/lanes.cjs" mcp- 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 Qwen Code
- Qwen Code loads project hooks only in a trusted folder.
Status
Built from Qwen Code's published documentation and covered by Lanes' automated tests. It has not yet been run against the real Qwen Code. Issues and reports are welcome.
Mixed teams work: one person can use Qwen Code 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
Why are the hooks not running?
Qwen Code loads project hooks only in a trusted folder. Trust the repository folder first.
Which tools are coordinated?
write_file and edit.
How do I add the MCP server?
qwen mcp add -s user -t stdio lanes node /path/to/lanes.cjs mcp.