Claude Cowork Setup Guide (2026): Get Tasks Running and Get More From Desktop Agent Mode

What Cowork Is

Cowork uses an agentic architecture (the same family as Claude Code) inside Claude Desktop, without requiring the terminal for basic use. You describe an outcome; Claude proposes a plan, runs work inside a controlled environment, and writes results back to your filesystem. Product overview: claude.com/product/cowork.

Eligibility and Availability

• Paid Claude plans: Cowork is available on Pro, Max, Team, and Enterprise (not on free-only usage).
• Claude Desktop only: Cowork requires the desktop app on macOS or Windows. It is not a web or mobile-only feature (Pro and Max users have additional mobile workflows that still rely on the desktop for local files—see Anthropic's article on assigning tasks from anywhere).
• Internet: An active connection is required during sessions.

Step 0: Will Your Machine Run Cowork?

If you have not installed Claude Desktop yet, Anthropic provides small readiness-check downloads. Run the program after downloading; if it reports that your computer is ready for Cowork, continue.

• macOS readiness check
• Windows x64 readiness check
• Windows arm64 readiness check

Step 1: Install or Update Claude Desktop

Install the latest Claude Desktop from claude.com/download. On macOS you can also use the direct DMG redirect linked from the help article. Staying current matters because Cowork is under active development.

Step 2: Open Cowork (Tasks Mode)

1. Open Claude Desktop.
2. Find the mode selector that includes Chat and the Cowork tab.
3. Click Cowork to switch to Tasks mode.
4. Describe the task as an outcome (what "done" looks like).
5. Review Claude's plan, then allow it to proceed.

Critical: The Desktop app must stay open while Cowork is working. Closing the app ends the session. Your computer should remain awake; sleep stops active tasks.

How a Cowork Task Actually Runs

Anthropic summarizes the loop as:

1. Analyze the request and create a plan.
2. Split complex work into subtasks when useful.
3. Execute in a virtual machine (VM) environment.
4. Coordinate parallel workstreams when appropriate.
5. Deliver outputs into your file system.

You get progress indicators, visibility into reasoning, and the ability to steer mid-task. Deletion protection means permanent file deletes require an explicit permission step.

Step 3: Choose a Workspace Folder

Cowork reads and writes files you grant access to. Best practice: create a dedicated folder (for example a cowork-projects directory) and point Cowork there, rather than your entire home directory. This limits blast radius if a task goes sideways and keeps outputs predictable.

Step 4: Global and Folder Instructions

Global instructions

Standing rules for every Cowork session—tone, role, default formats, quality bar.

1. In Claude Desktop go to Settings → Cowork.
2. Click Edit next to Global instructions.
3. Save when finished.

Folder instructions

When you select a local folder, you can add folder instructions for project-specific context. Claude may update these during a session as the work evolves.

Optional: context files in the folder

Many users keep lightweight Markdown files in the shared folder—style guides, glossary, constraints, acceptance criteria—so every task starts aligned. Keep them short and current; stale instructions cause stale output.

How to Get the Most Out of Cowork

1. Use Cowork only where it earns its cost

Cowork consumes more usage than standard chat because multi-step execution is token-heavy. Per Anthropic, if you hit limits often: batch related work into fewer sessions, use normal chat for quick questions, and monitor Settings → Usage. Read Usage limit best practices.

2. Projects for recurring and long-running work

Projects group related tasks into workspaces with their own files, links, instructions, and memory. Details: Organize your tasks with projects in Cowork.

3. Plugins (skills, connectors, sub-agents)

Plugins bundle capabilities for specific roles. Install and customize them carefully—each extra connector expands what Claude can reach. Start here: Use plugins in Cowork.

4. Scheduled tasks

Type /schedule in a task or use Scheduled in the sidebar. Scheduled tasks only run while the app is open and the machine is awake. Deep dive: Schedule recurring tasks in Cowork.

5. Mobile handoff (Pro / Max)

You can assign work from your phone and have results land in the same conversation while your desktop does the heavy lifting—still subject to desktop being available. See Assign tasks to Claude from anywhere in Cowork.

6. Extended desktop control (when you need it)

Anthropic documents additional modes where Claude can use your computer more directly. Read carefully before enabling: Let Claude use your computer in Cowork.

Safety, Permissions, and Compliance Notes

Read Use Cowork safely before you aim Cowork at sensitive data. A few highlights from Anthropic's documentation:

• Cowork is a preview with unique risks from agentic behavior and network access.
• Conversation history for Cowork is stored locally on your device.
• Cowork activity may not appear in the same compliance surfaces as other Claude products—do not use it for regulated workloads without explicit approval from your security team.
• Review MCP connectors and internet capabilities the same way you would for privileged software.

Teams and enterprises should also read Cowork for Team and Enterprise plans.

Current Limitations to Plan Around

• Memory: Supported within projects; not retained the same way across standalone Cowork sessions.
• No session sharing like some chat collaboration flows.
• Desktop required for execution; mobile complements certain plans but does not replace the desktop runtime for local files.
• Sleep and closed app stop work—design tasks around that reality.

Troubleshooting

• "Setting up Claude's workspace" on start: Expected while Cowork updates its workspace to the latest version.
• Task stopped mid-run: Confirm the app stayed open and the machine did not sleep.
• Usage limits: Reserve Cowork for multi-step, file-backed work; simplify shallow requests in chat.
• Missing output files: Re-check which folder you granted and where Claude said it would write.

Summary Checklist

1. Confirm paid plan + Desktop install + readiness check if unsure.
2. Open Cowork (Tasks), pick a dedicated folder.
3. Set global instructions; add folder instructions and light context files.
4. Start with a bounded task; steer from the plan if needed.
5. Add projects, plugins, or schedules only after the basics feel stable.
6. Stay inside usage and safety guidelines for your data class.

Conclusion

Cowork rewards clarity: a tight folder, explicit instructions, realistic session boundaries, and disciplined use of projects and schedules. Treat it like a junior teammate with root access to that folder—give sharp briefs, watch the plan, and keep Anthropic's safety guidance in the loop.