[BUG] [Cowork] Existing local-folder project disappeared after Chat/Cowork web/mobile merge (Jul 8, 2026)

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?

After the Chat/Cowork merge rolled out on web/mobile today (July 8, 2026), a Cowork project that was previously bound to a local folder on Windows disappeared from the Projects list. The project had been working normally before the merge (local folder access, file reads/edits all functioned via a device/computer-use connector).

What Should Happen?

Existing Cowork projects, including their local folder bindings, instructions, and memory, should be preserved through the Chat/Cowork merge rollout, not lost.

Error Messages/Logs

Steps to Reproduce

1. Have an existing Cowork project on Claude Desktop (Windows) bound to a local folder (e.g. C:\Users\<user>\Documents\Claude\Projects\<project>), created and used successfully before July 8, 2026.
2. 2. Wait for the Chat/Cowork web/mobile merge to roll out on the account (occurred today, Jul 8 2026 - see https://www.anthropic.com/news and in-app changelog).
3. 3. Open Claude Desktop or claude.ai and check the Projects list.
4. 4. The previously existing local-folder project is no longer listed.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

Working normally prior to the Jul 8, 2026 Cowork web/mobile merge rollout

Claude Code Version

N/A - reporting via Claude Desktop app (Cowork/Chat merged UI), not Claude Code CLI

Platform

Other

Operating System

Windows

Terminal/Shell

Other

Additional Information

Environment: Windows, Claude Desktop app, project folder under C:\Users\<user>\Documents\Claude\Projects\. Related but separate issue being filed alongside this one: after creating a brand-new project and re-attaching a local folder, folder access also fails even after approving the OS-level folder access permission dialog (device bridge tool not registered in session).