Brain and models
Choose model defaults, connect providers, set fallback order, inspect activity and choose where work runs.
TabsLink to Tabs
Brain & Models opens Models. The other tabs are Connections, Fallback order, Activity and Where work runs.
ModelsLink to Models
Agent manages your choices by default. Select a provider to see its model for Quick tasks, Everyday work, Complex work and Hardest problems. Each card shows the model name and ID, documented capabilities, a release date when verified, and official details. A CLI alias can change at runtime; its exact release date is not shown.
Owners and admins can select a card, search models and choose one. Select Save changes. Reset removes one choice. Use Agent defaults in Advanced routing rules removes all organization routing settings. Members can inspect the choices.
Automatic adjusts the tier to the task. Fixed by task uses the purpose rules without adaptive changes. Fixed models uses the exact configured chains. Tier choices apply when routing is on. Worker overrides, budgets and provider access still apply.
A custom server needs its own model ID. Agent does not invent a default for an unknown server.
ConnectionsLink to Connections
A provider is a model service, such as Anthropic, OpenAI, Gemini or an OpenAI-compatible server (Ollama, vLLM, OpenRouter, Groq). The banner says Workers can think, Text generation is degraded or No text provider can serve. Only owners and admins add or change providers.
New vendor connections start with a suggested model. Open the picker to change it. Connection settings holds its name, ID and optional embedding model. Local and custom servers holds endpoint presets. Enter an exact server model ID when no list is available. New suggested IDs keep existing connections, including disabled ones. Advanced model settings holds optional price and context data.
Fallback orderLink to Fallback order
Workers think at three tiers: Fast, Balanced and Deep. A chain lists the models for each tier, in order. When one model fails, the next one answers. Each worker can have its own chain. See Worker settings.
Where work runsLink to Where work runs
The Where work runs tab sets the organization's defaults:
- Required executor: Automatic, Native platform loop, Claude Code CLI, Codex CLI or Gemini CLI.
- Host: Automatic, Managed server host, or Requester's runner.
- CLI runtime: Automatic, Host sandbox or Container.
- Cost payer: see Who pays for work.
Each value comes from the platform, then the organization, then the role, then the worker. Permissions, availability and budgets still apply. Codex Cloud is not available here.
Checked against the product on 2026-10-08.
Was this helpful?
Related articles
- Model accounts and API keysConnect your own API keys or cloud model accounts. Work you ask for uses your accounts first, then the organization's, then the platform's.
- Who pays for workThe payer is the source that pays for a piece of work: automatic, the requester's own plan or keys, the organization's keys, or Agent.
- Run modesA run mode is a preset for how work runs: Speed, Balanced, Quality, Cost or Custom. Hard gates hold in every mode.
- Worker settingsAn owner or admin edits a worker in sections: profile, responsibilities, instructions, brain, governance and identities. Each save can carry a reason.