claude-code - 💡(How to fix) Fix [Feature Request] Add configurable storage path for scheduled-tasks SKILL.md files [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52430Fetched 2026-04-24 06:07:28
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Participants
Timeline (top)
labeled ×4

Fix Action

Fix / Workaround

Bug Description Cowork's scheduled-tasks feature stores SKILL.md files at a fixed path under the user's OneDrive folder (mine: C:\Users\Paddo\OneDrive\onedrive-OneNote Documents\Claude\Scheduled) with no config option to relocate it.

Two pain points:

  1. The path sits outside any of my project trees, so project-wide reference-integrity sweeps and governance audits can't see it. Stale pointers in scheduled-task SKILL.md files survive cleanup passes that catch the same drift everywhere else. I hit this concretely on 2026-04-23 — a quarterly scheduled task carried stale folder-path pointers that would have fired against nonexistent paths if I hadn't caught it manually.
  2. The folder name "onedrive-OneNote Documents" is hostile to CLI tools and ritual scripts.

Local workaround that works for me but not for anyone else: a directory junction at C:\Users\Paddo.claude\Scheduled\ pointing at the OneDrive path, plus discipline to use the scheduled-tasks MCP rather than reading SKILL.md files directly.

Ask: a config option to point Cowork's scheduled-tasks storage at a user-chosen folder. Even better, default to ${HOME}/.claude/Scheduled/ so it lives next to the rest of the Claude config tree. Existing installs keep their current path for back-compat.

Code Example

[]
RAW_BUFFERClick to expand / collapse

Bug Description Cowork's scheduled-tasks feature stores SKILL.md files at a fixed path under the user's OneDrive folder (mine: C:\Users\Paddo\OneDrive\onedrive-OneNote Documents\Claude\Scheduled) with no config option to relocate it.

Two pain points:

  1. The path sits outside any of my project trees, so project-wide reference-integrity sweeps and governance audits can't see it. Stale pointers in scheduled-task SKILL.md files survive cleanup passes that catch the same drift everywhere else. I hit this concretely on 2026-04-23 — a quarterly scheduled task carried stale folder-path pointers that would have fired against nonexistent paths if I hadn't caught it manually.
  2. The folder name "onedrive-OneNote Documents" is hostile to CLI tools and ritual scripts.

Local workaround that works for me but not for anyone else: a directory junction at C:\Users\Paddo.claude\Scheduled\ pointing at the OneDrive path, plus discipline to use the scheduled-tasks MCP rather than reading SKILL.md files directly.

Ask: a config option to point Cowork's scheduled-tasks storage at a user-chosen folder. Even better, default to ${HOME}/.claude/Scheduled/ so it lives next to the rest of the Claude config tree. Existing installs keep their current path for back-compat.

Environment Info

  • Platform: win32
  • Terminal: null
  • Version: 2.1.118
  • Feedback ID: 6ba3b3a9-c3c4-4a59-847e-c6f5a8c194fb

Errors

[]

extent analysis

TL;DR

To resolve the issue, consider adding a configuration option to allow users to specify a custom storage path for scheduled-tasks, defaulting to ${HOME}/.claude/Scheduled/ for new installations.

Guidance

  • Investigate the feasibility of introducing a configurable storage path for scheduled-tasks, ensuring backward compatibility for existing installations.
  • Evaluate the potential impact of changing the default storage path on the overall system and user experience.
  • Consider implementing a directory junction or symlink as a temporary workaround, similar to the local workaround described, to redirect the scheduled-tasks storage to a more convenient location.
  • Review the project's reference-integrity sweeps and governance audits to ensure they can accommodate the new storage path.

Example

No code snippet is provided as the issue does not contain sufficient technical details to generate a specific example.

Notes

The proposed solution assumes that introducing a configurable storage path is technically feasible and does not introduce significant complexity or security risks. Further analysis and testing are necessary to confirm the viability of this approach.

Recommendation

Apply a workaround, such as implementing a directory junction or symlink, until a configuration option for custom storage paths is available, as it provides a temporary solution to mitigate the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING