claude-code-ultimate-guide/guide/cowork.md

# Claude Cowork: Agentic Desktop for Knowledge Work

> **Reading time**: ~15 minutes
>
> **Purpose**: Understand Cowork's capabilities, limitations, and how it complements Claude Code for team workflows.

---

> **Research Preview** (January 2026) — Limited documentation available.
> Expect bugs, no production use recommended yet.

---

## Table of Contents

- [1. Overview](#1-overview)
- [2. Who Should Use Cowork?](#2-who-should-use-cowork)
- [3. Architecture](#3-architecture)
- [4. Claude Code vs Cowork vs Projects](#4-claude-code-vs-cowork-vs-projects)
- [5. Use Cases](#5-use-cases)
- [6. Security: Handle With Care](#6-security-handle-with-care)
- [7. Known Issues & Troubleshooting](#7-known-issues--troubleshooting)
- [8. Developer ↔ Non-Developer Workflows](#8-developer--non-developer-workflows)
- [9. Availability & Roadmap](#9-availability--roadmap)
- [Sources](#sources)

---

## 1. Overview

**Cowork** is Claude's agentic desktop feature that extends Claude's autonomous capabilities to non-technical users through the Claude Desktop app. Instead of terminal commands, Cowork accesses local folders and files directly.

### What is Cowork?

- **Research preview** released January 2026 for Max subscribers (macOS only)
- Extends Claude Code's agentic architecture to knowledge workers
- ~90% of Cowork was written by Claude itself ([Anthropic blog])
- Focuses on file manipulation, organization, and document generation

### Relationship to Claude Code

Cowork shares the same backend architecture as Claude Code:
- Same model capabilities (extended thinking, agentic loops)
- Same limitations (no internet access without explicit tools)
- Different interface: Desktop app vs Terminal

**Key difference**: Cowork cannot execute arbitrary code—it manipulates files only.

---

## 2. Who Should Use Cowork?

### Good Fit

| Persona | Use Case | Why Cowork |
|---------|----------|------------|
| **Project Manager** | File organization + status reports | Multi-step automation without coding |
| **Data Analyst** | Local CSV/Excel → formatted reports | Native Excel formulas output |
| **Writer/Editor** | Research notes → structured documents | Synthesis across many sources |
| **Operations** | Receipt screenshots → expense reports | Multi-format input processing |

### Poor Fit (For Now)

| Persona | Limitation | Alternative |
|---------|------------|-------------|
| **Security-conscious enterprises** | No audit trail, no access controls | Wait for enterprise features |
| **Heavy cloud users** | No Google Drive/Dropbox confirmed | Use native apps |
| **Anyone needing reliability** | Preview = bugs, unexpected behavior | Wait for stable release |
| **Code execution needs** | Files only, no scripts | Use Claude Code |

---

## 3. Architecture

### Local-First Design

```
┌─────────────────────────────────────────────────────────────┐
│                    CLAUDE DESKTOP APP                        │
│  ┌─────────────────────────────────────────────────────────┐│
│  │                     COWORK                               ││
│  │  ┌─────────────┐  ┌─────────────┐  ┌─────────────────┐ ││
│  │  │ Sub-Agent 1 │  │ Sub-Agent 2 │  │ Sub-Agent 3     │ ││
│  │  │ (Analysis)  │  │ (Transform) │  │ (Organize)      │ ││
│  │  └──────┬──────┘  └──────┬──────┘  └───────┬─────────┘ ││
│  │         └────────────────┴─────────────────┘            ││
│  │                          ↓                               ││
│  │  ┌─────────────────────────────────────────────────────┐││
│  │  │              LOCAL FOLDER SANDBOX                    │││
│  │  │  ~/Cowork-Workspace/                                 │││
│  │  │    ├── input/  (your files)                         │││
│  │  │    └── output/ (generated files)                    │││
│  │  └─────────────────────────────────────────────────────┘││
│  └─────────────────────────────────────────────────────────┘│
│                                                              │
│  ┌─────────────────┐                                        │
│  │ CHROME INTEGRATION │ ← Web tasks (with explicit action)  │
│  └─────────────────┘                                        │
└─────────────────────────────────────────────────────────────┘
```

### Key Technical Details

| Aspect | Details |
|--------|---------|
| **Access model** | Local folder sandbox (user grants permission) |
| **Cloud connectors** | Not confirmed (no Drive, Dropbox, etc. yet) |
| **Sub-agents** | Parallel execution with fresh context per agent |
| **Code execution** | **None** - Files only (no scripts, no commands) |
| **Browser** | Chrome integration for web research tasks |
| **Context limit** | ~200K tokens (~150-500 pages per session) |
| **Output formats** | Excel (.xlsx with formulas), PowerPoint, Word, PDF, text |

### What Cowork Cannot Do

- Execute shell commands or scripts
- Access cloud storage directly (as of Jan 2026)
- Run code in any language
- Access network resources without Chrome
- Persist memory across sessions (except via files)

---

## 4. Claude Code vs Cowork vs Projects

| Aspect | Claude Code | Cowork | Projects |
|--------|-------------|--------|----------|
| **Target user** | Developers | Knowledge workers | Everyone |
| **Interface** | Terminal/CLI | Desktop app | Chat interface |
| **Access** | Shell + arbitrary code | Folder sandbox only | Documents only |
| **Execute code** | Yes (full shell) | No | No |
| **Outputs** | Code, scripts, any file | Excel, PPT, docs | Conversations |
| **Maturity** | Production-ready | **Research preview** | Production-ready |
| **Security docs** | Extensive | None yet | Standard |
| **Context** | ~200K tokens | ~200K tokens | Project-scoped |
| **Memory** | CLAUDE.md files | Via files | Project knowledge |
| **Subscription** | Usage-based | Max only (~$200/mo) | All tiers |
| **Platform** | macOS, Linux, Windows | macOS only | All |

### Decision Flow

```
Need to execute code or scripts?
├─ Yes → Claude Code
└─ No → Need file manipulation?
         ├─ Yes (local files) → Cowork
         ├─ Yes (cloud files) → Wait or use native apps
         └─ No (just conversation) → Projects
```

---

## 5. Use Cases

### 5.1 File Organization

**Scenario**: Messy Downloads folder with 500+ files

```
INPUT:  ~/Downloads/ (mixed PDFs, images, zips, docs)
PROMPT: "Organize my Downloads folder. Create folders by type
        and date. Move files, don't copy. Show me the summary."
OUTPUT: Organized structure + summary.txt
```

**Source**: [YouTube demo - File Organization]

### 5.2 Expense Tracking

**Scenario**: Receipt screenshots → Excel report

```
INPUT:  ~/Receipts/ (20 JPG/PNG receipt photos)
PROMPT: "Extract expenses from these receipts.
        Create an Excel file with Date, Vendor, Amount, Category.
        Add a summary sheet with totals by category."
OUTPUT: expenses.xlsx with formulas + summary sheet
```

**Source**: [LinkedIn post - Expense tracking demo]

### 5.3 Report Synthesis

**Scenario**: Scattered notes → structured document

```
INPUT:  ~/Notes/ (15 markdown files, 3 PDFs)
PROMPT: "Create a project status report from these notes.
        Structure: Executive Summary, Progress by Area, Risks,
        Next Steps. Format as Word doc."
OUTPUT: status-report.docx
```

**Source**: [Anthropic blog]

### 5.4 Travel Planning

**Scenario**: Multi-source research → itinerary

```
INPUT:  ~/Trip/ (saved webpages, flight confirmations, Airbnb PDFs)
PROMPT: "Create a day-by-day itinerary for my Tokyo trip.
        Include all confirmations, local recommendations,
        and a packing checklist."
OUTPUT: tokyo-itinerary.docx + checklist.xlsx
```

**Source**: [YouTube tutorial - Travel planning with Cowork]

### 5.5 Meeting Preparation

**Scenario**: Multiple docs → briefing document

```
INPUT:  ~/Meeting/ (company report PDF, LinkedIn profiles, news articles)
PROMPT: "Create a briefing doc for my meeting with Acme Corp.
        Include: company overview, key people, recent news,
        talking points, questions to ask."
OUTPUT: acme-briefing.docx
```

---

## 6. Security: Handle With Care

> **No official security documentation exists for Cowork yet.**
> The following is community-derived best practice.

### Risk Matrix

| Risk | Severity | Description | Mitigation |
|------|----------|-------------|------------|
| **Prompt injection via files** | HIGH | Malicious files with embedded instructions | Use dedicated folder, no untrusted content |
| **Browser action abuse** | HIGH | Cowork taking unintended web actions | Review each web action before approval |
| **Local file exposure** | MEDIUM | Accidental access to sensitive folders | Minimal permission scope |
| **Data exfiltration** | MEDIUM | Sensitive data leaving local system | No credentials in workspace |
| **Incomplete operations** | LOW | Half-finished file operations | Backup before destructive ops |

### Security Best Practices

1. **Create a dedicated Cowork folder**
   ```
   ~/Cowork-Workspace/
   ├── input/    # Files you want processed
   └── output/   # Generated files
   ```
   Never grant access to Documents, Desktop, or home folder directly.

2. **Review task plans before execution**
   - Cowork shows its plan before acting
   - Read each step, especially file deletions or moves
   - Reject and refine if scope seems wrong

3. **Avoid instruction-like content in files**
   - Don't process files containing "ignore previous instructions..."
   - Be cautious with files from unknown sources
   - Especially PDFs and documents with embedded text

4. **No sensitive data in workspace**
   - No API keys, passwords, tokens
   - No personal financial documents
   - No confidential work documents
   - No credentials in any format

5. **Backup before destructive operations**
   - Before "organize my folder" → backup first
   - Before "rename all files" → backup first
   - Use Time Machine or manual copy

6. **Browser permission caution**
   - Grant Chrome access only when needed
   - Review each web action Cowork proposes
   - Revoke access after task completion

### What NOT to Do

```
DANGEROUS: "You have access to my Documents folder"
DANGEROUS: "Process all files in ~/"
DANGEROUS: "Here's my password file, extract credentials"
DANGEROUS: "Process this PDF from an unknown sender"
RISKY:     "Delete all duplicates" (without backup)
RISKY:     "Reorganize everything" (scope too broad)
```

---

## 7. Known Issues & Troubleshooting

> Based on community reports (January 2026)

### Common Issues

| Issue | Description | Workaround |
|-------|-------------|------------|
| **Incomplete tasks** | Cowork stops mid-operation | Break into smaller, explicit steps |
| **Node.js download prompts** | Unexpected download dialogs | Accept or cancel, report to Anthropic |
| **Session timeouts** | Long tasks getting interrupted | Keep app active, smaller batches |
| **Browser actions failing** | Chrome integration not working | Grant explicit permissions in System Preferences |
| **Excel formula errors** | Generated formulas don't work | Verify regional settings (comma vs semicolon) |
| **File permission errors** | "Cannot access folder" | Re-grant permissions in Desktop app settings |

### Reporting Issues

Since this is a research preview, feedback is valuable:
- **General support**: support.anthropic.com
- **Feature requests**: Through the Claude Desktop app feedback
- **Community discussion**: Reddit r/ClaudeAI

### Recovery Procedures

**If Cowork stops mid-task:**
```
1. Check ~/Cowork-Workspace/output/ for partial results
2. Review what was completed vs planned
3. Restart with explicit next step
4. "Continue from where you stopped: [describe state]"
```

**If files are in unexpected state:**
```
1. Don't let Cowork "fix" without understanding
2. Review manually what changed
3. Restore from backup if needed
4. Restart with clearer instructions
```

---

## 8. Developer ↔ Non-Developer Workflows

One of Cowork's strengths is enabling collaboration between technical and non-technical team members.

### Pattern 1: Dev Specs → PM Review

```
┌─────────────────────────────────────────────────────────────┐
│ DEVELOPER (Claude Code)                                      │
│                                                              │
│ > "Generate a technical spec for the new auth system.       │
│    Output as markdown in ~/Shared/specs/"                   │
│                                                              │
│ Output: ~/Shared/specs/auth-spec.md                         │
└──────────────────────────────┬──────────────────────────────┘
                               ↓
┌─────────────────────────────────────────────────────────────┐
│ PROJECT MANAGER (Cowork)                                     │
│                                                              │
│ > "Review the auth spec in ~/Shared/specs/.                 │
│    Create a stakeholder summary with timeline estimates     │
│    and risk assessment. Output as Word doc."                │
│                                                              │
│ Output: ~/Shared/docs/auth-summary.docx                     │
└─────────────────────────────────────────────────────────────┘
```

### Pattern 2: Research → Implementation

```
┌─────────────────────────────────────────────────────────────┐
│ ANALYST (Cowork)                                             │
│                                                              │
│ > "Research competitors' pricing pages. Save screenshots     │
│    and create a comparison matrix in Excel."                │
│                                                              │
│ Output: ~/Shared/research/pricing-comparison.xlsx            │
└──────────────────────────────┬──────────────────────────────┘
                               ↓
┌─────────────────────────────────────────────────────────────┐
│ DEVELOPER (Claude Code)                                      │
│                                                              │
│ > "Implement a pricing page based on the competitive        │
│    analysis in ~/Shared/research/. Use our design system."  │
│                                                              │
│ Output: src/pages/pricing.tsx (+ tests)                     │
└─────────────────────────────────────────────────────────────┘
```

### Pattern 3: Shared Context via CLAUDE.md

For teams using both tools, create a shared context file:

```markdown
# ~/Shared/CLAUDE.md

## Project: Acme Platform v2

### Conventions
- All specs in ~/Shared/specs/
- All docs in ~/Shared/docs/
- All research in ~/Shared/research/

### Current Sprint
- Auth system redesign
- Pricing page implementation
- Q1 stakeholder report

### Key Decisions
- Using Clerk for auth (see specs/auth-decision.md)
- Tailwind for styling
- Q1 deadline: March 15
```

Both Claude Code and Cowork can reference this file for context.

---

## 9. Availability & Roadmap

### Current Status (January 2026)

| Aspect | Status |
|--------|--------|
| **Subscription** | Max only (~$200/month) |
| **Platform** | macOS only |
| **Waitlist** | Available for Pro/Team plans |
| **Stability** | Research preview (expect bugs) |

### Expected Future

| Feature | Status | Notes |
|---------|--------|-------|
| Windows support | Announced | No date |
| Linux support | Announced | No date |
| Cloud connectors | Unknown | Not confirmed |
| Pro plan access | Waitlisted | Expected 2026 |
| Enterprise features | Unknown | Audit trail, SSO, etc. |

### How to Get Access

1. **Max subscribers**: Enable in Claude Desktop app settings
2. **Pro/Team subscribers**: Join waitlist at claude.ai/cowork
3. **Enterprise**: Contact Anthropic sales

---

## Sources

All information in this document is derived from:

| Source | Type | Link |
|--------|------|------|
| **Anthropic Blog** | Official | [claude.com/blog/cowork-research-preview](https://claude.com/blog/cowork-research-preview) |
| **YouTube Demo - File Org** | Community | Search "Claude Cowork file organization" |
| **LinkedIn Demos** | Community | Various posts tagged #ClaudeCowork |
| **Reddit r/ClaudeAI** | Community | Cowork megathread |

### Documentation Gaps

As of January 2026, the following official documentation is **missing**:
- Security guidelines
- Best practices guide
- API/automation documentation
- Known issues list
- Release notes / changelog
- Enterprise deployment guide

This guide will be updated as official documentation becomes available.

---

*Back to [AI Ecosystem Guide](./ai-ecosystem.md) | [Ultimate Guide](./ultimate-guide.md) | [Main README](../README.md)*