Models and profiles

Choose the model for a workspace and save recurring settings in a profile. A profile can group reasoning effort, approvals, instructions, and available tools so you can reuse them across workspaces.

List available models

With cocod running, ask the connected Codex installation for its current model catalog:

coco model list

coco model ls is the equivalent short spelling.

The output shows the value to pass as --model, its display name, whether it is the default, and the reasoning efforts it advertises. For scripts, use:

coco model list --json

Select a model

Choose a model when you create the workspace:

coco create refactor/cache --model gpt-5.6-sol

Without --model, Codex selects the model from its normal configuration. CoCo does not maintain a separate model catalog or alias list.

Save reusable settings

Save a named configuration file next to your normal Codex configuration:

~/.codex/dev.config.toml

model_reasoning_effort = "high"
approval_policy = "on-request"
sandbox_mode = "workspace-write"

For a profile named dev, the filename must be dev.config.toml below $CODEX_HOME, normally ~/.codex. The file itself is the configuration layer; do not wrap it in a [profiles.dev] table. Use keys supported by your installed Codex version; the Codex configuration reference lists the available settings.

Apply a profile

coco create refactor/cache \
  --base main \
  --profile dev

The special profile name default uses Codex’s normal base configuration and does not require default.config.toml.

Combine a profile and model

An explicit model overrides a model named inside the profile. Every other profile setting still applies:

coco create refactor/cache \
  --profile dev \
  --model gpt-5.6-sol

Keep profile files stable

CoCo records which named profile was applied when the workspace was created. When a command needs to load that conversation again, CoCo checks that the parsed profile still matches. If you changed or removed its settings, send and jump refuse to load it. Comments and formatting do not affect this check. list and status do not load the conversation or run this check.

When you want different settings, create another profile name and use it for a new workspace. CoCo checks the named profile file, not Codex’s base configuration layer. If you change the base configuration, inherited settings can therefore change the next time a workspace is loaded. Put settings that must stay fixed explicitly in the named profile.