Parallel Claude Code sessions

Run six Claude Code sessions in parallel.

Automatic git worktree isolation. Kanban session board. Per-session file traceability. Mobile review. Multi-session Claude Code work without the terminal-tab chaos.

Download

Also available for: macOS Apple Silicon macOS Intel Windows Linux

Nimbalyst — run parallel Claude Code sessions on a kanban board

Parallel Claude Code is the new normal.

Most Claude Code power users in 2026 run multiple sessions in parallel. A refactor in one. A feature in another. A bug fix in a third. The hard part is not the coding. It is the bookkeeping: which session is still running, which one needs input, which one already merged its branch, which files belong to which session.

Nimbalyst makes parallel Claude Code sessions tractable. Every session gets its own git worktree automatically. Every session is a card on a kanban board. Every session has a sidebar showing exactly which files it changed. You can run six sessions and still know what is going on.

Why Nimbalyst

What multi-session Claude Code needs

Session kanban: every session on one board

Six sessions on one screen. Drag between phases. Tag by type. Filter to find what is active right now.

Task kanban: tasks alongside the agents

Plans, bugs, features, and ideas live on their own kanban board next to your sessions. Drag tasks through their own phases. Link them to the sessions doing the work.

Automatic git worktree isolation

Each session runs in its own worktree and branch. Two sessions editing the same project at the same time cannot conflict in the working tree.

Per-session file traceability

Every session card shows exactly which files that session touched. Review the diffs inline before merging.

Link files to tasks to sessions

Files belong to tasks. Tasks belong to sessions. Click any file and see which task it serves and which session changed it last. The whole chain stays connected.

iOS app for mobile monitoring

Watch sessions, review diffs, and respond to agent questions from your phone while you are away from your desk.

Comparison

Parallel Claude Code: Nimbalyst vs terminal tabs

Feature	Terminal tabs	Nimbalyst
Session count	Limited by tab management	6+ tracked on a kanban board
Worktree isolation	Manual via git CLI	Automatic per session
Status tracking	Mental model only	Phases, tags, filters
File traceability	—	Per-session sidebar
Notifications when a session needs input	—	iOS push and desktop notifications
Mobile monitoring	—	iOS app

FAQ

Frequently asked questions

How do I run multiple Claude Code sessions in parallel?

In Nimbalyst, click new session for each task you want to run. Each session gets its own git worktree and branch automatically. They run independently and appear as cards on the kanban board. You can watch six or more at the same time without manual git or tmux setup.

Do parallel Claude Code sessions conflict?

Not in Nimbalyst. Each session lives in its own git worktree, so they cannot conflict in the working tree. They will only conflict at merge time if two sessions edit the same lines, which is the same merge conflict you would handle for two human contributors.

Can I see what each parallel session changed?

Yes. Every session card has a files-edited sidebar listing the files that session touched. Click into any file to review the diff inline. The traceability is per session, not just per branch.

How is this different from running multiple terminal tabs?

Tabs do not give you status, phase, tags, file-level traceability, automatic worktree isolation, or mobile access. The kanban board is the missing layer between the terminal and your project.

What models can run in parallel sessions?

Any model Claude Code or Codex supports. Mix Claude Opus and Sonnet sessions. Run a Codex session alongside two Claude Code sessions. The kanban board treats them all the same way.

Learn More

Nimbalyst is the open-source visual workspace for building with Codex, Claude Code, and more