Cowork With Your Files, Folders & Connected Tools

This is the heart of Cowork: Claude working directly on your real files and reaching into the tools you already use. Lesson 1 set it up; now let's actually put it to work.

Working on real files and folders

In Chat, you upload a file and Claude reads it. In Cowork, you give Claude a folder and it can read, edit, and create files inside it — the work lands as real files on your computer, not as text you have to copy back out.

Cowork handles a wide range of file types, including:

Documents — Word (.docx), PDF, .txt, Markdown, HTML
Spreadsheets — Excel (.xlsx), CSV
Slides — PowerPoint (.pptx)
Data — JSON, YAML, XML, TOML
Images — it can see and describe them
Notebooks & code — Jupyter, and most code files

The mental model: a folder is a workspace. Whatever's in it is Claude's material; whatever you ask for shows up in it as new or edited files.

Tasks that only make sense in Cowork

These are the jobs where copy-pasting in Chat would be miserable, so Cowork is where they belong:

Turn a pile of source material into a deliverable

This folder has my raw research — articles, notes, and a spreadsheet. Write me a 2-page briefing (briefing.md) that pulls the key findings together, with a short "what we should do" section at the end. Cite which source each finding came from.

Clean up and restructure data

Open expenses.csv, categorize each row (travel, software, meals, other), fix the inconsistent date formats, and save a tidy version as expenses-clean.csv. Then give me a one-paragraph summary of where the money went.

Reorganize a messy folder

This Downloads folder is a mess. Group the files into sensible subfolders by type and topic, rename anything with a useless name like "doc1final2", and leave a what-i-did.md explaining the new structure. Ask me before deleting anything.

Draft from a template

Using proposal-template.docx as the format and the notes in client-brief.md as the content, draft a tailored proposal and save it as acme-proposal.docx.

Notice the pattern: point at the material, describe the finished result, name the output file. Claude does the multi-step middle.

Working with images and screenshots

Cowork can see images in your folders — analyze a screenshot, read a chart, transcribe a photo of handwritten notes, or critique a design mockup, then write up what it found.

Connecting Cowork to your tools

Files on your computer are only half of it. Cowork also reaches into the apps and services you use through connectors (built on the same MCP standard you'll meet in Module 8). Once connected, Claude can pull in and act on information that lives outside your folders — for example email and other services your plan supports.

The standout connector for everyday work is Claude in Chrome: it lets Cowork drive your browser to do web tasks — look things up, pull information off a page, fill things in — without you switching windows back and forth. So a task can span your local files and the web in one go:

Check the three competitor pricing pages I've bookmarked, pull their plans and prices into a comparison table, and save it as pricing-comparison.md next to my own pricing notes.

Connectors are managed in the app's settings. Add only the ones you need, and only grant the access a task actually requires — more on that in the next lesson.

On Team/Enterprise plans, admins can control which connectors and tools are available and how much access each one gets. If you're on a work account and don't see a connector, that's likely an admin setting, not a bug.

How a Cowork task actually unfolds

You state the goal and point at the folder (and any connectors it needs).
Claude makes a plan and starts working — reading files, drafting, editing, calling tools — in multiple steps.
It pauses for approval before anything that changes things: creating or editing files, using a connector, deleting. You approve, deny, or redirect.
You review the result — real files in your folder — and iterate: "good, but make the summary shorter and add a risks section."

It's the same describe → it works → you review → you refine loop from Module 1, except now the "it works" step touches your real stuff.

Tips for getting great results

Be specific about the output. Name the file, the format, and the shape you want. "Summarize this" is weak; "write a 1-page summary.md with three sections: decisions, actions, risks" is strong.
Let it orient first. For a big or messy folder: "Before you change anything, read everything and tell me what's here and how you'd approach this." Then green-light the plan.
Work in passes. Get the structure right, then ask for polish. Don't try to specify everything in one giant prompt.
Keep tasks scoped to a folder. Give Claude exactly the material it needs — not your entire home directory.

Summary

In Cowork, a folder is a workspace: Claude reads, edits, and creates real files across Word/PDF/Excel/PowerPoint/CSV/images/code and more.
The best Cowork tasks are the ones too tedious to copy-paste in Chat: synthesize source material, clean data, reorganize folders, draft from templates.
Connectors extend Cowork to your other tools; Claude in Chrome lets it do browser tasks, so work can span your files and the web at once.
Pattern that works: point at the material → describe the finished result → name the output.
Claude works in steps and asks before changing things — you review the real files it produces and refine.