Agents & adapters

Arthur Loop does not ship a model. It coordinates the agent CLIs you already pay for — one of them as the master, the rest following the loop.

The master agent

Configured as flow.master_agent, chosen first in the arthur init interview. The master gets the Arthur Loop skill and a KICKOFF.md interview seeded into the instance, and coordinates from there: creating jobs, reading status, answering for the loop. The console warns when no live master session is coordinating.

What arthur agents detects

Honest reading of that table: Claude Code and Codex ship complete prompt packs today. The other four are detected, seedable with instructions files, and workable as masters — but they run on the generic playbook, not a tuned pack.

Advisors and executors are adapters

An adapter is a runbook plus a prompt pack, not code. Shipped advisors: chatgpt-browser (your own logged-in browser conversation), claude-code, codex, and manual (you paste). Shipped executors: codex, claude-code, manual. Adding one is a docs-and-prompts contribution — the contract lives in docs/adapters.md.

Trackers

Tickets can flow in from atlas-tasker, from any CLI via command templates (rendered to argv, never a shell), or none. The console's Atlas list is read-only; tickets become jobs one at a time, never in bulk.

Quota sources

The governor reads quota from codexbar (Codex, Claude, and Gemini subscription readouts), any command that prints a percent, a file, or none. Reserve policy and polling cadence live beside it in config.