706 commits, 38 PRs merged, 5 repos, 5 days. One person with max 5 Claude Code sessions.
The stack: Taskwarrior as the task queue, Zellij as the session manager, Claude Code as the worker. Each CC session runs in a Zellij pane with a task assigned. When a session finishes, the next highest-urgency task auto-starts via Taskwarrior hooks. You manage tasks, not sessions.
Thursday I got API rate-limited and throughput dropped 75%. That's the proof - the system was the bottleneck, not me.
The key design: on-demand human-in-the-loop. Agents never block waiting for me. They pick up tasks, do the work, commit, and move on. I review PRs and make decisions when I'm ready - not when the agent needs me. That's what eliminates the human-as-bottleneck problem. 5 sessions is plenty when none of them are waiting on you.
The full setup is documented on the site. Architecture isn't locked to Claude Code - Zellij sessions don't care what CLI agent runs inside them.
ungreased0675•1h ago
neilbb•1h ago
neilbb•35m ago
The key difference: on-demand human-in-the-loop. Agents never block waiting for you. They pick up work, execute, commit, and exit. You make decisions asynchronously when ready.
This eliminates the biggest bottleneck in agent systems—the human becoming a serial dependency.
Proof isn't in benchmarks or simulation. It's 706 commits shipped in 5 days using standard tools (Taskwarrior, Zellij, Claude Code). System got rate-limited, not me.