[macOS][Scheduled Tasks] Automatic runs steal foreground focus and render the scheduler payload twice

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

26.825.51511 (build 7377)

What subscription do you have?

Not disclosed; not relevant to this client-side reproduction.

What platform is your computer?

Darwin 25.6.0 arm64 arm

What issue are you seeing?

When a standalone Scheduled Task fires automatically while another Codex task is foregrounded, Codex Desktop automatically switches to and resumes the newly created scheduled task.

The single scheduler payload is then displayed twice in the live task:

1. once as the Scheduled trigger card; and
2. once as a projected user message.

This was an automatic scheduler fire, not a foreground Run now execution.

Bounded session inspection showed:

• exactly one host scheduler payload;
• one projected user message containing that payload;
• zero model-issued automation-control calls; and
• zero model Goal calls.

The foreground switch interrupts active work, and the duplicate rendering can make a saved task prompt occupy a large portion of the live UI.

What steps can reproduce the bug?

1. Configure an active standalone Scheduled Task in Codex Desktop.
2. Keep a different Codex task open in the foreground.
3. Allow the schedule to fire automatically.
4. Observe Codex Desktop switch to and resume the newly created scheduled task.
5. Observe the same scheduler payload rendered once as the trigger card and again as a user message.

No session or task identifier is included in this public report.

What is the expected behavior?

An automatic Scheduled Task run should remain in the background unless the user opens it, and its scheduler payload should be rendered once.

Additional information

In-product feedback was submitted first through Codex’s /feedback flow. The app confirmed: Feedback recorded (no logs). The correlation identifier is intentionally withheld from this public issue.

Possibly related but not duplicates:

• #35950 and #36414 describe scheduled tasks that stall until manually opened; this report concerns an automatic foreground switch.
• #33503 describes a Run now tool-manifest difference; this report concerns an automatic scheduler fire and duplicate rendering.

Attachments, screenshots, raw logs, diagnostics, local paths, task IDs, private content, and account identifiers: none.

No source files, tests, or code entry points are named. First reproduce an automatic Scheduled Task fire while another task is foregrounded, then trace the run lifecycle and live-task rendering; done means the run stays in the background unless opened and the scheduler payload appears only once.