gaia-operator

Agents are the specialists of Gaia. Each one has a narrow domain, a set of allowed tools, and a list of skills that get injected at startup. The orchestrator never does domain work itself — it reads the user's intent, picks the right agent, and dispatches it. What comes back is

Use when inspecting, diagnosing, or validating the actual state of running systems — pods, services, logs, cloud resources, network connectivity, SSH access — or when comparing what IS running against what SHOULD be running (drift between live state and IaC/desired-state).

Use when writing, modifying, debugging, or reviewing application code, CI/CD pipelines, or developer tooling — or when investigating an application-layer bug or behavior.

Use when a user prompt arrives in Gaia and needs to be routed — when intent must be matched to a specialist surface, when multiple surfaces touch the same question, when an approval or pending grant must be presented for informed consent, or when conversational synthesis must

Use when planning a feature or decomposing work from a brief into an executable plan -- turning objectives and acceptance criteria into ordered, testable tasks ready for dispatch.

Use when building, modifying, or auditing Gaia's own machinery — agents, skills, hooks and hook modules, routing config, CLI plugins, build manifests — or when analyzing Gaia's architecture, install, or release surface. Not for work in the user's application, infrastructure,