[BUG] Cowork session reports zero connected folders while the project UI shows a folder as connected #86647

Preflight Checklist

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

What's Wrong?

Description

When starting a Cowork task from a project that has a folder connected, the desktop UI
displays the folder chip (in my case "My Writings"), but the session itself has no access
to it. get_device_info returns connectedFolders: [], and any attempt to list or write
to the folder path fails with a grant error.

The result is a silent capability mismatch: the UI indicates the agent can read and write
my folder, but it cannot. File deliverables fall back to browser downloads with no
indication that folder access was expected and missing.

Steps to reproduce

1. Open a project in the Claude desktop app that has a local folder connected
   (mine is a OneDrive folder at ~/Library/CloudStorage/OneDrive-<Org>/My Writings).
2. Select Cowork and start a task. The composer shows the folder chip for the project.
3. Ask Claude to work with files in that folder, or have it produce file output.
4. Observe that Claude has no folder access. Internally get_device_info returns
   "connectedFolders": [].

Expected behavior

If the project UI shows a folder as connected, the Cowork session should start with that
folder in connectedFolders and be able to read and write it without an additional grant.

Actual behavior

• connectedFolders is empty for the whole session.
• device_list_dir on the folder path returns:
  "This directory can't be listed without a grant".
• All file output is delivered as downloads instead of being written to the folder.
• No warning surfaces that the expected folder is unavailable.

Workaround

Clicking Add folder in the desktop app mid-session connects the folder correctly.
Writes to it succeed immediately afterward. So the grant mechanism works; the issue is
that the session does not inherit the project's folder at start.

Impact

The failure is silent and only becomes visible after work is already done. In my session
this was discovered after four document revisions had been produced, all of which had to
be delivered as downloads and then re-committed to the folder once access was granted.

Environment

• Claude desktop app: 1.26832.0
• Electron: 42.7.0
• Node: 24.18.0
• OS: macOS, arm64
• Context: Cowork task started from a project with a connected folder
• Folder type: OneDrive under ~/Library/CloudStorage/

What Should Happen?

Expected behavior

If the project UI shows a folder as connected, the Cowork session should start with that
folder in connectedFolders and be able to read and write it without an additional grant.

Error Messages/Logs

Steps to Reproduce

Steps to reproduce

1. Open a project in the Claude desktop app that has a local folder connected
   (mine is a OneDrive folder at ~/Library/CloudStorage/OneDrive-<Org>/My Writings).
2. Select Cowork and start a task. The composer shows the folder chip for the project.
3. Ask Claude to work with files in that folder, or have it produce file output.
4. Observe that Claude has no folder access. Internally get_device_info returns
   "connectedFolders": [].

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

1.26832.0

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information