Think of Claude’s three products like a workshop with three very different workers. One is a whiteboard buddy who talks ideas through with you. One is an assistant who takes your to-do list and runs off to finish it. One is an engineer who builds the actual machine. They look similar at a glance, but handing the wrong job to the wrong worker wastes hours.
I kept confusing them for weeks, and I know I’m not alone. So when I found this crystal-clear breakdown from the creator over at Futurepedia, I had to share it. The author lays out exactly what Chat, Cowork, and Code each do, and the simple line that ties it together: Chat to think, Cowork to delegate, Code to build. Let me map the whole workshop for you.
🧠 Chat is the whiteboard buddy
This is the worker everyone already knows. It’s your back-and-forth for brainstorming, writing, research, and working through a decision. The original poster calls it a thinking partner, and that’s spot on. You can beef it up with Projects for permanent context, Connectors for your email or calendar, and Artifacts for that little doc or app window that pops open next to the chat.
But here’s the key detail the expert points out: everything Chat does happens inside one turn. It answers, then hands it back and waits for you. That’s perfect when the work IS the conversation. Naming a product, weighing a pricing change, decoding a contract clause you don’t fully get.
The warning sign? The moment you start copying Chat’s output into docs, stitching pieces together, or doing busy work around the answer. The creator says that’s your signal you’re in the wrong mode. That assembly work should have been delegated.
🍳 Cowork is the assistant who runs the kitchen
Here’s where you stop asking questions and start assigning work. You give Cowork a goal, and it builds a checklist, works through it step by step, and often spins up sub-agents to handle separate tasks at once. Then it comes back with a finished result.
The author uses a great analogy I love: Chat is a vending machine, Cowork is a kitchen. With the vending machine you drop in a prompt and grab the result. With the kitchen, you place an order, and it gathers ingredients, works through a multi-step recipe, plates it, and brings it out done. Three things make it different from Chat:
- The finish line moves. Chat is done when it gives an answer. Cowork doesn’t stop until the goal is actually achieved, whether that takes 2 minutes or 40.
- It gets its own workspace. A desk it keeps building on all session. It saves drafts, spreads out research, changes course, and stacks work step after step.
- It can run without you. With scheduled tasks, you set it up once and walk away. The person who shared this paints the picture: Monday morning while you’re asleep, Cowork reads last week’s email threads, pulls meeting transcripts, checks client news, and has a briefing doc plus a drafted follow-up email waiting with your coffee.
One nuance worth knowing. Cowork runs two ways. The desktop version works with the real files on your computer. The mobile and web version runs in the cloud, so it keeps going even when your devices are off, but it can’t touch your local files unless your desktop app is left open and connected.
The contributor shared a clever workaround I’m stealing: drop any files you want Cowork to use into a Google Drive folder and set that as its home base. With the Drive connector on, Cowork can read and save there from any device, computer on or off. Note that web and mobile Cowork is still in beta and rolled out to Max subscribers first.
🛠️ Code is the engineer
If Cowork is your assistant, Code is your builder. Apps, websites, automations, Chrome extensions, productivity tools. You describe what you want in plain English, and it writes all the actual code to make it real. And no, the author is clear you do NOT need to be a developer.
On desktop, you point Code at a folder and it builds the whole project there, every file and line. The creator recommends starting on desktop and skipping the terminal and developer tools entirely. On mobile and web you get two paths:
- Remote control. If Code is running on your home computer, you steer that exact session from your phone. The work still happens on your machine; your phone is just a window.
- Cloud sessions. These need a GitHub repo, which is just a project folder that lives online. Make a free GitHub account and an empty repo, or ask Code to push your desktop project up, then connect the cloud session to it.
Here’s the insight that made it all click for me. The expert explains that Cowork and Code share the same agentic engine underneath. Same core that plans and keeps going without you. Load just your files and apps and it’s Cowork. Add a code repository and it becomes Code.
The simple rule to remember
The original poster boils the whole thing down, and it’s genuinely useful:
- Chat to think when the work is a conversation. Brainstorming, writing, decisions.
- Cowork to delegate when you’d hand it to an assistant. A multi-step goal with a finished deliverable like a doc, spreadsheet, report, or organized folder. Describe the outcome, walk away, come back to it done.
- Code to build when your problem sounds like “I wish this tool existed.” Describe it, your engineer builds it.
Once this clicks, you stop defaulting to Chat for everything and doing the assembly yourself. The author also teased a fourth product called Design, still in beta, covered in a separate deep dive.
This breakdown genuinely changed how I reach for Claude. Watch the full video for the walkthrough and the little demos that make each one land.