lanes
Skill9 starsChanged 3 months agoMITView on GitHub
Parallel work inside tmux, for a server you reach over SSH (also from a phone). Each lane is a git worktree with its own branch and its own tmux window, Claude Code open in it; do in it whatever you want. Alt+<number> switches between them. Lanes merge with /merge-up and /merge-down, like /parallel-work's streams. Also shows lane status and cleans up merged lanes.
- Reads credentials
4 other projects use a version of this.
Adopted by
Most recently taken up by
- KrishP147/skillstheir own version, first seen Nov 1, 2026
- grrowl/bb-lanestheir own version, first seen Oct 20, 2026
- thebpandey/lanestheir own version, first seen Oct 2, 2026
- palpen/claude-skillstheir own version, first seen Apr 14, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- KrishP147/skills★ 37same name
- thebpandey/lanes★ 9same name
- grrowl/bb-lanes★ 2same name
- palpen/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository56 other files it gives its agents.
- .claude/agents/CLAUDE.mdCLAUDE.md
- .claude/hooks/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .claude/prompts/CLAUDE.mdCLAUDE.md
- .claude/rules/CLAUDE.mdCLAUDE.md
- .claude/skills/CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- vision/CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- scaffold/llms.txtllms.txt
- architecture-checkSkill
- backlog-reviewSkill
- bootstrapSkill
- brainstormSkill
- buildSkill
- claude-sense-checkSkill
- code-qualitySkill
- commitSkill
- continueSkill
- custom-hooksSkill
- dashboardSkill
- debug-sessionSkill
- deploySkill
- discoverSkill
- doctorSkill
- fix-issueSkill
- framework-upgradeSkill
- handoffSkill
- help-meSkill
- ideateSkill
- manual-testSkill
- merge-downSkill
- merge-upSkill
- optimizeSkill
- parallel-workSkill
- performance-checkSkill
- phase-reviewSkill
- pr-statusSkill
- quality-checkSkill
- quickstartSkill
- refine-loopSkill
- researchSkill
- retrospectiveSkill
- security-auditSkill
- skill-createSkill
- skill-evalSkill
- sprint-endSkill
- sprint-startSkill
- story-cycleSkill
- testing-cycleSkill
- test-validatorSkill
- UAT-cycleSkill
- undo-workSkill
- uninstallSkill
- weekly-maintenanceSkill
- wrap-upSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 35
All worktrees share one object store: merges between a lane and its parent are local, with no push or fetch.
- Very specific: line 40
Run the scripts directly; there is no need to read them first.
- Distinctive: line 45
Run from the main checkout, on your working branch (not the default branch), with a clean tree.
- Distinctive: line 91
Run from the main checkout.
- Very specific: line 106
All lanes merged: /lanes cleanup.
- Distinctive: line 112
Only the main checkout deploys, migrates a shared database or touches a live service.
- Distinctive: line 117
Create lanes from your working branch, never from another lane.
- Distinctive: line 118
Keep lanes short: merge up after each finished piece, clean up when the lane's work is done.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
lanes
/parallel-work opens each stream in a new tab of a desktop terminal. Over SSH
there is no desktop: /lanes opens each stream as a window in the tmux session
you are in. The session keeps running when the connection drops, so the lanes
keep working while your laptop sleeps or your phone locks.
main ──► your branch (main checkout, the window you started from)
├─ <branch>-a ~/lanes/<repo>/a tmux window "a"
├─ <branch>-b ~/lanes/<repo>/b tmux window "b"
└─ ... one letter per lane- Lanes are made by
/parallel-work'snew-worktree.sh:.env,.env.local,.claude/settings.local.json,CLAUDE.local.mdand.mcp.jsonare copied in, and the parent is recorded, so/merge-up,/merge-downand/sprint-endtreat a lane as a stream. - The worktrees live outside the repository (
~/lanes/<repo>/), so a Docker build context or a dirty-tree check in the main checkout never sees them. - All worktrees share one object store: merges between a lane and its parent are local, with no push or fetch.
Commands
Run the scripts directly; there is no need to read them first. Paths are relative
to the skills folder (${CLAUDE_PLUGIN_ROOT:-.claude}/skills).
start <letter> ...
Run from the main checkout, on your working branch (not the default branch), with a clean tree. Two lanes that change the same files will conflict when they merge: give each lane its own part of the work.
bash "${CLAUDE_PLUGIN_ROOT:-.claude}/skills/lanes/scripts/lane-start.sh" a b cPer lane: branch <branch>-<letter>, worktree ~/lanes/<repo>/<letter>, and a
window named after the letter that installs dependencies (from the lockfile:
pnpm, npm, yarn, bun, uv or poetry) and then opens claude. Optional:
a:<story-id> opens it on /story-cycle <story-id> instead. Outside tmux the windows go into a session
named after the repo; the script prints how to attach to it. It also binds
Alt+<number> to jump to a window, and prints each lane's window number and key.
Settings, as environment variables:
| Variable | Default | Use |
EXOSUIT_LANES_DIR | ~/lanes/<repo> | where the worktrees go |
EXOSUIT_LANE_SETUP | from the lockfile | first command in each lane; empty skips it |
EXOSUIT_LANE_CLAUDE | claude | how Claude Code starts, for example with --model |
EXOSUIT_LANE_SESSION | the current session | which tmux session gets the windows |
EXOSUIT_LANE_ALT_KEYS | on | 0 leaves Alt+<number> unbound |
The first start in a new folder shows Claude Code's folder-trust question once. Its default is "No, exit": in that window press Down to "Yes, I trust this folder", then Enter, and Claude Code opens. Enter alone closes it.
status (default)
bash "${CLAUDE_PLUGIN_ROOT:-.claude}/skills/lanes/scripts/lane-status.sh"Tell the user what it means: BEHIND above 0, that lane should run /merge-down;
AHEAD above 0, work not merged up yet; DIRTY above 0, work in progress; WINDOW no,
the lane's window was closed (open one with tmux new-window -c <worktree>).
Status also binds the Alt keys again, for a tmux server that restarted.
cleanup
bash "${CLAUDE_PLUGIN_ROOT:-.claude}/skills/lanes/scripts/lane-cleanup.sh"Run from the main checkout. For every lane fully merged into its parent: removes
the worktree, deletes the branch (git branch -d only) and closes its window.
Lanes with uncommitted or unmerged work are kept and listed. Also closes windows
whose lane folder is gone. Tell the user first: closing a window ends the
Claude Code session in it.
Working with lanes
- From your branch:
/lanes start a b. - Work in each lane's window as you like: Claude Code, a shell, tests, a story.
- A piece of work done in a lane:
/merge-downfirst, so conflicts are solved in the lane that made the change; then the project's test and typecheck commands (fromCLAUDE.md); then/merge-up, which is now a fast-forward of your branch. Never merge red work up. - The other lanes run
/merge-downwhenstatusshows them behind. - All lanes merged:
/lanes cleanup. A sprint branch then ships with/sprint-end.
Rules
- Two or three lanes. Every lane runs its own Claude Code, and they share one usage limit.
- Only the main checkout deploys, migrates a shared database or touches a live service. Lanes run unit tests and the typecheck.
- One lane at a time owns database migrations. A second migration waits for that
lane's
/merge-up, then/merge-down, so migration numbers do not collide. - A dev server in a lane gets its own port, never one a running service uses.
- Create lanes from your working branch, never from another lane.
- Keep lanes short: merge up after each finished piece, clean up when the lane's work is done.
Moving between lanes in tmux
| Keys | What it does |
Alt+1 to Alt+9 | go straight to that window, without Ctrl-b. In Termius: tap Alt, then the number |
Alt+0 | back to the window you were in before |
Ctrl-b w | list of windows to pick from |
Ctrl-b <number> | go to that window; the status bar shows each number and name |
Ctrl-b n / Ctrl-b p | next / previous window |
Ctrl-b d | leave tmux; every lane keeps running |
The Alt keys are bound by start and status (scripts/lane-keys.sh) on the
running tmux server, for every session, until the server stops. A key the user
bound already is left as it is. With tmux's defaults the first window is 0, so
lanes a, b, c sit on windows 1, 2, 3 and Alt+1, Alt+2, Alt+3 reach them. In a
Mac terminal the Option key must send Meta: iTerm2, Profiles, Keys, Left Option
key: Esc+; Terminal.app, Profiles, Keyboard, Use Option as Meta key.
status from the window you started the lanes from shows every lane without
visiting them.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

