How to Work Claude Code (Cowork): The Complete Guide

What Exactly Is Claude Cowork (and How Does It Differ from Chat)?

If you've searched "how to work Claude Code" expecting a coding tool, you're close — but the feature built for general knowledge work is called Cowork. Cowork is an autonomous AI agent built into the Claude Desktop application for macOS and Windows. Rather than answering questions in a chat interface, Cowork takes a goal from you and works through it independently — reading and writing local files, moving between applications, and synthesizing information across multiple sources — then returns a finished deliverable. You do not need to coordinate each step.

Think of it this way: Claude Chat gives you a conversation partner. Cowork gives you a capable colleague you can delegate an entire project to and walk away from. It brings the agentic capabilities found in Claude Code to general knowledge work, making it accessible to non-technical users who need real file and application handling without writing a single line of code.

For a full technical overview, see the Claude Cowork Desktop Architecture Overview.

Who Can Use Cowork?

Cowork is available to paid plan subscribers. Team and Enterprise admins can enable or disable Cowork organization-wide from Organization settings, giving businesses centralized control over who can run autonomous tasks. Conversation history and task data are stored locally on each user's device and are not captured in Anthropic's Compliance API at this time — an important privacy consideration for enterprise deployments.

If you're on a Team or Enterprise plan, check with your admin to confirm Cowork is enabled before following the steps below. More details are available in the Use Claude Cowork on Team and Enterprise Plans guide.

How Do You Set Up and Start Using Cowork?

Getting started is straightforward. Here's the exact sequence:

1. Download and install Claude Desktop from claude.com/download. macOS and Windows are both supported; Windows requires the latest version of the application.
2. Open Claude Desktop and locate the mode selector at the top of the interface.
3. Click the Cowork tab to switch from Chat mode to Cowork (Tasks) mode.
4. Grant folder access. Cowork can only read and write files in folders you explicitly connect. Grant access to a specific folder or directory you want it to work in — not your entire drive.
5. Describe your task in plain language. Write what outcome you want, not a question to answer.
6. Review Claude's stated approach if prompted, then let it run. Keep the desktop app open — closing it ends the session.
7. Monitor progress via the step-by-step indicators, and jump in to steer or correct if needed.
8. Configure Dispatch in application settings if you want to push tasks remotely from the Claude mobile app to your desktop machine.

The full onboarding walkthrough is available at Get Started with Claude Cowork.

What Tasks Is Cowork Actually Good At?

Cowork is designed for multi-step knowledge work that would otherwise require you to manually touch dozens of files or switch between multiple applications. Here are the core use cases it handles well:

• File organization and cleanup: Point Cowork at a folder full of unnamed screenshots, duplicate PDFs, and outdated drafts. Ask it to rename files based on content, deduplicate assets, sort by type and date, and archive old items into labeled subfolders — without touching anything manually.
• Report assembly from multiple sources: A consultant with 40 PDFs, meeting notes, and raw data CSVs spread across a project folder can ask Cowork to read the entire set, synthesize the key findings, and produce a formatted Word document with an executive summary, section headers, and source citations.
• Receipt and invoice data extraction: Cowork uses OCR to extract vendor name, date, amount, and tax from scanned receipt images and unstructured invoice PDFs, then populates a structured spreadsheet and moves processed source files into an Archive subfolder.
• Financial reconciliation and anomaly flagging: Cross-reference bank statement PDFs against a committed expenses spreadsheet, flag items that lack a matching budgeted line, and produce a reconciliation report with conditional formatting — ready for review without manual row-by-row checking.
• Remote background workflows via Dispatch: Trigger tasks from your phone while away from your desk. Cowork runs on your local machine, processes new files that arrived overnight, and sends a completion notification so you return to finished work rather than a queue.
• Due diligence and investment research synthesis: Load a directory with annual reports, competitor filings, and market data CSVs, then ask Cowork to run a comparative analysis and output a formatted presentation with charts and speaker notes.

How Do You Write a Good Cowork Task Prompt?

The single biggest mistake new users make is treating Cowork like a chat interface and expecting a text reply. Cowork is designed to produce finished files and completed actions. Frame your request as a delegation — describe the outcome you want, not a question to answer.

Here's a concrete example of a well-formed task prompt for organizing a Downloads folder:

"Sort all the files in my Downloads folder. Rename files that have generic names (like 'Screenshot_001') using their actual content. Create subfolders by type: Images, PDFs, Documents, Archives. Move anything older than 2023 into an 'Old Files' subfolder."

And for extracting invoice data:

"Process all the receipt images and PDF invoices in this folder. For each file, extract: vendor name, invoice date, total amount, tax amount, and payment method. Create an Excel spreadsheet with one row per invoice, add a SUM row at the bottom for Amount and Tax columns, and move all processed source files into an 'Archive' subfolder."

Notice the pattern: a clear output format, explicit field names, and a stated file management action at the end. Ambiguous instructions lead to incomplete results or mid-task interruptions.

When Should You Use Cowork vs. Claude Chat vs. Claude Code?

What Are the Most Common Cowork Pitfalls and How Do You Avoid Them?

Closing the Desktop App Mid-Task

The Claude Desktop app must stay open for the entire duration of a Cowork session. Closing it ends the task immediately. Keep the window open or minimized — not closed. For very long tasks, set your OS sleep mode to "Never" or use a dedicated device.

Granting Access to an Overly Broad Folder

Giving Cowork access to your entire Documents folder or root drive can cause unintended file modifications or slow the agent down with irrelevant files. Always create a dedicated, isolated working folder for each Cowork task and grant access only to that folder.

Vague or Multi-Part Prompts

Ambiguous instructions lead to incomplete results or mid-task interruptions. Write a single clear outcome with explicit constraints. Instead of "Organize my files and write a report," say: "Sort all PDFs in this folder by year into subfolders, then create a summary Excel file listing the file count per year."

Permission Denied Errors

Cowork can only access folders explicitly connected in the Cowork settings. If it cannot read or write a target folder, verify that you granted access to the correct path and check folder permissions at the OS level — particularly for network drives or system-protected directories.

Web Search Failures in Enterprise Environments

Enterprise admins can disable web search and web fetch in Organization settings. If these tools fail, check with your admin to confirm they are enabled before troubleshooting further.

Is Cowork Worth It for Team and Enterprise Users?

For organizations handling high volumes of document-heavy workflows — finance teams processing invoices, consultants assembling reports, analysts synthesizing research — Cowork offers a meaningful reduction in manual, repetitive work. The key organizational advantages are centralized admin controls (enable or disable Cowork organization-wide from Organization settings), local data storage that keeps task data off Anthropic's Compliance API, and the Dispatch feature that lets team members trigger tasks remotely from mobile devices.

The tradeoff is that Cowork runs on each user's local machine, so it requires the desktop app to stay open during task execution. For workflows that need to run unattended on a server or integrate programmatically with other systems, Claude's API-based Managed Agents are the better fit.

For teams evaluating the right plan, see the Team Plan overview and the Enterprise Plan overview.