QWE AI Academy Key takeaway: stop picking a lane
Most recaps bury this: on Pro or Max, if the message box still shows separate Chat and Cowork labels, you do not have the merge yet – even after the September 16, 2026 headline. Same plan, different clocks. Help Center wording is plain: nothing to enable; the unified UI shows up when your account is in the wave.
Claude Cowork and chat are now one Claude means one thread can answer a quick question, then move into research, a finished doc, and a deck – no mode pick first. Claude routes depth. Cloud work can keep running after the laptop closes. Docs, Slides, and Design sit in that thread (beta on paid plans).
Below: old toggle vs unified surface, a copy-paste walkthrough for the winner, and rollout traps competitors gloss over.
What just changed (short version)
Cowork was the multi-step lane – files, connectors, longer runs. Chat stayed turn-by-turn. People guessed which box owned a task, and work started in one place did not carry cleanly into the other. Anthropic’s announcement ends that choice.
As of that September 16, 2026 post: Pro and Max on web, desktop, and mobile over the coming weeks; Team and Free “soon”; Enterprise admins get at least 30 days’ notice. Tasks, projects, connectors, skills, artifacts, and files carry over. Global instructions land under Instructions for Claude in Settings → General. The Code tab stays put – this merge is chat + former Cowork, not Claude Code.
Method A vs Method B: toggle or just ask
No unified UI yet? You’re still on Method A.
| Method A – Chat / Cowork toggle | Method B – one Claude | |
|---|---|---|
| How you start | Pick Chat or Cowork in the message box | Type the goal in any conversation |
| Who decides depth | You, before the first message | Claude, from the request |
| Context carry | Easy to strand work across modes | Same thread holds Q&A + deliverables |
| How you know you have it | Toggle visible | Toggle gone (Help Center test) |
| Best when | Rollout has not hit your account | You want brief → doc → slides without restarting |
Method B wins once it’s live. Method A still works until the UI lands – but every handoff costs context and clicks.
Walkthrough: one thread from brief to deck
Assume Method B (no Chat/Cowork split). Open Claude on web, desktop, or mobile on a Pro or Max account that already lost the toggle.
1. Start with the messy goal, not the tool name
Don’t write “open Cowork.” Write outcome + constraints:
From the attached call notes and CRM export, draft a two-page churn risk memo for our Friday ops review.
Use our usual severity labels. Call out accounts that need a human touch this week.
Then build a four-slide handout I can present in Claude and download as PPTX.Attach files or point at connectors you already linked. Unclear inputs? Claude asks first – default is check before actions. You can switch to fewer check-ins later if you want longer stretches without prompts.
2. Let it draft the living doc
Want an editable document in-chat? Ask in plain language or use the entry points in the Claude Docs guide:
- Natural language: “Turn this into a shareable ops memo.”
- Slash:
/docs - Message box: Output → Docs
It may ask a couple questions, then draft on screen. Edit yourself, comment for Claude, or request another pass. Export: Word (.docx), PDF, Markdown, Google Docs. Docs is beta on Pro, Max, Team, and Enterprise – not Free – and on by default on Pro/Max/Team (Settings → Capabilities to turn off).
Turns out Docs burn the same plan usage pool as other Claude work. A research pass + multi-section memo + deck chews quota faster than short Q&A – plan for that before a marathon session.
3. Spin slides from the same conversation
Stay put. Ask so the deck inherits the memo’s framing:
From this memo, make four ops slides: risk tiers, accounts to call, owners, next checkpoints.
Keep every number identical to the memo. I'll present here, then download PPTX.Edit on the canvas, present in Claude, or download PowerPoint or PDF (product post). Design also runs inside conversations; standalone Design still works if that’s your habit. Deliverables get a shareable link you can open on your phone.
Pro tip: When the first run looks right, schedule the recurring version – “same memo shape every Friday” – so Claude starts without a fresh briefing. Pair connectors you already trust instead of re-pasting context weekly.
4. Check progress off-desk
Cloud-backed sessions are why Cowork landed on web/mobile earlier: leave work running, glance from your phone, finish edits at the desk. Same conversation. No product hop.
Think of the old setup like two desks in one office – you kept walking the hallway with a half-finished stack. One Claude is a single desk with drawers; the tools still exist, you just stopped labeling the chairs.
Edge cases that actually bite
Staged UI. Pro/Max is not “today for everyone.” Message box still says Chat and Cowork? Method A. Don’t hunt a hidden flag – accounts on the same plan flip on different clocks.
Usage math. Claude Docs counts toward plan limits. Heavy doc + deck days are why Max exists for some teams. As of the pricing page tied to this launch window: Pro $20/mo ($17/mo annual); Max from $100/mo (5×) or $200/mo (20×). Pricing and bundled Docs/Slides/Design notes can change – recheck claude.com/pricing before you budget.
Check-in default. Factory setting is not full autopilot. Claude asks before actions unless you prefer fewer check-ins. Chatty mid-task usually means intentional control.
Code is still separate. Model picker and Code tab stay where they were. Software shipping stays on Claude Code; this merge folds knowledge-work agent behavior into everyday chat.
Enterprise lag. Admins get ≥30 days’ notice. Docs/Slides/Design are beta; org owners choose when those tools turn on. Team/Free timing is only “soon” – no hard public calendar date in the announcement materials.
Will Anthropic drop the Cowork name in the UI entirely, or keep it as a Recents label forever? The brand already slides toward “just Claude,” but help articles still teach both worlds during the handoff – so vocabulary may lag the product for a while.
FAQ
Do I need to migrate my old Cowork projects?
No. Open the app and continue – tasks, projects, connectors, skills, artifacts, and files carry over. Old Cowork global instructions sit under Instructions for Claude (Settings → General).
I still see Chat and Cowork – am I missing a feature flag?
No flag. You’re mid-wave. On Pro or Max the visible toggle is the signal Method B isn’t on your account yet. Keep working as today. When the labels vanish, describe the task in any thread and let Claude pick depth. Free/Team follow Pro/Max; Enterprise follows admin notice windows.
How is Claude Slides different from older Design decks?
Slides is the in-conversation path: draft, edit, present, export PPTX/PDF – built because decks ate a huge share of Design usage. Design still covers broader visual work and remains usable standalone. Use Slides when the deck should grow out of the same chat as the brief. Use standalone Design when you’re already in a pure visual workflow and don’t need the memo thread glued on.
Open Claude on the device you use most, check whether the Chat/Cowork split is gone, and run one real deliverable – short memo plus a small deck – from a single prompt. That’s the product shift in one sitting. Capability list and carry-over rules: Anthropic’s Help Center article next to the blog post.