If Claude in the browser is the showroom and the API is the engine, Claude Cowork is the workshop. It is the desktop app that gives Claude controlled access to a folder on your machine, a sandboxed Linux shell, and the connectors you already use — Gmail, Drive, Notion, Slack, Jira. For technical practitioners, this is the fastest way to turn a chat habit into an automated workflow.
Install and Mount a Folder
Download the Claude desktop app, sign in, and switch into Cowork mode. The first thing it asks is which folder you want it to work in — pick a project directory, not your whole home folder. Cowork can read, write, edit, and run files in that folder via a sandboxed Linux shell. That scope boundary is the whole point: tight enough to be safe, broad enough to actually get work done.
Run Your First Real Task
Skip the toy demos. Pick something you would normally avoid: clean up a 200-file Downloads folder, dedupe a CSV, rename a batch of photos by EXIF date, refactor a messy markdown notes directory. Tell Cowork the goal and let it propose the plan. You will watch it use bash, Read, Write, and Edit to do the work, and you will start to feel the difference between asking Claude a question and pointing Claude at a problem.
Write a Skill
Skills are reusable instructions Cowork loads on demand. They live as markdown files with frontmatter, and they are the single highest-leverage thing you can build. Drop a folder like this into your workspace and Cowork will load it whenever the trigger words match:
---
name: weekly-status-report
description: Build a weekly executive status report from my project notes folder. Use when the user says "weekly status" or "Friday update".
---
1. Read all .md files modified in the last 7 days under ./notes/
2. Group findings by project (folder name = project name).
3. For each project: 2-3 bullets on progress, 1 bullet on risk, 1 bullet on next week.
4. Write output to ./reports/status-YYYY-MM-DD.md and open it.Now “weekly status” is a one-line command, not a 45-minute slog.
Wire Up Connectors and MCP
Cowork speaks MCP (Model Context Protocol), which means any service with an MCP server can be plugged in — Gmail, Calendar, Drive, Notion, Stripe, Linear, and dozens more. Connect them once in settings and they become first-class tools Cowork can call. Now your “weekly status” skill can pull from Gmail threads and Notion docs, not just local files. The trick is to add connectors lazily: only wire up what your current workflow needs, or you will drown in available tools.
Automate With Scheduled Tasks
The final unlock is scheduled tasks. Once you have a skill that works reliably, schedule it — daily morning briefing at 7am, inbox triage at 5pm, weekly status Friday afternoon. This is the moment Cowork stops being a chatbot and becomes a coworker who runs in the background. Start with one schedule, monitor its output for a week, and then add the next.
In Conclusion
Cowork is where Claude leaves the browser and joins your actual workflow. Mount a real folder, run a real task, write one skill, wire one connector, schedule one job — that five-step path will move more work off your plate than any productivity book on the shelf. Up next in this series: Claude Code, the terminal-native sibling of Cowork built specifically for engineers who live in a repo.
