Choosing the Right Level
A decision framework for picking Chat, Co-work, or Code for any task. Practical scenarios you'll actually face.
Three questions tell you which level to use, every time:
1. Am I working with files? No: Chat. Yes: Desktop, or Code if recurring.
2. Will I do this again the same way? Yes: Code.
3. Think, or act on files? Think: Chat. Act once: Desktop. Act repeatedly: Code.
Each question rules out two levels, so you rarely need all three. "No files" ends the decision at Chat.
Why it matters: when Chat frustrates you because you are pasting files all day, the easy conclusion is that Claude is not useful for your work. It is not Claude. It is the wrong level.
Ten real situations, part one. Run the three questions:
1. Hire a full-time employee or a contractor? No files, pure thinking. Chat.
2. A 60-page financial report from your CFO; find every assumption behind the revenue forecast. Files, one-time. Desktop.
3. A Monday pipeline report to your VP from the same CRM export, every week. Files, recurring. Code.
4. A difficult message to a team member about performance. No files, sensitive writing. Chat.
5. Six months of support tickets in a folder; find the top 10 complaint categories. Files, one-time. Desktop.
Part two:
6. A daily summary of your 20 most important emails with suggested replies. Files, daily. Code.
7. Preparing arguments for a salary negotiation. No files, thinking. Chat.
8. Budget vs. actuals spreadsheet; flag every line more than 15% over. Files, first run is one-shot. Desktop, then Code if it becomes monthly.
9. Three versions of one announcement: employees, customers, investors. No files. Chat.
10. Five weekly update docs from your team, combined into one summary every Friday. Files, recurring. Code.
Aim to make this call in under five seconds.
Four traps:
Chat for file work. Symptom: 5+ minutes per session copying content into the browser. Fix: Desktop.
Code too early. A bad manual process plus automation equals a bad process running forever. Validate first.
Over-automating creative work. A weekly LinkedIn post that needs fresh thinking each time is not an automation candidate. Test: would the exact same instructions produce a good result every week? If no, keep it in Chat.
One level for everything. Copy-paste friction, repetition, and creative-versus-consistent are your signals to switch.
Start simple, expand as friction appears. Chat first: it is where you build prompting instincts and learn what Claude is useful for. Consistent copy-paste friction means try Desktop. The same Desktop task three weeks running means consider Code.
Let your own friction drive the progression, not a schedule.
The typical arc: Chat in week 1, Desktop by week 3, Code by week 6. By day 90, people following it report reclaiming 3-5 hours per week from tasks Claude now handles automatically. Each automation frees time for higher-leverage work, and the whole system compounds.
Three questions: working with files? repeating it? think or act? Chat for thinking and writing, Desktop for files, Code for recurring automation. The ten scenarios give you practice; the four traps tell you what to avoid. Start with Chat, expand when friction says so, and validate before you automate. You now have the full mental model plus a 90-day progression.