Codex Desktop Scheduled inbox renders one run as two user-like messages

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

Codex desktop 26.825.51511 (build 7377).

What subscription do you have?

ChatGPT Pro.

What platform is your computer?

Darwin 25.6.0 arm64 arm

The affected run was observed on macOS 26.6.2 (build 25G83).

What issue are you seeing?

Opening one completed standalone Scheduled run can render the declarative inbox summary as a separate user-like message above the larger automation-trigger card.

Exact native task readback for the affected item showed one persisted scheduled execution. This report therefore concerns duplicate-looking presentation of a single run, not duplicate automation execution.

The issue was observed once on August 31, 2026. Recurrence and the renderer implementation are not proved.

In-product Feedback ID:

no-active-thread-01a05c16-ef66-75f2-b1f7-dd39f62add65

No logs, diagnostics, screenshots, or attachments were included with the feedback or this issue.

What steps can reproduce the bug?

1. Allow a standalone local Scheduled task to complete normally.
2. Open Scheduled in Codex Desktop.
3. Select the completed run.
4. Observe that the declarative inbox summary appears as a separate user-like bubble above the automation-trigger card.
5. Compare the presentation with exact task readback, which shows one persisted scheduled execution rather than two runs.

The behavior has been observed once. A second natural-run reproduction is not yet available.

What is the expected behavior?

One scheduled execution should render as one coherent scheduled input. If the inbox summary is metadata, it should be visually grouped with the automation trigger or otherwise styled so that one run cannot appear to contain two user messages.

Additional information

The Scheduled documentation describes the Scheduled view as an inbox and states that standalone scheduled tasks start a new chat for each run. The current presentation makes the inbox summary look like an additional user request, which complicates run auditing even though only one execution persisted.

A prompt-level presentation mitigation was applied to the affected automation, but that does not establish an upstream renderer fix.

Start at the Codex Desktop Scheduled view and compare the completed run’s persisted task readback with its rendered inbox presentation. Confirm whether the declarative inbox summary and automation-trigger card come from one execution, then identify the relevant renderer tests or entry point. Done means one scheduled execution appears as one coherent scheduled input without implying a second user message.