Skip to main content

​
Claude Agent SDK Integration

Overcut supports using Anthropic’s Claude Code Agent SDK as an alternative execution engine to the default Overcut Agent architecture. This integration allows you to leverage Claude’s native coding capabilities while maintaining all existing Overcut functionality.

​
Overview

The Claude Agent SDK integration provides:
  • Claude Code Intelligence: Claude’s advanced understanding of code patterns, architecture, and best practices
  • Intelligent Task Delegation: Automatic coordination between specialized agents based on context
  • Seamless Tool Integration: Full access to Overcut’s ticketing, pull request, and workflow tools
  • Consistent Experience: Same agent personalities and capabilities across both execution modes
  • Enhanced Performance: Leverage Claude’s latest capabilities for complex coding tasks

​
Architecture

​
Execution Modes

Overcut supports two execution modes:
  1. Overcut Agent Mode (Default): Uses Overcut’s Agent architecture
  2. Claude Agent Mode: Uses Anthropic’s Claude Code Agent SDK directly
The execution engine is selected when configuring each workflow step. For a side-by-side comparison of the two engines, see Execution Engines.

​
Key Benefits

  • Advanced AI Capabilities: Access to Claude’s state-of-the-art reasoning and code generation
  • Flexible Execution: Choose the best AI engine for each specific task type
  • Seamless Integration: All Overcut tools work with both engine types
  • Intelligent Coordination: Automatic collaboration between multiple agents in sessions

​
Setup and Configuration

​
Prerequisites

You need permission to manage workspace LLM Models and edit the workflow. You also need credentials for one of these providers:
  • Anthropic: An Anthropic API key or a Claude subscription token generated with claude setup-token. Choose one authentication method, not both.
  • AWS Bedrock: A Bedrock API key or a complete IAM credential pair, plus the AWS region and model or inference-profile ID.
See LLM Models for every provider field, including the optional Anthropic Base URL and Fallback Model settings.

​
LLM Model Setup

Create a compatible model

Open LLM Models, select Add LLM Model, and choose Anthropic or AWS Bedrock. Enter the provider credentials and model settings, then save the model and keep it active.

Set the Claude default (optional)

Open Settings. Under AI, choose the model in Default Claude Engine Model. This setting is separate from Default LLM Model and can be cleared.

Select the Claude engine

In the Workflow Builder, open the agent step and set Execution Engine to Claude.

Apply an override when needed

For an agent session, use Coordinator Model Override to choose another compatible model for the coordinator. A run-agent step uses the selected agent’s model, followed by the configured workflow and workspace defaults when needed.

​
Model Compatibility

The Claude engine accepts only custom Anthropic or AWS Bedrock models that are active, belong to the current workspace, and are not system models. It does not fall back to a system model. If the selected model is not compatible, choose or create a compatible model in LLM Models. An Anthropic model configured with only a Claude subscription token works with the Claude engine, not the Overcut engine. An Anthropic-compatible gateway can be used through Base URL only when it supports the Anthropic /v1/messages API. For provider configuration fields and model assignment behavior, see LLM Models.

​
Model Selection

​
Claude model resolution

Claude-engine steps use the first configured model in this order:
  1. Coordinator override
  2. Agent model
  3. Workflow default
  4. Workspace Claude default set through Default Claude Engine Model
  5. Main workspace default set through Default LLM Model
Default Claude Engine Model is separate from Default LLM Model and can be cleared. Clearing it lets resolution continue to the main workspace default. The first model resolved by this order must be active, belong to the current workspace, be a non-system model, and use Anthropic or AWS Bedrock. The Claude engine does not skip an incompatible selection or fall back to a system model. See LLM Models for the canonical model cascade and compatibility rules.

​
Getting Started

Create a compatible LLM Model, select Claude as the step’s Execution Engine, and run the workflow. Set Default Claude Engine Model for a workspace-level default. For an agent session, use Coordinator Model Override when that session needs a different compatible model.