[BUG] Cowork broken since Chat/Cowork merge rollout 8–9 July: projects disappear within 24h (ongoing data loss) and connector tools never reach Cowork sessions (Windows 11, Desktop 1.20186.0)

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?

Since the Chat/Cowork merge rollout reached my account (forced re-login/update on the morning of 9 July 2026; the merge rolled out from 8 July per #75603), the Cowork surface is broken in ways consistent with a single root cause — my account appears to be in a broken post-merge state. Environment: Windows 11 Home 25H2 (Build 26200.8655), Claude Desktop 1.20186.0, Max plan.

Ongoing, reproducible project data loss. I have worked exclusively in Cowork for the last month. On 10 July, every project created in Cowork during that month disappeared — the only projects remaining are ones created in normal chat more than a month ago. I created a new project in Cowork on 10 July; on 11 July it had also disappeared. So projects created in Cowork now disappear within roughly 24 hours, reproducibly, while chat-created projects are unaffected. This is ongoing data loss, not a one-off event. Possibly related: #75603 (project lost in the same merge rollout, currently mislabelled invalid), #45076, #56484.
Connector tools never reach Cowork sessions. Directory connectors (Microsoft 365, Google Drive, Shopify, Xero, Klaviyo, Slack, Semrush, Metricool, Canva) all work correctly in normal chat, but their tools never load in any Cowork session. Connectors appear in the + menu with no error badge, show as connected in Settings, all tools on Always allow, no Reconnect prompt — the tools simply never arrive in the session. This is the inverse of #73544 (custom connectors failing while directory connectors work), so filing separately. Very similar signature to #75625 (device bridge tools not registered in session after the merge).
Sessions cannot reach linked folders. Cowork sessions that do open throw "The requested project was not found" and cannot connect to their linked Google Drive folders. Working files are intact in Drive; the sessions cannot reach them.

Already tried, no effect: connector toggle off/on, full quit and restart, tool access mode Auto to On demand, complete uninstall and clean reinstall with sign-out/sign-in.
Diagnostics: %LOCALAPPDATA%\Claude\logs contains only chrome-native-host — no main.log and no MCP/connector logs at all. %APPDATA%\Roaming\Claude does not exist. Suggests the connector/MCP subsystem is not initialising or logging for Cowork on this install. For engineers: affected registration UUIDs a18583b2-26ca-41f2-bbca-e6327987941e and a0854f3f-0ce0-49e6-bb41-09e40cc001b6 (org ID on request).
Impact: I run a business through Claude on a Max plan with a month of complex work built up in Cowork, now lost or inaccessible, and Cowork is unusable for new work since anything created there disappears within a day. I have raised this through official support five times with no human response and would ask that this be escalated.
Related issues: #75603, #75625, #76344 (all post-merge Cowork breakage), #73544 (inverse connector symptom), #45076, #56484.

What Should Happen?

Projects created in Cowork should persist to my account like chat-created projects do, connector tools that show as connected should load in Cowork sessions, and sessions should be able to reach their linked folders. Existing projects, folder bindings and history should have been preserved through the Chat/Cowork merge rollout, and no project data should ever be silently deleted.

Error Messages/Logs

"The requested project was not found" — shown when opening Cowork sessions since 9 July.
No logs available to paste: %LOCALAPPDATA%\Claude\logs contains only chrome-native-host — no main.log and no MCP/connector logs at all. %APPDATA%\Roaming\Claude does not exist. The absence of connector/MCP logs appears to be part of the bug.

Steps to Reproduce

Environment: Windows 11 Home 25H2 (Build 26200.8655), Claude Desktop 1.20186.0, Max plan, directory connectors connected (Microsoft 365, Google Drive, Shopify, Xero, Klaviyo, Slack, Semrush, Metricool, Canva). Account went through the Chat/Cowork merge rollout / forced re-login on 9 July 2026.
Create a new project in Cowork. It works normally that day.
Quit the app and return the next day. The project has disappeared. (Reproduced: project created 10 July, gone 11 July. A month of Cowork-created projects disappeared the same way on 10 July, while projects created in normal chat over a month ago remain.)
Open any Cowork session and click + to add a connector. Connectors appear with no error badge and Settings shows them connected, but their tools never load in the session. The same connectors work correctly in normal chat.
Sessions linked to Google Drive folders throw "The requested project was not found" and cannot reach the folders.

Already tried with no effect: connector toggle off/on, full quit and restart, tool access mode Auto to On demand, complete uninstall and clean reinstall with sign-out/sign-in.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

Unknown exact build — everything worked until the forced re-login/update on the morning of 9 July 2026

Claude Code Version

1.20186.0 (Claude Desktop; reporting a Desktop/Cowork issue, not CLI)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

Timeline: account went through the Chat/Cowork merge rollout / forced re-login on the morning of 9 July 2026. All Cowork-created projects from the previous month disappeared on 10 July. A new project created in Cowork on 10 July had disappeared by 11 July. Projects created in normal chat over a month ago remain intact throughout.
Not an isolated account: #75603, #75625 and #76344 all report Cowork breakage starting with the same 8 July rollout, on both Windows and macOS. #75603 was auto-labelled invalid by the bot but describes the same project-loss regression.
Previously commented with this account's details on #73544 (18h and 17h ago) before realising the symptom set there is the inverse of mine.
Happy to provide the org ID, timestamps of the disappeared projects, or run any diagnostics on request — this account currently reproduces the failure daily, so it may be useful for debugging.