Claude Cowork transforms how you work with documents and files. But before you can organize folders, analyze spreadsheets, or generate reports, you need to set up the environment. Let's get started.
Before you begin, ensure you have:
Why the subscription requirement? Cowork's agentic capabilities—filesystem access, document processing, persistent context—require significant infrastructure. The Pro and Max tiers support this enhanced functionality.
The Desktop app is your gateway to Cowork. Unlike the web interface, it has direct access to your filesystem with your permission.
Claude Desktop has three tabs across the top of the window:
Select the Cowork tab when you want Claude to work with files on your computer. You'll know you're in Cowork mode when you see the folder access panel.
The first time you use Cowork, Claude will ask for folder access. This is a critical security boundary—Claude can only access folders you explicitly approve.
To grant access:
Best practices for folder access:
When you're in Cowork mode, the interface has three main sections:
Where you communicate with Claude. This works like standard chat, but with enhanced context awareness:
Shows what Claude is actually doing:
This is your visibility into Claude's actions. You see exactly what will change before it happens.
Where Claude presents results:
You can preview, download, or open artifacts directly from this panel.
Let's put Cowork to work with a practical first task: organizing a messy folder.
Setup: Pick a real folder you already have — your Downloads folder, a project folder with mixed files, or any workspace that could use organization. Grant Claude Cowork access to that folder.
Task: In Claude Cowork, ask:
"Organize these files by type: put all text files in a 'docs' folder, all Word documents in an 'office' folder, and all images in an 'images' folder. Use consistent naming."
What happens:
Why this matters: You didn't write any code. You described what you wanted, and Claude executed it safely with your approval.
Cowork doesn't execute blindly. Every significant operation requires your approval:
This approval workflow is your safety net. Claude proposes, you approve, then Claude acts.
Cowork shines when working with document formats. Try this:
Task: Create a simple Word document with structured content.
"Create a Word document called 'project-plan.docx' with these sections: Overview, Timeline, Budget, and Team. Add placeholder content for each section."
Claude will:
You can then open the document in Word to see a properly formatted file—not just text, but actual document structure.
After completing the initial setup, try these tasks to explore Cowork's capabilities:
As you start using Cowork, keep these safety principles in mind:
Issue: Cowork mode doesn't appear
Issue: Folder access denied
Issue: Claude Desktop won't launch on Windows
Issue: Operations are slow
Plan Your First Real Cowork Task:
"I work with [describe your actual documents and files]. What is one task I do weekly that involves organizing, processing, or creating files? Design the Cowork prompt I would use — include what folder to grant access to, what outcome I want, and what constraints matter (e.g., don't delete anything, preserve folder structure)."
What you're learning: Task design for agentic AI — translating a real work need into a specific, safe Cowork prompt. The folder access decision and constraint specification are the skills that make Cowork effective from day one.
Test the Approval Workflow:
"In your granted folder, ask Claude to rename 3 files using a consistent naming pattern. Before approving, read the Execution Panel carefully: What files will change? What will the new names be? Approve only if every change looks correct. Then describe what you observed in the propose-approve-execute cycle."
What you're learning: Approval workflow fluency — the habit of reading the execution plan before clicking approve. This is the single most important safety skill for Cowork, and practicing it on a small operation builds the reflex before you attempt bulk operations.