Session Persistence via tmux Integration or cmux-server

[icedac]

Background

The primary reason people use tmux is not for pane splitting — it's for session persistence powered by the tmux
server architecture. Even after a server restart, plugins like tmux-resurrect can fully restore the last
window/pane layout, making it a critical workflow feature.

Proposal

Option A: Native tmux Session Integration (Preferred)

Allow cmux to attach to and manage existing tmux server sessions directly.

• List available tmux sessions and let users pick one to open inside cmux
• Preserve all the benefits of the tmux server (detach/reattach, background processes, session survival)
• cmux becomes a frontend to tmux rather than a replacement

Option B: Implement a cmux-server

If native tmux integration isn't feasible, cmux should implement its own persistent server daemon:

• cmux-server: A background process that keeps sessions alive independently of the terminal
• Session resurrection: Automatically save and restore the last window/pane layout on crash or restart (similar
  to tmux-resurrect)
• Detach/reattach semantics so users can disconnect and reconnect without losing state

Why This Matters

Without session persistence, cmux is limited to the lifecycle of a single terminal window. This is the single
biggest reason power users stick with tmux — not panes, not splits, but the guarantee that work survives
terminal closure.

[alexph-dev]

Totally supporting this idea. Had a similar, even gonna try to wrap each cmux panel into tmux so that when i ssh to my macbook - i can check all panels