Cowork Troubleshooting Guide

🌐 Languages: English Français Українська 🇺🇦

Reading time: ~8 minutes

Purpose: Diagnose and resolve common Cowork issues

Diagnostic Decision Tree

Use this flowchart to identify your issue:

What's happening?
│
├─ Cowork won't start or isn't visible
│   └─ Go to: § SETUP ISSUES
│
├─ "VM connection timeout" or "workspace failed"
│   └─ Go to: § VM & CONNECTION ISSUES (VPN likely cause)
│
├─ Cowork can't access my files
│   └─ Go to: § PERMISSION ISSUES
│
├─ Task stops mid-execution or "context limit"
│   └─ Go to: § EXECUTION ISSUES
│
├─ Output is wrong or unexpected
│   └─ Go to: § OUTPUT ISSUES
│
├─ Browser/Chrome integration problems
│   └─ Go to: § BROWSER ISSUES
│
└─ Something else
    └─ Go to: § GENERAL TROUBLESHOOTING

Known Error Messages (Quick Reference)

Error Message Likely Cause Quick Fix
Failed to start Claude's workspace — VM connection timeout after 60 seconds VPN active Disconnect VPN → retry
Chrome native messaging host not found Extension mismatch Manual host installation (see below)
Context limit reached (at ~165K, not 200K) System overhead Break task into smaller batches
Access denied — path outside allowed directories Folder not granted Re-grant folder access
Session terminated unexpectedly Sleep/background Keep app foreground, disable sleep
Cannot connect to Chrome Permissions missing Grant Accessibility permission

Setup Issues

Cowork Option Not Visible

Symptoms:

Solutions:

Step Action
1 Check subscription: Must be Pro or Max tier
2 Update app: Claude Desktop → Check for Updates
3 Restart app: Quit completely (Cmd+Q on macOS, Alt+F4 on Windows), relaunch
4 Check region: Some features may have regional rollout
5 Clear cache: macOS: Delete ~/Library/Application Support/Claude/ and restart. Windows: Delete %APPDATA%\Claude\ and restart

“Cowork is not available”

Symptoms:

Solutions:

App Crashes on Cowork Launch

Symptoms:

Solutions:

macOS:

# Check crash logs
open ~/Library/Logs/DiagnosticReports/

# Reset app preferences (caution: loses settings)
rm -rf ~/Library/Preferences/com.anthropic.claude.plist

# Reinstall app
# Download latest from claude.ai

Windows:

# Check crash logs
explorer %LOCALAPPDATA%\CrashDumps

# Reset app preferences (caution: loses settings)
rmdir /s /q "%APPDATA%\Claude"

# Reinstall app
# Download latest from claude.ai

VM & Connection Issues

“VM Connection Timeout” (VPN Issue)

Exact Error:

Failed to start Claude's workspace — VM connection timeout after 60 seconds

Root Cause: VPN software creates routing conflicts with Cowork’s internal VM networking. This is the #1 reported issue on r/ClaudeAI.

Solutions:

Priority Action
1 Disconnect VPN completely before starting Cowork
2 If VPN required: Use split tunneling to exclude Claude
3 Try mobile hotspot as workaround

Why It Happens: Cowork runs in a sandboxed virtual machine. VPNs intercept and reroute network traffic at the system level, breaking the host↔VM communication channel. There’s no fix that keeps VPN active.

Workaround for VPN-Required Environments:

  1. Disconnect VPN
  2. Complete Cowork tasks
  3. Reconnect VPN
  4. Note: Some corporate environments may block this workflow

“Workspace Failed to Initialize”

Symptoms:

Solutions:

  1. Restart Claude Desktop completely (Cmd+Q on macOS, Alt+F4 on Windows)
  2. Check for OS updates (VM requires specific APIs)
  3. Ensure 4GB+ free RAM
  4. macOS: Try in Safe Mode (hold Shift during boot). Windows: Try clean boot (msconfig → Selective startup)

Permission Issues

“Cannot access folder”

Symptoms:

Solutions:

Step 1: Check System Permissions

macOS:

  1. Open System Settings → Privacy & Security (macOS 13+) Note: On macOS 12 and earlier, use System Preferences → Security & Privacy
  2. Go to Privacy → Files and Folders
  3. Find Claude or Claude Desktop
  4. Ensure your workspace folder is listed and checked

