The latest Claude apps let you pick Chat or Cowork from the same message box — which means the same small question comes up every time: “which one should handle this?” The rule is simpler than it looks. Chat is the default; Cowork is for two specific signals. One flowchart settles most cases.
🟢 Model references match the current lineup · model notice · Fable subscription
Fable 5 and 5.1 subscription (updated September 7, 2026): Claude Fable 5.1, released September 1, 2026, is the current Fable model and Fable 5 is now legacy. Plan terms are the same for both — Max and Team Premium plans include Fable at up to 50% of the weekly usage limit; Pro and Team Standard use usage credits (
Update (September 27, 2026): Since September 16, 2026 Cowork is built into every conversation and the Chat/Cowork picker is gone (rolling out to Pro and Max; Anthropic's words: "Claude Cowork is now just Claude"). File and folder work still happens in the desktop app, and scheduled tasks run in the cloud. Any "pick a mode" wording below reflects the pre-integration state. Details: Claude Cowork explained (after the integration).
Chat is the default
Questions, writing, brainstorming, translation, analyzing pasted material, reviewing a code snippet — for most everyday work, Chat is the fastest and lightest option. Upload files into the conversation when needed; use a project and its documents and instructions attach to every conversation automatically. Above all, Chat shines at work you steer as you go — you can redirect mid-course with a single message.
It is also the lighter option on usage. Cowork executes many steps on its own, so long tasks consume more — and per the official docs, auto-approve mode uses more of your usage limit because Claude performs safety checks on each action for you. Routing a one-line question through Cowork is simply wasteful.
Two signals that mean Cowork
- Signal 1 — the task touches files on your computer. Organizing a messy Downloads folder, sorting hundreds of screenshots, turning a receipts folder into a spreadsheet. Chat cannot open your local folders; Cowork connects to one and reads, writes, and saves results inside it.
- Signal 2 — you want to step away and collect the result. Describe the outcome, do something else, come back to finished work — long delegated jobs that create and edit multiple files.
Either signal on → Cowork. Both off → Chat. That is the whole rule.
Cheat sheet
- Planning a trip, polishing an email → Chat
- Cleaning up a messy Downloads folder → Cowork
- Drafting and revising a blog post → Chat
- Receipts folder → expense spreadsheet → Cowork
- Pasting a report for feedback → Chat
- Summarizing a whole folder of meeting notes → Cowork
- Debugging questions, concept explanations → Chat
Three rules when you use both
- Memory does not cross over. Cowork sessions do not know what Chat remembers about you (stated in the official docs). If a task needs current context, write it into the prompt. The related article below covers the mechanics.
- Never give the same job to both sides at once. You risk conflicting results or two sessions editing the same files. One job, one side.
- Record decisions in documents. Project files are the bridge between the two spaces. Keep a status document updated and any new session — on either side — starts from the same picture.
Common beginner mistakes
- Expecting Cowork to remember your chats — it will not. Pass context via documents or the prompt.
- Connecting a folder of important originals first — start with something low-stakes, or a copy.
- Sending one-line questions to Cowork — Chat answers faster and burns less usage.
Related
- Chat projects vs. Cowork projects — what carries over (tested)
- What is Claude Cowork? — Beginner guide
- Claude vs. Claude Code vs. Cowork — which one to use