Project's connector-synced folder stays permanently empty after interrupted sync — no fix via refresh/relaunch/reconnect
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?
I had Claude provide a write up. I have a Claude Code project (ha-config-readonly, on macOS/Claude Desktop) with a "Home Assistant" connector (Web, Custom) that syncs my Home Assistant config files into a local project folder for review.
Timeline:
The project's synced folder was working normally for an extended session — automation YAML files, dashboard config, etc. were all readable.
I had Claude Desktop open during a Verizon internet outage this morning.
At some point after that (I noticed it later, mid-conversation with Claude), the project's local synced folder became completely empty — no config files, just an internal .claude metadata subfolder. No error was shown to me in the UI.
The Home Assistant connector still showed as "Connected" (checkmark) throughout.
Troubleshooting already tried, none of which fixed it:
Used the in-app "refresh" on the project files view — no change.
Fully quit and relaunched Claude Desktop (Cmd+Q, reopen) — no change.
Explicitly disconnected and reconnected the Home Assistant connector from the connectors settings screen — reconnect succeeded (shows connected), but the local folder still did not repopulate.
Rebooted the actual Home Assistant instance (Home Assistant Green hardware) and relaunched Claude Desktop again — no change.
Current state: Connector shows connected and reconnects successfully, confirming the underlying connection/auth is fine. But the project's local synced folder remains empty, and nothing I've tried triggers a fresh resync.
One more clue: the folder's content was cleared around the same time I asked a question from within the project's "Project files" chat session and it appeared to spawn a new session/"area" — it's possible that action created a fresh sync context that didn't inherit or re-fetch the previously-synced snapshot, rather than the outage itself being the direct cause.
Expected behavior: After a sync is interrupted (e.g. by a network outage) and the connector is confirmed reconnected, the project should be able to recover by re-syncing the connected files — not remain permanently empty with no user-facing error or way to force a full resync.
Environment: macOS (Darwin 25.5.0), Claude Desktop app.
What Should Happen?
Expected behavior: After a sync is interrupted (e.g. by a network outage) and the connector is confirmed reconnected, the project should be able to recover by re-syncing the connected files — not remain permanently empty with no user-facing error or way to force a full resync.
Error Messages/Logs
Steps to Reproduce
Steps to reproduce:
Open a Claude Code project with a connector attached (in my case, "Home Assistant" — Web, Custom type) that syncs external files into a local project folder.
Use the project normally in an active chat session — files sync in and are readable/editable through Claude.
While the app is open and mid-session, experience an internet connectivity interruption (in my case, an ISP outage).
Continue using the same chat session after connectivity returns — no error was shown at this point.
At some point after the outage, ask a question from within the project's "Project files" chat, which caused the app to create a new session/"area" under the project.
Notice the project's local synced folder is now completely empty (only an internal .claude metadata subfolder remains) — files that were previously readable are gone.
Attempt recovery: refresh the project files view (no effect) → fully quit and relaunch Claude Desktop (no effect) → disconnect and reconnect the Home Assistant connector, which succeeds and shows "Connected" (no effect on the folder) → reboot the underlying Home Assistant server and relaunch Claude Desktop again (no effect).
Folder remains permanently empty with no error message, despite the connector showing a healthy "Connected" state throughout.
Note: I wasn't able to isolate a minimal, deliberate repro — this is the actual sequence of events from a live session, so the network interruption and/or the "new area" creation in step 5 are my best guesses at the trigger, not confirmed causes.
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
1.26832.0
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_