> ## Documentation Index
> Fetch the complete documentation index at: https://docs.claboard.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Orchestration View

> Mission control for multi-agent parallel execution with DAG graph, timeline, and live observability

The Orchestration View is your mission control for managing multiple Claude agents running in parallel. It provides three viewing modes: dependency graph, execution timeline, and live observability dashboard.

## View Modes

Switch between modes using the toggle buttons at the top right of the orchestration view.

<Tabs>
  <Tab title="Graph">
    Interactive SVG dependency graph showing tasks as nodes and dependencies as directed edges. Nodes are color-coded by status: gray (backlog), amber (in progress), green (done). Running tasks pulse with an animated progress bar.

    **Conditional edges** are color-coded:

    * **Gray solid** — Always (default dependency)
    * **Green dashed** — On Success (runs only if parent succeeds)
    * **Red dashed** — On Failure (runs only if parent fails)
  </Tab>

  <Tab title="Timeline">
    Gantt-style horizontal timeline showing when each task started, how long it ran, and wave groupings. Features include:

    * Auto-scaling time axis (minutes/hours/days)
    * "NOW" marker (red dashed line)
    * Running task bars with pulse animation
    * Hover tooltips with token/cost/model info
    * Dependency edge overlays with conditional coloring
  </Tab>

  <Tab title="Live">
    Real-time observability dashboard showing all active agents, file access patterns, and a live activity feed.

    **Agent Activity Cards** — Each running agent shows: task title, model, elapsed time, tool call count, token usage, cost, and active files being accessed.

    **File Heatmap** — Visual map of which files are being accessed by which agents. Conflicts (multiple agents accessing the same file) are highlighted in red.

    **Live Feed** — Chronological stream of all tool calls across all agents with timestamps, tool names, and file paths. Includes a pause button.

    **Stats Bar** — Total agents running, tool calls, tokens, cost, and conflict count.
  </Tab>

  <Tab title="Battle">
    Gamified arena view where running agents appear as avatar sprites on a 2D map. Features include:

    * Emoji projectiles that fly between agents on token usage
    * HP bars that decrease as tokens are consumed
    * Explosion effects with shrapnel particles on impact
    * Critical hit damage numbers floating up
    * File conflict lines with "VS" markers
    * Victory crowns and defeat skulls
    * Idle bobbing animation for active agents

    See [Battle View](/features/battle-view) for full details.
  </Tab>
</Tabs>

## Wave Execution

Tasks are grouped into **waves** based on their dependency structure:

```
Wave 0: [Tasks with no dependencies]     → run in parallel
Wave 1: [Tasks depending on Wave 0]      → start when Wave 0 completes
Wave 2: [Tasks depending on Wave 0 + 1]  → start when deps complete
```

## Live Agent Cards

Each running Claude agent gets a named card in the sidebar with a unique avatar (e.g., 'Agent Nova') (Graph/Timeline modes) showing:

* Task title and key
* Model (Haiku/Sonnet/Opus) and elapsed time
* Live token usage (input/output breakdown)
* Real-time cost estimate
* Last tool call with file path
* Turn count
* Token progress bar

## File Conflict Detection

When multiple agents access the same file simultaneously, Claude Board detects potential conflicts:

* **Write/Edit conflicts** trigger an `agent:file_conflict` event
* The Live view highlights conflicting files in red
* Agent cards show conflict warnings

<Tip>Set max concurrent agents to 2-3 and use task dependencies to prevent agents from editing overlapping files simultaneously.</Tip>

## Graph Interaction

* **Hover** a node to highlight its dependency edges
* **Click** a node to open task details
* **Shift+drag** from one node to another to create a dependency edge
* **Drag** nodes to reposition them (positions are saved)

## Auto-Refresh

The view automatically refreshes on `task:updated` events — instant updates when tasks change status, dependencies are modified, or new tasks are created.