[BUG] Windows Desktop: linked computer stuck on "Asleep or app closed", cloud sessions and cloud scheduled tasks fail with "not connected to the bridge" (survives reboot, re-login, device removal, app update)
Status Fixed / completed
Maintainer reply None cached
Activity 10 comments · opened Sep 25, 2026 · closed Sep 25, 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?
Since scheduled tasks moved to the cloud, my Windows PC can't be reached from cloud sessions or cloud scheduled tasks.
- In the computer picker for a cloud scheduled task and a linked cloud session, the PC shows "Claude Desktop (Windows) · Asleep or app closed". At the same time the PC is awake and online, and the desktop app is open and signed in.
- Every call to the computer from a linked cloud session (
get_device_info,device_bash) fails immediately with:The device this session is bound to is not connected to the bridge. - It has failed every time from ~00:35 UTC to at least ~00:56 UTC on 2026-09-25, and is still failing.
Impact: I have ~12 cloud scheduled tasks that use local folders on this PC, and none of them can reach it.
What Should Happen?
With the PC awake and the desktop app open and signed in, the computer should show as online, and linked cloud sessions and scheduled tasks should be able to reach its connected folders.
Error Messages/Logs
# From a linked cloud session, repeated between ~00:35 and ~00:56 UTC on 2026-09-25:
get_device_info -> The device this session is bound to is not connected to the bridge.
device_bash -> The device this session is bound to is not connected to the bridge.
# Computer picker UI:
Claude Desktop (Windows) · Asleep or app closedSteps to Reproduce
- On Windows, have Claude Desktop open and signed in, with cloud scheduled tasks that have local folders attached (tasks migrated to cloud).
- Open a cloud scheduled task or a cloud session linked to this computer.
- The computer picker shows "Asleep or app closed", and any device tool call fails with "not connected to the bridge".
Already tried, none of which fixed it:
- Restarted the PC
- Signed out and back in to the desktop app
- Removed the PC from trusted devices to force it to pair again
- Updated Claude Desktop to the latest version (it had been pinned with updates disabled)
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
Unknown. It worked before scheduled tasks moved to the cloud.
Claude Code Version
Claude Desktop for Windows (MSIX), updated to latest on 2026-09-25 (2.9939.x); cloud session side
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Other
Additional Information
- The timing lines up with #96911 (Windows, device bridge
connect frame sent->handshake timeout, 00:06-00:24 UTC the same day, same error string). That report recovered by itself; mine is still down past 00:56 UTC, so this may be a server-side bridge issue that hasn't cleared for some devices. - Possibly related: #88692. After I removed the trusted device, existing sessions and scheduled tasks may still be tied to the old device ID. The error text doesn't say whether the device is offline or its ID no longer matches, so I can't tell which it is.
- Other similar reports: #75416, #58097, #94229, #95802.
- I've also opened a support ticket so the pairing can be checked on the account side.
Showing cached comments. Read the full discussion on GitHub ↗
9 Comments
Same symptoms here — Windows Desktop 2.9939.2, Cowork cloud session.
@malcolm-ingram do you mean that your current outage/bug as of today, self recovered after 70min outage? Just clarifying.
Do you mean that your current bug/outage as of today, self-recovered after 70mins? Just clarifying. Thanks!
This is ridiculous, i spent the entire laast two days rebuilding all my projects because of this forced cloud migration, now im getting this error too saaying computer is offline or asleep inside the app. I spend several hundreds a month on claaude and spent 6 months building this system all for it to be destroyed in 1 week because of a forcded cloud migraation of aall the schedulers and taasks
Im so glad im not the only one. Last 2 days were a disaster, outages for all my scheduled tasks, lost history, I still don't have scheduled tasks in my sidebar, bugged completely broken.
"6 months building this system all for it to be destroyed in 1 week because of a forcded cloud migraation of aall the schedulers and taasks"
Literally me too.
@claude fix yo shit
Same issue here. Same version (2.9939.2, d3e504), same day (25.09.2026), same error ("not connected to the bridge", computer shown as "Asleep or app closed" while the app is open). Survives app restart, Windows reboot, disabling "Require trusted devices", removing stale device entries and new tasks. Full details in my comment on #88692. Also reported to support (Fin conversation 215476095422155).
Update: self-recovered on my side at around 02:47 UTC (25.09.2026), with no further local action. The device bridge works again, and the same session can reach my computer and local folders. Same pattern as malcolm-ingram's report, but the outage lasted several hours for me. It still looks like a server-side bridge issue that clears on its own.
ya its back for me, but im so annoyed and pissed off, as @Loneplanet117 all my scheduled tasks aare missing from the sidebar and i have to spend the week redoing scheduled tasks thaat auto migrated. This is ridiculous, they should of let us keep the option of running tassks locaally or on the cloud.
Update: Recovered on its own as well. @apishdadi and yes, backwards compatibility is non-existent in 2026 it seems - they could have least let us keep local by default. 😂
Yes, that's correct @Loneplanet117 . I had the issue impact me mid session at approx. 550k context. The defect impacted all sessions active and historical across Desktop CoWork and Web. It self corrected just after one hour.