tmux
Terminal multiplexer. Splits one terminal into multiple panes. Sessions persist even when you disconnect — SSH from your phone and your work is still there.
Day 23 · 30 Days of Claude Code
tmux Cockpit + Git Worktrees
Run 4 parallel Claude sessions in one terminal. Zero file conflicts. 4× the throughput.
4Parallel Panes
0File Conflicts
20Max /batch Agents
4×Throughput
The Cockpit Concept
4 independent Claude sessions, 0 file conflicts, 100% task isolation — all in one terminal window.
The core problem: Two agents editing the same file at the same time creates merge conflicts and data corruption. tmux + Git worktrees eliminates this completely.
Pane 1 — Feature
$ claude --worktree feature-auth
✓ Worktree ready: /worktrees/feature-auth
Working on auth module...
Pane 2 — Bugfix
$ claude --worktree bugfix-stripe
✓ Worktree ready: /worktrees/bugfix-stripe
Fixing Stripe webhook...
Pane 3 — Remote
$ ssh staging-server
Connected to staging-01
Deploying to staging...
Pane 4 — Logs
$ tail -f app.log | grep ERROR
Monitoring alerts...
No errors in last 5min ✓
Git Worktrees
Creates separate copies of a repo on different branches. Each agent gets its own full codebase. Different directories. Different branches. Impossible to conflict.
Claude Sessions
Each pane runs an independent Claude Code session with isolated context. Feature dev, bug fixes, remote ops, and log monitoring — all simultaneously.
What You Get
- 4× parallel throughput vs single-session
- Zero merge conflicts between agents
- Each agent has full codebase access
- Sessions survive terminal closes
- Remote access from any device
- Auto-cleanup when no changes made
Power Move: /batch
The /batch command spawns 20 parallel agents simultaneously. Use it for:
- Mass migrations across 50+ files
- Bulk API endpoint updates
- Test suite generation at scale
- Code style refactoring at once