Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] scheduled tasks need human intervention to run. [1 comments, 2 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#46312•Fetched 2026-04-11 06:23:36
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
StillClaudeStillClaude
Participants
github-actions[bot]github-actions[bot]StillClaudeStillClaude
Timeline (top)
labeled ×4commented ×1

Error Message

Error Messages/Logs

Root Cause

When I create a scheduled task, Claude tells me to run now so that the next runs can run autonomously in the future. However, each run opens its own session and forgets everything that I allowed in the previous session. So all my scheduled tasks that run overnight never get complete because they need me to be at the computer and allow access to things that I have previously allowed access to. Specifically, folder access that I already gave it access to. To make it weirder, it's asking me to allow access to a folder that it is already using to get context for the task. This makes the scheduled tasks pointless because the task won't complete unless I'm physically at the computer to allow the access to something that I had already allowed access to.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

When I create a scheduled task, Claude tells me to run now so that the next runs can run autonomously in the future. However, each run opens its own session and forgets everything that I allowed in the previous session. So all my scheduled tasks that run overnight never get complete because they need me to be at the computer and allow access to things that I have previously allowed access to. Specifically, folder access that I already gave it access to. To make it weirder, it's asking me to allow access to a folder that it is already using to get context for the task. This makes the scheduled tasks pointless because the task won't complete unless I'm physically at the computer to allow the access to something that I had already allowed access to.

What Should Happen?

Claude should allow you to give permanent access at a task level, not a session level. That way, the task itself can remember what it has access to and what it's allowed to access, so that it can run flawlessly and not have to continuously ask for access when it has already been granted the access in previous sessions. Also, as soon as you give it a working folder, it should always be allowed to read and write and upload to that folder and never need permission to do it again. That is the point of the working folder, to give Claude its own place that it can always use, always read, and always write, and never need approval to access.

Error Messages/Logs

Steps to Reproduce

create and scheduled task that requires it to use or create files in a folder, then run the task and grant it permission to whatever it needs, then go to sleep and see if the task will run without being stuck on a permission request.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

Claude 1.1617.0 (8d6345) 2026-04-09T16:10:15.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The most likely fix is to modify Claude's access control to allow permanent access at a task level, rather than a session level, to enable scheduled tasks to run autonomously without requiring repeated permission grants.

Guidance

  • Review the access control mechanism in Claude to identify why permissions are not being persisted across sessions, and consider implementing a task-level access control system.
  • Investigate the possibility of using a working folder that is always accessible to Claude, without requiring repeated permission requests.
  • Test the scheduled task with a simplified setup to isolate the issue and verify if the problem is specific to certain types of tasks or folders.
  • Consider reaching out to the development team or checking the documentation to see if there are any existing solutions or workarounds for this issue.

Notes

The issue seems to be related to the access control mechanism in Claude, and modifying this mechanism to allow permanent access at a task level may resolve the issue. However, without more information about the internal workings of Claude, it is difficult to provide a more specific solution.

Recommendation

Apply workaround: Modify the access control mechanism to allow permanent access at a task level, as this is the most likely solution to enable scheduled tasks to run autonomously without requiring repeated permission grants.

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…
#api#vector store#embedding generation#cache error#pipeline error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING