Claude Lane Stack
A small AI coding factory for one person
One human. One AI project manager. Real CLI coding agents on a durable conveyor.
Talk to Claude Code — it runs Codex / Qwen / Grok / Kimi / AGY, checks work, merges to main, reviews at night.
🏭 Factory, not five chats 🛡️ Owned paths 🌙 Night review 📦 Auto-merge to main
One PM holds context Writers stay in their lane Independent Codex Sol rail You never merge by hand
✨ Why this exists
Working with AI coding tools usually means: five windows, copy-paste, midnight merges, and zero review discipline.
Claude Lane Stack turns that into a conveyor — plain files + git, no mandatory cloud DB.
😩 Typical AI coding ✨ Lane Stack
Re-explain context every chat One PM holds the plan
Models overwrite each other
owns_paths on every task
Nobody reviews the AI Typed night shift (review → fix → re-review)
You merge branches
PM merges main after checks
“What were we doing?”
resume-project → Now / Blocked / Next
Jobs die at ~2 min Bash Detached processes (survive chat close)
[!TIP] New here? Start with the Beginner guide — zero jargon, factory metaphors.
🔌 CLI agents we plug into
This is not “one model does everything.”
The stack is a control plane that runs real CLI coding agents as durable processes.
CLI Required? Role
Claude Code
Yes
PM (dev-orchestrator), watchers, chat with you
OpenAI Codex CLI Optional Day writer · night Sol review · onboard · docs · emergency
Qwen Code Optional Daytime durable writer
Grok (xAI CLI) Optional Daytime durable writer
Kimi CLI Optional Daytime durable writer (often full-profile default)
AGY (Gemini-oriented) Optional Daytime durable writer
You ──chat──► Claude Code · dev-orchestrator ← always
│
run-supervisor + run-controller
┌─────┬─────┬─────┬─────┐
▼ ▼ ▼ ▼ ▼
Codex Qwen Grok Kimi AGY
│ │ │ │ │
└─────┴─────┴─────┴─────┘
│
owns → L1 verify → acceptance → main
-
Mix and match — install what you pay for;
agents-doctor/adocbuilds the profile -
One protocol — owns, verify,
acceptance.json, progressive accept -
Switch writer — change
main_writein adoc (e.g.codex→qwen) -
Codex for night quality when available
Profile Writers Review
claude-only
Claude only
light
claude-codex
Codex process
Codex Sol night
claude-qwen / grok / kimi / agy
that CLI
as configured
full
multi-writer ready
Codex night
🧠 How it works (60 seconds)
You (chat) → PM (dev-orchestrator)
│ plan-critique · task YAML in .agents/runs/
▼
run-supervisor ← Claude watches one run
│
▼
run-controller ← durable OS process
│
▼
writer CLI process ← codex / qwen / grok / …
│
▼
owns → L1 tests → acceptance.json
│
▼
PM merges → main → (night) Codex review
You don’t hand-launch “Qwen the coder” for normal work.
You talk to the PM. The PM starts the conveyor. The writer is a background process, not a random brand-named subagent.
☀️ Day vs 🌙 night
Day Night
Goal Ship fast Independent quality
Product code Writer from adoc Repair after findings
Watch
run-supervisor
night-shift
LLM review every commit? No Yes — Codex Sol
Done
acceptance.json + main
Finding fixed + re-review
🎭 Who is who
Role Kind Does
You Human Say what you want
dev-orchestrator
Claude agent (PM)
Plan · dispatch · merge · chat
run-supervisor
Claude (watch)
One run until accepted/blocked
run-controller
OS process
DAG · retry · owns/verify/accept
Writer process CLI (Codex/Qwen/…) Implements the task card
lane-supervisor
Claude (1 action)
Typed lane-ctl recovery
emergency-writer
Claude → Codex
After terminal block only
night-reviewer / night-shift
Codex Sol
Night review + findings
project-onboarder
Codex
Project passport
docs-maintainer
Codex
Docs refresh
Built-ins Claude may also use: Explore, Plan, general-purpose (research / side tasks — not the daytime product conveyor).
Aliases: codex-implementer → emergency-writer, etc. → agents/claude/README.md
📋 Task card = contract
Every unit of work lives under .agents/runs/<slug>/tasks/*.yaml:
Field Meaning
owns_paths
Files this task may touch
verification[]
Focused L1 checks
lane:
Matches adoc main_write
Receipts
report → owns → verify → acceptance.json
[!IMPORTANT]
No acceptance.json → not done. Chat green ≠ shipped.
🚀 Quick start
① Install once
git clone https://github.com/VKirill/claude-lane-stack.git
cd claude-lane-stack && git checkout v1.14.16 # or: main
./install.sh
export PATH="$HOME/.agents/bin:$PATH"
Needs: Claude Code · Git · Python 3 (+ PyYAML/jsonschema) · Node · rsync · flock
Optional: Codex · Qwen · Grok · Kimi · AGY · Linux: bubblewrap
② Prepare your project once
cd /path/to/your-project
agents-doctor --apply . # or: adoc
③ Start the PM
# if you use the host launcher:
cc # menu → 1 = dev-orchestrator
# or raw:
claude --agent dev-orchestrator --name lane-pm-myproject
In chat When
/project-onboard
First time on a repo
/resume-project
After a break
“Add dark mode to settings” Normal feature work
⚙️ adoc (simple)
Knob Meaning
Writer main_write
codex / qwen / grok / kimi / agy
Model / effort e.g. Codex luna + max
Fast mode
Codex service_tier: fast
Workspace
in_place · worktree · auto
Plan critique off · structural · LLM before dispatch
🧰 Commands cheat sheet
Command Purpose
agents-doctor / adoc
Detect CLIs · write profile
resume-project .
Now / Blocked / Next
run-init · run-validate · run-board
Runs (usually via PM)
run-controller start|watch|status
Durable lifecycle
lane-ctl …
Typed control plane
night-shift · night-shift-all
Night review/repair
plan-critique --run-dir …
Plan quality gate
❓ FAQ
No. Claude Code alone works (claude-only). Each extra CLI is a pluggable writer (or Codex review rail).
A built-in Claude Code subagent for multi-step side tasks (docs). PM may use it for research. Product features still go through the conveyor.
Claude Code host limit. Write