3 ms·

Hey jlongo78, thanks for the feedback and insights. "persistent session replay" are you meaning more of a "resume" than "replay" ? I'm a little bit con

by raykamp 7mo ago

Hey jlongo78, thanks for the feedback and insights. "persistent session replay" are you meaning more of a "resume" than "replay" ? I'm a little bit confused by the description, but curious to understand. If I'm understanding it correctly, I think you'll appreciate what ccmux offers for streamlining the switch/resuming sessions: a sidebar that shows ongoing tasks that can be named. Each one requires just a mouse click or key binding to switch into.

jlongo78 7mo ago
[flagged]
- raykamp 7mo ago
  Mind if I ask what line of software you work in? The ccmux sessions are tied 1-to-1 with claude code sessions. If a the ccmux "workspace", ccmux's tmux session, gets killed or a user intentionally kills/deactivated a ccmux session, it can be reactivated easily. Under the hood it's just ccmux tracking claude code session IDs and attempting to resume said session when reenabling. Your input has me thinking there could be a couple features to consider: - A search feature to search through all claude code sessions and resurrect one as a ccmux session. - Right now ccmux sessions have two things to quickly indicate their specific task/intention: a configurable name and they clearly show the git branch name they have checked out. I originally opted for this very lightweight approach, but perhaps more context is required about the task at hand, especially for long-running multi-day sessions.
  - jlongo78 7mo ago
    [flagged]
    - raykamp 7mo ago
      OK, that's great input. Expanding on that idea, the short freeform note/summary could be optionally auto generated and continually maintained (if scope shifts) by the Claude session. Akin to AI summarizing changes and writing git commits for us.
      - jlongo78 7mo ago
        [flagged]