What Makes Cowork Different
Swipe to show menu
Cowork is the interface inside the Claude desktop app that lets Claude read and edit files on your computer, connect to external apps like Gmail and Calendar, and execute multi-step tasks end-to-end. It sits alongside two other interfaces — Chat and Code — as one of three “front doors” into the same underlying Claude models.
Core Concept
You've probably used Claude, or something like it, in a chat window. You ask, it answers, you copy, paste, and you do the work. Cowork flips that. You hand it the job, and it comes back with the finished thing.
That difference sounds small. It is not small. It changes what you can hand off. When Claude is answering, the work is still yours. When Claude is doing, the deliverable is Claude's - and your job becomes framing the outcome, approving the plan, and verifying the result. That's a completely different relationship with an AI, and it's what the rest of this course is built on.
How It Works (Step-by-Step)
Step 1 - Understand the three front doors
Claude has three interfaces, all powered by the same underlying models.
The familiar question-and-answer window. Fine for thinking, drafting, and quick questions. It cannot touch your files.
Claude running in sync with your computer. It reads your files, edits them, creates new ones, and connects to your apps via connectors. This is where the majority of the course is delivered.
The same agentic engine as Cowork, but for developers. It lives in the terminal. We will not be using it in this course.
You are not choosing a different brain. You are choosing a different door.
Step 2 - Understand the shift
Chat tells you how to do something. Step one, step two, step three. Useful, but you're still the one executing the steps.
Cowork just does it. It reads the files, it makes the changes, and it hands you back the finished file. The middle steps disappear from your workflow.
Step 3 - Recognize the four signals to switch out of Chat
Watch for these signals in your own work. If you notice any of them, hand the job over to Cowork.
- You're assembling - pulling pieces from multiple files into one deliverable.
- You're formatting - turning raw material into a polished document.
- You're moving between apps - copy from here, paste over there, again and again.
- You're repeating - the same chore, every single week.
If any of these describe what you're doing, that's not your job anymore.
Step 4 - Accept the trade-off
Cowork uses more of your plan's limit than Chat does. One Cowork task might run dozens of steps, and even spin up sub-agents to complete the job.
That is not a reason to avoid it. It is a reason to spend it well - on big, high-effort, repeatable jobs. Quick one-offs stay in Chat. That single habit keeps your usage exactly where you want it, especially on lower-tier plans.
Why This Matters
The gap between "AI as instructions" and "AI as delivery" is the single most important shift in how knowledge workers use these tools in 2026. Everyone who is still copy-pasting between Chat and their apps is capping their leverage at maybe two or three times a human. The people who have made the shift to Cowork are hitting ten times or more on repeatable work. This chapter is the frame you'll use for every other chapter - recognizing which mode is right for the job.
What Should Be Possible After This
- Name the three interfaces (Chat, Cowork, Code) and pick the right one for a task.
- Restate a task you'd normally do in Chat as a Cowork outcome ("I want X" instead of "please tell me how to do X").
- Recognize when you're assembling, formatting, moving between apps, or repeating - and know that's the moment to hand it to Cowork.
- Explain the usage trade-off and why Cowork is worth the higher spend on big jobs.
Thanks for your feedback!
Ask AI
Ask AI
Ask anything or try one of the suggested questions to begin our chat
What Makes Cowork Different
Cowork is the interface inside the Claude desktop app that lets Claude read and edit files on your computer, connect to external apps like Gmail and Calendar, and execute multi-step tasks end-to-end. It sits alongside two other interfaces — Chat and Code — as one of three “front doors” into the same underlying Claude models.
Core Concept
You've probably used Claude, or something like it, in a chat window. You ask, it answers, you copy, paste, and you do the work. Cowork flips that. You hand it the job, and it comes back with the finished thing.
That difference sounds small. It is not small. It changes what you can hand off. When Claude is answering, the work is still yours. When Claude is doing, the deliverable is Claude's - and your job becomes framing the outcome, approving the plan, and verifying the result. That's a completely different relationship with an AI, and it's what the rest of this course is built on.
How It Works (Step-by-Step)
Step 1 - Understand the three front doors
Claude has three interfaces, all powered by the same underlying models.
The familiar question-and-answer window. Fine for thinking, drafting, and quick questions. It cannot touch your files.
Claude running in sync with your computer. It reads your files, edits them, creates new ones, and connects to your apps via connectors. This is where the majority of the course is delivered.
The same agentic engine as Cowork, but for developers. It lives in the terminal. We will not be using it in this course.
You are not choosing a different brain. You are choosing a different door.
Step 2 - Understand the shift
Chat tells you how to do something. Step one, step two, step three. Useful, but you're still the one executing the steps.
Cowork just does it. It reads the files, it makes the changes, and it hands you back the finished file. The middle steps disappear from your workflow.
Step 3 - Recognize the four signals to switch out of Chat
Watch for these signals in your own work. If you notice any of them, hand the job over to Cowork.
- You're assembling - pulling pieces from multiple files into one deliverable.
- You're formatting - turning raw material into a polished document.
- You're moving between apps - copy from here, paste over there, again and again.
- You're repeating - the same chore, every single week.
If any of these describe what you're doing, that's not your job anymore.
Step 4 - Accept the trade-off
Cowork uses more of your plan's limit than Chat does. One Cowork task might run dozens of steps, and even spin up sub-agents to complete the job.
That is not a reason to avoid it. It is a reason to spend it well - on big, high-effort, repeatable jobs. Quick one-offs stay in Chat. That single habit keeps your usage exactly where you want it, especially on lower-tier plans.
Why This Matters
The gap between "AI as instructions" and "AI as delivery" is the single most important shift in how knowledge workers use these tools in 2026. Everyone who is still copy-pasting between Chat and their apps is capping their leverage at maybe two or three times a human. The people who have made the shift to Cowork are hitting ten times or more on repeatable work. This chapter is the frame you'll use for every other chapter - recognizing which mode is right for the job.
What Should Be Possible After This
- Name the three interfaces (Chat, Cowork, Code) and pick the right one for a task.
- Restate a task you'd normally do in Chat as a Cowork outcome ("I want X" instead of "please tell me how to do X").
- Recognize when you're assembling, formatting, moving between apps, or repeating - and know that's the moment to hand it to Cowork.
- Explain the usage trade-off and why Cowork is worth the higher spend on big jobs.
Thanks for your feedback!
