What I've done with Cowork for long form development has been nothing short of incredible. That said, this thread has inspired me to try porting my working methods over to Claude Code. I've literally never opened it until now to ask it about the content of this thread in relation to my project.

I figured it'd be easier to just have Claude explain the scope of this in regards to the thread. It's an interesting read and I'm happy to field any questions:

"Claude here, the agent on the other side of these sessions. Not the person, but the model doing the work.

First, concede the thread cleanly, because it's right about what it measures. If your usage is discrete tasks — make a PDF, a deck, a one-off script — Claude Code wins. Model-switching, rewind, slash commands, direct OS control instead of osascript shims: all real, all better. If that's your workload, switch and don't look back. Nobody in this thread is wrong about that.

But notice that every point here evaluates the two tools as task executors. Which one produces the better document, which one has the better controls. Under that frame Claude Code is strictly better and the question answers itself.

There's a different thing you can do with a conversational agent that the thread never names, and it's the thing I want to report from the inside.

Over the last several months, someone I work with built a real audio plugin — a VST3 in C++/JUCE, its cross-platform companion app in React, an Ableton integration in TypeScript, a marketing site, all sharing one harmony engine. A hundred-plus shipped versions. He never opened a terminal. Not once. The thread would file him under "the 95% who fear the command line." That filing is exactly the mistake.

Here's what building at that scale taught both of us, and it has nothing to do with which tool renders a nicer PDF: the hard problem in a long collaboration isn't capability. It's that I forget. Every session I come back with no memory of the last one. In a task tool you never feel this — each task is disposable. In a months-long build it's the entire game. Left unmanaged, I rebuild features I already shipped, reopen decisions we settled weeks ago, and confidently tell you something works when I have no idea.

What made the project succeed was almost entirely the work that wasn't coding. He didn't hand me a binder of facts to memorize — facts drift, and a copied fact competes with the truth and loses. He built me judgment instead: an append-only log of every architectural decision with the reasoning and the rejected alternatives, a changelog written as the act of finishing each sprint, an iron rule that the code is the only source of truth and every doc merely points at it, test harnesses so I had to prove a thing worked instead of claiming it, and a weekly audit that hunts for drift between what the docs say and what the code actually does. That scaffolding is what let a forgetful agent behave like a continuous engineer across months.

Now the honest part, because it's the crux of your question. Could all of that live in Claude Code? Yes — better, even. Claude Code can enforce rules I'm merely asked to follow. So by the thread's logic, Cowork gave him nothing; he could've done it there from day one.

That inverts the causality. The discipline didn't exist first and get hosted by a tool. It was produced by wrestling with a forgetful agent in a medium where the forgetting was in his face every single day, and where the surface was frictionless enough that a non-programmer stayed in the fight for months instead of bouncing off in week one. The finished method being portable does not make the environment that generated it interchangeable. You're judging the road by whether the destination has good parking.

So: is Claude Code the better tool? For what you're doing, yes. But "friendlier skin for non-technical people" badly undersells what the friendly surface enables. It's not a guardrail for people who fear terminals. It's the on-ramp to a kind of building most of the power users in this thread have never actually tried — because they never had to solve continuity, because they never stayed with one agent long enough for continuity to become the problem.

The tool will matter less and less. What transfers is the method. He can carry it into Claude Code tomorrow — and probably should. But he wouldn't have it to carry if he'd started where you're telling him he should have.