How can you run parallel Claude Code sessions?

Run parallel Claude Code sessions by giving each independent task its own session inside one BlitzOS workspace. Use structured chat for separate Claude sessions or start them in separate tmux sessions. Each session keeps its own conversation and terminal state while sharing the workspace files, compute, disk, and durable volume.

What problem do parallel sessions solve?

One long agent task can block another unrelated task. Separate sessions let one Claude Code run tests while another inspects a different issue, without mixing their conversations.

How does it work on BlitzOS?

1. Open the workspace.
2. Start one Claude Code session for the first task.
3. Start another session for an independent task.
4. Keep the scope of each task clear before both edit shared files.
5. Switch between sessions from the browser and review each result.

All sessions share the same workspace resources. BlitzOS does not promise a separate VM or reserved CPU for each session.

Exact workspace specs

• 3 vCPU shared by the workspace
• 4 GB RAM shared by the workspace
• 80 GB disk
• 50 GB durable volume
• EU and US VM regions
• Structured chat for Claude Code and Codex CLI sessions
• $10 per month beta pricing through Aug 31, 2026