Running multiple Claude Code sessions doesn't require multiple terminal windows. tmux lets you split a single terminal into panes and run independent sessions side by side.
# Start a tmux session
tmux new -s dev
# Split into panes
Ctrl+b, then % # vertical split (side by side)
Ctrl+b, then " # horizontal split (top and bottom)
# Navigate between panes
Ctrl+b, then arrow keys
Start a Claude Code session in each pane and assign each one a focused task:
Pane 1: feature work — implementing the new API endpoint
Pane 2: test runner — watching the test suite and reviewing failures
Pane 3: review session — reading diffs and suggesting improvements
Use named windows to organise work by concern rather than by position:
# Create named windows for distinct tasks
Ctrl+b, c # new window
Ctrl+b, , # rename current window
# Navigate between windows
Ctrl+b, n # next window
Ctrl+b, [0-9] # jump to window by number
This pairs especially well with git worktrees — each pane gets its own worktree, so sessions never collide on the same files.
# Set up isolated worktrees for each Claude session
git worktree add ../project-auth feature/auth
git worktree add ../project-tests bugfix/flaky-test
tmux turns one terminal window into a full multi-session workspace — no app switching, no lost context.
Log in to leave a comment.
The /security-review command scans your uncommitted changes for injection vectors, auth gaps, hardcoded secrets, and other common vulnerabilities.
The SessionStart hook fires when any session begins or resumes, making it ideal for loading environment variables and running one-time setup scripts.
Ask Claude to write property-based tests for your functions using fast-check — it identifies the mathematical invariants in your code and generates tests that cover inputs you'd never enumerate by hand.