Appearance
Skip to content
Published on npm as @gaia-ai/gaia
Agents work the tickets. You keep the workflow.
GAIA orchestrates AI agents through the same ticket lifecycle your team already follows, state by state, with a human wherever you want one.
$ npm install -g @gaia-ai/gaia
a ticket, moving through its states
AGENT
qualification
The agent reads the ticket, classifies it as bug or feature, and publishes a versioned handoff before any work starts.
AGENT
spec
Design decisions, an implementation plan, and checkable acceptance criteria, committed to the repo as the contract for the build.
AGENT
coding
Implemented in an isolated git worktree on its own branch; the acceptance checks run before the agent hands the ticket over.
HUMAN
review
Fresh eyes give an independent verdict on the diff, with the full run transcript available right on the ticket.
AGENT
done ✓
The merge request lands, the ticket closes, and the status is mirrored back to the customer's origin issue.
⌁
Distributed conductors
Run one on every machine your code runs on.
⎇
Worktree per ticket
Isolated branches, no stepping on each other.
✓
Server-owned transitions
No orphaned runs, no client-side cleanup.
§
Process as code
Workflow skills are versioned in your repo.
OWNERSHIP
Every state has an owner
A ticket moves through explicit states. An agent qualifies, specs, codes; a human reviews. Ownership is your call, per state, and changing it is a config edit, not a re-org.
CONDUCTORS
Runs where your code runs
A conductor is a daemon on any machine you own. It registers itself, claims tickets it can work, creates a git worktree per ticket, and drives the agent to the next state.
Watch a ticket get worked
A real run, condensed: coding, tests, review, a change request, and the merge.
GAIA-142 · Fix login redirectcoding
✓ conductor studio-m1 claimed GAIA-142 · worktree feat/gaia-142
AGENT · CLAUDE Run intake: loading @gaia/implement-ticket, reading the spec handoff and the acceptance criteria.
AGENT · CLAUDE Implementation complete in the worktree. Running the acceptance validation before handoff.
✓ playwright · 12 passed, 0 failed · login-redirect.feature
AGENT · CLAUDE Verification summary published to the ticket. Writing the next state.
✓ state written: review · run retired by the server
HUMAN · REVIEWER The redirect works, but keep the return URL after login. Sending it back.
↺ state written: coding · changes requested
AGENT · CLAUDE Preserving the return URL now, regression scenario added to the feature file.
✓ playwright · 13 passed, 0 failed · keeps return URL after login
✓ state written: review
HUMAN · REVIEWER Looks good. Approving.
✓ review verdict published · routing to merge
!241 · Fix login redirect
feat/gaia-142 → develop
ARCHITECTURE
Four pieces, cleanly separated
A shared control plane, conductors on your machines, the agents you already use, and a workflow that lives in your repo.
Control plane
The shared source of truth for projects, tickets, and runs. Your conductors talk to it over an API; the cockpit UI reads from it live.
Conductor
A daemon on any machine you own. It registers itself, claims tickets it can work, creates a git worktree per ticket, and drives the agent.
Agents
The AI CLIs doing the work: Claude, Codex, Kimi, OpenCode, Pi. Each is an addon; swapping agents is a config line, not a migration.
Skills
The workflow itself, written as versioned skill files in the repo. What "qualify" or "review" means is code-reviewed, not tribal knowledge.
Claude CodeCodexKimiOpenCodePi
FAQ
Questions, answered
Which agents does GAIA support?
Claude Code, Codex, Kimi, OpenCode, and Pi ship as addons today. An agent is a plugin, so adding another CLI is an addon package, not a fork, and swapping the agent a project uses is one line in the conductor config.
Do I need to host something?
Yes, one thing: the control plane, the shared server that holds projects, tickets, and runs. Conductors and agents run on your own machines and connect outward to it. There is no GAIA cloud and no account with us.
Does my code leave my machines?
No. Conductors work in local git worktrees on hardware you own. The control plane stores tickets, states, and run metadata, not your repository. Agents talk to their own model providers under your existing keys and policies.
Can a human own a workflow state?
Any state can be owned by a human or an agent, and you can change ownership per state at any time. A common setup lets agents qualify, spec, and code while review stays human, but that split is yours to decide.
How is this different from a coding agent in my editor?
An editor agent helps one person in one session. GAIA runs the whole lifecycle across a team: tickets queue up centrally, any registered machine picks them up, every run is recorded with its transcript and footprint, and the process itself is versioned in the repo.
What does it cost?
GAIA is MIT licensed and free. You pay only what you already pay: your own infrastructure and your agents' model usage.