Scheduled task starts in default (manual-approval) permission mode instead of the configured bypassPermissions

What happened

I run Claude Code in bypassPermissions mode by choice. When a task created via the scheduled-tasks MCP server fires, the resulting session appears to start in the default permission mode rather than bypassPermissions.

Partway through the same run, a system notice stating that bypass permissions mode was active did appear — so the mode seems to be applied late, or the scheduled-task session does not inherit the configured mode at startup.

Why it matters

Scheduled tasks are non-interactive by definition — no one is present to approve a prompt. A task that starts in manual-approval mode can block on the first gated tool call and produce no output, which is indistinguishable from a task that is simply still running. The failure is silent.

Expected behaviour

A scheduled-task session should start in the same permission mode the user has configured, and that mode should be in force before the first tool call.

Steps to reproduce

1. Configure Claude Code to run in bypassPermissions mode.
2. Create a scheduled task (scheduled-tasks MCP, create_scheduled_task) whose prompt runs a shell command.
3. Let it fire.
4. Observe the permission mode at the start of the run.

Environment

• Claude Code 2.1.233
• Windows 11 (10.0.26200)
• Task created and fired via the scheduled-tasks MCP server

Notes

• I could not find a permission-mode setting for scheduled tasks in ~/.claude/settings.json or in a task's own directory, so this does not look like something that can be configured locally.
• Observed on one run; I have not yet confirmed the start-state from a log, so treat the "starts in default mode" part as an observation rather than a captured trace.