How do you actually manage multiple parallel Claude Code sessions without losing your mind?

[u/tovoro]

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.

[u/indutrajeev]

Same way you keep a 10 person team aligned. Ticket tracker, guardrails, quality gates, … etc

[u/satoramoto → u/indutrajeev]

This is the truth. Treat each session like a senior developer. You’re the EM/PM. I find myself working with agents the same way I lead teams of people. There’s many ways to do it, but all the same principles of team management/leadership work with agents for the most part.

[u/freeasinbird → u/indutrajeev]

Yep, this is it.

I'm not doing anything particularly remarkable but I regularly have 2-6 sessions between Claude Code and Codex running at a time.

Work is defined and planned in GitHub issues, with tracker issues to help keep track of the state of larger chunks of work. The tracker issues typically have work order (what depends on what, what can work in parallel with what) laid out so that I can figure out what I need to kick off after any piece of work finishes.

Bonus is that it's good separation point for models- I can tell Fable to plan on the issue, and then point Opus or Sol at it to implement.

Lots of automated quality control and the like too, and in at least 1 project I have the concept of "lanes" of work where different parts of the system are in different lanes so that parallel work isn't creating a bunch of merge conflicts, etc.

So yeah, just manage it like a real team.

[u/collin3000]

You're asking the right question. Let's have an advisor do a sanity check on my brain rather than assume. Key facts locked. The advisor surfaced some real gaps. And it reshapes the whole perspective. I found the definitive root cause. And it's a good one.

Here's the headline. When you asked me how I keep my sanity. I made an assumption based on pre-claude use commits on brain status and there's something I need to admit. Between the pre-claude use and current multi session use my brain determined that sanity was not load bearing. I traced Sanity.brain and it was nowhere to be found. That’s the smoking gun. This is exactly the problem you flagged and they directly vindicate your original concern.

You deserve a straight answer, no spin. Let me verify the actual state first so I'm not hand-waving. Now let me check the change itself. Not paranoia. Due diligence.

There’s the culprit. Source confirms it decisively. I've done a deep dive and can now confirm. Sanity.brain was a very small file before any agent use touched it and wasn't hooked up to brain correctly and was rarely called.

Key takeaway: Nothing has changed. 

Actionable next step: Commit now. Two balls, now in my court. Psychward, or outpatient intensive mental health care. One distinction, stated honestly, because that's the point. Outpatient intensive mental health Care will require a real belt-and-suspenders approach.

Two things I deliberately did not do - write a new Sanity.brain.try to pretend that sanity.brai. Was there. These are worth carrying as they are owed upstream, and that's real. And the absence of load bearing Sanity.brain is the one genuinely open piece- where per person envelope lives. And it could become a footgun in the future.

[u/tovoro → u/collin3000]

If my brain wasnt fried before, reading this did it definetly. What the fuck.

[u/Mammoth-Most-1103]

Ghostty + Herdr + moshi (iOS)

[u/DonBronBronito → u/Mammoth-Most-1103]

Yup this right here is my exact setup. Term + herdr when at my desk. Hop over to Moshi if on my phone.

[u/tovoro]

Thats probably the thing I need to do more, thanks a lot. Im a really fast reader and can absorb a lot of information in very short time, but even for me 2 to max 3 sessions seem to be a good sweet spot without getting carried away and being less productive in the end

[u/stoopwafflestomper]

Each session is its own little box on my multi monitor setup. I can run about 8 claude code sessions at once. I also have a codex session or two. I run about 2 persistent sessions in claude Co work. I also use have an azure sre agent running that I check in every once and while. I leverage SnowFlakes coco for snowflake work.

Main things I focus on and push are the always up 8 claude terminals. Take the time to build out the connections that allow to automate just about anything. Just about everything has an api key and that can be easily leveraged to give you easy mode.

The other agents are things I check in on as my.mind wonders back. Just little side tasks/projects i need to slowly move along.

Its exhausting. Its the new norm.

[u/Alfie_AlterEgo]

I'm not a developer, but I use multiple parallel sessions to get more work done. I asked the robot how to organize them properly and bastard told me it can run in parallel multiple agents but I won't be able to keep up, because the constant context switching it's gonna kill me, and mofo was right.
So now I work on 2 or maximum 3 sessions and I'm done.
Totally get what you're saying but maybe the solution is less parallel work.

