Anthropic Redesigned the App Eleven Days Before My Book Launch
On July 7, Anthropic merged Chat and Cowork into a single window. Two tabs became one home, with a selector in the message box to switch between them. Cowork also landed on the web and the iPhone, where before it was desktop-only.
If you're a Claude user, that's a nice update. If you're eleven days from launching a printed book that teaches people how to use Claude — with the files built, the ISBNs assigned, and the cover locked — it reads a little differently.
My first thought was the obvious one: how much of the book just broke?
Don't guess. Scan.
I could have started rereading the manuscript from page one, hunting for trouble. Instead I did the thing the book itself teaches. I opened Claude, explained what changed, and had it sweep all ten chapters for every place the old interface appears — every tab, every toggle, every "switch to Chat mode."
Yes, I used Claude to find out how badly Claude had broken my book about Claude. The irony was not lost on me.
The scan came back in minutes, and the news was better than I expected. Out of an entire manuscript, the damage was confined to one chapter — the one on Deep Research, where I tell readers exactly where to find the Research toggle and how to get from Cowork back to Chat. Three passages and one reference card.
Why so little broke
It wasn't luck. Almost everything in the book describes what to do with Claude — give it real context, push back on the first draft, verify what comes back — and none of that depends on where a button sits. The only places that broke were the places I described the screen instead of the work.
That's the lesson if you're writing anything about software, whether it's a book or an onboarding doc for your team. Describe the work, and your material survives a redesign. Describe the pixels, and you're one product update away from a correction.
The fix
The rewrite took an evening. The three passages now match the new interface, and I checked that the changes didn't ripple — same page count, every chapter starting on the same page, so the table of contents still tells the truth. The ebook got the same fixes the same night.
But patching the text only solves this redesign. It does nothing about the next one.
So the book now carries a note in the introduction that says, plainly: Claude changes fast, this already cost me a rewrite during final production, and when your screen doesn't match a page, come to this website. There's now an updates section on the book's page here that logs every interface change that affects the book, newest first, with what to do about it.
Software moves faster than print. A printed book can't chase it — but it can point somewhere that does.
What I'd tell you to steal
If you make anything that references a living product, three moves are worth copying. Write about behavior, not button locations, wherever you can. Keep one URL you control and print that, because you can update a webpage at midnight but not a paperback. And when the product does move, don't reread your whole manuscript in a panic — have the AI sweep it and show you exactly what broke.
Eleven days out, that turned a crisis into an evening's work.
The book launches July 18. The interface it describes is current as of this week — and when that stops being true, the page you're reading now is where I'll say so.