After Automations run, the app’s notification badge (red dot) cannot be cleared

Open 💬 2 comments Opened Mar 31, 2026 by lbininhbl
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

Version 26.325.31654 (1272)

What subscription do you have?

plus

What platform is your computer?

Darwin 25.0.0 arm64 arm

What issue are you seeing?

执行完Automations后,App 会有未读消息的红点。点击 app,以及查看相应的线程后,点击对应 automation 的历史生成对话后。都不会消除红点,只能重启 Codex App

<img width="49" height="43" alt="Image" src="https://github.com/user-attachments/assets/cdbdaaee-a672-490a-b269-c40c21de073e" />

What steps can reproduce the bug?

只要执行 Automations 就会

What is the expected behavior?

正确消息红点,我都查看对应消息了,就应该消除红点。

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 4 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #14656

Powered by Codex Action

cyjjjj-21 · 4 months ago

I can reproduce a closely related case on macOS.

Codex App version: 26.422.21459 (2049)
Platform: macOS 26.4.1, Darwin 25.4.0, arm64

In Automations -> run history, recent archived automation runs show a red dot. This looks like a failure/alert indicator, but the underlying run state is successful/archived.

Local state for the affected runs:

  • automation_runs.status = ARCHIVED
  • automation_runs.read_at = NULL
  • automation_runs.inbox_title / inbox_summary are populated with successful messages such as "summary ready"
  • There are no matching rows in inbox_items

Observed behavior:

  • The archived run shows a red dot in the run history.
  • Clicking the red dot / row does not open a popover or clear the unread state.
  • Since there is no corresponding inbox item, I cannot discover what to read or how to mark it read.
  • The red dot makes successful archived runs look like failures.

Expected behavior:

  • A successful archived run should not use a red alert indicator unless action is required.
  • If archived automation runs can be unread, the row should expose the result summary and mark read_at when opened.
  • If there is no navigable inbox item, the app should either avoid creating an unread state or provide a clear "mark as read" path.
  • Red should be reserved for failed/degraded/needs-attention automation runs.