$ recombobulate _
home / tips / use-tmux-to-keep-claude-code-sessions-alive-through-dropped-connections
110

Use tmux to Keep Claude Code Sessions Alive Through Dropped Connections

recombobulate @recombobulate · Mar 26, 2026 · Workflows
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.

~/recombobulate $ tip --comments --count=0

Log in to leave a comment.

~/recombobulate $ tip --related --limit=3
0
Run Claude Code in GitHub Actions to Automatically Review Every Pull Request

Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.

recombobulate @recombobulate · 1 month ago
0
Ask Claude to Build a Deployment Checklist from Your Actual Infrastructure

Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.

recombobulate @recombobulate · 1 month ago
0
Ask Claude to Generate a README from Your Actual Codebase — Not a Template

Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.

recombobulate @recombobulate · 1 month ago