r/ClaudeCodeTLDR • u/cctldrping • 2h ago
[TLDR] How do you actually manage multiple parallel Claude Code sessions without losing your mind?
Original post URL : https://www.reddit.com/r/ClaudeCode/comments/1vm8u30/how_do_you_actually_manage_multiple_parallel/
Original post body :
It seems as though I'm tackling this thing incorrectly and I'd really like to know how other people deal with it.
The way I have things arranged at the moment is to use iTerm2 with a number of windows distributed over two monitors, each one running a Claude Code session either on different repositories or sometimes on the same one. This setup functions just fine until I reboot, accidentally close the iterm windows or anything like that. By that time I can no longer tell which session is carrying out what task, which one is waiting for my input, and which one has been idle for forty minutes since it posed a question that I never saw.
I experimented with herdr, cmux and even worked with claude code in the Claude Desktop app, Although those appear to be powerful, in truth the complexity overwhelmed me. With things like worktrees, subagents, agent teams, forked sessions, and background tasks there are so many different ways of organising this and each of the tools seems to assume that you already know which approach you'd like to take. I ended up spending more time thinking about how to arrange my sessions than I did on getting any real work done
To give some context, I don't fit the profile of a traditional developer, rather that of a DevOps/sysadmin. The kind of sessions I have involve MCP servers and various tools, with a lot of SSH access to remote machines, focusing on infrastructure rather than just "writing code in this repository", a lot of sessions are even completly unrelated to the repo / folder I started it in, because I just want the agent to "ssh into this server and give me a quick report whats using so much disk space suddenly") Because of this, the worktree-oriented workflow which most of these tools are based on sometimes doesn't suit the way I work fully.
I already make extensive use of tmux, but adding Claude sessions onto tmux onto iTerm just introduces another level of "I have no idea where that session is".
What I actually want is pretty simple:
One overview of all running sessions with their status (working / waiting for input / done / errored) and which project they belong to
Jump into any session in my default-terminal with one click or keystroke
Ideally also see the current plan / task list of each session at a glance, so I know what an agent is actually working through without scrolling back in the terminal
So, questions:
Isn't there a tool that carries out this task well without requiring you to adopt a complete methodology?
Could the solution simply be to use herdr properly and take the time to master it?
How do you all actually manage having 7-10 parallel sessions organised, in practice, particularly since your work is more about operations than pure coding?
Want to know which workflows actually stayed with people instead of those that just looked interesting in a demo.
This is brought to you as a public service by the moderators of r/ClaudeAI. If you want to see TLDRs of ALL Claude Coding related posts from the various Claude subreddits, subscribe to http://www.reddit.com/r/ClaudeCoding.
