Skip to content
Dustin's AI Lab
Go back

The Day Opus 4.8 Went Haywire: tool call cannot be parsed

A one-day timeline from 2026-06-02: from hopping on X for moral support, to someone finally pinning down the root cause of tool call cannot be parsed.

This post has been merged into No Error Doesn’t Mean Success: Silent Failures, Opus Fabricating Tool Output, and the Hook That Finally Stops It. All of the original content lives there now, and that’s the only copy that gets updated.


15-Minute AI Adoption Diagnosis

Fill in a short form to book your free 1-on-1 diagnosis, and find out how you can work with AI without the pain and get a real productivity lift.

Book my free diagnosis
Share this post on:
Previous Post
Letting AI Write CAD From an Engineering Drawing: A Single Vision Model Can't Be Trusted to Read Topology
Next Post
A Week of Making Tutorial Videos With Claude Code: Remotion Animation and ffmpeg Pitfalls