Skip to content

root / tags / boris-cherny

#Boris Cherny

8 fiches

AI Coding Agents & Skills Auto-verified translation

Reflecting on a year of Claude Code

Boris Cherny (Head of Claude Code) and Cat Wu (Head of Product, Claude Code) publish a short LinkedIn video, "Reflecting on a year of Claude Code," in which they put forward a thesis: **product and engineering roles are merging**. At Anthropic, the product team, devrel, and design **all write code**; many engineers **ship products end to end** (idea → build → legal/marketing/security → release into the world). Their conclusion: AI benefits profiles with **curiosity**, **product taste**, and a taste for **end-to-end ownership**. The note mainly captures the **comment-thread discussion** (55 comments, 28 substantive): a consensus that **reframes** the thesis — it is not roles disappearing, it is that **shipping becomes cheap**, which shifts value toward judgment and defining the right problem — set against a lucid minority on the flip side (accountability, governance, IP).

#Boris Cherny#Cat Wu#Claude Code

Boris Cherny (Head of Claude Code, Anthropic) et Cat Wu (Head of Product, Claude Code, Anthropic) — vidéo ~47 s publiée par Claude for Business sur LinkedIn · repartagée par Claude. Commentateurs cités : Omer K. · Syed T. · Andrei K. van Noordt · Kristóf Nagy · Natasha Egan · Natasha Newbold · Rehan Nazir · Noman A. · Kevin Schoovaerts · Sunny Vara · Paul Breuler · Ron H. · Mohammadjavad Sayadi · Chris Bounds · Mohamed Anis · Panny Malialis · David H. · plebs.me · James Hutchinson · Dewayne J Grunden II · e.a. (28 commentaires de fond retenus sur 55).

Transformation & Adoption Auto-verified translation

Steps of AI Adoption (tableau/artifact + post LinkedIn « I talk to engineers at other companies every day… »)

**Boris Cherny** (Creator & Head of Claude Code @Anthropic) publishes a framework table on LinkedIn, **« Steps of AI Adoption »**, mapping an engineering team's adoption of agentic AI across **5 stages (0→4)**, each characterized by an **order of magnitude of agents driven** and a **transformation of the engineer's role**: **0 Gated** (0 agents, locked-down access), **1 Assisted** (~1 agent — "you + one agent", supervised pair programming), **2 Parallel** (~10 agents — **orchestrator**), **3 Supervised autonomy** (~100 agents — **manager of managers**, an org tree), **4 AI-native** (~1,000+ agents — **VP steering by intent**). The table crosses five columns: number of agents, *what it looks like*, *the bottleneck*, *the products that help*, *the guardrails*. **Central thesis**: consuming more tokens does not move you up a level — advancing to the next stage requires **identifying and breaking the next bottleneck** AND **building the next set of guardrails**. Concretely: giving Claude a trustworthy **self-verification loop** (tests + build + lint + e2e on a real environment), enabling **Auto mode** (avoiding blocking permission prompts), making **code review and security review the default**, adopting multi-agent interfaces (Agent view CLI, Desktop, iOS/Android apps, Tag), then `/loop`, `/batch`, `/goal`, **dynamic workflows** and **worktree isolation** for subagents. On steering: usage (dashboard) measures **activity, not return**; the right question is *"would we have spent engineering effort on this anyway? if so, how many manual engineer-hours would it have cost?"* — that's the ROI. The real payoff arrives when **fixing and maintaining happens in the background** and teams focus on *building*. Anthropic sits at **stage 3, heading toward 4**; Boris Cherny states he has personally reached **level 4**.

#Boris Cherny#Claude Code#Anthropic

Boris Cherny (Creator & Head of Claude Code @Anthropic)

Strategy & Frameworks Auto-verified translation

Loop Engineering for Product Managers

Long-form essay by **Shubham Saboo** (X/Twitter) advancing a thesis on the Product Manager role in the age of agents: the next key skill is **not prompt engineering** but **Loop Engineering** — designing a *system that improves with every run* rather than writing the perfect prompt every time. A **loop** is a repeated cycle: change what shapes the agent's behavior → run it → evaluate the output → keep the change if quality rises, revert otherwise → **compound the learning** so the next version starts ahead. For a PM, the entry point is not code but the **durable artifacts** that encode their judgment: PRD-review skill, customer-call *summarizer*, evaluation rubric, launch checklist, research workflow, `CLAUDE.md`, prompt template, prioritization framework. Because they are reused, these artifacts **compound in both directions** — and **drift** silently (a CLAUDE.md that keeps growing, a checklist that gets ignored…): the model has not regressed, the artifacts have drifted unwatched. A loop has **5 parts**: trigger, action, **proof**, memory, **stop condition** (the most critical). **Evals** become PM work (testing the artifact against known examples: 3 good / 3 bad PRDs, 5 understood calls, 2 past launches). **Memory** lives on **GitHub** (the repo becomes "product memory": commits, diffs, eval results, decision log, rollback). Recommended first loop: a **weekly product signal loop** (every Friday). Taste remains central — but it now needs **proof**. Cites Boris (creator of Claude Code): "he no longer writes prompts, he writes loops."

#Loop Engineering#product management#augmented PM

Shubham Saboo (@Saboo_Shubham_)

