Cowork · Lesson 01 Pro ~11 min read Install + first session

Cowork: a real coworker on your desk.

Cowork turns the Claude desktop app into a real working environment — Claude (or Copilot, when GA) reads your files, runs scripts, drafts documents, automates the boring stuff. It's not a chat upgrade; it's a different category. This lesson covers what Cowork actually is, how to install it, the security model that keeps your data safe, and your first useful session.

The mental model

Cowork isn't a smarter chatbot. It's a coworker with desk access.

The difference between Cowork and regular AI chat is the difference between asking a consultant for advice over the phone vs. handing them a laptop with access to your files. Same intelligence, dramatically different leverage.

Cowork can read files in folders you've connected, edit them, run code in a sandboxed Linux environment, call connected services like Outlook or SharePoint, and present finished work back to you. You stay in the chat window — but the work happens on your actual machine, with your actual data.

This means your prompts change. Instead of 'how do I summarize this report,' you say 'read the report in my Downloads folder and produce a 5-slide deck of the key findings.' You're delegating outcomes, not requesting answers.

Workflow 01 Install and set up Cowork

1

Get Cowork running with your folder connected

Cowork lives inside the Claude desktop app. Installation is straightforward but the folder-connection step is the one most people miss — without it, Cowork has nothing to work on.

The prompt that works

Setup stepsSetup sequence: 1. Open the Claude desktop app (or Copilot Frontier Firm tenant) 2. Toggle on 'Cowork mode' in settings 3. Click 'Connect a folder' — pick one specific folder you want Claude to work in (Documents, a project folder, etc.) 4. Test it: ask 'list the files in my connected folder' 5. If you see your real file names, you're set up correctly

Best use cases

  • First-time setup on a new computer
  • Switching to a new working folder for a different project
  • Connecting an additional folder (you can have multiple connected)
  • Verifying after a major software update
Don't connect your entire user folder or 'C:\' — that gives Cowork access to too much. Connect specific working folders only. You can always add more later.
Time savings: Setup time: ~10 min. After that, every session is faster than starting from scratch in chat.

Workflow 02 Understand the permission model

2

What Cowork can and can't do without asking

Cowork has a security model designed to keep you in control. Some actions are automatic (reading files in your connected folder); others require explicit permission (writing files outside the folder, running code that touches the network, deleting things).

The prompt that works

The permission mapWhat Cowork can do automatically: • Read any file in your connected folder(s) • Create new files in your connected folder(s) • Edit existing files in your connected folder(s) • Run code in its sandbox (the Linux environment, not your real machine) What requires your permission: • Delete files (always asks) • Write to folders you haven't connected • Take actions in connected apps (sending email, etc.) • Access browser cookies or saved passwords (never, even with permission)

Best use cases

  • Understanding why Cowork asks before deleting
  • Knowing what's safe to delegate without oversight
  • Setting up a project where you want stricter limits
  • Onboarding a teammate who's worried about access
Cowork never reads files outside your connected folders. If you ask it to 'find all my tax documents,' it can only search what you've connected — by design.
Time savings: Trust calibration: 20 min of reading this once = years of confident delegation.

Workflow 03 Run your first useful session

3

A real first task that proves the value

The fastest way to internalize Cowork is to give it a real task that would take you 30+ minutes manually. Don't start with 'hello.' Start with something you've been putting off.

The prompt that works

First useful taskTry this exact prompt (modify for your situation): "Look through my connected folder. Find any documents from the last 90 days that look like meeting notes, call transcripts, or interview write-ups. For each one, give me: - The date (from the filename or content) - A 2-sentence summary of the main topic - Any action items mentioned that don't seem to have been done yet Present it as a single markdown table I can copy."

Best use cases

  • Triaging a backlog of meeting notes
  • Finding orphaned action items across documents
  • Building a quick index of recent work
  • Catching up after a vacation or absence
Resist the urge to use Cowork for things you'd be faster at directly. The win comes from tasks where the manual version would be 30+ minutes — file synthesis, batch operations, anything tedious.
Time savings: First real task: typically saves 30-60 min vs. doing it manually.
About Cowork

Cowork is currently a research preview from Anthropic. The Microsoft Copilot version is rolling out through the Frontier Firm program and will be generally available in M365 Copilot over time. The capability and concepts in this lesson apply to both — the entry point differs, the work pattern is identical.

Your first 60 minutes with Cowork

Install Cowork. Connect one specific folder. Run the 'find recent meeting notes' prompt above. The first time the table appears with real summaries from your real files, you'll get why this is a different category from chat.

Back to Claude Mastery → Try a prompt in the playground →

What you can do now

  • Install and authenticate Cowork in the Claude desktop app
  • Connect a specific working folder (not your whole drive)
  • Run a real task that would have taken you 30+ minutes manually
  • Understand which actions require permission and which don't
  • Know how to disconnect a folder if you want to stop access
Pro
Up next in Claude Mastery

Lesson 02 · File workflows: batch operations, transformations, cleanups

Once Cowork is connected, the biggest immediate win is anything involving multiple files at once. Renaming, reorganizing, converting formats, extracting data — the patterns that save you hours. See the track →