Common Claude Cowork errors and how to fix them

TL;DR. The 12 most common Cowork problems and the fix for each. Written so an operator can self-serve in 60 seconds without paging IT. About 70% of "Cowork did something weird" tickets resolve to "your prompt was ambiguous" — train the team on Prompt anatomy and ticket volume drops 60% in two weeks.

For each error: the symptom in plain language, the cause, the fix, and when to escalate.

1. "Cowork can't access this folder"#

Symptom: Cowork says it can't read or write to a folder it should have access to.
Cause: Folder grant was revoked, the path moved, or the cloud sync isn't fully synced.
Fix: Settings → Folder access → re-grant. Check the cloud sync status. Verify the path exists in Finder/Explorer.
Escalate: if the grant disappears repeatedly across sessions.

2. "It started planning, then didn't act"#

Symptom: Cowork produces a plan but never executes.
Cause: Approval was missed; a long thinking step timed out.
Fix: Scroll up, find the "Approve" prompt, click. If no approve button, send a message: "approved, proceed."
Escalate: never — this one is on the operator.

3. "It modified files I didn't expect"#

Symptom: Files outside the intended scope were edited or moved.
Cause: The prompt didn't constrain scope; Cowork interpreted broadly.
Fix: Restore from cloud-sync version history. Tighten the next prompt to name source and destination explicitly.
Escalate: if cloud-sync history isn't enabled — talk to IT immediately.

4. "The output is wordy and generic"#

Symptom: Word docs that read like marketing copy.
Cause: Prompt didn't specify voice, length, or constraints.
Fix: See Output quality issues. Add word count caps and a stop-word list to CLAUDE.md.

5. "Cowork hit a usage limit mid-task"#

Symptom: A long-running task stops with a quota message.
Cause: Heavy work on Pro seats; quota resets every 5 hours.
Fix: See Usage limits. Wait for reset or upgrade the operator's seat.
Escalate: if the operator hits limits more than twice a week — they need a Max seat.

6. "Cowork can't reach the web"#

Symptom: Web search returns nothing or fails.
Cause: VPN active (most common), network restrictions, Anthropic's web tool unavailable.
Fix: Disconnect VPN — see VPN & network. Try again in 5 minutes if it's a transient outage.
Escalate: if persistent without VPN, contact IT to check egress rules.

7. "OCR misread an obvious number"#

Symptom: Receipt or invoice extraction shows a wrong amount.
Cause: Image quality, faint print, decimal/thousand separator confusion.
Fix: Always use a Review tab for low-confidence rows. Re-run with higher-resolution images. Add an explicit currency/separator rule to CLAUDE.md.

8. "Cowork ignored my CLAUDE.md"#

Symptom: Output doesn't reflect house rules.
Cause: CLAUDE.md missing, in the wrong location, or the rule was buried.
Fix: Confirm CLAUDE.md is at the workspace root. Move the violated rule to the top. State it as a hard rule, not a preference.

9. "It made up a number"#

Symptom: Output contains a figure that isn't in the source.
Cause: Cowork inferred. Most common in summaries and variance commentary.
Fix: Add an explicit "cite every number" rule to the prompt. Use [CONFIRM] placeholders for values not in source.
Escalate: if persistent in finance workflows, treat as a quality bar issue and tighten the prompt.

10. "Memory contains something that shouldn't be there"#

Symptom: Cowork "remembers" a fact you don't want it to.
Cause: Memory feature accumulated a sensitive fact.
Fix: Memory settings → review entries → delete. Add a CLAUDE.md rule: "Do not store the following in Memory: ..."

11. "An MCP connector authorization expired"#

Symptom: A connector that was working fails with auth errors.
Cause: OAuth token expired, vendor revoked, scopes changed.
Fix: Reconnect via the connector's settings page. Check vendor's audit log.
Escalate: to whoever owns the connector inventory.

12. "Scheduled task didn't fire"#

Symptom: A scheduled run didn't produce its expected output.
Cause: Laptop was asleep, account logged out, schedule misconfigured.
Fix: Verify the schedule, check the laptop was awake at the scheduled time. For always-on workflows, see Scheduled tasks.

Tinkso's take#

The most common error is actually a prompt not specifying what it should have. About 70% of "Cowork did something weird" tickets resolve to "your prompt was ambiguous." Train the team on Prompt anatomy and the ticket volume drops 60% in two weeks.