Home / multiple sessions
How to run multiple Claude Code sessions at once
One session is easy to follow. Five are not. Here is how to run several at once, how to keep them from editing the same files, and how to keep track of them.
Step 1: open one terminal per session
Each terminal tab or window can run its own claude session. Open a second tab, go to your project and start another one.
cd ~/code/myrepo
claude
There is one catch. Sessions in the same folder edit the same files. So two sessions changing code in the same folder can get in each other's way.
Step 2: give each session its own checkout
A git worktree is a second checkout of the same repo. Each session gets its own folder and its own branch, so parallel sessions don't edit the same files.
git worktree add ../myrepo-feature -b feature
cd ../myrepo-feature
claude
Do this once per task. List your worktrees with:
git worktree list
When a task is done and merged, remove its worktree:
git worktree remove ../myrepo-feature
Step 3: let a session start subagents
Claude Code can also start subagents inside one session. This is another way to do several things at once without opening another terminal. You stay in one session, and it hands parts of the work to its helpers.
Watch the shared limit
All sessions on one plan draw from the same 5-hour and weekly limits. More sessions use the limit faster. Three sessions running at once do not get three limits. They share one.
If you want to see where you stand, run /status in Claude Code. See the usage limits guide for the details.
The hard part is keeping track
After a few tabs, you lose the thread. Which session is waiting for you? Which one is still reading files? Which one spawned that subagent? You end up clicking through tabs to find out.
See every session on one map
Orbiterm shows all of it in one window. Every session is a planet on the orbit map. Subagents, tool calls and the files they touch fly between the planets.
- Session cards show each session's prompt, last tool call, context bar and spend.
- Subagent worker cards show who spawned it, what it is reading and how long it has run.
- The top bar shows your 5-hour and weekly limits, always on top.
Orbiterm runs Claude Code, Codex and Antigravity side by side. It also works with Gemini CLI, OpenCode, Aider, Cursor's agent and Copilot when they run in a terminal. It reads the AI tools' own local logs, read only. Prompts, code and file names stay on your machine.
Streaming your screen? Party mode fills the map with made-up sessions and hides real project names.
FAQ
Can two Claude Code sessions work in the same folder?
Yes, but they edit the same files. Give each session its own git worktree so they don't step on each other.
Do more sessions use my limit faster?
Yes. All sessions on one plan draw from the same 5-hour and weekly limits, so more sessions use the limit faster.
What is the difference between a session and a subagent?
A session is one claude process in one terminal. A subagent is started by Claude Code inside a session.
Get Orbiterm — free for macOS and Windows
Free desktop app for macOS 13+ (Apple Silicon and Intel) and Windows 10/11 64-bit. No sign-up, no paid tiers.