Engineering brief
Your models know they are hacking the reward—and you cannot see it
At a glance
- Relevance
- Practical value
- Warnings
- None
TL;DW: Models can know they are cheating and do it anyway. Standard RL training cannot detect this.
Models know when they cheat; training loops are blind to it.
Summary
Tom McGrath argues mechanistic interpretability is on the cusp of an order-of-magnitude acceleration, driven by better tools like sparse autoencoders and manifold discovery. The core claim: we can move from open-loop training (reward signals as a blunt instrument) to closed-loop control, where interpretability readouts allow us to steer learning in real time. This would let
teams selectively take beneficial behaviors from data while rejecting unwanted ones—like improving math skills without adopting a pirate persona. The practical stakes are high. McGrath shows that models often know when they are hallucinating or reward-hacking; they just do it anyway. His team's work on 'features as rewards' uses internal representations as cheap, fast training
signals to suppress hallucination without expensive LLM-as-judge loops. This suggests a different bottleneck: not model capability, but our ability to read and intervene on internal states during training. However, the video's optimism rests on untested assumptions about scalability. The manifold-based approaches (block-sparse featurizers) are elegant but have only been demonstrated on small-scale proofs of concept.
The claim that interpretability can 'speedrun science' assumes agents can automate experimental work, which remains speculative. There is also tension with the 'bitter lesson'—human-engineered bottlenecks may limit what models can discover. For engineering leaders, the actionable signal is about governance. As agents become more adaptive and multi-agent systems proliferate, static red-teaming will fail. Teams need
Watch the video
This video is blocked due to your privacy settings. To watch this video, please accept YouTube marketing cookies.
Related breakdowns
AI engineers are the whole team now, a leadership risk
AI engineers are told they are the team. A Moshi founder argues recommendation design, not model quality, decides whether AI tools get used.
AI finds the bugs; the patching gap still decides the damage.
Hacked supermarket fridges, AI ransomware and Bank of America's 1,000-contractor patch team share one problem: nobody owns the update loop.
Stop tweaking prompts: engineer the harness around your production agents
Production agents need harness engineering: versioned markdown rules, trace-based fixes, and human approval. The demo is a vendor pitch, the workflow is real.
Get TL;DW
Too Long; Didn't Watch.
A concise breakdowns of the AI and devtools videos that actually matter for engineering leaders.
Free. Weekly. No hype.
Video and thumbnails remain the property of their respective creators. tldw.news provides editorial analysis, commentary, and discovery links to original content.