@itsmariahbrunner — Claude at Work
Cowork turns Claude into a desktop agent that actually executes tasks — not just answers questions. Here's everything you need to use it well from day one.
What Cowork actually is
Most people use Claude by typing a question, reading the answer, and then going and doing the thing themselves. That's chat. Cowork is different. You describe an outcome, Claude makes a plan, and then it executes that plan directly on your computer — reading and writing real files in folders you've given it access to. You step away. You come back to finished work.
It's built on the same agent architecture that powers Claude Code — the tool developers use to build entire software projects autonomously. Cowork is that same engine, packaged for everyone else. No terminal required.
Chat vs. Cowork — the actual difference
How to get set up — step by step
Go to claude.com/download and download the app for Mac or Windows x64. Windows arm64 is not currently supported. Make sure you're on the latest version — Cowork requires it. Sign in with the same account as your claude.ai subscription.
At the top of the desktop app you'll see three tabs: Chat, Cowork, and Code. Click Cowork. If you're on a paid plan (Pro, Max, Team, or Enterprise), it's available to you. If you don't see it, make sure your app is updated to the latest version.
Click "Work in a folder" and select the directory you want Claude to work in. Start with a dedicated project folder or your Downloads folder — not your entire Documents folder. Claude can only read and write within folders you've explicitly given it access to. You stay in control of what it can touch.
Important: Claude can make real changes to files in this folder. Start with something safe while you're learning.Tell Claude what you want done in plain language. The more specific you are about what success looks like, the better the output. Don't just say "organize this folder" — say "sort files by type into subfolders, rename anything with a generic name based on its content, flag duplicates for review, and create a summary document of what you did." More specific brief = better result every time.
Claude will show you its planned approach before taking any significant action. Read the plan. If something looks off, say so. This is your chance to course-correct before it executes. For potentially destructive actions — like deleting files — Claude will always ask for your explicit approval.
Cowork runs locally — the Claude Desktop app needs to stay open and your computer needs to stay awake while tasks are running. If you close the app or your computer sleeps, active tasks will stop. For long tasks, disable sleep mode before you step away. You can come back in 20 minutes or 2 hours — the task will be waiting for you.
Chat is asking a colleague a question. Cowork is delegating a project and checking back when it's done.
The features that actually matter
You don't have to wait for one task to finish before starting the next. Queue up multiple tasks and Claude works on them in parallel — spinning up sub-agents to handle independent workstreams simultaneously. While it's building your weekly report, it's already processing your inbox summary and organizing your project files.
This is the thing that makes Cowork feel genuinely different from chat. You stop waiting and start delegating. Give it three things to do, walk away, come back to all three done.
"1. Read all the PDFs in the /reports folder and create a one-page summary of each. 2. Pull together the key numbers from last month's spreadsheets into a single comparison table. 3. Rename all the files in /photos with descriptive names based on their content." — All three run in parallel.
Create tasks that run on a schedule you define — daily, weekly, monthly, or on-demand with a single click. Claude Desktop needs to be open for scheduled tasks to run, but otherwise they fire automatically without you touching anything.
This is the highest-leverage use of Cowork for most people. The Monday morning briefing you set up once that pulls from your files and connectors every week. The Friday EOD summary that compiles the week's work. The monthly report that generates itself. You set the logic once — Cowork runs it forever.
"Every Monday at 8am: Read the files in /current-projects, pull the latest from my Notion project boards, and create a weekly priorities doc in /briefings with the top 5 things I need to move forward this week. Format it as a clean one-pager."
Cowork can connect to your existing tools via integrations — Gmail, Notion, Slack, Google Drive, and more. Once connected, Claude can pull context from those tools directly into its work, not just the local files you've given it access to. Connect in Settings → Integrations — it takes about 60 seconds per tool.
This is what takes Cowork from "useful file organizer" to "genuine work agent." When Claude can read your inbox, your project boards, and your documents simultaneously, the quality of what it produces is completely different from working off isolated files.
"Check my Gmail for anything from clients in the last 48 hours, cross-reference with the active project files in /clients, and draft response emails in /drafts for anything that needs a reply — flagging anything that needs my judgment before sending."
Instead of re-explaining who you are and how you work every session, you can set global instructions that apply across all Cowork sessions, and folder-specific instructions that kick in whenever Claude works in a particular folder. Tell Claude your tone preferences, your role, your formatting standards, what to always ask before deleting anything — once, and it applies forever.
"I'm a marketing manager at a B2B SaaS company. My communication style is direct and concise. Always create a backup copy of any file before editing it. When writing anything client-facing, use formal language. Never delete files without listing them first and getting my approval."
Cowork works on your local files and connected tools. But pair it with Claude in Chrome and it can also complete tasks that require browser access — pulling live data from websites, filling out forms, researching across multiple tabs. Cowork handles the file and document side; Chrome handles the web side. Together they cover most of what a human assistant would do on a computer.
"Use Chrome to pull the latest pricing from our three main competitor websites. Save it to /research/competitor-pricing.txt. Then use Cowork to compare it against our current pricing doc in /sales and write a one-page analysis of where we're positioned."
What to actually use Cowork for — by task type
Sort, rename, move, consolidate, deduplicate. Turn chaos into structure without touching a single file yourself.
"Organize my Downloads folder. Sort by type, rename generic files based on content, create subfolders for Work/Personal/Receipts, flag anything over 6 months old."
Read across multiple documents simultaneously and produce a single coherent output — summaries, comparisons, reports.
"Read all PDFs in /reports from the last 30 days. Create a 2-page synthesis of the key themes, data points worth keeping, and open questions across all of them."
Build finished, formatted work products — Word docs, PowerPoints, Excel spreadsheets — ready to use, not just ready to edit.
"Take the notes in /meeting-notes from this week and produce a formatted project status report in /outputs as a Word doc. Include: what was decided, what's blocked, and next steps by owner."
Any task you do on a predictable cadence is a candidate for scheduling. Set the logic once, let Cowork run it on autopilot.
"Every Friday at 4pm: Read my project folders, check Notion for status updates, and write a 1-page week-in-review in /weekly-reviews with wins, blockers, and next week's priorities."
With Gmail connected, Cowork can read your inbox, triage by urgency, draft responses, and flag what needs your attention.
"Check my Gmail from the last 24 hours. For each email that needs a response, draft a reply in /email-drafts. Flag any that involve commitments I should add to my task list."
Pull data from PDFs, screenshots, or documents and produce clean, structured spreadsheets with working formulas.
"Read the receipt images in /expenses and create an Excel spreadsheet with: date, vendor, amount, category. Add a totals row and a pivot by category. Save to /accounting."
The biggest reason people get disappointing results from Cowork isn't the tool — it's the brief. Vague instructions produce vague work. Here's how to write a brief that gets you exactly what you wanted.
Don't describe the process — describe the output. What file should exist when it's finished? What should be in it? What format?
Tell Claude what to do when it hits something ambiguous — stop and ask, flag it in a list, skip it. Otherwise it has to guess.
What should it never do? What needs your approval? What's off-limits? State this upfront — especially for anything involving deletion or modification.
For any task with real consequences, add "Show me your plan before you start" to your prompt. Review it, adjust, then let it run.
What to know before you rely on it
Cowork doesn't remember what it did last time. Document important context in files Claude can read — a "project-context.txt" in your folder that explains ongoing work, preferences, and decisions made. Reference it in your prompts.
Tasks stop if you close the app or your computer sleeps. For long tasks, disable sleep mode before stepping away. You can check in anytime — Cowork keeps you informed of what it's doing as it works.
Multi-step agentic tasks are compute-intensive. Batch related work into single sessions rather than running lots of small separate tasks. Use Chat for quick questions that don't need file access. Monitor your usage in Settings → Usage.
Claude can read, edit, create, and delete files in the folders you give it access to. Start with a dedicated Cowork folder while you're learning, not your main Documents or Desktop. Use global instructions to require approval before deletions.
Cowork is for knowledge work: organizing files, writing documents, synthesizing research, automation. Claude Code is for software development: writing code, running tests, managing repositories. Both live in the desktop app under separate tabs. Don't try to use Cowork for coding — that's what Code is for.
Cowork launched in January 2026 and is actively being developed. Some features are still being added. Anthropic is iterating fast based on how people actually use it — expect it to get significantly better over the coming months.
I want to start using Cowork but I need help writing my first task brief properly. My job / role: [describe what you do] The task I want to hand off: [describe the work you want Cowork to do — as much detail as you have] The files or folders involved: [what files it would need access to, roughly where they live] What tools I use: [e.g. Gmail, Notion, Slack, Google Drive — anything you want it to pull from] Using this context, do three things: 1. Write me a complete Cowork task brief A specific, well-structured prompt I can paste directly into Cowork. It should include: the exact output I want (file name, location, format), what to do with edge cases, any constraints (nothing to delete, always ask before X), and a request to show me the plan before executing. 2. Suggest a global instruction I should set Based on my role and how I described the task, write a 3–5 sentence global instruction I can add in Settings that will make all my future Cowork tasks better — covering my tone, format preferences, and any standing rules about how Claude should handle my files. 3. Give me two more tasks I should consider automating with Cowork Based on what I do, what are two other recurring tasks in my work that Cowork could take off my plate? For each, give me a one-sentence brief I could test with. Be specific — the more concrete the task brief, the better Cowork will perform.
Want more of this?
Follow for daily content on real Claude workflows — Cowork, Projects, Skills, models, prompts. Practical stuff for non-technical professionals.