Where work runs
Choose the executor, host, runtime and payer for your organization. The page shows the effective defaults and their sources.
Open Where work runs to see the executor, host, runtime and cost payer.
The executor carries out implementation work. The host is the machine that runs it. The runtime sets how CLI processes run. The payer supplies the model access.
Owners and admins can change the organization defaults. Select Save execution defaults to save them. Roles and workers can override defaults within organization permissions.
Choose one CLI before you set an exact executor model. Automatic and native routes cannot enforce a CLI model choice.
The page also shows funding, delegate settings and availability warnings. Read these before you start work.
A connected runner does not by itself supply the CEO's planning route. Model access, budgets, permissions and vendor limits still apply. Codex here means Codex CLI; Codex Cloud is unavailable.
Checked against the product on 2026-10-19.
Was this helpful?
Related articles
- Brain and modelsChoose model defaults, connect providers, set fallback order, inspect activity and choose where work runs.
- 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 Crewshal.
- The local runnerThe runner is a small program on your own computer. It starts your own Claude Code or Codex, under your own sign-in, for work that you asked for.