Last refreshed: June 9, 2026
sessiondata.img). Second most common: a scheduled task depends on a local process that stops when your machine sleeps. Both are fixable in minutes.Claude Cowork stops working for a small set of predictable reasons. This page covers the five most common failures, how to diagnose which one you’re hitting, and the exact fix for each.
Claude Cowork Error Quick-Reference
Claude Cowork issues: quick diagnosis
| Symptom | Most likely cause | Fix |
|---|---|---|
| Cowork won’t launch | App update pending | Quit Claude desktop app, reopen — auto-updates on restart |
| MCP tools not showing | MCP server not running or config error | Check claude_desktop_config.json syntax; restart app |
| “Not connected” in Cowork panel | Plugin not loaded or credentials expired | Re-authenticate the plugin from Settings > Capabilities |
| Skills not triggering | Skill description doesn’t match your prompt | Use the exact trigger phrase from the skill description |
| File tools not working | No folder selected | Select a working folder via the folder icon in Cowork |
| Scheduled tasks not running | Claude desktop app not running at scheduled time | Keep app running in background; check task log for errors |
| Computer use not responding | Permission not granted for target app | Claude will prompt for permission — approve in the dialog |
| Symptom | Most Likely Cause | Fix |
|---|---|---|
| Cowork won’t start / hangs on launch | Cowork VM disk full (sessiondata.img) | Clear sessiondata.img or expand VM disk allocation |
| Scheduled tasks stop running overnight | Local process killed when machine sleeps | Use GCP Cloud Run cron instead of local scheduler |
| Tool calls return empty responses | MCP server disconnected | Restart Claude Desktop; re-authenticate MCP servers |
| File edits not saving | Workspace folder not mounted | Reconnect folder via Cowork settings |
| Browser automation stops mid-task | Chrome extension lost connection | Reload extension; check tab is in allowed group |
Claude Cowork Error Quick-Reference
| Symptom | Most Likely Cause | Fix |
|---|---|---|
| Cowork won’t start / hangs on launch | Cowork VM disk full (sessiondata.img) | Clear sessiondata.img or expand VM disk allocation |
| Scheduled tasks stop running overnight | Local process killed when machine sleeps | Use GCP Cloud Run cron instead of local scheduler |
| Tool calls return empty responses | MCP server disconnected | Restart Claude Desktop; re-authenticate MCP servers |
| File edits not saving | Workspace folder not mounted | Reconnect folder via Cowork settings |
| Browser automation stops mid-task | Chrome extension lost connection | Reload extension; check tab is in allowed group |
Claude Cowork Error Quick-Reference
| Symptom | Most Likely Cause | Fix |
|---|---|---|
| Cowork won’t start / hangs on launch | Cowork VM disk full (sessiondata.img) | Clear sessiondata.img or expand VM disk allocation |
| Scheduled tasks stop running overnight | Local process killed when machine sleeps | Use GCP Cloud Run cron instead of local scheduler |
| Tool calls return empty responses | MCP server disconnected | Restart Claude Desktop; re-authenticate MCP servers |
| File edits not saving | Workspace folder not mounted | Reconnect folder via Cowork settings |
| Browser automation stops mid-task | Chrome extension lost connection | Reload extension; check tab is in allowed group |
Error 1: “useradd failed: exit status 12”
What it means: The Cowork VM’s internal disk (sessiondata.img) is full. No new sessions can be provisioned.
Fix: Quit Claude Desktop. Move sessiondata.img from %APPDATA%\Claude\vm_bundles\claudevm.bundle\ (Windows) or ~/Library/Application Support/Claude/vm_bundles/claudevm.bundle/ (macOS) to your Desktop. Relaunch Claude Desktop — it recreates a fresh image. Full walkthrough: Claude Cowork useradd Failed Error Fix.
Error 2: Scheduled Tasks Stop Running
What it means: Tasks that were running on schedule suddenly stop firing. Often appears as tasks last running a few days ago with no new entries.
Causes: Machine went to sleep, Claude Desktop was quit, or the local runner process died. Cowork tasks require Claude Desktop to be open and running on an active machine. They are not fully cloud-hosted — they depend on the local Cowork environment being live.
Fix: Reopen Claude Desktop and manually trigger one task to verify it runs. For tasks that need to run reliably without the machine being awake, move them to a GCP Cloud Run cron job or a cloud VM instead of Cowork’s local scheduler.
Error 3: MCP Tools Not Available in Cowork
What it means: Cowork tasks can’t access Notion, Gmail, or other connected services that work fine in Chat.
Fix: MCP servers must be configured in claude_desktop_config.json — the same config file Claude Desktop uses. If an MCP server appears in Chat but not in Cowork, verify it’s listed in the desktop config, not just the web interface. Restart Claude Desktop after any config changes.
Error 4: File Access Denied or Path Not Found
What it means: A Cowork task fails trying to read or write a file that should be accessible.
Fix: Cowork’s VM mounts specific directories from your machine. If the file is outside a mounted path, Cowork can’t reach it. Check that the file path is within your configured working directories. On Windows, path separator issues (\ vs /) inside the Linux VM can also cause this — use forward slashes or escape backslashes in task prompts.
Error 5: Tasks Run but Produce Wrong Output
What it means: Cowork is running but the results are stale, wrong, or missing context from previous runs.
Fix: Cowork tasks don’t have memory of previous runs by default. If your task depends on knowing what happened last time — what was published, what changed — you need to build that context explicitly into the task prompt, typically by reading a log from Notion or a local file at the start of each run. The task prompt is the only persistent instruction; Claude doesn’t remember prior task outputs.
Why did Cowork tasks stop running overnight?
Cowork requires Claude Desktop to be running on an active machine. If your computer slept, hibernated, or Claude Desktop was closed, scheduled tasks won’t fire. For always-on reliability, route tasks through a cloud runner instead.
Why can Cowork not find my files?
Cowork’s Linux VM only has access to directories you’ve configured as mount points. Files outside those paths are invisible to the VM. Verify your working directory configuration in Claude Desktop settings.
Does Cowork work on Windows?
Yes, Cowork is available on both Windows and macOS via Claude Desktop. The VM behavior and file paths differ slightly between platforms but the core functionality is the same.
Frequently Asked Questions
Why does Claude Cowork stop working when my computer sleeps?
Claude Cowork scheduled tasks depend on a local process that gets killed when your machine sleeps or the lid closes. The fix is to run scheduled tasks via GCP Cloud Run or another always-on host rather than relying on the local Cowork scheduler.
How do I fix the Cowork VM disk full error?
The most common Cowork failure is a full sessiondata.img file on the Cowork VM. Open the VM settings, clear sessiondata.img or increase the disk allocation. This resolves the majority of ‘Cowork won’t start’ issues.
Why are my Claude Cowork MCP tools returning empty responses?
Empty MCP tool responses usually mean the MCP server has disconnected. Restart Claude Desktop and re-authenticate the affected MCP servers through Settings > Capabilities. If the issue persists, check that the MCP server process is still running.
Is Claude Cowork the same as Claude in Chrome?
No. Claude Cowork is a desktop agent for file management and task automation. Claude in Chrome is a browser extension that gives Claude control of your active Chrome tab. They are separate tools that can be used together but serve different purposes.
What should I do if Claude Cowork file edits aren’t saving?
If file edits aren’t saving, the workspace folder is likely not properly mounted. Go to Cowork settings and reconnect the folder. Make sure you’ve granted Cowork write access to the directory, not just read access.
Frequently Asked Questions
Why is Claude Cowork not working?
The most common reasons Claude Cowork stops working are: (1) a pending app update — quit and reopen the Claude desktop app to apply updates; (2) an MCP server configuration error — check your claude_desktop_config.json for syntax issues; (3) expired plugin credentials — re-authenticate from Settings > Capabilities; (4) no working folder selected — click the folder icon in the Cowork panel to select one. Most Cowork issues resolve with an app restart.
How do I fix MCP tools not showing in Claude Cowork?
If MCP tools are not appearing in Cowork, check three things: (1) your claude_desktop_config.json file has valid JSON syntax — a single missing comma breaks the entire config; (2) the MCP server command is correct and the binary or package is installed; (3) you restarted the Claude desktop app after editing the config. Use ‘claude mcp list’ in your terminal to verify which servers are loaded. If a server shows as loaded but tools don’t appear, the server may be failing silently — check its logs.
Why are my Cowork skills not triggering?
Skills trigger based on the description and trigger phrases in their SKILL.md. If a skill isn’t firing, check that your prompt closely matches the trigger language in the skill description. Skills are loaded by Claude based on semantic matching — if your prompt is ambiguous, Claude may not recognize which skill to invoke. Try using the exact trigger phrase listed in the skill’s description. You can view installed skills in Settings > Capabilities > Skills.
Why did Claude Cowork stop working after an update?
App updates occasionally reset plugin configurations or require re-authentication. After a Claude desktop app update: (1) re-open the Cowork panel; (2) check if any plugins show ‘reconnect’ prompts in Settings > Capabilities; (3) verify your MCP servers are still listed in claude_desktop_config.json — updates don’t modify this file, but a fresh install might. If a plugin stopped working, re-authorize it from Settings.
How do I select a working folder in Claude Cowork?
Click the folder icon in the Cowork panel header to open the folder picker. Select the directory you want Claude to read from and write to. Without a selected folder, file tools (Read, Write, Edit) won’t have access to your files. The selected folder path persists across sessions. You can change it at any time by clicking the folder icon again.
What should I do if Claude Cowork computer use isn’t responding?
Computer use in Cowork requires explicit permission for each application. When Claude needs to control an app, it will show a permission dialog — you must approve it before Claude can interact with that app. If the permission dialog doesn’t appear, try re-stating your request. If computer use worked before but stopped, check that the target application hasn’t been updated or moved. Browsers (Chrome, Edge, Safari) are read-only in computer use — for browser automation, use the Claude in Chrome extension instead.
📖 Related Claude Guides








