[BUG] Claude Cowork can list but not read files in macOS FileProvider paths (Google Drive, Microsoft OneDrive)

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Claude Cowork fails to read files from its working folder when that folder is inside a FileProvider sync'd path (e.g. Google Drive).

Listing files in FileProvider paths works correctly. The prompt dialog will correctly autocomplete '@' paths, and Claude is able to see lists of files. But all attempts by Claude to read the contents of files always fail.

What Should Happen?

Claude Cowork should be able to read and write files in FileProvider paths (like Google Drive) just the same as if they were folders on the local disk.

Error Messages/Logs

Some examples of errors encountered by Claude Cowork:

pdftotext -layout "/sessions/session-name/mnt/path/to/file.pdf" /sessions/session-name/file.txt 2>&1 && cat /sessions/session-name/file.txt

Syntax Error: Couldn't find trailer dictionary
Syntax Error: Couldn't find trailer dictionary
Syntax Error: Couldn't read xref table

Syntax Warning: May not be a PDF file (continuing anyway)
Syntax Error: Couldn't find trailer dictionary
Syntax Error: Couldn't find trailer dictionary
Syntax Error: Couldn't read xref table

---

cat "/sessions/session-name/mnt/path/to/file.md"

Exit code 1
cat: '/sessions/session-name/mnt/path/to/file.md': Resource deadlock avoided

cat: '/sessions/session-name/mnt/path/to/file.md': Resource deadlock avoided

---

Claude Cowork also **succeeded** at listing files

ls -la "/sessions/session-name/mnt/path/"

total 12
drwx------ 14 session-name session-name      448 Feb 20 01:59 .
drwxr-xr-x  7 session-name session-name     4096 Mar  1 20:39 ..
-rw-------  1 session-name session-name     6148 Feb 20 02:00 .DS_Store
-rw-------  1 session-name session-name      177 Mar 16  2025 Some document.gdoc
-rw-------  1 session-name session-name      177 Mar 28  2025 Another document.gdoc
-rw-------  1 session-name session-name     2075 Feb 20 01:58 Markdown file.md
-rw-------  1 session-name session-name   491029 Apr 24  2024 A PDF file.pdf
...

Steps to Reproduce

1. Install Google Drive MacOS app
2. Configure Google Drive for "Stream" mode (via FileProvider), NOT "Mirror" mode (which requires downloading your entire Drive to your computer)
3. Open Claude Cowork
4. Click "Work in a folder," "Choose a different folder"
5. Select "Google Drive" from the sidebar in the Finder open dialog, choose a folder in Google Drive
6. Claude Cowork asks "Allow Claude to change files in \<folder\>?", click "Allow"
7. Prompt Claude Cowork to read some file in the folder (note that '@' reference complete works fine..)
8. Claude thrashes and ultimately fails to read the file

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude 1.1.4498 (24f768) 2026-02-26T19:47:09.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

User impact

Enterprises store data in the cloud for security, compliance, durability and to preserve a single source of truth. Google Drive "Streaming" and Microsoft OneDrive "Files On-Demand" simulate local file access to cloud resources without downloading them. The distinction should be invisible to local tools. Claude Cowork seems to fail to read files using standard file system APIs that would transparently bridge to FileProvider paths when necessary.

Alternatives considered

• Google Drive Connector: requires granting blanket permissions to the entire Drive rather than scoped access to the relevant folder.

• Google Drive mirroring: requires separate sync configuration for folders used with Claude Cowork (full Drive does not fit on machine), may break some compliance policies.

• Full disk access: requires granting blanket permissions to the entire _system_ (including the entire Drive) rather than scoped access to the relevant folder.

Related issues

• #24134
• #26981