20 Nov 2026
Approval date for these lesson notes. This page records the notes. It is not a deploy record.
- Claude Code for Designers · Module 6, Automation and Maintenance
- Orchestrating Design Agent Teams · Module 2, Orchestration Patterns
Claude Code's experimental advisor. The main model does the work and tends to consult a stronger model before committing to an approach, when an error keeps recurring, and before declaring a task done. The advisor reads the full conversation, including every tool call and result. Turn it on with /advisor opus, with advisorModel set to opus, or with claude --advisor opus. Use it as the critic. A read-only subagent can map the repo, or run tests and report only failures, and your instructions say when to consult. The advisor must rank at or above the main model. A weaker one is not attached, and the main model runs without it. It isn't available on Amazon Bedrock, Google Cloud's Agent Platform, or Microsoft Foundry. On Claude Platform on AWS or Claude Models on Google Cloud (Anthropic managed), it needs Claude Code v2.1.300 or later. On the Anthropic API, the session also needs the feature flag fetched from Anthropic. On a subscription plan, advisor usage counts toward plan limits. With API billing it is charged as extra tokens. Kleos's post is 18 November 2026, 16:19 UTC (19 November 2026, 03:19 Sydney).
- Agentic Prototyping · Module 5, Visual QA Loops
The spoken line on the pass-or-fail check now names Addy Osmani, then the figure: Addy Osmani says flaky tests train a rerun instead of a fix, and slow tests mean fewer runs. He says that on the Claude Code team, about ninety percent of the code is written and reviewed by Claude.