Claude Cowork Files Aren’t Appearing? Use This Safe Troubleshooting Checklist

Cihan’s view: TRY this checklist on a harmless sample folder; SKIP broad access or sensitive files until you know which surface and permissions the task is using.

Evidence label: documentation-based troubleshooting guide with an illustrative example. The workflow below is based on Anthropic’s current help documentation. It was not run as a hands-on Claude Cowork test here.

A missing file is often treated as an AI failure. In Cowork, it may be a setup or permission mismatch instead. The session surface matters, as does where the task runs. Diagnose those boundaries before changing the prompt.

The example

Imagine a fictional folder named handover-sample containing:

handover-sample/
├── project-status.md
├── open-questions.txt
└── owners.csv

You ask Claude for a three-file handover pack, but it says owners.csv is missing. Do not add more folders or reconnect your whole home directory yet. Use the sequence below.

The four-check diagnosis

1. Confirm which surface started the task

Claude’s current help says Cowork is available across paid-plan surfaces, but the exact experience varies. On desktop, web and mobile, Chat and Cowork share one home. Some accounts now have the unified Claude experience, where you describe the task in a normal conversation and Claude decides how to handle it.

Write down the surface you used: Claude Desktop, claude.ai, mobile, or the Chrome side panel. If the instructions you are following mention an old Chat / Cowork selector that you cannot see, stop treating that missing selector as an error. The interface may have moved to the unified experience.

2. Check where the session can run

Cloud sessions use the files and connectors available to your Claude account. A local file is reachable from a desktop session only when the Claude Desktop app is open and the relevant folder has been connected. If the app is offline, that local path is not available to the session.

Ask for a boundary report before asking for the deliverable:

Before doing any work, report:
1. Which session surface you are using.
2. Whether this task is running in the cloud or through the desktop app.
3. Which exact folder or uploaded files you can see.
4. The filenames you cannot see.
Do not open, move, rename, delete or edit any file yet.

The useful artifact at this stage is a short access report, not a confident-sounding handover pack.

3. Check permissions and the output location

If Claude can see the folder but the file is not appearing where expected, ask it to state the output path. Anthropic’s troubleshooting guidance specifically recommends checking the granted file-access permissions and the output location Claude identified when finishing.

Use this bounded follow-up:

Use only the files currently visible in handover-sample.
Do not request another folder. Do not write or delete anything.
List the source files you can read, the files you cannot read, and the exact output folder you would use.
Then stop for approval.

Compare that list with your own folder view. A file that is absent from the visible source list is not evidence that Claude ignored it; it may be outside the connected folder or blocked by permission.

4. Retry with a harmless read-only sample

Create a new folder containing only the three fictional files above. Do not begin with financial documents, customer exports, private email or a company-wide folder. Ask Claude to produce a proposed file map in chat, with no writes. If the sample works, the original problem is likely related to the original folder boundary, surface or permissions rather than the handover prompt itself.

Acceptance checks

The diagnosis is complete only when:

• the session surface is recorded;
• the task’s cloud/desktop boundary is clear;
• the exact visible and missing filenames are listed;
• the proposed output location is explicit;
• no source file was edited, moved or deleted; and
• the same read-only request works, or fails clearly, on the harmless sample folder.

If the missing file contains sensitive information, stop. Ask the owner to decide whether the file should be connected at all. Cowork can read files, browse, run code and use connected apps; write actions carry more risk than read actions, and prompt injection can arrive through external content. Keep the first diagnostic pass read-only and review every proposed action.

TRY / SKIP

TRY this sequence for a small, non-sensitive folder when you need to separate an access problem from a prompt problem. SKIP reconnecting broad folders, signed-in sites or sensitive company data just to make one deliverable appear. If the boundary remains unclear, use a manual upload of approved sample material or stop for an owner review.

Official sources: Get started with Claude Cowork · Use Claude Cowork safely

About Cihan

Creator and operator focused on practical AI for business professionals. Background and editorial approach →