Codex Desktop regression: local scheduled task now requires filesystem approval on every run

What version of the Codex App are you using (From “About Codex” dialog)?

26.901.51231

What subscription do you have?

Plus

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What issue are you seeing?

I have a local Codex Desktop scheduled task that generates an HTML file in its trusted workspace and sends it through the Outlook connector as an attachment.

The task ran unattended successfully through September 3, 2026. Starting September 4, the same unchanged task began launching with a managed read-only filesystem profile. It now pauses every day for permission to write the HTML attachment.

Verified details:

Windows 11

Codex Desktop build: 26.901.51231

Automation ID: daily-outlook-brief-html

Automation type: heartbeat

Workspace is marked trusted

Windows sandbox is configured as elevated

Outlook send-email action is approved

Automation prompt and configuration have not changed

September 1–3 runs received workspace-write access

September 4 onward runs received read-only access

Each approval grants write access for that run only (scope: turn)

There is no permissions or execution-environment control in the automation editor that I can find. Please confirm whether this change is intentional, identify any supported persistent permission setting, or restore workspace-write access for trusted local scheduled tasks.

What steps can reproduce the bug?

Feedback ID: no-active-thread-01a08844-f98a-74f3-a308-f233b7433915

What is the expected behavior?

Expected: A local scheduled task should retain write access to its trusted workspace, or provide a persistent per-task permission setting.
Actual: Every execution requires an interactive, one-run filesystem approval, preventing unattended operation.

Additional information

No response

No source file, test, or code entry point is named. Start with the Codex Desktop scheduled-task execution and filesystem permission flow, using feedback ID no-active-thread-01a08844-f98a-74f3-a308-f233b7433915 and the September 3–4 behavior change as the reproduction context. Done means trusted local tasks retain workspace-write access or expose a supported persistent per-task permission setting without prompting on every run.