AI Coding Agents & Skills Auto-verified translation

Anthropic pauses Claude Agent SDK subscription change on day it was due to take effect

Article by **Paul Sawers** published on **The New Stack** on **June 16, 2026**, about the **suspension by Anthropic** — *"on the very day it was scheduled to go live"* — of the billing split meant to separate **Agent SDK** usage from Claude subscription limits. **Anthropic's cited message**: *"We're pausing the changes to Claude Agent SDK usage described below. For now, nothing has changed."* **The article's contribution is not the announcement but the surrounding context**, in three circles. **Circle 1 — Anthropic's week**: on June 9, the release of **Fable 5 and Mythos 5**, the first generally available Mythos-class models with hardened cybersecurity safeguards; a few days later, a **US government export control directive** forces Anthropic to **withdraw both models for all its customers worldwide**. The pricing suspension is read as *"a little good news"* in this context. **Circle 2 — collateral damage from the timing**: companies that had already passed the change on to their own customers find themselves caught out; **Conductor**, a multi-agent coding tool built on the Agent SDK, has to issue a denial (*"Anthropic has delayed the subscription updates to Claude plans"*). **Circle 3 — the underlying tension, which extends beyond Anthropic**: a quote from **Boris Cherny** (head of Claude Code) in April, during an earlier restriction, stating that subscriptions *"weren't built for the usage patterns of these third-party tools"* — an admission that **flat-rate plans and open-ended agentic usage don't mix**; **GitHub** settled the matter the same way, removing in June **Copilot**'s flat-rate *premium requests* model in favor of **token-based billing**, despite protests. Added to this, **the same week**, a **proposed class action** was filed in a California federal court, alleging that **Max** tiers fall well short of the usage multipliers advertised for intensive coding sessions. Anthropic does not say when a revised approach will arrive, only that it *"works to update the plan to better support how users build with Claude subscriptions."* **The author's final take**: between government pressure on Fable and Mythos, a planned **IPO**, and **rumored price cuts at OpenAI**, Anthropic is trying to **keep its developer base on its side** — and the suspension is, for now, a means to that end.

#Anthropic#Claude Agent SDK#Claude subscription

**Paul Sawers** — journaliste tech · signe ici pour **The New Stack**. Registre de **presse spécialisée** : l'article ne relaie pas seulement l'annonce · il la replace dans une série (les changements de facturation successifs d'Anthropic) · la compare à un précédent sectoriel (GitHub Copilot) et l'articule à trois pressions concomitantes (export control, IPO, concurrence). Sourçage explicite et attribué — le billet de Zed · l'analyse de Matthew Diakonov · le post de Conductor · une déclaration antérieure de Boris Cherny.

AI Coding Agents & Skills Auto-verified translation

Anthropic's Boris Cherny: Why Coding Is Solved, and What Comes Next

Interview with Boris Cherny (creator of Claude Code, Anthropic) at a Sequoia event (hosts: Asia, Lauren Reader). Cherny states ***"coding is solved"***: he himself has written **0 lines of code** since late 2025, the model writes **100%**, *"a few dozen PRs/day, 150 PRs in a single day record"*. Account of the genesis of Claude Code (Anthropic Labs incubator late 2024, Mike Krieger in charge of round 2, pre-PMF build *"for the next model"*, a first release that didn't take off, **exponential growth started with Opus 4 in May 2025**, accelerating with each new model 4 → 4.5 → 4.6 → 4.7). Current personal setup: **"most of my work I do from my phone"** (iOS), 5-10 sessions, **"a few hundred agents going, a few thousand at night"**, **`/loop` is the future** (cron + repeat jobs, agents babysitting CI, rebasing PRs, clustering Twitter feedback). **Routines** = the server-side equivalent, running with the laptop closed. SaaS outlook: no apocalypse, but a **reshuffling of Helmer's 7 Powers framework** (switching costs ↓, process power ↓, network effects/scale economies/cornered resources unchanged) and **10× more disruptive startups** over the next 10 years. Pivot analogy: the **Gutenberg press** (10% literacy in the 1400s → 70% over the following centuries, books 100× cheaper within 50 years), *"software will be similarly democratized, but faster than 50 years"* — *"the best person to write accounting software is not an engineer, it's a really good accountant."*

#Boris Cherny#Anthropic#Claude Code

Boris Cherny (créateur de Claude Code, Anthropic) interviewé par Lauren Reader (Sequoia) avec introduction d'Asia (Sequoia).

AI Coding Agents & Skills Auto-verified translation

How to Use Claude Code Like the People Who Built It

Cat Wu and Boris Cherny (Anthropic) explain how to use Claude Code like its creators: antfooding, plan mode, subagents, hooks, and extensibility — Every's AI & I podcast

#Claude Code#Cat Wu#Boris Cherny

Rhea Purohit (interviewer: Dan Shipper) · Cat Wu · Boris Cherny

Architecture & Construction Auto-verified translation

HOW CLAUDE CODE IS BUILT

Building Claude Code - AI-first Architecture - Product Engineering - Pragmatic Engineer

#Claude Code#Anthropic#AI

Gergely Orosz (auteur de l'article) · Boris Cherny · Sid Bidasaria · Cat Wu (équipe fondatrice de Claude Code)