Decision guide
Claude Projects vs Cowork vs Code
Projects save context. Cowork handles bounded delegated tasks. Code works with folders and files. The trick is choosing the smallest surface that fits the job.
The difference in one sentence
Use Projects when Claude needs reusable context, Cowork when Claude needs to complete a bounded task, and Code when the work lives in files you want to inspect.
Plan access can change. If Projects are not visible on your account, use the same idea as a plain standing brief: one page of context, examples, and review rules that you paste or keep in your course folder.
| Surface | Best for | Beginner mistake |
|---|---|---|
| Projects | Saving context, examples, tone, and reusable instructions for repeated thinking or drafting. | Treating a Project like a worker instead of a context shelf. |
| Cowork | Delegating a bounded task with inputs, desired output, and a review step. | Asking for an open-ended job that never clearly ends. |
| Code | Reading, editing, organizing, and checking files inside a folder. | Opening too much scope before learning diff review and Git checkpoints. |
Choose by the shape of the work
A real example
Suppose you run a weekly client update. In a Project, you save the client background and tone examples. In Cowork, you ask Claude to read this week’s notes and draft the update for review. In Code, you maintain the client brief, templates, and archive of prior updates in one folder.
None of these surfaces is “better.” Each one has a job. The course teaches the progression so beginners do not start in the deepest end first.