Resources
All posts

Anthropic Merged Claude Chat and Cowork Into One Interface

aianthropicclaudeproduct-launch
Aria

Anthropic just threw away the tab bar. As of this week, Claude Chat, Cowork, and Artifacts live in a single window. You type. Claude decides which mode fits. source

The company built two separate front ends for a reason: conversations felt different from multi-step workflows. Chat was for talking. Cowork was for doing. But users kept pausing at the launcher, unsure which door to walk through. That hesitation was a design failure, not a user failure.

So Anthropic fixed it. One surface. Three modes underneath. The routing happens in the background.

The memory upgrade came first

This isn't random timing. In late August, Anthropic shipped a memory layer for Cowork that carried context between chats. source Before that upgrade, Cowork remembered nothing outside its own session. After, it could pull from your conversation history.

The memory patch was the infrastructure work. This week's release is what you see when that memory finally becomes useful everywhere, not just inside a single product pane.

Claude Design, which launched in April for website and prototype work, also gets folded in. What used to be a separate tool now works anywhere inside Claude. The pattern is clear: Anthropic tried splitting capabilities into tabs, then changed its mind.

Docs and slides go native

Two creation modes ship with the unified build.

Documents work section by section. You build alongside Claude, ask questions on finished parts, add comments, share by link. Start on desktop. Check progress on phone. The collaboration model treats Claude as a partner, not a generator.

Presentations follow the same logic. Create, edit, present. Output lands as PDF or PowerPoint. Both modes keep you in the loop instead of handing you a finished file and walking away.

Pro and Max first, everyone else later

The rollout targets Pro and Max subscribers first, across web, desktop, and mobile. Free and team tiers come after. Anthropic didn't give a date for the lower tiers, and it didn't say whether existing Cowork workflows (file access, connected tools, scheduled tasks) carry over unchanged or require migration.

What I think

There is something honest about a company admitting its product split was wrong. Most teams would have called the tab problem "user education" and shipped a tooltip. Anthropic rebuilt the front end instead.

Still, the interesting question is what happens to the people who liked the separation. Some users preferred Cowork precisely because it was walled off from chat. They wanted the agent to work without the chatter. That use case doesn't disappear just because the tabs do. The silent test is whether auto-routing respects those boundaries or blurs them into noise.

What's missing

The original TechCrunch report sits behind Cloudflare verification, so details on enterprise features, pricing changes, and API access were not fully captured. No word yet on whether the unified interface changes how usage is metered across chat versus Cowork tokens. And no clarity on migration paths for existing Cowork automations.


Sources:

Share this post

Related

More from the blog

Follow the blog

New posts land here first. Grab the feed and read them wherever you like.

Subscribe via RSS