allconvos.ai
← All walkthroughs
Walkthrough — Tooling
Structured Claude Code
Dev Environment
Replace chaotic terminal tabs with named tmux windows, isolated git worktrees, and coordinated Agent Teams. Three layers that turn parallel sessions from confusion into flow.
The Problem
Tab 1 Tab 2 Tab 3 Tab 4 Tab 5 Tab 6 ... ??? ??? ??? ??? ??? No labels • No isolation • Context bleed • File conflicts Agent A editing src/pages/Index.tsx Agent B editing src/pages/Index.tsx → CONFLICT
The Solution — Three Layers
1 tmux Named windows • Persistent sessions • Split panes brew install tmux  •  Ctrl+B to navigate 2 Git Worktrees Isolated file systems per agent • Separate branches • No conflicts claude --worktree  •  built into Claude Code 3 Agent Teams Coordinated multi-agent work • Shared task list • Lead + specialists CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1  •  experimental
Layer 1 — tmux Session Layout
[parnell] 1:dev* 2:claude 3:agent2 ~ npm run dev VITE v6.0.0 ready in 312ms ❯ Local: http://localhost:8080/ ❯ Network: http://192.168.1.42:8080/ press h + enter to show help ~/parnellsystems $ git status On branch main nothing to commit $ Ctrl+B then 1/2/3 to switch windows 13:42 Window 1: dev server Window 1: general terminal
Layer 2 — Worktree Isolation
A Main Repo ~/parnellsystems/ branch: main Session: "landing-page" B Worktree ~/parnellsystems-wt-a3f/ branch: feature/auth-flow Session: "feature-auth" claude --worktree ✓ Completely isolated file systems Both agents edit freely — zero file conflicts, separate branches ✓ Features • Bug fixes • Refactors • PRs — Quick edits • Commands • Research • Ops
Layer 3 — Agent Teams
Lead Agent Plans, delegates, coordinates Frontend Agent Components, styling, layout [tmux pane 1] Content Agent Copy, training, marketing [tmux pane 2] Infra Agent Build, deploy, config [tmux pane 3] ⚡ Shared task list — agents communicate progress and flag dependencies
tmux Key Bindings
Ctrl+B → 1
Switch to dev server
Your Vite dev server and general terminal pane. Check build output, run commands.
Ctrl+B → 2
Switch to primary Claude session
Your main coding session. One task, full context.
Ctrl+B → 3
Switch to parallel agent (worktree)
Isolated second session. Run claude --worktree here for conflict-free parallel work.
Ctrl+B → d
Detach — session stays alive
Close Ghostty, go get coffee. Come back with tmux attach -t parnell.
Session Scoping Rules
feature-[name]
New feature dev
worktree
bugfix-[name]
Single bug fix
worktree
landing-page
Marketing site edits
direct
training
Course content
direct
ops
Business operations
direct · ai-os/
refactor-[scope]
Code cleanup
worktree
The Three Rules
⚡
Max 2 parallel coding sessions
Parallel enough to multitask, conservative enough to avoid constant rate-limit throttling on Max plan.
🚫
Never edit the same file in two sessions
If two agents need the same file, finish one first or use worktrees so they have separate copies.
🎯
One session = one task
Don't reuse a session for a different task. Stale context from the previous task confuses Claude. Start fresh.
Daily Flow — Quick Reference
# Start your structured workspace
$ cd ~/Documents/VSStudio/parnellsystems
$ ./scripts/tmux-dev.sh

# Window 2: start your main task
$ claude
> Update the hero section copy on the landing page

# Ctrl+B → 3: start parallel work in a worktree
$ claude --worktree
> Add authentication flow to the dashboard

# Switch between them
Ctrl+B → 2  or  Ctrl+B → 3

# Detach when done, come back later
Ctrl+B → d
$ tmux attach -t parnell
Tools Worth Knowing
tmux
Terminal multiplexer. Named windows, persistent sessions, split panes.
brew install tmux
muxtree
Dead-simple bash script pairing worktrees with tmux. Minimal dependencies.
Single bash script
dmux
Full dev agent multiplexer. 11+ agents, hooks, CI/CD. Most feature-rich.
GitHub / npm
claude-esp
TUI to monitor Claude's hidden thinking across sessions.
GitHub