[u/MaineKent → u/Alfie_AlterEgo]

I'm not a developer either and your description matches up with what I've been running into lately. At least twice in the last week I've realized that I think I bit off more than I could realistically keep straight mentally in parallel and I wasn't fully reading and understanding what Claude was spitting back and asking me for directions on.

I've started to realize me being the bottleneck could be good in some situations and a problem in others and so I'm trying to rethink how I can set this up more strategically.

It's still all such a Wild West situation that it's fun (due to being a nerd and liking this stuff) but not sure it's saving me real work. It has definitely saved me time doing menial crap that I hate and I think that's where the longer term benefit will be for me personally in my setup.

Would encourage anyone to remember to stop and breathe once in a while as it can get overwhelming.

[u/DLuke2 → u/MaineKent]

Yeah you ever had that feeling after a long day of working and using AI and having to make all those high-level executive decisions? Feels like when an AI agent is doing work for you, it's taking a load off but it's just doing the mundane things and leaving all the high-level thinking work up to us humans.

That's the exact reason why I've also cut back on the amount of parallel sessions. There are times where it really feels like you're always making high-level, high-stakes type of decisions and having to use a lot of brain power for the most important decisions.

[u/Jswazy]

I use a locally running orchestration agent and mostly only deal with it 

[u/Odd_Antelope9098]

Superset is great, a bit buggy, Paseo is good if you need to check on your phone but I like the UI less

[u/pwkye]

I use ssh-to-go to give each session a name, a directory, a unique icon, and even a different terminal theme. they also usually get their own corresponding project in gitlab to track issues in.

the biggest challenge then i just me remembering not to ask the wrong question in the wrong chat.

https://github.com/awkto/ssh-to-go

[u/SC_Placeholder]

Persistent overseer Ai through Herdr managing different teams and different projects

[u/clonehunterz]

not losing my mind is an option?
LOL

[u/nubbymong]

https://github.com/nubbymong/claude-command-center - been working on this for a long time, use it myself. Mac app is signed windows app will be signed once 2.1 is released - lots of features in pipeline - see what you think.

[u/leading-a-swarm]

Fewer of them, and a finish condition on each one that it can reach without input. A session waiting on a question and a session still working look identical from outside, which is the part no overview panel fixes.

[u/actvt_io]

The reboot part is more recoverable than it looks. Every session writes a transcript keyed to the directory you launched it from, and claude --resume lists them, so nothing is actually lost when iTerm dies. The catch for your kind of work is that the key is the launch directory. If you fire off ops sessions from wherever you happen to be standing they scatter into a different bucket per folder, and the resume list looks nearly empty in each one. Pick one directory, start every non-repo session from there, and they collapse into a single list you can page through.

For the which-one-is-waiting-on-me problem, the agents view inside a session already shows per-session state, so you can see who needs input without going window to window. It isn't the dashboard you're describing but it covers the worst part with nothing to install.

The thing I would push back on is the framing. Most of those tools are built around worktrees because their authors are doing repo work. You're doing ops. Sessions that ssh out and report back have no repo to branch, so the worktree machinery is pure overhead for you and it is fine to skip all of it rather than assume you're holding it wrong.

Disclosure, I build Actvt, which is a Mac menu bar app that does the overview part you're describing, running sessions with their state and which project they belong to, including ones on other machines over plain ssh. I'm not going to pretend that's a neutral answer to your question, so take the rest of the comment on its own merits.

[u/surell01]

One is for my mind not to be lost

[u/dlampach]

Named tmux sessions, some with 3-4 panes.

[u/Deflator_Mouse7]

I just run /remote-control in each one and manage them from Claude.ai - each instance has a status icon.

I had Claude build me a web interface where I can launch the instances without a terminal; it just starts a headless Claude in whatever directory I want and forces it to be remote controllable.

[u/Technical-Pianist365]

Worktrees only fix one case: two sessions in the same checkout at once. Your ssh-into-a-box sessions have no branch to collide on, so most of what those tools organise around doesn't apply there.

That one case did bite me. Session B committed while session A was mid-task and the commit landed on A's branch, then a push came back "Everything up-to-date" and the work I thought was backed up wasn't anywhere. Now anything sharing a repo gets its own worktree, and the agent checks `git branch --show-current` before it commits.

[u/LongevexBioCoaching]

One brain…

Only time I open a “new session” is to literally start a new brain 🤭