tmux/claude: restore Claude sessions on tmux-resurrect (claude --resume) #8

Open
opened 2026-06-03 18:19:36 +00:00 by jmz · 0 comments
Owner

Context

@continuum-restore on + tmux-resurrect restore window/pane layout after a
reboot, but not the Claude processes — restored panes come back as a bare shell.

Proposal

Persist each window's Claude session id and, on resurrect restore, relaunch
claude --resume <id> in the matching pane so a reboot brings the whole working
set back.

Implementation sketch

  • On session start (a Claude hook), stash the session id in a tmux user option on
    the pane/window (e.g. @claude_session_id) — resurrect can persist user
    options via its save hooks.
  • Provide a resurrect restore hook / resurrect-processes strategy that, for
    panes tagged with @claude_session_id, runs claude --resume <id>.
  • Investigate resurrect's custom-command capture vs. a post-restore script.

Effort

Medium–large; needs verifying resurrect's user-option persistence and process
restore hooks. Lower priority than the attention-routing bundle.

## Context `@continuum-restore on` + tmux-resurrect restore window/pane *layout* after a reboot, but not the Claude processes — restored panes come back as a bare shell. ## Proposal Persist each window's Claude session id and, on resurrect restore, relaunch `claude --resume <id>` in the matching pane so a reboot brings the whole working set back. ## Implementation sketch - On session start (a Claude hook), stash the session id in a tmux user option on the pane/window (e.g. `@claude_session_id`) — resurrect can persist user options via its save hooks. - Provide a resurrect `restore` hook / `resurrect-processes` strategy that, for panes tagged with `@claude_session_id`, runs `claude --resume <id>`. - Investigate resurrect's custom-command capture vs. a post-restore script. ## Effort Medium–large; needs verifying resurrect's user-option persistence and process restore hooks. Lower priority than the attention-routing bundle.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jmz/dotfiles-public#8
No description provided.