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*).