Lesson 01

⁠

Estimated time: 8 minutes

Learning objectives

By the end of this lesson you'll be able to:

• Define Claude Cowork and explain what makes it a different way of working with Claude
• Understand Cowork as Claude working in your environment — on your files, in your apps, with your tools
• Tell Chat, Cowork, and Code apart, and know which to reach for when

Introducing Cowork

This video introduces Claude Cowork and the type of work it's built to do. Notice how Cowork functions: not as a smarter chatbot, but as a different way of working with Claude entirely.

Key takeaways

• Cowork is Claude built for the work, not just the answer. It meets you where you work — whether it's local on your machine, cloud apps, or your browser.
• Cowork is about delegating. Chat is still where you go to think out loud, draft, or ask. Cowork adds something new: the ability to describe an outcome and have Claude plan, execute, and deliver the whole thing.
• Cowork is built for multi-step, longer-running work. Tasks that span several tools, take a while to complete, and end in a real artifact — Cowork is designed to handle that whole arc end-to-end.
• You stay in control. Claude shows you its plan before it starts, by default asks before it takes actions that matter (sending, deleting, sharing), and lets you steer at any point.

What Cowork actually is

Cowork is a mode of Claude inside the desktop app where Claude works on tasks alongside you. You point it at a folder on your computer, connect the apps where your work lives (Gmail, Slack, Google Drive, your calendar), and describe what you want done. Claude makes a plan, works through the steps, uses the tools and files it needs, and saves a real deliverable back to your folder. You can also run Cowork in the cloud (in beta, on eligible plans) to start and check on tasks from the web and the Claude mobile app.

The mental model that matters most: Cowork is about delegating, not just chatting. Chat is still incredibly powerful — it's where you'll go to think through problems, draft and refine, brainstorm, ask questions, and have Claude as a sounding board. Cowork doesn't replace any of that. What it adds is something new: the ability to hand Claude an entire piece of work — context-gathering, analysis, file production, tool use — and have it come back completed.

This is the single biggest shift for new Cowork users to make, and it's essential to really get this down. Most people's first instinct — coming from Chat — is to type a question, see what comes back, type a follow-up, and iterate. That works in Cowork too, but you'll get the most out of it when you reach for it for the work you'd normally do yourself, not the work you'd normally ask about.

But the differences between the two go even deeper than this. Mechanically, Chat is turn-by-turn. It can pull from your tools, but you stitch the steps together yourself. It is purpose-built for bounded exchanges and quick thinking. Cowork, on the other hand, sustains a whole piece of work: it pulls from many tools at once, runs through multi-step plans, and returns the finished output. That's the gap uploads to Chat can't fully close.

You can see what makes a great Cowork task below.

How Cowork works in your environment

Cowork works in your environment. Not adjacent to it.

• On your files — Claude reads what's in the folder you point it at, writes finished outputs back.
• In your apps — Claude pulls context from the email, calendar, messaging, drive, CRM you've connected.
• In your browser — for web tools that don't have a connector, Claude in Chrome reads and acts on the page itself: dashboards, portals, or anything behind a login.
• With your tools — Claude takes action, not just describes what to do.

Chat vs. Cowork vs. Code

Now that you know what Cowork is, take a moment to see how it fits alongside the other two ways you work with Claude in the desktop app — Chat and Claude Code.

The three modes are built for different shapes of work. Chat is turn-by-turn dialogue — quick exchanges, brainstorming, exploratory thinking, one tool at a time. Cowork is what you've just been reading about: a workspace where Claude reaches across many tools, sustains work over time, and produces finished outputs. Code is a full development environment that runs inside your codebase, with terminal and git access — built for developers writing and shipping software.

The interactive below has two parts: a three-way comparison so you can see all three at a glance, and a six-task challenge that asks you to pick the right mode for each scenario.

To recap: Chat is for thinking with Claude. Cowork is for delegating to Claude. Code is for building software with Claude. Most knowledge workers will live in Chat and Cowork — and use them for very different things.

Lesson reflection

Think about a task you did recently where the value was in the doing, not just the thinking. Maybe it spanned multiple tools. Maybe it ended in a deliverable you assembled by hand. Maybe it's something you do every week that you'd love to leverage AI to handle for you.

Hold on to that task — you can come back to it in Lesson 3 when you start identifying your own Cowork use cases, and again in Lesson 4 when you delegate your first real task.

What’s next

In the next lesson, you'll get Cowork set up: install the desktop app, point Claude at a working folder, add your first connectors, and learn the permissions model that keeps you in control of what Cowork can do.