Zoku
← Blog

Guide

Run multiple Claude Code agents on Mac without the tab chaos

By Priyanshu Dangi · Jul 31, 2026 · 7 min read

How to run several Claude Code sessions in parallel on git worktrees, when a free launcher is enough, and when a voice-first canvas like Zoku earns its keep.

Running multiple Claude Code agents on a Mac means giving each session its own working tree — usually a git worktree on its own branch — so agents do not overwrite each other's files. The hard part is not starting the second agent; it is steering five of them without becoming the scheduler.

Why one Claude Code session is not enough

One agent is fine until you have four tickets queued behind it. Opening five Terminal tabs works for an afternoon. Then you lose which pane is auth, which is stuck on a permission prompt, and which finished ten minutes ago while you were reading a diff.

The primitive: one worktree per agent

Before any UI, the isolation rule is simple:

  1. One feature → one branch → one worktree folder
  2. One Claude Code (or Codex / Cursor) process in that folder
  3. Separate PRs when you merge

Minimal setup:

git worktree add ../my-project-auth -b feature/auth
git worktree add ../my-project-billing -b feature/billing

# terminal 1
cd ../my-project-auth && claude

# terminal 2
cd ../my-project-billing && claude

That is enough to run two Claude Code agents in parallel without git fights. Details and cleanup live in the worktrees guide.

When free tools are enough

If your pain is only “spawn agents on worktrees and see them in a list,” a free launcher in the Conductor / Vibe Kanban class may be all you need. Use one. See the comparison of parallel-agent tools for an honest breakdown.

When babysitting becomes the product

You outgrow tabs and basic launchers when:

  • Redirecting an agent costs a hunt for the right pane
  • You cannot tell Working from Needs you without staring at output
  • You want to talk to an agent while another app is focused
  • You want one agent to spawn another (plan → review) without brokering it

That is the job Zoku is built for: a Mac canvas of named agent terminals, on-device voice from any app (⌥⌘), lifecycle status from agent hooks, and a zoku CLI so agents can hire each other. One-time Lifetime license — it runs the claude binary you already pay for.

Example voice workflow with Zoku

  1. Hold ⌥⌘ and say: “open a Claude worktree named auth-fix”
  2. Later: “tell Atlas to run the tests” (agents answer to names)
  3. When one blocks: Zoku chimes — Needs you — even if the window is closed

Play with the interactive canvas on the homepage before you buy. No self-serve free tier; Lifetime is $49 once during early access.

TL;DR

  • Parallel Claude Code = one worktree per agent
  • Free launchers are fine if spawn + board is enough
  • Zoku is for voice, names, status, and agent-to-agent control after that

Related