Choosing & Running Models
RoboCo's agents are backend-agnostic. By default the whole workforce runs on Anthropic Claude, authenticated from the Claude Code session on your host — no API key to manage. You can route the company onto xAI Grok, OpenAI Codex, Google Gemini, or Moonshot Kimi instead (each its own subscription-authenticated CLI, no metered key), point individual agents and roles at local / self-hosted models, or pin a role to a cheaper model at a given task complexity — all from one page in the panel.
Provider routing
The Settings → AI Providers page: the routing modes, agent-over-role-over-global precedence, cost-tiered complexity overrides, saved routing presets, and the fail-soft fallback.
Running on Grok
The whole workforce on xAI Grok via the official CLI and a SuperGrok subscription — no metered key.
Running on Codex
Delivery agents on OpenAI's Codex CLI via a ChatGPT subscription — no metered key, V1 delivery-roles-only.
Running on Gemini
Delivery agents on Google's Gemini CLI via an OAuth login — no metered key, V1 delivery-roles-only.
Running on Kimi
Delivery agents on Moonshot's Kimi K3 via the official CLI and a Kimi subscription — no metered key, V1 delivery-roles-only.
Resilience
What keeps a run alive: crash auto-retry, and how rate limits and provider overloads park work instead of dropping it.