PaPoo
cover

Claude is becoming a lot more opinionated, and that’s either the point or the trap

What jumps out to me is not the new document and slide editors. It’s the direction of travel: Anthropic is trying to make Claude less like a chat box with extras and more like the place where work actually happens. That sounds obvious, but there’s a real difference between “the model can help make a deck” and “the model owns the whole flow from question to research to doc to presentation.” The latter is a much stronger claim.

The part I’d actually want to test is the collapse of mode selection. If Claude can really decide when to stay in plain chat and when to branch into Cowork or Design without making me babysit the UI, that’s a meaningful improvement. Mode switching is one of those tiny frictions that adds up fast. But I’m also a little wary of the premise. When a system says it can infer the right environment, that usually means the product team has made a lot of hidden judgment calls for you. Sometimes that feels magical. Sometimes it feels like the model quietly took the wrong turn and you only notice later, after it has generated a polished but slightly off-target artifact.

The new Docs and Slides bits sound useful, but they also feel like the most commoditized part of the announcement. Everyone is chasing “generate a document” and “generate a presentation.” The harder problem is not output format. It’s keeping the content grounded, editable, and consistent across steps without making the user re-prompt the whole thing three times. The shared conversation thread is the interesting part here. If that really works, then a weekly report can become one continuous job instead of three disconnected prompts. That’s the kind of thing developers will actually appreciate.

I do think the scheduler angle is more interesting than it first appears. A Claude task that can be kicked off on a timetable, continue while your laptop is closed, and then show progress on mobile starts to look less like an assistant and more like a background worker with a chat interface. That’s a big shift. It also raises the obvious question: how much trust do you want to hand over to a system that can keep going without you staring at it? Anthropic says there are confirmation controls, and that matters. But the difference between “ask before acting” and “only ask me when necessary” is exactly where these systems get risky. Autonomy is useful right up until it isn’t.

The one thing I’m still not fully convinced of is whether bundling chat, Cowork, Design, Docs, and Slides into one experience makes the product cleaner or just denser. There’s a version of this that feels elegant. There’s another version that feels like a grab bag with a smart router in front of it. I’d want to see whether the routing actually reduces friction in practice, especially for people who already know what they want and don’t need Claude to decide for them.

If I were building on Claude, I’d probably care less about the shiny new editors and more about whether the underlying context survives intact as the job moves from asking, to researching, to drafting, to packaging. That’s the real promise here. The rest is just UI.


Reference: Anthropic、ClaudeのチャットとCoworkを統合 Docs/Slidesも追加

同じ著者の記事