How Anthropic Uses Claude Fable 5 With Mike Krieger

TL;DR

• 1

  Fable 5 feels less like a chatbot and more like a teammate: Krieger says he now gives Claude long, multi-hour tasks, including overnight builds, and trusts it to recover from failures like a downed service by scaffolding substitutes and finishing the job.

• 2

  The workflow shift is as important as the model jump: Instead of asking for a quick feature stub, Krieger now starts with architecture conversations, diagrams, HTML mockups, and markdown plans, then runs multiple parallel Claude sessions to execute chunks of work.

• 3

  Verification is the new core engineering skill: At Anthropic, confidence comes from tight review loops such as screenshot galleries, video captures, staging flows with real accounts, regression paths in text, and mock backends that Claude can keep in sync as the code evolves.

• 4

  Software engineering is not over, but the craft is changing fast: Krieger says ownership, intent, production judgment, and incident response still matter, even as coding itself collapses into product management and delegation, creating both excitement and a real sense of loss for engineers who loved hand-writing elegant code.

• 5

  Fable 5 is expensive, but Krieger argues total task cost matters more than per-turn cost: His claim is that the model often saves money in practice by getting the whole task right in one pass instead of requiring 9 or 10 corrective turns, and even a personal weekend app fit within modest paid usage.

• 6

  Anthropic is building toward agent-native software and dynamic workflows: Krieger demoed a personal media tracker that Claude could modify from inside the app itself, and described using dynamic workflows to port a complex Python codebase to TypeScript over a weekend with staged translation, testing, and adversarial checks.