Skip to main content

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.

Workspace-level configuration covers the things that apply to the entire workspace and every project inside it: the workspace profile, default LLM model, integrations, team membership, and platform-wide credentials. Project-specific configuration (workflows, agents, repositories, project vault, project permissions) lives inside each project under Project Settings. This page covers the workspace Settings page. For the full picture of what’s at the workspace level versus inside a project, see Multi-Project Workspaces.

​
Settings

The Settings page (Account → Settings in the sidebar) contains the workspace profile and the workspace-wide defaults that projects inherit. All fields are saved together when you click Save Changes.

Open the workspace

From the global workspace switcher, choose the workspace you want to configure.

Open Settings

Click Settings in the workspace sidebar. The current workspace settings are displayed.

Update settings

Update any of the fields. See the sections below for details on each field.

Save changes

Click Save Changes. A confirmation message appears when your changes are saved successfully.

​
Workspace Name

The workspace name identifies your workspace throughout the application. It appears in workspace switchers, breadcrumbs, and other UI elements.
  • Required: Yes

​
Timezone

The timezone selector determines when scheduled workflows execute. The field displays a curated list of major world timezones, sorted by UTC offset and showing current offset information (e.g., “(UTC-8) America Los Angeles (PST)”).
  • Default: UTC
  • Description: Timezone used for scheduled workflows. All workflows will run according to this timezone.
The timezone options automatically account for daylight saving time changes and are sorted from west to east by UTC offset.

​
Default LLM Model

The Default LLM Model selector sets the workspace-wide default that workflows and agents inherit when they use the default model placeholder. This value is resolved at runtime through a cascading priority system.
  • Default: Falls back to system default if not set
  • Description: Default model used by agents in this workspace when no other model is specified
The selector displays all available models. When saved, any workflow or agent that uses the default model placeholder will automatically inherit the workspace selection.
Teams should leave workflow and agent model pickers at their default model placeholder unless they have a justified override. Once the workspace value is set, all placeholder usages resolve to the workspace default without per-workflow setup.

​
How existing vs. new workflows behave

  • Existing workflows keep running exactly as configured. Any step that already has a specific model selected continues to use it. Steps that use the default model placeholder immediately inherit the newly saved workspace value during the next execution.
  • New workflows (and newly created agents) start with the default model placeholder. Until you set a workspace default, those executions fall back to the platform-wide system default. After you set it once, every new workflow automatically inherits it.
  • No retroactive edits occur. This feature relies on runtime resolution, not bulk edits to workflow definitions. You can therefore experiment safely without rewriting historical definitions.

​
Model resolution order

When a workflow step runs, the system determines which model to use by checking the following sources in priority order:
PrioritySourceWhen it wins
1Coordinator overrideA coordinator or runtime hook explicitly overrides (e.g., manual re-run forcing a model).
2Agent/step configThe agent definition itself has a specific model selected (Agent Builder, Agent Run/Session forms).
3Workflow defaultThe workflow metadata form has a default model set. See the Workflow Metadata defaults guide for workflow-level overrides.
4Workspace defaultThe value saved on the Settings page; applies whenever upstream layers use the default model placeholder.
5System defaultThe platform-wide fallback when every other layer uses the default placeholder.
If a level uses the default model placeholder, it is skipped so the next layer can supply a specific model.

​
Auto-Improve Workflows

The Auto-Improve Workflows toggle controls whether workflows in the workspace can use self-improvement features. Turn it on when you want workflow dashboards to expose the Self-Improvement panel and let each workflow run retrospective analysis.
  • Description: Enables automatic retrospective analysis of workflow runs to generate improvement suggestions
This workspace setting is a prerequisite for workflow-level self-improvement. If the toggle is off, workflow dashboards show a prompt directing you to enable it here first. Once enabled, each workflow dashboard exposes a Self-Improvement panel where you configure retrospective cadence, sample size, and view retrospective activity.
See Workflow Self-Improvement for the full walkthrough on configuring cadence, sample size, validation limits, and viewing retrospective results.

​
Workspace Secrets

Platform-wide credentials, most importantly the Claude API key required to use the Claude Agent SDK as an execution engine, are stored in Workspace Secrets, under Workspace → Security → Workspace Secrets. They are available to every project in the workspace.

Open Security → Workspace Secrets

From the workspace sidebar, click Security, then select the Workspace Secrets tab. The current Claude API key status is displayed.

Set or update the key

Enter a new Claude API key (the field is never pre-filled for security) and click Set Key or Update Key. The form clears once the key is saved successfully. If a key already exists, you’ll see a confirmation message: ”✓ API key is currently configured.”

Clear when needed

Use Clear Key to remove the stored secret. A confirmation dialog guards against accidental removal.
Trying to use the Claude Agent SDK in a workflow step when no Claude API key is configured shows a warning directly in the Agent Run and Agent Session forms. This prevents misconfigured runs and guides you back to Workspace Secrets. See the Claude Agent SDK integration guide for more details.
Secrets are encrypted at rest and never exposed to the browser. The form field is always empty for security reasons, even when a key is already configured. A confirmation message indicates whether a key exists without revealing its value.
For project-scoped secrets (credentials used by a single project’s workflows, agents, and MCP servers), use the Project Vault instead.