Windows:

  1. Right-click the workspace folder → Properties → Security tab
  2. Ensure your user account has Full Control
  3. Check that Claude Desktop is not blocked by Windows Defender or antivirus

Step 2: Re-grant Access

  1. In Cowork, start a new task that needs folder access
  2. When prompted, click “Grant Access”
  3. Navigate to your workspace folder
  4. Select it explicitly

Step 3: Full Disk Access (Last Resort)

  1. System Settings → Security & Privacy → Privacy
  2. Full Disk Access → Add Claude Desktop
  3. Restart the app

Workspace Shows Empty

Symptoms:

Solutions:

“Access denied” for Specific Files

Symptoms:

Solutions:

Execution Issues

Task Stops Mid-Execution

Symptoms:

Possible Causes and Solutions:

Cause Solution
Context limit Break task into smaller batches (see note below)
Timeout Keep app active, reduce task scope
App backgrounded Keep Claude Desktop in foreground
Network issues Check internet connection
File locks Close other apps using the files

Context Limit Reached Early (Known Bug)

Symptoms:

Why It Happens: System overhead (tool definitions, safety instructions, execution logs) consumes ~25-35K tokens before your task even starts. The effective usable context is closer to 165K, not 200K.

Workarounds:

Strategy Implementation
Batch processing Process 10-20 files per session, not 50+
Fresh session Start new conversation to reset context
Progressive output Save intermediate results to files
Checkpoint prompts “Save progress to checkpoint.txt, continue in new session”

Token Budget Reference:

Task Type Estimated Tokens Sessions (Pro tier)
Simple Q&A 5K-10K Many
File inventory (20 files) 20K-30K 6-8
Small file org (10-20 files) 30K-50K 3-5
Large file org (50+ files) 80K-150K 1-2
Multi-doc synthesis 50K-100K 2-3
OCR batch (10+ images) 60K-100K 2-3

Recovery:

1. Check ~/Cowork-Workspace/output/ for partial results
2. Review what was completed vs planned
3. Restart with explicit next step:
   "Continue from where you stopped. The following files
   were already processed: [list]. Next, process: [remaining]"

Task Runs Forever

Symptoms:

Solutions:

  1. Wait up to 5 minutes for complex tasks
  2. Type “Status?” to check progress
  3. If no response, start new conversation
  4. Break task into smaller pieces

“Node.js Download” Prompts

Symptoms:

Solutions:

Session Terminates Unexpectedly

Symptoms:

Common Causes:

Cause Prevention
Computer sleep Disable sleep during long tasks, or check “Prevent sleep while app is active”
App closed Keep Claude Desktop visible, not minimized
Network interruption Ensure stable connection for long operations
Usage quota exhausted Monitor quota, batch large tasks appropriately

Important: Cowork sessions require the desktop app to remain open. There is no:

Recovery:

  1. Restart Claude Desktop
  2. Check output folder for partial results
  3. Resume manually with explicit continuation prompt
  4. For critical tasks, break into smaller checkpointed batches

Connector Reliability Issues

Symptoms (if using Gmail, Drive, or other connectors):

Current Status (January 2026):

Workarounds:

Symptoms:

Check Status:

During Outages:

Output Issues

Excel Formulas Don’t Work

Symptoms:

Solutions:

Issue Fix
Regional syntax Specify in prompt: “Use semicolons for formula separators” (EU) or “Use commas for formula separators” (US)
Formula as text Cell may be formatted as text; change to Number format
Missing sheet reference Ensure cross-sheet references include sheet name

Example Fix Prompt:

The Excel formulas aren't working. Please regenerate the file
using European regional settings (semicolon separators in formulas).

Wrong File Format

Symptoms:

Solutions:

Missing Content in Output

Symptoms:

Solutions:

OCR/Extraction Errors

Symptoms:

Solutions:

Browser Issues

Chrome Integration Not Working

Symptoms:

Solutions:

Step 1: Check Chrome Installation

Step 2: Grant Chrome Permissions

  1. System Settings → Security & Privacy → Privacy
  2. Accessibility → Add Claude Desktop
  3. Screen Recording → Add Claude Desktop (if needed)

Step 3: Test Browser Access

In Cowork: "Open Chrome and search for 'test'"

