Skip to main content
Ensure every Overcut workflow runs on the right LLM without touching each agent individually. This guide walks workspace admins and workflow builders through:
  1. Validating prerequisites and supported providers
  2. Choosing a workspace-wide default model
  3. Setting workflow-level defaults and coordinator overrides
  4. Verifying the cascade through the UI and execution logs
  5. Rolling back safely when governance needs change
Use this guide alongside the Workflow Execution Control and Agent Session docs to understand how defaults are enforced during runtime.

​
Prerequisites

  • Workspace admin access to edit Account → Settings.
  • Published agents and workflows that use the default model placeholder so they can inherit new defaults automatically.
  • An active custom LLM Model from Anthropic or AWS Bedrock if you run steps with the Claude engine. The model must belong to the current workspace and cannot be a system model. See LLM Models for compatible configuration options.

​
Step 1: Choose workspace defaults

1

Open workspace settings

Navigate to Account → Settings and locate the Default LLM Model and Default Claude Engine Model fields.
2

Choose the main workspace default

Use Default LLM Model to select the main model for the workspace (e.g., gpt-4.1).
3

Choose the Claude workspace default

If you use the Claude engine, select an active Anthropic or AWS Bedrock custom model in Default Claude Engine Model. This selection is separate from Default LLM Model and does not change the default used by the Overcut engine.
4

Save and capture evidence

Click Save Changes.
To stop using a Claude-specific workspace default, clear the selection in Default Claude Engine Model and click Save Changes. Claude steps can then fall through to Default LLM Model, but only if that model is compatible with the Claude engine.
Setting the workspace defaults means workflows that leave their metadata field empty or set to the default model placeholder inherit the applicable choice automatically.

​
Claude engine model resolution

The Claude engine checks these settings in order and uses the first model that is not set to the default model placeholder:
  1. Coordinator override
  2. Agent model
  3. Workflow default
  4. Default Claude Engine Model
  5. Default LLM Model
That first resolved model must be active, owned by the current workspace, non-system, and provided by Anthropic or AWS Bedrock. If it is not eligible, the Claude engine does not skip it and try a lower-priority setting. If no setting resolves to a model, the step fails because the Claude engine has no system-model fallback. This order applies only to the Claude engine. The Overcut engine uses its own cascade and can use a system model as its final fallback. See Workspace Settings for the canonical Claude resolution rules and LLM Models for engine compatibility.

​
Step 2: Override specific workflows

Some workflows (e.g., code review or red-team testing) may require a stronger or different model.
1

Edit Workflow Metadata

In the workflow builder, click the canvas to open the Workflow Settings and find the Default LLM Model selector.
2

Select a workflow default

Choose a model key (for example gpt-5.1-codex) and save the workflow.
3

Save the workflow

Click Save.
When set, agents and coordinators left on the default model placeholder fall back to the workflow default. Workflows left on the default model placeholder continue to fall back to the workspace default.

​
Step 3: Configure coordinator overrides

Use coordinator overrides when a multi-agent session needs a faster planning model, but its child agents should continue using the workflow default.
Guidelines:
  • When not set, the coordinator will fall back to the workflow default, or the workspace default if the workflow default is not set.
  • Keep overrides scoped to steps that truly benefit from a different coordinator model.
  • Child agents never inherit the coordinator override; they evaluate their own modelKey → workflow default → workspace default chain.

​
Step 4: Configure agent overrides

Use agent overrides when an agent needs a different model than the workflow default.
1

Edit Agent Settings

In the “Agent Roles” menu, select an agent to edit its settings.
2

Select a model

Choose a model key (for example gpt-5.1-codex) and save the agent.
Guidelines:
  • When not set, the agent will fall back to the workflow default, or the workspace default if the workflow default is not set.

​
Next steps