Show HN: Ccmux – Reduce context switching for parallel Claude Code sessions

[raykamp]

I’ve been running parallel Claude Code instances while working on different tasks. Two problems kept slowing me down:

  1. I was constantly jumping between terminals to see which session needed input.

  2. Using git worktrees added setup friction (installing deps, bootstrapping environments, etc.), which discouraged parallel work.

So I built ccmux.

It’s a thin layer on top of tmux that:

  - Adds a glanceable sidebar UI showing all Claude Code sessions

  - Surfaces attention-needed states with visible alerts

  - Wraps git worktrees with a lightweight workflow abstraction so spinning up parallel tasks feels cheap

Technical details:

  - tmux provides the pane/session orchestration

  - The sidebar is built with Python’s Textual (rich TUI)

  - Each Claude Code session runs as a window in a nested tmux session.

I now use it daily to juggle multiple AI coding sessions without losing context. Happy to answer questions or dive into implementation details.

[jlongo78]

Parallel agent sessions get unwieldy fast. One pattern that helps: treat each session as a named unit tied to a specific task scope, not just a terminal tab. When you can search past conversations by content rather than scrolling history, context recovery after switching becomes trivial. Also worth considering persistent session replay - being able to rejoin a long-running agent mid-task without re-prompting saves significant time across a workday.

[raykamp]

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.

[JPHutchins]

Cool! I think that the git worktrees are essential for efficiently working on simultaneous tasks in one repo, and anything to lower the friction is welcome.

[raykamp]

Agreed! Before using ccmux I essentially abandoned using worktrees on certain projects because the setup and teardown was too cumbersome.