> ## Documentation Index
> Fetch the complete documentation index at: https://docs.overcut.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Default Model Configuration

> Plan, configure, and verify workspace, workflow, and coordinator default LLM selections with rollback guidance.

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

<Note>
  Use this guide alongside the [Workflow Execution Control](/docs/workflows/workflow-execution-control) and [Agent Session](/docs/workflows/agent-session) docs to understand how defaults are enforced during runtime.
</Note>

***

## 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.

***

## Step 1: Choose a workspace default

<Steps>
  <Step title="Open workspace settings">
    Navigate to <code>Account → Settings</code> and locate the <strong>Default LLM Model</strong> field.
  </Step>

  <Step title="Pick an approved model">
    Use the dropdown to select a model (e.g., <code>gpt-4.1</code>).
  </Step>

  <Step title="Save and capture evidence">
    Click <code>Save</code>.
  </Step>
</Steps>

<Note>
  Setting the workspace default means workflows that leave their metadata field empty or set to the default model placeholder inherit this choice automatically.
</Note>

***

## Step 2: Override specific workflows

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

<Steps>
  <Step title="Edit Workflow Metadata">
    In the workflow builder, click the canvas to open the <strong>Workflow Settings</strong> and find the <strong>Default LLM Model</strong> selector.
  </Step>

  <Step title="Select a workflow default">
    Choose a model key (for example <code>gpt-5.1-codex</code>) and save the workflow.
  </Step>

  <Step title="Save the workflow">
    Click <code>Save</code>.
  </Step>
</Steps>

<Note>
  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.
</Note>

***

## 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.

```yaml theme={null}
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.

<Steps>
  <Step title="Edit Agent Settings">
    In the "Agent Roles" menu, select an agent to edit its settings.
  </Step>

  <Step title="Select a model">
    Choose a model key (for example <code>gpt-5.1-codex</code>) and save the agent.
  </Step>
</Steps>

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

* Review the [Building Blocks](/docs/building-blocks) guide to see how agents inherit models.
* Learn how execution locks and priorities interact with these defaults in [Workflow Execution Control](/docs/workflows/workflow-execution-control).
* Share compliance outcomes via the [Privacy & Security](/docs/privacy-and-security) guidance.