◈AI Codex
Agents & OrchestrationCore Definition

Advisor tool: pairing a fast executor with Opus-level judgment

In brief

The Advisor tool runs a fast model for most tasks while escalating complex decisions to Opus — combining speed and depth in a single agent workflow.

4 min read·Advisor Tool

Contents

♡Sign in to save

The Advisor tool is an API beta feature that pairs two Claude models in a single agent workflow: a fast executor (typically Sonnet or Haiku) handles most of the work, while a separate Opus instance acts as an advisor called only when complex decisions arise. The result is an agent with near-executor speed and near-Opus judgment.

The architecture

Standard agentic workflows face a tradeoff: powerful models (Opus) produce better judgment but are slower and more expensive. Fast models (Sonnet, Haiku) handle routine steps efficiently but can miss nuance on complex decisions.

The Advisor tool resolves this. Most of the time, the executor model runs. When the executor encounters a decision point that warrants deeper analysis — an ambiguous requirement, a risky action, a multi-path problem — it invokes the advisor. Opus evaluates the situation and returns guidance. The executor continues with that guidance.

In practice, most agent steps are routine: read a file, call an API, parse a response. The few steps that require real judgment — "should I delete this file?", "which of these three approaches fits the architecture?" — are where Opus input actually matters. The Advisor tool pays for Opus reasoning only on those steps.

API setup

The Advisor tool requires the anthropic-beta: advisor-tool-2026-03-01 header:

import anthropic

client = anthropic.Anthropic()

response = client.messages.create(
    model="claude-sonnet-4-6",
    max_tokens=4096,
    extra_headers={"anthropic-beta": "advisor-tool-2026-03-01"},
    tools=[{"type": "advisor", "name": "advisor"}],
    messages=[{"role": "user", "content": "Your task here"}]
)

The executor model (specified in model) calls the advisor tool when it needs guidance. Advisor responses come from Opus automatically — you do not configure which model to use as the advisor.

When it is worth using

The Advisor tool is most valuable for long-running agents with a mix of routine and complex decisions. If your agent mostly does simple sequential tasks, the overhead of the advisor pattern is not worth it. If your agent hits genuine decision points — where the right path depends on context, judgment, or tradeoffs — the Advisor tool makes those moments more reliable without slowing down the whole workflow.

It is also a useful pattern for reducing costs on Opus-heavy workflows: if you currently run everything on Opus for safety, the Advisor tool lets you shift most execution to Sonnet while preserving Opus judgment where it matters.

Further reading

Official training on this: Introduction to subagents (4 lessons · 45 min) on Claude Academy, free.

Weekly brief

For people actually using Claude at work.

Each week: one thing Claude can do in your work that most people haven't figured out yet — plus the failure modes to avoid. No tutorials. No hype.

No spam. Unsubscribe anytime.

What to read next

All articles →
update·11 min

Projects redesigned: a coordinator, parallel threads, and memory that persists

On September 17, 2026 Anthropic put Projects into beta as something closer to a work queue than a folder. You set the goal and the context; Claude proposes tasks, delegates them to parallel threads — each a Claude Code cloud session on its own branch — and assembles the results. Plus project memory and a Library. Beta for select Pro and Max subscribers using cloud sessions.

How It Works·13 min

ant apply: your agents, skills, and schedules as files in the repo

On September 3, 2026 Anthropic shipped `ant apply` in version 1.30.0 of the ant CLI. It reads agents, environments, skills, memory stores, and scheduled deployments from files in your repository, prints a plan, and reconciles the Claude API against them once you approve. A committed claude-lock.json maps each file to the resource it created. This is the piece that was missing between clicking an agent together in the Console and having one your team can review, diff, and roll back.

implementation·11 min

Anthropic’s commerce agent blueprint: two reference agents you can run in an afternoon

On September 2, 2026 Anthropic published a commerce agent blueprint at github.com/anthropics/commerce-agents — a shopping agent and a merchant agent, both runnable locally, with integration points for catalog search, cart, checkout, preferences, and order history. The reported results are carts up to 35% larger and shoppers 60% more likely to complete a purchase. Here is what the blueprint actually gives you, what it deliberately does not, and the one guardrail that decides whether any of it is shippable.