Guest article by **Peter Walker**, Head of Insights at **OpenRouter**, published on **October 22, 2026** in the Substack newsletter **OnlyCFO** (approximately **1,500 words**, OpenRouter charts). The piece addresses chief financial officers and draws its figures from the traffic of the author's inference gateway.
#tokenomics#inference economics#CFO
Peter Walker — Head of Insights d'OpenRouter ; article invité dans la newsletter OnlyCFO.
Episode of the video podcast **In Good Company** by **Norges Bank Investment Management** (Norwegian sovereign wealth fund), published on YouTube on **October 21, 2026**, **43 minutes**, in English. **Nicolai Tangen**, the fund's CEO, interviews **Eric Schmidt**, former CEO of Google (2001-2011).
#superintelligence#AGI#scientific discovery
Eric Schmidt (invité) · ancien PDG de Google ; Nicolai Tangen (hôte) · directeur général de Norges Bank Investment Management.
Talk by **Eno Reyes** (co-founder and CTO of **Factory**, whose "droids" agents are described in the introduction as used by hundreds of thousands of developers and companies such as **Nvidia** and **MongoDB**, right after a **$150 million Series C**), published on **September 22, 2026** on the **FirstMark Capital** channel (25 min 51 s video, transcript of about 5,300 words). He presents the "software factory" as an agent-driven feedback loop, and the role of humans as stewards of this factory.
#software factory#software factory#Factory
Eno Reyes — cofondateur et CTO de Factory ; conférence vidéo (FirstMark Capital).
Threat intelligence report published by Anthropic's **Threat Intelligence** team on **September 10, 2026** on anthropic.com (~36,000 words including indicators of compromise, downloadable PDF, unsigned). It covers abuse disrupted between **December 2025 and August 2026** across **seven** domains: cyber, influence, surveillance, conventional weapons, biology, fraud, distillation. All cases involve Haiku, Sonnet, or Opus; none involve Fable or Mythos, except for one distillation attempt.
#threat intelligence#AI misuse#Generative Threat Group
Anthropic — équipe Threat Intelligence (rattachée aux Safeguards) · rapport institutionnel non signé publié sur anthropic.com.
Article by **Chase Covington**, **Tomer Slaney** (partners, New York) and **David Pralong** (senior partner, Charlotte), published by the *McKinsey Transformation Practice* in **September 2026** (exact day unspecified, dated the 1st by convention); 8 pages, 2 exhibits whose content is not reproduced in the text. **(1)** Finding: the transformation office (TO) is slow to modernize its own tools; in a turnaround involving **3,000** employees, **more than 15** people produced a **300-page** report every four weeks. **(2)** Three pillars entrusted to agents: *performance intelligence*, *single source of truth*, *conversation facilitation*. **(3)** Reported gains: **35 to 40%** of time on core tasks, sometimes **70%**; a central team reduced from **ten to three** people. **(4)** Guardrails: cascading errors between agents, false alerts, traceability of each step. **(5)** Sequence: reporting first, action automation next, change management within the TO. The authors present the text as "a first look at the opportunity for TOs". The cases are not named, no measurement method is described, and two of the tools cited (**Wave**, **Lilli**) belong to McKinsey. The text follows on from [[sternfels-mckinsey-60000-people-20000-agents-officechai-2026-01-14]], where McKinsey already counts its agents among its workforce.
Product announcement published on the **Cloudflare** blog on **August 4, 2026** by **Will Papper**, as part of **Agents Week**: **Cloudflare Wallets**, presented as *"the programmable wallet for the agentic Internet"*. **The problem stated** is precise and well chosen: an agent that wants to try an API has to go through a login page **designed for humans**, have a human add a payment method, generate an API key, then figure out how to call the service. Two structural gaps explain this — *"Agents do not have a stable identifier to sign up for an API, and they do not have a native way to pay for APIs"* — with the consequence that *"AI agents often give up on these tasks entirely, kicking registration, payment methods, and API key generation back to humans"*. **The proposed architecture comes down to two wallet types**: **Account Wallets**, intended for humans who own a Cloudflare account (fund, delegate, withdraw), and **Virtual Wallets**, intended for agents, **operating via API key** and whose spending cap is **set by the account holder**. The announced guardrails are explicit: **allocation, allow list, maximum amount per transaction**. **The payment rail is the x402 protocol** (payments attached to HTTP requests) and the currency is **stablecoin** — which places the offering in a distinct camp from schemes built on card networks. **The most interesting argument is counterintuitive and central**: *"These limits may seem like constraints, but counterintuitively they give agents more freedom. If an agent is responsible for $10, you can worry less about its spending than if it is responsible for $1,000."* → **the cap is not what constrains autonomy, it is what makes it acceptable.** **Second component, more strategic than the first**: identity, via a **`cloudflare.pay`** namespace — a research agent could live at `research.example.cloudflare.pay`, giving the merchant certainty that it is talking to the agent of an identified organization. Cloudflare claims a deliberately minimal ambition (*"a human-readable identifier for a not-very-readable keypair, similar to the URL and IP-address pairings used in DNS"*), built on its existing building blocks (**Turnstile**, Bot Management, **Web Bot Auth** and its keypairs), and states its intent to adopt the schemes of the **x402 Foundation** as they emerge. **A decisive caveat about the status of the text**: **almost everything is in the future tense**. What exists on the day of the announcement is the **reservation of a handle**; payments, Virtual Wallets, guardrails, and the ramps for accessing funds are announced (*"Soon, you will be able to…"*). This is a **staking of position on a namespace**, more than a service going live.
#Cloudflare Wallets#agentic commerce#Agents Week
**Will Papper** — auteur de l'annonce sur le blog Cloudflare (lecture annoncée : 8 minutes). Publication rattachée à l'**Agents Week** de Cloudflare et étiquetée *Agents Week · AI · AI Bots · Developer Platform · Developers · Payments · Product News · x402*.
**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)
Anthropic launches Claude Fable 5 (a Mythos-class model made safe for general use) and Claude Mythos 5 (the same model, with guardrails lifted, restricted to cyberdefenders via Project Glasswing): state-of-the-art performance in software engineering, vision, long-context memory, and life sciences.
Televised debate on BFM Business (*Tech & Co Business* program, "The Debate" segment, 17 minutes) with **Rémi Jacquet** (CEO of Cast Software France, founder in 2023 of a think tank of about a hundred CIOs on the impact of generative AI on development, partnership with Cigref / Epita) and **Didier Girard** (CTO and CEO of **SFEIR**, a French IT services company (ESN) of about 1,000 people). Strong theses: *"writing code has become an anti-pattern"* (Girard), AI produces code of higher quality than most engineers and is *"2 to 10× more efficient"* — this is a reality, but the profession is not disappearing. The developer becomes a **conductor / agent manager / arbiter**, 14-day sprints are replaced by one-hour to half-day ***bolts***, the **Pizza Team** (8-10 people) no longer works in the agentic era, a new role is emerging — the ***product engineer*** —, the lifespan of a skill drops from **10 years to 1 year**, and **token** consumption becomes the *fuel* of value creation (NVIDIA anecdote allegedly paying bonuses in tokens, taxi driver metaphor for a driver who doesn't consume gas). SFEIR claims *"1,000 people, production capacity of 10,000"*. On the Cast side: positioning on ***harness engineering*** (deterministic vs probabilistic AI, control and guardrails), aligned with Sylvain Duranton's (BCG X) op-ed in *Les Échos* stating that *"an agent = an LLM + harnesses"*. Historical pivot: 2024 *prompt engineering* → 2025 *context engineering* → 2026 *harness engineering*. Key warning: *"the stronger AI becomes, the more we let our guard down — the more risks there are"* (Jacquet). Pivotal role of HR in the transformation, complete overhaul of the SDLC, recommendation to juniors to solidify software architecture fundamentals (*"code is the score, you need to master the symphony"*).
Episode #351 of the French-language podcast **If This Then Dev** (Bruno) with **Julien Lépine**, Chief Technology Officer of **AWS France** (13 years at Amazon), recorded on the sidelines of the **AWS Summit Paris** (April 1, 2026, ~10,000 attendees). Pivot thesis: in the agentic era, writing code becomes secondary, and value shifts toward **understanding context, architectural trade-offs, and human accountability**. Central proof point: the **redevelopment of Amazon Bedrock** — a critical platform handling thousands of billions of requests — by a team of **6 people in 72 days** (vs. an estimated 30 people / 18 months), **code entirely generated by AI**, without vibe coding. AWS is **standardizing internally on Kiro** (IDE + CLI, running on Claude Sonnet/Opus) for ~30,000 developers (announced by Matt Garman at re:Invent). Throughline: **keeping control** without reviewing everything — via **formal modeling (TLA+)** and **Raisonnement automatisé** to prove invariants and bound agents, **blameless post-mortem**, and the principle that "responsibility for an agent's action rests with the person operating it." Emergence of the **AI DLC** (sprints → multiple daily **Bolts**) and the risk of **cognitive overload / burn-out**.
#AWS Summit Paris#Amazon Web Services#code agents
**Julien Lépine** — Directeur de la technologie (CTO) d'Amazon Web Services France · 13+ ans chez Amazon ; ses équipes accompagnent les clients AWS sur le cloud · la data et l'IA. **Hôte** : Bruno (créateur et animateur du podcast *If This Then Dev*).