[BUG] Cowork scheduled tasks never fire, even with app open and Cowork actively used (not just late — related to #36131)
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?
Scheduled tasks created via Cowork's scheduler stop firing entirely and never resume, even with Claude Desktop running continuously and Cowork actively used. Tasks remain enabled: true but nextRunAt/fireAt stays frozen at the original scheduled time long after it's passed, and lastRunAt never updates (or is stuck weeks in the past).
What Should Happen?
Enabled scheduled tasks should fire at their scheduled cron/fireAt time as long as Claude Desktop is running, regardless of which view is focused.
Error Messages/Logs
None.None — this is the core problem. No error, exception, or log entry appears anywhere reachable from the Cowork session. list_scheduled_tasks just shows the task silently not having run.Steps to Reproduce
- In Cowork, create a scheduled task (recurring cron or one-time fireAt), e.g. 30 minutes out
- Leave Claude Desktop running, confirm via Task Manager it's active
- Wait past the scheduled time
- Call list_scheduled_tasks — nextRunAt/fireAt is unchanged, lastRunAt never populated
- Actively use Cowork/Dispatch in the meantime — does not trigger the missed task to fire
Claude Model
Not sure / Multiple models
Is this a regression?
Yes, this worked in a previous version
Last Working Version
Unknown exact version — last confirmed successful run was 2026-08-07 to 08-10
Claude Code Version
2.1.234
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Other
Additional Information
Ruled out directly: app not running (confirmed active in Task Manager), stuck app state (full quit/relaunch didn't help), Cowork view not focused (unlike #36131, persisted even with active Cowork/Dispatch use), machine sleep, Windows Home edition (upgraded to Pro), Hyper-V disabled (enabled it). Currently checking whether the separate "Virtual Machine Platform" Windows feature (distinct from Hyper-V) is enabled, as an untested lead. Possibly related to #36131 (tasks firing late until Cowork focused, macOS) but this is worse — never fires at all, on Windows.