Claudeverse – Mission Control for Parallel Claude Code Workers

Claudeverse — Mission Control for Claude Code

Invite-only beta · macOS · iPad mirror

Mission Control

for Claude Code.

Developers are becoming managers of parallel AI workers.

Assign, monitor, and approve work across multiple Claude workers from a single command center. Mirror the workforce to an iPad over your local WiFi — step away from the desk, stay in command.

Request beta invite

Why this exists ↓

macOS 13+ · Apple Silicon & Intel · Requires Claude subscription

The shift

5 Claude sessions open.

0 idea what's happening.

Running Claude in parallel is already how you work. The tooling just hasn't caught up.

Today — iTerm2 + tmux

5 sessions. 0 awareness.

Which one needs you right now?

$ claude --resume…

running tests

awaiting input

$ claude

refactoring auth

…

$ claude

approval needed

waiting…

$ claude

writing docs

Tab-switch. Squint. Repeat.

With Claudeverse

5 workers. 1 command center.

One needs review. The rest are running.

backend-refactor Working

auth-migration Requires Review

docs-rewrite Working

pipeline-ci Working

spike-streaming Idle

Glance. Approve. Back to work.

No telemetry · No cloud · Everything stays on your machine · macOS only

The bottleneck moved

Generating code isn't the problem anymore.

Claude solves the typing part. The new bottleneck is everything else.

Attention

What is each worker doing right now?

Orchestration

Who works on what, in what order, with what context?

Approvals

Which decisions need a human signature, and when?

Coordination

How do parallel workstreams stay coherent?

Context Management

What does each worker know, remember, and share with the others?

Claudeverse is the command center for managing all of it.

Built for the manager-of-workers workflow

Run a workforce, not a window-juggling act.

Every feature is designed to reduce managerial overhead.

Parallel workforce

Run as many Claude workers as you want. Each gets a stable identity, its own context, and survives restarts.

Worker escalation

Deterministic status detection drives macOS notifications and a dock badge the moment a worker needs you.

Review queue

Approvals from every active worker surface in one place. Resolve them in batches without context-switching.

Traceability layer

Knowing a worker is done is table stakes. Knowing why it's stuck is the real value. Every worker's thought process is auditable in one timeline.

Command center

Every active worker, every state, every approval — one frame. Switch into any worker's terminal in a single click.

MCP profile management

Configure MCP servers globally or per-worker without touching ~/.claude. Toggle tools per worker independently.

Token oversight

Live input + output tokens per worker, plus lifetime totals across your workforce. Know what every worker is spending.

Full TUI fidelity

PTY-backed xterm.js. Slash commands, plan mode, approvals, image paste — every Claude CLI feature works exactly as you expect.

Model-neutral engine Soon

The orchestration layer is model-neutral by design. Compare a Claude worker, a Gemini worker, and a local Llama worker — same workspace, same command center.

Remote oversight

Step away from the desk. Stay in command.

Mirror the full workforce to an iPad over your local WiFi. Watch every worker live, approve from the couch — nothing leaves your network.

iPad command center, not desk anxiety.

The whole workforce streams to an iPad over your local WiFi. See every worker's state at a glance, drop into any terminal, approve a stuck worker — without going back to the desk.

iPad command center

Scan a QR in Safari — no app to install. The full workforce streams live over your local WiFi.

Local network, no cloud

Mirror happens entirely on your LAN. Nothing touches a third-party server.

Beyond Claude

Your tools will change.

Your command center shouldn't.

The model wars are still being fought. Whoever wins a year from now, you keep your workforce and the workflow you built around it.

One workspace

3 vendors

backend-refactor claude · sonnet Working

schema-review gemini · 2.5-pro Working

log-parsing llama · local Working

Cross-model review

Have Claude review what Gemini wrote. Catch hallucinations and disagreements before they ship.

Capability routing

Long-context jobs to one model. Throwaway scripts to a local one. Spend where it matters; save where it doesn't.

Vendor independence

If pricing changes, a competing tool ships, or the API shifts under you, your workflow doesn't break.

Anthropic will only ever manage Claude workers.

Claudeverse manages your AI workforce.

Engine is model-neutral by design today. Multi-vendor UI ships post-MVP1.

Invite-only beta

Join the private beta.

Claudeverse is invite-only while we polish the first release. Drop your email and we'll send you an invite code.

Claudeverse Command

macOS · iPad command center

Beta access

Request an invite

We'll send an invite code once a spot opens. No spam, no marketing — just your code.

What's inside

Unlimited workers & workspaces

macOS escalations + dock badge

iPad command center (mirror over local WiFi)

Traceability layer (full execution timeline)

MCP profile management

Have an invite code?

Questions

What is Claudeverse, in one sentence?

It's the command center for developers who run multiple Claude workers in parallel. Assign work, watch progress across all of them in one frame on your Mac — and mirror the whole workforce to an iPad over your local WiFi.

How is this different from running Claude in a few iTerm2 tabs?

iTerm2 organizes terminals. Claudeverse coordinates workers. The difference is everything: persistent identity across restarts, deterministic status detection, one-place approvals, an iPad mirror so you can step away, an execution timeline that tells you why a worker is stuck — not just that it's stuck. Tab-juggling stops being the workflow.

What if Anthropic builds their own multi-session orchestrator?

Anthropic will manage Claude workers. Claudeverse manages your AI workforce — across vendors. The engine is model-neutral; you can spawn a Gemini or local Llama worker in the same workspace. Plus the depth surfaces (iPad mirroring, traceability timeline, MCP profile management, native macOS craftsmanship) live a layer above where any model vendor will prioritize.

Do I need a Claude subscription?

Yes. Claudeverse wraps the Claude CLI, so you need either a Claude Pro / Max subscription or Anthropic API access. Claudeverse itself doesn't make API calls — it doesn't add to your Claude bill.

What Mac do I need?

macOS 13 Ventura or later on Apple Silicon (M1/M2/M3/M4) or Intel. Claudeverse is macOS-only for now — Windows and Linux are on the roadmap.

How does iPad command center work?

Claudeverse runs a lightweight local server on your Mac. Scan a QR code in Safari on the iPad — no app to install. The workforce streams over your local WiFi. Nothing leaves your network.

Is Claudeverse affiliated with Anthropic?

No. Claudeverse is an independent product built on top of the Claude CLI. It is not made by, endorsed by, or affiliated with Anthropic.

Does Claudeverse collect any data?

No telemetry, no usage data, no conversation content ever leaves your machine. Everything is stored locally in SQLite. We never see your prompts or Claude's responses.

The shift is already happening

Developers are becoming

managers of parallel AI workers.

Claudeverse is the command center for the new workflow. Request a beta invite while the program is still open.

Claude Code gave developers workers. Claudeverse gives them command.

Request beta invite →