[P2][Windows][26.901.6511.0] Activity View hides heartbeat-attached chats with new ordinary messages

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

26.901.6511.0 — verified from the installed OpenAI.Codex AppX package, not the About dialog.
Bundled/running local app-server executable reports codex-cli 0.153.4.

What subscription do you have?

ChatGPT Pro.

What platform is your computer?

Windows 11 Pro, version 25H2, build 26200.9168, x64.

Requested PowerShell platform output:

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

P2 — Chats with a scheduled automation attached are absent from Activity View even when they receive new messages from ordinary, user-initiated work unrelated to that automation.

I use Activity View to find chats with new messages. When an affected chat has an automation attached, it does not appear there. I have to turn Activity View off, scroll through the normal task list, and find the chat manually.

The automation type present in this installation is a heartbeat attached to an existing task. This report concerns visibility of ordinary conversation activity in those tasks; a newly scheduled automation run is not necessary to describe the reported symptom.

What steps can reproduce the bug?

Steps based on my observed workflow:

1. Use an existing Codex Desktop chat with an active scheduled heartbeat attached.
2. Send an ordinary work request in that same chat, unrelated to the scheduled automation.
3. Switch to another chat and allow a new response to arrive in the automation-attached chat.
4. Enable Activity View and look for the chat with the new message.
5. Observe that the chat is absent.
6. Disable Activity View and locate the chat in the normal task list; it remains accessible with its new messages.

Frequency has not been measured with a controlled test matrix.

What is the expected behavior?

A chat receiving new ordinary messages should be discoverable in Activity View under the same activity/unread rules as other chats. Attaching a heartbeat should not suppress the chat's unrelated interactive activity.

Additional information

• Observed/reported on September 9, 2026.
• Read-only local diagnostics confirmed active automations with kind = "heartbeat" and target_thread_id pointing to existing local tasks.
• The regular task-list API still returned recently updated tasks targeted by active heartbeats.
• These diagnostics confirm the automation configuration and continued existence of the tasks. They do not independently prove their absence from the rendered Activity View; that symptom and the workaround are the user's direct observations. No controlled UI reproduction was performed during report preparation.
• Workaround: turn Activity View off and find the chat in the normal task list.
• Related/likely duplicate: https://github.com/openai/codex/issues/39156. That issue began as a Linux report and now includes macOS and Windows confirmations. This report records the same user-visible symptom on Windows AppX version 26.901.6511.0, specifically for new ordinary messages unrelated to the automation.
• No private chat contents, task titles, local paths, thread identifiers, automation prompts, credentials, or raw logs are included.

No source files, tests, or entry points are named. Compare the symptom with related issue #39156 and reproduce it with a heartbeat-attached chat receiving an ordinary message; done means the chat appears in Activity View under the same activity and unread rules as other chats.