AgentOSAgentOS

Orchestration

Spawn worker sessions for parallel feature development.

AgentOS supports a conductor/worker pattern for parallel development.

How It Works

A conductor session can spawn worker sessions, each with its own:

  • Git worktree (isolated branch)
  • Environment setup
  • Dev server port

Workers run independently while the conductor coordinates.

Creating a Conductor

  1. Create a new session
  2. Enable Conductor mode
  3. The session gets access to orchestration tools

Spawning Workers

From a conductor session, use Claude Code to spawn workers:

Spawn a worker to implement the auth module

Claude uses the spawn_worker MCP tool to:

  1. Create a git worktree with feature/{task} branch
  2. Copy environment files
  3. Run package install
  4. Start a new terminal session

Viewing Workers

Workers appear nested under the conductor in the sidebar:

📋 Conductor Session (3 workers)
   └─ Worker: auth-module
   └─ Worker: api-endpoints
   └─ Worker: unit-tests

Click the conductor to toggle between:

  • Terminal view - Conductor's terminal
  • Workers view - List of worker sessions with status

Worker Status

Each worker shows:

  • Current status (running/waiting/idle)
  • Branch name
  • Last activity

Getting Worker Output

The conductor can check worker progress:

What's the status of the auth-module worker?

Claude uses get_worker_output to fetch the worker's terminal output.

Killing Workers

Workers can be killed individually or all at once:

  1. Click the worker in the sidebar
  2. Select Kill Worker

Or from the conductor:

Kill all workers

MCP Configuration

AgentOS auto-generates .mcp.json for conductor sessions with these tools:

ToolDescription
spawn_workerCreate a new worker session
list_workersGet all workers and their status
get_worker_outputFetch terminal output from a worker

Use Cases

Parallel Feature Development

I need to build a dashboard. Spawn 3 workers:
1. API endpoints for data fetching
2. React components for the UI
3. Unit tests for both

A/B Testing Approaches

Spawn 2 workers to try different approaches:
1. Worker A: Use Redux for state
2. Worker B: Use Zustand for state

Divide and Conquer

This refactor is large. Spawn workers for:
1. Migrate user module
2. Migrate product module
3. Migrate order module
4. Update all imports