[BUG] Windows 11 Pro: Cowork sessions cannot create or edit local (file-reading) scheduled tasks - reserved "Scheduled" folder is unreachable

Status Open
Maintainer reply None cached
Activity 0 comments · opened Sep 4, 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?

On Windows 11 Pro, I cannot create or edit local (file-reading) scheduled tasks through Cowork.

My existing scheduled tasks fire correctly from D:\OneDrive\Scheduled\<task>\SKILL.md.

Asking a Cowork session to EDIT an existing task has no effect. The top-level folder named "Scheduled" is never mounted into a session (it appears to be a reserved name), so a session cannot reach the folder the scheduler fires from. The session's edit lands in a different copy and the live task is left unchanged, with no error.

A cloud session can only CREATE cloud tasks, which cannot see local files, and there is no "run on my computer" or local option exposed on my account. So I cannot create a new local file-reading task through Cowork either.

The only ways to change a task are the desktop app's own Edit form, or hand-editing the SKILL.md file directly. None of the local scheduled-task estate can be automated through Cowork itself.

Previously reported under #24962 (now closed as completed), but that issue was scoped to a different Windows 11 Home machine (DNS / sessiondata.vhdx / NAT). This Pro-specific scheduled-task behaviour persists.

What Should Happen?

A Cowork session should be able to create and edit local, file-reading scheduled tasks, either directly or through an exposed "run on my computer" / local option, so the local scheduled-task estate can be managed through Cowork rather than only by hand in the app or by editing SKILL.md files. The top-level "Scheduled" folder should be reachable by a session (or the reserved-name restriction lifted) so a session's edit reaches the folder the scheduler actually fires from.

Error Messages/Logs

Steps to Reproduce

Edit failure: (1) Have an existing local scheduled task that fires from D:\OneDrive\Scheduled\<task>\SKILL.md. (2) In a Cowork session, ask Claude to change that task's instructions. (3) The session reports success, but on the next run the live task is unchanged, because the edit landed in a different copy - the session cannot reach the reserved top-level "Scheduled" folder that the scheduler fires from. Create failure: (4) In a Cowork session, ask Claude to create a new scheduled task that reads a local file. (5) Only a cloud task is created (which cannot see local files), and there is no option to make it run locally on this machine. Environment: Windows 11 Pro, Claude Desktop / Cowork 1.34493.1.0, coworkUserFilesPath = D:\OneDrive, ~54 local scheduled tasks.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

1.34493.1.0 (Claude Desktop / Cowork, Windows 11 Pro)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_

View original on GitHub ↗