Running 4 to 7 Claude Code sessions at once (14 at peak)
On 8 November a ps snapshot on my Mac showed 14 Claude Code sessions running. That was a peak. A normal day is 4 to 7.
I have 3-4 work projects and about as many personal ones. Any task that changes code or researches something goes to an agent. You don't need 14 sessions for this to get messy, though. Two sessions in two different projects are already enough for me to start losing track of the one that is waiting.
Where the time goes
Claude Code stops for three reasons: a permission prompt, a question, or a finished turn. All three mean the same thing: nothing moves until I look.
The finished turn is the sneaky one. A finished agent looks done, so it feels like nothing is owed. But nobody has read the result yet, and the session has no next task. An unread result costs the same as a waiting prompt.
Two people on r/ClaudeCode describe the same thing:
"I usually have 5 to 10 sessions going and kept losing the one that was waiting on me, so I ended up writing my own terminal."
"what broke wasn't the code, it was me forgetting which session finished an hour ago and has been waiting on me since"
One checkout, two agents
It has happened to me: two agents in one checkout, and a commit on the wrong branch. Now every session gets its own git worktree and its own branch. Without tooling, a new session means something like this:
git worktree add ../myrepo.worktrees/fix-auth -b fix-auth
cp .env ../myrepo.worktrees/fix-auth/
cd ../myrepo.worktrees/fix-auth && claude
git does not put untracked files like .env into a new worktree, so without the cp line the agent starts in a checkout that cannot run the app. Two dev servers from two worktrees also want two different ports.
What I tried first
Terminal tabs. Inconvenient, and the UI doesn't help. To get what I needed I had to stack several programs on top of the terminal, and I still couldn't see plan limits, files, or projects grouped together.
Tools built on tmux. I tried several and stopped using them for the same reasons. In some of them the text output broke (rendering glitches). tmux itself shows you the panes, but it can't tell you which agent is blocked on a question. Tools built on it guess from the screen (capture-pane and pattern matching), and a permission prompt and an idle prompt can look alike, while the agent's interface changes from one release to the next.
VS Code with the Claude Code extension. This was my main tool for a year. I dropped it for two reasons. Every project is a separate window, so I couldn't see several sessions at once. And the memory: with 2-4 projects open, each VS Code window took 1-2 GB. When I was building a game in UE5, 32 GB of RAM was not enough.
The rules I keep
They hold no matter what you run the agents in.
- One session, one worktree, one branch. Quick tasks too.
- Unread counts as waiting. A finished turn counts as waiting until someone has read the result.
- Only a status you can trace. Is a
runninglabel worth anything if you don't know where it comes from? No. It sends you back to the pane, and then it saved you nothing. - Closed is not lost. A closed session resumes later, so closing one doesn't cost the conversation.
What I built for it
I wanted one app that does this without a pile of extensions: easy control, plan limits in view, and as little of the machine as possible. Splitlane is a desktop app where each agent runs in a real terminal pane and the app shows which session is waiting for you (full disclosure: my project, free, GPL-3.0-or-later).
npm test. The rail, its pane header and the title bar all say so.Because of rule 3, the status source matters most. As of November 2026, for Claude Code and Codex it is read from the agent's own records and the process tree under the pane, not from what the terminal shows. The trade-off: that covers two agents only, and every change to their record format means checking again. Eight more agents report through hooks.
⌥⇥jumps to the next session waiting for me. A finished run I haven't looked at stays marked until its pane is on screen.- Every new agent session in a git repository gets its own worktree, branch,
.envcopy and ten ports inSPLITLANE_PORT. - A paired phone shows the same list with a Needs you section on top and can answer a permission prompt. I use it when I'm away from the desk.
Plan usage and the sessions that don't fit the pane grid sit in the sidebar. I haven't measured its memory against VS Code, so there is no number here.
What doesn't work yet
- The last six agents (Copilot, Kiro, Factory, Antigravity, Openclaw, Amp) have no status beyond "process is alive", so their row can say
runningwhile the agent is waiting for you. - Local only, no SSH. On a remote box, tmux or herdr will fit better.
- Release builds are macOS (Apple Silicon) and Linux; Windows builds only from source. I use it daily on macOS; Linux has had far less hands-on use.
If you keep several agents running some other way, I'd like to hear how you notice the one that's waiting.