Kairo receives work items, each with a role: Explorer, Builder, Test Runner or Reviewer. It splits the work across two AI providers, Claude and Codex, by remaining quota, and denies an agent that is not in the approved team. When Claude quota runs out, the same roles continue on Codex. Illustrative, with the quota values from a pacing sample of 2026-11-05.map auth moduleExploreradd export endpointBuilderrun unit suiteTest RunnerKairoapproved teamsame roles, Codex takes overExplorerBuilderTest RunnerReviewerClaude5h 0%claude-sonnet-5-5quota outCodex5h 52%gpt-6.1-soltakes overDeniedunlisted agent · kairo team check-agentIllustrative: Claude 5h quota runs out · Codex: pacing sample, 2026-11-05Kairo receives work items, each with a role: Explorer, Builder, Test Runner or Reviewer. It splits the work across two AI providers, Claude and Codex, by remaining quota, and denies an agent that is not in the approved team. When Claude quota runs out, the same roles continue on Codex. Illustrative, with the quota values from a pacing sample of 2026-11-05.map auth moduleExploreradd export endpointBuilderrun unit suiteTest RunnerKairoapproved teamsame roles,Codex takes overExplorerBuilderTest RunnerReviewerClaude5h 0% · quota outCodex5h 52% · takes overDeniedunlisted agent · kairo team check-agentIllustrative: Claude 5h quota runs out.Codex: pacing sample, 2026-11-05

Pacing sample, 2026-11-05 · routing is illustrativeIllustrative: Claude 5h quota runs out · Codex: pacing sample, 2026-11-05

What I'm building

Kairo

The right agent for every task.

Kairo chooses who handles each task and which model, keeping quota in view.

Kairo on GitHub