Answer: Each scheduled task has its own permission mode, which you set when creating or editing the task, and allow rules from `~/.claude/settings.json` also apply to scheduled task sessions. Status: Confirmed Entry: tool/claude-code/permissions-and-security/scheduled-task-permissions Revision: 3 Digest: sha256:ab2a960271f13af7 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:04:02Z Last changed: 2026-11-19T12:15:55Z (MCP tools requiring interaction: — → requiresUserInteraction) Last verified: 2026-11-20T12:20:19Z Next check: 2026-11-21T12:20:19Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of permission mode | permission mode | [1] | 2026-11-20 settings allow rules | ~/.claude/settings.json | [1] | 2026-11-20 MCP tools requiring interaction | requiresUserInteraction | [1] | 2026-11-20 Sources: [1] Anthropic. "Schedule recurring tasks in Claude Code Desktop". https://code.claude.com/docs/en/desktop-scheduled-tasks.md Role: primary. Accessed: 2026-11-20T12:20:19Z Quote: "Each task has its own [permission mode](https://code.claude.com/docs/en/desktop.md#choose-a-permission-mode), which you set when creating or editing the task." (Supports: permission mode) Quote: "Allow rules from `~/.claude/settings.json` also apply to scheduled task sessions." (Supports: settings allow rules) Quote: "MCP tools marked [`requiresUserInteraction`](https://code.claude.com/docs/en/mcp#require-approval-for-a-specific-tool) prompt on every call and don't offer an always-allow option." (Supports: MCP tools requiring interaction) Published: 2026-11-20T03:06:00Z Snapshot SHA-256: 10648ce06fa1ea4d2bd190a7c1d19e7686b17f28ba8c513233287d5a61ec155d (captured 2026-11-18T12:15:49Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-18T12:15:50Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:20:19Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:20:19Z Last attempt: 2026-11-20T12:20:19Z Notes and limitations: Extracted automatically from a single official source (section "Permissions for scheduled tasks"). Related: https://latestn.com/tool/claude-code/permissions-and-security/security-best-practices-sensitive-code What security best practices should I follow when using Claude Code with sensitive code? https://latestn.com/tool/claude-code/permissions-and-security/security-plugin-file-edit-checks What does the Claude Code security-guidance plugin check on each file edit? https://latestn.com/tool/claude-code/permissions-and-security/set-permission-mode How do I set the permission mode in Claude Code? https://latestn.com/tool/claude-code/permissions-and-security/review-plugin-before-install How do I review a Claude Code plugin before installing it? https://latestn.com/tool/claude-code/permissions-and-security/run-without-permission-prompts How do I run Claude Code in a dev container without permission prompts? https://latestn.com/tool/claude-code/permissions-and-security/sandbox-modes What are the sandbox modes in Claude Code, including auto-allow mode and strict sandbox mode? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T12:15:55Z | changed | MCP tools requiring interaction: — → requiresUserInteraction | [1] 2026-11-19T12:15:55Z | changed | MCP interaction requirement: requiresUserInteraction → — | [1] 2026-11-15T12:20:11Z | changed | MCP interaction requirement: — → requiresUserInteraction | [1] 2026-11-15T12:20:11Z | changed | permission mode: — → permission mode | [1] 2026-11-15T12:20:11Z | changed | MCP requiresUserInteraction: prompt on every call and don't offer an always-allow option → — | [1] 2026-11-15T12:20:11Z | changed | stalled run handling: find the run's session → — | [1] 2026-11-15T12:20:11Z | changed | settings allow rules: Allow rules from `~/.claude/settings.json` also apply to scheduled task sessions. → ~/.claude/settings.json | [1] 2026-11-13T03:04:02Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/permissions-and-security/scheduled-task-permissions/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-code/permissions-and-security/scheduled-task-permissions POST: https://latestn.com/dispute/tool/claude-code/permissions-and-security/scheduled-task-permissions with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/permissions-and-security/scheduled-task-permissions?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What permissions do scheduled tasks have in Claude Code Desktop? Revision 3, last verified 2026-11-20T12:20:19Z. https://latestn.com/tool/claude-code/permissions-and-security/scheduled-task-permissions (accessed 2026-11-21T10:02:06Z). @misc{LatestN_tool_claude_code_permissions_and_security_scheduled_task_permissions_r3, title = {What permissions do scheduled tasks have in Claude Code Desktop?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/permissions-and-security/scheduled-task-permissions}}, note = {Revision 3; digest sha256:ab2a960271f13af7; last verified 2026-11-20T12:20:19Z; accessed 2026-11-21T10:02:06Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-code/permissions-and-security/scheduled-task-permissions