Debugging across the whole stack with Claude Fable 5.1

Summary
This promotional demonstration video from Anthropic showcases Claude Code operating with the Claude Fable 5.1 model (1M context) to troubleshoot an automotive software bug. Without spoken voiceover, the video illustrates an engineer handing off a complex, multi-system vehicle climate failure ticket to Claude Code, which analyzes telemetry across boundaries, locates the root cause in code, verifies the fix, and resolves the issue in a simulation bench.

What is shown

• [00:00 - 00:06]: A vehicle center display simulator fails to turn on cabin heat, dropping the request (CLIMATE_REQ 0x3A2) with no status confirmation from the thermal controller.
• [00:10 - 00:20]: The user pastes a customer support ticket log into the Claude Code terminal UI (running Fable 5.1, 1M context) asking the agent to investigate while the user works on a separate brake safety pull request.
• [00:21 - 00:39]: Claude Code launches three explore agents in parallel to inspect support tickets, join ECU telemetry, and pull climate app logs.
• [00:40 - 00:54]: Telemetry analysis aligns timestamps between heat requests and heater activation, identifying an invariant 600s gap across 214,312 data points.
• [00:55 - 01:05]: Claude presents a hypothesis about a 600s retry timer; the engineer notes the ECU cannot take over-the-air updates so the fix must be in the app. Claude greps the code and finds #define RETRY_AFTER_S 600 in climate_app/src/wake_scheduler.c.
• [01:06 - 01:10]: Asked to prove the theory, Claude explains the car wake vs. heater wake sequence and adjusts retry timing to 90s, validating heat within 2 minutes across the dataset.
• [01:11 - 01:18]: Claude Code reruns the vehicle simulation bench (4.12.0-rc3), successfully confirming the heat request and bringing the cabin to 72°F.
• [01:19 - 01:30]: Outro titles display "Stay on track with Fable 5.1" and the Claude Code logo.

Claims & numbers

• Fable 5.1 context size is listed as 1M context in the CLI header ([00:10]).
• Claude Code identifies a constant 600s delay across 214,312 deltas ([00:51]).
• Claude reports that in 90% of delayed starts, the gap between request and heat-on is exactly 600 s ([00:57]).
• Claude determines the car heater wakes within 30s (worst case 46s), making a 90s retry sufficient to resolve the issue across the entire dataset ([01:09] - [01:10]).

Notable quotes

• [00:07]: "Debug across every boundary"
• [01:04]: "Found it. Since the wake update, heat-on is two steps: the car wakes, then the heater."
• [01:19]: "Stay on track with Fable 5.1"

Assessment
This is a stylized official product marketing video demonstrating Claude Code's multi-agent exploration and root-cause debugging workflow on an embedded software system. The terminal interactions and telemetry visualisations are accelerated and dramatised for presentation purposes rather than an unedited real-time capture.

Described by gemini-3.8-flash on 2026-09-29 from the video's audio and frames.