“Chrome Native Messaging Host Not Found”

Exact Error:

Chrome native messaging host not found

or silently fails with no Chrome interaction.

Root Cause: The native messaging host allows Claude Desktop to communicate with Chrome. It may not install correctly during setup.

Manual Fix:

# 1. Find the Claude native messaging manifest
ls ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/

# 2. If empty or missing "com.anthropic.claude.json", create it:
mkdir -p ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts

# 3. Create manifest (adjust path if Claude is installed elsewhere)
cat > ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude.json << 'EOF'
{
  "name": "com.anthropic.claude",
  "description": "Claude Desktop Native Messaging Host",
  "path": "/Applications/Claude.app/Contents/Resources/native-messaging-host",
  "type": "stdio",
  "allowed_origins": [
    "chrome-extension://YOUR_EXTENSION_ID/"
  ]
}
EOF

# 4. Restart Chrome and Claude Desktop

Note: The extension ID varies. Check Chrome extensions (chrome://extensions) to find the Claude extension ID if installed.

If Still Failing:

  1. Completely uninstall Claude Desktop
  2. Delete ~/Library/Application Support/Claude/
  3. Reinstall from claude.ai
  4. Re-grant all permissions

Browser Actions Failing

Symptoms:

Solutions:

Web Research Returns Poor Results

Symptoms:

Solutions:

Windows-Specific Issues

Installation Problems

Symptoms:

Solutions:

Step Action
1 Run installer as Administrator (right-click → Run as administrator)
2 Ensure Windows 10 (build 1903+) or Windows 11
3 Temporarily disable antivirus during installation
4 Check Windows Event Viewer for specific error codes

PATH and Permission Issues

Symptoms:

Solutions:

  1. Verify installation path: Check that Claude Desktop is installed in %LOCALAPPDATA%\Programs\Claude\ or C:\Program Files\Claude\
  2. Run as Administrator: Right-click Claude Desktop → Run as administrator (for initial setup)
  3. Folder permissions: Ensure your workspace folder is not in a system-protected location (avoid C:\Windows\, C:\Program Files\)
  4. Controlled Folder Access: Windows Security → Virus & threat protection → Ransomware protection → Allow Claude through Controlled Folder Access
  5. Firewall: Ensure Windows Firewall allows Claude Desktop for both private and public networks

Windows Defender Blocking

Symptoms:

Solutions:

  1. Open Windows Security → Virus & threat protection
  2. Go to Protection history and check if Claude was blocked
  3. Add Claude Desktop to Exclusions if needed (Settings → Virus & threat protection → Manage settings → Exclusions)

VPN on Windows

The same VPN routing conflict applies on Windows. If you experience VM connection timeouts:

  1. Disconnect VPN before launching Cowork
  2. If using corporate VPN, check if split tunneling is available
  3. Windows-specific: Some VPN clients (e.g., Cisco AnyConnect) may require a full restart after disconnecting

General Troubleshooting

Cowork Doesn’t Understand Request

Symptoms:

Solutions:

Better Prompt Pattern:

Task: [clear single objective]
Input: [exact folder/files]
Output: [exact format and location]
Constraints: [any limitations]
Example: [what success looks like]

Files in Unexpected State

Symptoms:

Recovery:

1. DON'T let Cowork "fix" without understanding
2. Review manually what changed
3. Restore from backup if needed
4. Restart with clearer instructions

Prevention:

Context Confusion Across Tasks

Symptoms:

Solutions:

Reporting Issues

When to Report

Report to Anthropic when:

How to Report

  1. General Support: support.anthropic.com
  2. Feature Requests: Claude Desktop app → Feedback
  3. Community: Reddit r/ClaudeAI

What to Include

- Operating system and version (macOS or Windows)
- Claude Desktop version
- Subscription tier
- Steps to reproduce
- Expected vs actual behavior
- Screenshots if applicable
- Relevant error messages

Quick Fixes Summary

Issue Quick Fix
Can’t see Cowork Update app + restart
Permission denied Re-grant folder access in System Settings
Task stops Break into smaller batches
Excel formulas broken Specify regional syntax in prompt
Chrome not working Grant Accessibility permission
Wrong output Be more explicit in prompt
Files missing Check backup, review what Cowork did

Prevention Checklist

Before starting any task:

*← Security Cowork Documentation*