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 Workspace → General Settings.
  • Published agents and workflows that use the default-model placeholder so they can inherit new defaults automatically.

​
Step 1 — Choose a workspace default

1

Open Workspace Settings

Navigate to Workspace → Settings → General and locate the Default Model field.
2

Pick an approved model

Use the dropdown to select a model (e.g., gpt-4.1).
3

Save and capture evidence

Click Save.
Setting the workspace default updates the workspaceDefaultModelKey recorded with every workflow run. All workflows that leave their metadata field empty or set to default-model now inherit this choice.

​
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 default-model will fall back to the workflow default. Workflows left on default-model will 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. 
steps:
  - id: "code-review-session"
    action: "agent.session"
    params:
      goal: "Complete review plan"
      agentIds: ["coordinator", "code-reviewer"]
      coordinatorModelKey: "azure-openai-gpt-5.1-codex"
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