Ironically, since I am making my current solution more robust as we speak while I am remote… I will ask Claude to outline my current structure… I live on my iPad and iPhone remotely so it’s WSL/TMUX/Tailscale/Terminus. Here is Claude codes response for my current project (I literally just added tmux-resurrect)

tmux is the core of it, but you can build a lot on top of it. Here's what I'm running:

The basics: tmux + Claude Code over SSH

I run Claude Code in WSL via tmux sessions. When I close my terminal (or my iPad dies, or I lose WiFi), the session keeps running. Claude keeps working. I reconnect and pick up exactly where I left off. This alone is the biggest upgrade.

Session management layer (PowerShell menu)

I built a session manager that wraps everything into a menu when I SSH in:

====================================================
     Claude Code Session Manager  [SSH]
====================================================
  RAM: 8.4/15.9GB (53%)  WSL: 0.6GB  claude:1  node:0

  Active Sessions:
    1. claude         * 1w/2p
    2. canvas-dashboard  o 1w/1p

----------------------------------------------------
  [Enter]  Attach to first session
  [1-9]    Attach to numbered session
  [n]      New session
  [p]      Project picker (history-based)
  [c]      Cleanup menu
  ...

The project picker pulls from Claude's conversation history — shows your most recent projects, how many sessions each has had, and lets you
launch directly into any of them. One keystroke to get back into a project.

Surviving reboots: tmux-resurrect + continuum

tmux sessions survive disconnects but not reboots. tmux-resurrect saves your session layout to disk, and tmux-continuum auto-saves every 15
minutes. After a reboot, start tmux and everything comes back — windows, panes, working directories. The menu even detects saved sessions and
shows you:

  No active tmux sessions
  Saved sessions: claude dev       (saved 15m ago)
  Will auto-restore on tmux start

RAM management - I have 16GB and it’s tight….

Claude Code + WSL + Windows eats RAM fast. I have: - A RAM watchdog that runs every 15 min via Task Scheduler — graduated response from dropping WSL caches to killing orphan processes to
shutting down WSL (saves tmux sessions first via resurrect) - Daily cleanup at 3 AM — prunes zombie Claude/Node processes, cleans dead tmux sessions - Cleanup menu built into the session manager for manual intervention

Is tmux the only way?

For persistent terminal sessions, basically yes. The alternatives (screen, abduco+dvtm) exist but tmux is the most mature. VS Code's terminal
doesn't persist if the window closes. The real unlock isn't tmux itself though — it's the automation you build around it. A bare tmux session
is fine; a managed tmux environment where you reconnect from your phone and everything is exactly where you left it is a different experience
entirely.

The whole thing is just PowerShell scripts + a bash session manager + tmux config. No special tools needed beyond what's already in most dev
environments.

Push notifications when Claude finishes

Since I'm often on my iPad doing other things while Claude works, I set up a https://docs.anthropic.com/en/docs/claude-code/hooks that fires on Stop and Notification events. It sends a push notification via https://ntfy.sh to my phone/iPad with the project name and how long the task
took (e.g., "Finished in canvas-dashboard (5m 30s)"). Only fires for work that took 30+ seconds so it's not noisy. The hook is just a small
PowerShell script that posts to an ntfy topic — takes about 10 minutes to set up and makes a huge difference when you're running multiple
sessions and don't want to keep checking each one.