Feature · Settings
Where work runs
Choose where your crew runs work.
How it works
Read the current defaults
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.
Change the defaults
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.
Check access and limits
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.
From the help article Where work runs, checked against the product on .
What you can do
The operations this feature's screens call. Each one is POST /api/<name>, and the badge says who may call it.
ViewergetExecutionProfileGets the execution profile.
Types:
{ workerId?: string }returnsimport('./execution.js').ExecutionProfileDto
AdminNo API tokensupdateOrgExecutionProfileUpdates the org execution profile.
Types:
{ policy: import('./execution.js').ExecutionPolicyInput }returnsimport('./execution.js').ExecutionProfileDto
AdminNo API tokensupdateDelegateSettingsUpdates delegate settings.
Types:
UpdateDelegateSettingsRequestreturnsDelegateSettingsDto
ViewergetSpendSummaryGets the spend summary.
Types:
GetSpendSummaryRequestreturnsSpendSummaryResponse
Screens
What it records
The feature writes these events to the audit log, the permanent record of what happened.
- Policy changed
- Budget reserved
- Checkpoint saved
- Context retrieved
- Delegate ended
- Integration changed
- Memory recalled
- Model called
- Policy evaluated
- User signed in