claude-code - 💡(How to fix) Fix [BUG] Cowork scheduled tasks ignore "Always allow" folder/tool permissions — prompts reappear every run (macOS) [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#47180Fetched 2026-04-13 05:39:20
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
labeled ×4commented ×1

Error Message

Error Messages/Logs

No specific error message — the issue is behavioral. Each scheduled task run displays permission prompts such as:

Code Example

{
  "permissions": {
    "allow": [
      "WebSearch(*)",
      "WebFetch(*)",
      "Read",
      "Write",
      "Edit",
      "Glob",
      "Grep",
      "Bash(curl:*)",
      "Bash(ls:*)",
      "Bash(cat:*)",
      "Bash(mkdir:*)",
      "mcp__slack__*",
      "mcp__gmail__*"
    ]
  }
}

---

No specific error message — the issue is behavioral. Each scheduled task run displays permission prompts such as:

"Allow Claude to access [folder path]?"
"Allow Claude to use [tool name]?"

These prompts appear on every run despite previously selecting "Always allow." The task stalls until the user manually clicks "Allow," defeating the purpose of scheduled automation.
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?

Cowork scheduled tasks repeatedly prompt for folder/tool permissions on every run, even after selecting "Always allow." The permission does not persist between scheduled task sessions.

Context: I have 6 scheduled tasks in Cowork (price checkers on Amazon.sa, a market crash scanner, and a Gmail action items task). All tasks post results to Slack via the Slack MCP connector. Every time a scheduled task runs, it re-prompts for folder access and tool permissions, even though I have previously selected "Always allow."

What I tried (none of these resolved the issue):

  1. Clicking "Always allow" on every permission prompt during manual "Run now" — permissions do not persist to the next scheduled run.
  2. Creating ~/.claude/settings.json with explicit allow rules:
{
  "permissions": {
    "allow": [
      "WebSearch(*)",
      "WebFetch(*)",
      "Read",
      "Write",
      "Edit",
      "Glob",
      "Grep",
      "Bash(curl:*)",
      "Bash(ls:*)",
      "Bash(cat:*)",
      "Bash(mkdir:*)",
      "mcp__slack__*",
      "mcp__gmail__*"
    ]
  }
}
  1. Restarting Claude Desktop after applying settings — still prompts on every scheduled run.

Related closed issue: #40470 was filed for the same problem and is now closed, but the issue persists on macOS. Issue #30356 (Chrome browser permissions) and #33027 ("Always allow" missing from scheduled task prompts) also describe the same underlying problem.

Environment:

  • macOS (Mac Mini)
  • Claude Desktop (latest version as of April 2026)
  • Claude Cowork with scheduled tasks
  • Connected MCPs: Slack, Gmail
  • Plan: Paid plan (Pro/Max)

What Should Happen?

Scheduled tasks should respect the user's "Always allow" permission selections and ~/.claude/settings.json allow rules. Once a user grants "Always allow" for a tool or folder, subsequent scheduled runs should execute without re-prompting.

The scheduled task runner should inherit the account's permission settings (including defaultMode and allow rules), enabling unattended automation — which is the entire purpose of scheduled tasks.

Error Messages/Logs

No specific error message — the issue is behavioral. Each scheduled task run displays permission prompts such as:

"Allow Claude to access [folder path]?"
"Allow Claude to use [tool name]?"

These prompts appear on every run despite previously selecting "Always allow." The task stalls until the user manually clicks "Allow," defeating the purpose of scheduled automation.

Steps to Reproduce

  1. Create a scheduled task in Cowork (e.g., a daily price checker that uses WebSearch, WebFetch, and posts to Slack via the Slack MCP connector).
  2. Run the task manually using "Run now."
  3. When permission prompts appear, select "Always allow" for each one.
  4. Wait for the next scheduled run (or click "Run now" again).
  5. Observe that the same permission prompts reappear, despite having selected "Always allow" previously.

Additional attempt: 6. Create ~/.claude/settings.json with explicit allow rules (WebSearch, WebFetch, Read, Write, mcp__slack__, mcp__gmail__, etc.). 7. Restart Claude Desktop. 8. Run the scheduled task again — permission prompts still appear.

Claude Model

None

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

Related issues (all describe the same underlying problem):

  • #40470 — Scheduled tasks prompt for permissions despite bypassPermissions defaultMode set in settings.json (now closed, but issue persists)
  • #30356 — Chrome extension permission dialog reappears on every scheduled task run
  • #33027 — "Always allow" option missing from scheduled task permission prompts
  • #24433 — "Always allow" for MCP tools does not persist across Cowork sessions
  • #30953 — Claude Code Desktop should honor managed-settings.json for all permissions

Scheduled tasks affected (all exhibit this behavior):

  • 4x Amazon.sa price checkers (Kindle Colorsoft, Kindle Paperwhite Signature, EPSON L3252, Logitech MX Master 4) — use WebSearch/WebFetch + Slack MCP
  • 1x Market Crash Scanner — uses WebSearch + Slack MCP
  • 1x Gmail Action Items — uses Gmail MCP + Slack MCP

Impact: Scheduled tasks are effectively unusable for unattended automation, which is their primary purpose. The user must be present to click "Allow" on every run.

extent analysis

TL;DR

The issue can be mitigated by exploring alternative permission persistence methods, such as modifying the settings.json file or utilizing a different approach to manage permissions for scheduled tasks.

Guidance

  • Review the settings.json file format and ensure that the allow rules are correctly defined for the tools and folders used by the scheduled tasks.
  • Investigate the possibility of using a different permission management approach, such as utilizing environment variables or command-line flags to pass permission settings to the scheduled tasks.
  • Verify that the bypassPermissions defaultMode is set correctly in the settings.json file, as mentioned in related issue #40470.
  • Consider testing the scheduled tasks with a minimal set of permissions to isolate the issue and identify the specific permissions that are not being persisted.

Example

No code example is provided, as the issue is related to permission persistence and requires further investigation into the settings.json file and the scheduled task configuration.

Notes

The issue appears to be related to a regression, as it worked in a previous version. The fact that related issues #40470, #30356, #33027, #24433, and #30953 describe the same underlying problem suggests that there may be a deeper issue with permission management in the Claude Code Desktop application.

Recommendation

Apply a workaround by modifying the settings.json file or utilizing a different approach to manage permissions for scheduled tasks, as the root cause of the issue is not immediately clear and may require further investigation.

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