> ## Content Index > Fetch the complete content index at: https://www.livain.com/llms.txt > Use this file to discover other available public pages before exploring further. # Claude just merged Chat and Cowork — the decision that disappeared, and the caveat that didn't - URL: https://www.livain.com/blog/claude-merged-chat-and-cowork/ - Published: 2026-09-17T09:42:56.000Z - Updated: 2026-09-17T09:43:06.000Z - Description: Chat and Cowork are now one conversation with a full agent runtime underneath. What changes for operators: no more routing, deliverables inside the chat — and the local-tasks caveat most coverage skips. - Author: Remco Livain - Tags: AI, Marketing Tech, Claude Until this week, every conversation with Claude started with a decision nobody should have to make: is this a chat question, a Cowork task, or something for Code? Anthropic just killed that decision. Chat and Cowork are now one conversation, with the full agent runtime underneath. I recorded my take, intercut with Anthropic's own announcement and their Docs/Slides/Design demo: ### The decision that disappeared The routing choice sounds trivial and wasn't. Chat was the question-and-answer box. Cowork was where the real work happened: multi-step tasks, files, connectors, jobs that kept running after you closed your laptop. So before every task you did a little triage in your head, and you paid for it whether you noticed or not. Cal Newport described the cost in *Deep Work*, and it applies to tool-switching as much as task-switching: > "When you switch from some Task A to another Task B, your attention doesn't immediately follow — a residue of your attention remains stuck thinking about the original task." Three surfaces meant two extra switches per piece of work. [Anthropic's announcement](https://claude.com/blog/cowork-is-now-claude?ref=livain.com) frames the merge as convenience. I'd frame it as attention arithmetic: the triage is gone, and Claude decides what the task needs — an answer, a document, a deck, or a long-running job. ### Deliverables live in the conversation now The second change matters even more for anyone producing client work. You used to get a text answer, or a Word file exported to your computer that you then edited, saved, and re-uploaded to keep Claude in the loop. Now a doc, a slide deck, or a design is a living thing inside the conversation. You change it, Claude sees the change, you keep going. For small teams — or a solo operator running [client reporting](https://www.livain.com/blog/monthly-client-report-to-90-day-review/) and decks every week — the ping-pong between chat and file system was the real friction, and it's gone. ### Your computer becomes a capability, not a place Local folders, the built-in browser, computer use: all still there. But they're no longer a separate room you walk into. Any conversation can reach for them when the task needs it. Which brings me to the caveat that most coverage is skipping: **the runtime lives in the cloud, and your Mac doesn't.** "Keeps running after you close your laptop" is true for cloud tasks only. Anything touching local files needs the desktop app open. If your Monday routine reads files on your machine, closing the lid still stops it. One Claude is true for the interface; it's not yet true for where work physically runs. That distinction is the kind of thing that quietly breaks [scheduled routines](https://www.livain.com/blog/scheduled-claude-code-routine-failed-agentic-workflows-context/) when nobody checks it. ### Why now The timing isn't an accident. Meta's Muse showed what a consumer-first, one-app assistant feels like, and suddenly every vendor is collapsing their surfaces into a single front door — Anthropic here, Google with Gemini, X with Grok. The assistant is becoming the place where work is briefed, produced, and delivered. That's the same shift I keep tracking from the other side: platforms opening their tooling to assistants, whether that's [ad platforms](https://www.livain.com/blog/meta-just-opened-ads-manager-to-claude-heres-the-setup-that-actually-works/) or [infrastructure providers deciding what AI may consume](https://www.livain.com/blog/cloudflare-block-ai-training-ai-crawl-control/). It's rolling out to Pro and Max over the coming weeks; if your message box still shows the three tabs, that's normal, there's nothing to switch on. The interfaces are finally consolidating. The judgement about what to brief them with was never in a tab. ### Sources & further reading **External** [Anthropic: Cowork is now Claude](https://claude.com/blog/cowork-is-now-claude?ref=livain.com) (the announcement) Cal Newport, *Deep Work* (Grand Central, 2016) **Related posts** [Cloudflare now lets you block AI training on your website](https://www.livain.com/blog/cloudflare-block-ai-training-ai-crawl-control/) [Meta just opened Ads Manager to Claude](https://www.livain.com/blog/meta-just-opened-ads-manager-to-claude-heres-the-setup-that-actually-works/) [I replaced a monthly client report with a 90-day review](https://www.livain.com/blog/monthly-client-report-to-90-day-review/)