AI Builders Brief
?
← BACK TO TODAY

Follow builders, not influencers.

2026.05.13

25+ builders tracked

TL;DR

Waymo won by making safety the product, not the tradeoff. Anthropic shipped auto mode for Claude Code, pushing safer no-prompt use and tightening the agent loop.

BLOG UPDATES
1
Anthropic Engineering

Claude Code auto mode: a safer way to skip permissions

Anthropic adds auto mode to Claude Code for safer no-prompt use

Lead: Anthropic launched Claude Code auto mode, a middle ground between constant approval prompts and fully unsafe permission skipping, using model-based classifiers to decide which actions can run without human clicks.

Numbers:

  • Manual prompts are accepted 93% of the time, contributing to approval fatigue.
  • Evaluation on 10,000 real internal tool calls, 52 real overeager actions, and 1,000 synthetic exfiltration attempts.
  • Full pipeline results: 0.4% FPR on real traffic, 17% FNR on real overeager actions, and 5.7% FNR on synthetic exfiltration.
  • Stage 1 alone: 8.5% FPR, 6.6% FNR on real overeager actions, 1.8% FNR on synthetic exfiltration.

So What: Auto mode is built for builders who want more autonomy without turning off guardrails: safe reads and in-project edits pass through, while risky shell commands, external fetches, cross-boundary actions, and destructive operations get routed to a transcript classifier. Anthropic says the system is designed to block “dangerous actions that aren’t aligned with user intent,” while letting routine coding move fast. The company also strips assistant text and tool outputs from the classifier to reduce prompt injection risk, and adds a server-side probe that warns the agent when fetched content looks suspicious. In practice, this is a safer alternative to `--dangerously-skip-permissions`, but Anthropic is explicit that it is not a replacement for careful human review on high-stakes infrastructure.

PODCAST HIGHLIGHTS
1

Waymo won by treating safety as the product, not the tradeoff

The Takeaway: Dmitri Dolgov’s edge is simple: ignore hype, build for the long tail, and make safety the foundation from day one.

  • Waymo didn’t win by chasing demos; it won by grinding through the ugly middle, where “easy to get started” turns into brutally hard product work.
  • Dolgov rejects the fake split between end-to-end AI and structured systems: the real answer is end-to-end plus the extra machinery needed for validation, simulation, and deployment at scale.
  • Safety isn’t a slogan at Waymo; it’s the operating system, and the payoff is measurable: more than 170 million fully autonomous miles and a reported 13x safety advantage over human drivers in cities where it operates.

Dmitri Dolgov, Waymo’s co-founder and longtime technical leader, has been building autonomy for nearly two decades, from the DARPA challenge to today’s robotaxi fleet. His story is less about genius flashes than stubborn accumulation: learning physics in Moscow, getting hooked on autonomy as a “light switch moment,” then spending years turning a research project into a real service.

What stands out is how unsentimental he is about progress. The AV boom-and-bust cycles didn’t surprise him; breakthroughs always create a rush of optimism, but they don’t erase the “long tail” of hard problems. His answer was patience, not pivoting. “It’s not going to be an easy problem, but it’s a very important one,” he said.

That mindset shows up in Waymo’s architecture too. The company’s foundation model powers the driver, simulator, and critic, blending multimodal sensing with world understanding and language. But Dolgov is clear that vanilla end-to-end isn’t enough for a system that has to operate safely in the real world. The result is a philosophy that feels almost old-school: earn trust, validate relentlessly, and let the product prove itself one mile at a time.

STAY UPDATED

Daily builder insights, straight to your inbox.

Prefer RSS? Subscribe via RSS

ARCHIVE