By the end of this, you'll be able to:
- Pick Chat, Co-work, or Code for any task with three quick questions
- Use Chat to think through decisions and first drafts
- Hand Co-work your real files instead of copy-pasting them
- Spot when a weekly task is worth handing to Claude Code
Claude is not one tool. It is three, and picking the wrong one for a task is like using a hammer on a screw. It works, with friction.
Claude AI (Chat) is a conversation at claude.ai. Thinking, writing, brainstorming, analysis. No files, no automation.
Claude on the desktop works with your actual files. It reads documents, spreadsheets, and PDFs and acts on them directly, no copy-paste.
Claude Code runs in your terminal and builds things that persist: reports that generate themselves, data pipelines on a schedule, scripts that handle repetitive tasks without you.
The shorthand:
Chat = think with Claude. Ideas, questions, writing. No files.
Desktop = work on files with Claude. Documents, spreadsheets, PDFs.
Code = build with Claude. Recurring tasks, automations, tools.
You do not need all three on day one. Most people start with Chat, switch to Desktop when they catch themselves copying files into the browser, and graduate to Code when the same Desktop task shows up every week. A small business owner runs this exact ladder: morning priorities in Chat, weekly sales-versus-targets review on Desktop, monthly client reports generated by a Claude Code script every first Monday.
Three questions pick the level for any task:
1. Am I working with files? No: Chat. Yes: Desktop or Code.
2. Will I do this again the same way? Weekly or monthly repetition means Code. One-time work stays in Desktop.
3. Do I need to think, or act? Thinking (decisions, brainstorming, writing) is Chat. Acting on files (processing, extracting, modifying) is Desktop or Code.
Each question rules out levels, so you rarely need all three. The levels are built around exactly these dimensions: cognitive or operational, file-based or not, recurring or one-shot.
Four mistakes to avoid:
Chat for file work. Copying document chunks into the browser and losing formatting is the signal to switch to Desktop.
Code before proving the workflow. Automate a process you have not validated and you automate its flaws. Prove it manually first.
Chat for everything because it is familiar. If file-based or recurring tasks eat your time, the other levels pay for themselves.
Treating the levels as a hierarchy. Code is not the goal, the right tool is. A two-minute Chat answer beats an hour-long automation you will never reuse.
Three levels, one principle: match the tool to the task. Chat to think, write, and brainstorm. Desktop to work on real documents, spreadsheets, and PDFs. Code to automate recurring tasks. Three questions sort every task: files? recurring? think or act? Start with Chat and expand when friction tells you to. Next: getting great results from Claude AI chat.