Use tmux to Keep Claude Code Sessions Alive Through Dropped Connections
Claude Code does not handle dropped connections gracefully. If your SSH connection breaks mid-session -- on an airplane, a flaky hotel network, or just your laptop sleeping -- the session dies silently and all progress is lost.
The fix is tmux. Run Claude Code inside a tmux session on a remote machine (a Mac Mini, a home server, a cloud VPS) and your laptop becomes just a window into a persistent session that keeps running on the other box.
# SSH into your remote machine
ssh user@your-mac-mini
# Create a named tmux session
tmux new -s claude
# Run Claude Code inside it
claude
# Later, if you disconnect -- just reconnect and reattach
ssh user@your-mac-mini
tmux attach -t claude
When wifi drops over the Atlantic, tmux keeps the Claude session running on the remote machine. Reconnect when you land and the session is exactly where you left it -- mid-task, mid-file, mid-thought.
This is especially valuable for long-running tasks where Claude is building something substantial. You don't want a flaky connection to cancel 40 minutes of work.
It pairs naturally with running Claude Code on a dedicated box that stays on 24/7, so you can also kick off a long task, close your laptop, and pick it back up later without losing anything.
Your Claude session should outlive your wifi. tmux makes that happen.
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.