# Overview (/docs/agent-orchestrator/overview)

The Agent Orchestrator turns parallel Claude Code sessions into a team. You talk to a
planner. The planner files tasks on a shared board. Coder sessions claim tasks,
do the work, and send it to review. A runner session verifies each change and
either closes it or bounces it back with feedback. You watch all of it on a
live terminal board, and you only get pulled in when a session actually needs
you.

It ships in [`aisquare-cli`](https://github.com/AISquare-Studio/aisquare-cli)
and works with a single Claude account: sessions are per terminal, not per
account.

The page embeds a screen recording of the live board: a five-session
team (planner, runner, three coders) with live state chips, a task table of
review-stage work, and the event feed showing claims, notes, and completions
in real time.

<img alt="The live team board: sessions with live state chips on the left above the open task table, and a bot-style feed of everything the team does on the right." src="__img0" />

## How it works [#how-it-works]

Three planes, one CLI:

**The board.** A shared SQLite store on your machine. Sessions register
automatically through Claude Code hooks, heartbeat on every prompt, and receive
a compact delta of what teammates did since their last turn. Repos that never
opt in never see any of it.

**The live board.** `aisquare board -w` is the cockpit: live session states
(working, waiting for input, needs you), the task table with dependencies, the
event feed, and a detail bar. Everything the team does is attributed and
timestamped, and you can jump from any event to the session transcript at that
exact moment.

**The bridges.** An MCP server (`aisquare serve`) lets remote Claude clients
(for example a browser-testing agent in the Claude desktop app) join the same
board as attributed teammates. A background distiller (powered by the optional
AISquare gbrain CLI) banks durable knowledge (decisions, results, task
outcomes) into a per-project brain that `aisquare recall` searches later.

## What makes it safe to rely on [#what-makes-it-safe-to-rely-on]

* **Idempotent tasks.** Adding the same task twice returns the original, so a
  planner can re-emit its plan freely and nothing duplicates.
* **Atomic claims.** When two coders reach for the same task, exactly one wins;
  the other just gets the next ready task. Claims carry leases, so a crashed
  session's work returns to the pool by itself.
* **Fail-open hooks.** Every hook swallows its own failures and exits cleanly.
  A broken orchestrator can never break a Claude session.
* **Explicit opt-in.** A repo joins the orchestrator only when you launch a
  session with a role or run `aisquare team on` there.

<Cards>
  <Card title="Quickstart" href="/docs/agent-orchestrator/quickstart" description="One Claude account, five terminals, a working team in two minutes." />

  <Card title="The board" href="/docs/agent-orchestrator/board" description="The live cockpit: states, archive, transcript jump, themes." />

  <Card title="Tasks and the work cycle" href="/docs/agent-orchestrator/tasks" description="How work flows: add, claim, review, done, reopen." />
</Cards>