explainx / blog
Boris Cherny mapped Claude Code adoption in five steps — Gated (0) through AI-native (1,000+ agents). Bottlenecks, guardrails, and products per step from Anthropic's July 16, 2026 framework.
Jul 7, 2026
On July 7, 2026, @ClaudeDevs published the definitive Claude Code loops guide by @delba_oliveira — how the team categorizes loops by trigger, stop criteria, and primitive. explainx.ai maps each type to real commands, skills, and the loop-engineering corpus you already have on-site.
Jun 29, 2026
For the first time, more U.S. businesses on Ramp pay for Anthropic than OpenAI — 34.4% vs 32.3% in April 2026, with Anthropic quadrupling share in a year while OpenAI grew 0.3%. The viral X thread tied it to loop engineering and Dario Amodei's claim that some Anthropic engineers barely write code anymore. Here is what the index actually counts, what it does not, and why workflow beats chat.
Jun 20, 2026
Every developer asking "how do I actually build one of these loops?" gets the same answer: five components, three levels, and one feedback gate that says no. This guide walks you from a blank terminal to a working autonomous agent loop in under an hour — no orchestration framework required.
Update — July 17, 2026: Kr$na's viral final 10% dev cycle chart — 5-minute idea, 2-hour demo, 6-month polish — maps Step 1–2 (fast yellow demos) vs Step 3+ (red-bar verification in the background).
On July 16, 2026, Boris Cherny — creator of Claude Code — published Steps of AI Adoption on Anthropic's site. Lance Martin reposted it July 17; the thread hit 251K+ views in hours. Cherny's thesis: he talks to engineers daily who see one person 10× output while the rest of the org stays gated — and the gap is not "more tokens," it is bottlenecks and guardrails per maturity step.
Cherny mapped five steps (0–4): from legacy approval gates with zero agents to AI-native intent steering with 1,000+ agents where Claude kicks off most loops. Anthropic says it operates at Step 3; Cherny claims he personally hit Step 4.
This post translates Cherny's framework into a builder checklist — with product names, bottlenecks, and links to explainx.ai's loop engineering and Claude Code loops guide corpus.
| Step | Name | Your role | ~Agents | Unlock | Main bottleneck |
|---|---|---|---|---|---|
| 0 | Gated | — | 0 | — | Legacy security, cost-per-token mindset, no approval path |
| 1 | Assisted | You + agent (pair) | ~1 | Afternoon task → between meetings | Your attention; must read every edit |
| 2 | Parallel | Orchestrator | ~10 | Team-week backlog → one afternoon | Reviewing many streams; steering prompts |
| 3 | Supervised autonomy | Manager of managers | ~100 | Background maintenance runs continuously | Trust + decision throughput; token efficiency |
| 4 | AI-native | VP steering by intent | 1,000+ | Quarter migration → kickoff + monitor | Automating work at scale; per-task guardrails |
Cherny on X: "There's no one right path through the steps… at each step, tokens aren't enough… you need to find and break down the next set of bottlenecks, and build up the next set of guardrails."
What it looks like: Only older or lighter/faster models are approved. Latency stacks through AI gateways and custom auth. No MCP governance. Internal access to AI tools is gated or process-heavy. Claude-generated code or artifacts have no IT path to host — outputs stay local only.
Bottleneck: Legacy security and approval processes; orgs optimize cost-per-token containment instead of outcomes; lack of technical voices in procurement decisions.
Products Cherny lists:
How to reach Step 1: Executive or buyer alignment, escalating blockers, and frameworks for launching Claude securely — not buying more seats.
For enterprises still here after Fable export controls, Step 0 often means region-locked chat while engineering pilots Claude Code on personal machines. That mismatch is exactly what Cherny describes when one engineer 10×'s and the org chart says "not approved."
What it looks like: One engineer, one agent — a fast pair programmer. You run one session at a time and review almost every change before merge.
Unlock: A change that used to fill an afternoon becomes something you finish between meetings.
Bottleneck: Your attention and low trust. Without a self-verification loop you believe you must read everything — work stays synchronous: you watch Claude work instead of starting the next task.
Products:
Guardrails: Plan mode, spend caps, centralized policy, OTel into existing stacks.
How to reach Step 2:
Pair with Claude Code model vs effort — Step 1 teams often burn tokens on max effort while still reviewing every line manually.
What it looks like: One engineer orchestrates 5–10 agents on separate worktrees or git checkouts, jumping between sessions. Claude checks its own work — tests, build, lint, security scan — before you see diffs. Auto mode always on. Automated code review and security review default on. Claude writes most of the code; you review final diffs, not keystrokes. Maintenance backlogs start shrinking.
Unlock: A backlog that used to take the team weeks becomes one engineer's afternoon of orchestration.
Bottleneck: Reviewing output — six streams of diffs instead of one. Prompting and steering as you juggle sessions.
Products:
Guardrails: Manual merge still required; same quality bar for human and agent code; pre-approve safe bash and MCP commands in settings.json.
How to reach Step 3:
This is where explainx.ai's should developers stop reviewing AI code? debate lands: Step 2 still reviews, but the unit of review shifts from tokens typed to harness output.
What it looks like: Claude writes all or nearly all code. "Did you read the code?" becomes "what context was the model missing and how do we fix it next time?" Proactive maintenance runs in the background — cleanup that waited for someone with time now runs continuously.
Unlock: Work you would have kicked off manually now starts proactively.
Bottleneck: Trust in the loop and team decision throughput. The agent tree is too deep to babysit — scaling agent count before the loop earns widespread trust is the trap. Token efficiency at scale requires OTel or Analytics and a culture that experiments then controls cost after PMF.
Cherny's test: "Is this something an engineer would have done?"
Products:
/loop, /batch, /goalCLAUDE.md and Skills for standards — skills registryCLAUDE.mdGuardrails: Sandboxing, encoded standards, cost monitoring, proactive routines scoped to well-defined streams (bug triage, dependency upgrades, migrations).
How to reach Step 4: Scaled automation of domain use cases — code migration, fuzzing, feature-building, feedback remediation. Code with Claude Tokyo shipped managed agents, scheduling, and vaults as infrastructure for this step.
For advisor + executor splits (Fable plans, Sonnet executes), see Fable advisor + Sonnet executor — a common Step 3 pattern before full autonomy.
What it looks like: The loop is fully closed. Most agents are kicked off by Claude, not humans. Hundreds to thousands of agents run; you steer by intent and monitor by exception.
Unlock: A quarter-long migration becomes a workflow you kick off and check on.
Bottleneck: Identifying and automating work at scale while enforcing the right guardrails per work type — not one blanket policy.
Products:
Guardrails: Per-workflow cost caps, exception-based monitoring, separation between automation lanes (migrations, triage) and human-gated lanes (production deploys, security-sensitive refactors).
Cherny wrote Anthropic is pushing toward Step 4; he personally claimed Step 4 on July 17, 2026. Treat that as internal dogfooding signal, not a guarantee your team can copy day one without Step 2–3 harness investment.
Beyond the table, Cherny's thread named concrete advance requirements:
| Theme | Cherny's guidance |
|---|---|
| Verification | Give Claude ways to verify its own work end to end |
| Permissions | Auto mode for permissions; pre-approve safe commands |
| Review defaults | Automated code review + security review on by default |
| Multi-agent UI | Agent view in CLI, Desktop, iOS — manage multiple agents |
| Background payoff | Fixing and maintaining in the background; teams focus on building |
| No universal path | Every team different — break bottlenecks, don't just buy tokens |
When the published page had Safari scroll bugs, Cherny pointed to a Google Doc mirror of the same framework — worth bookmarking if the claude.ai page misbehaves.
Cherny's ladder is descriptive, not a certification. Common misreads:
| Misread | Reality |
|---|---|
| "We bought Enterprise so we're Step 3" | Step 0–1 is about behavior, not SKU — one supervised session is still Step 1 |
| "We run 10 Cursor tabs so we're Step 2" | Step 2 requires self-verification, auto mode, and automated review — not just parallel chats |
"We enabled /loop so we're Step 4" | Proactive loops without trust + cost controls is Step 3 at best — often Step 2 with extra tokens |
| "One 10× engineer means the org is advanced" | Cherny's opening observation — individual heroics without guardrails widens internal inequality |
Run Cherny's question at Step 3+: would an engineer have done this task? If yes, automate. If no, keep a human gate.
Boris Cherny's Steps of AI Adoption (July 16, 2026) names five maturity levels for Claude Code teams: Gated (0) → Assisted (~1) → Parallel (~10) → Supervised autonomy (~100) → AI-native (1,000+). Each step defines your role, the unlock, the bottleneck, Anthropic products, and guardrails to advance. Tokens alone do not move you forward — verification loops, auto mode, automated review, worktree isolation, routines, and cost monitoring do. Anthropic reports Step 3 org-wide; Cherny claims Step 4 personally. Map your team by behavior, not license tier.
Official sources: Steps of AI Adoption (Boris Cherny, Jul 16, 2026) · @bcherny X thread (Jul 17, 2026) · Claude Code docs
Framework accurate as of July 17, 2026 per Boris Cherny's published adoption ladder and X commentary. Product names and step definitions may change — verify on Anthropic's Claude Code documentation before planning enterprise rollouts.