Add silent mode for recurring automation completion badges
Problem
Recurring automations that run frequently (for example every 5 minutes) create an unread/completion badge next to the thread name after each run. This produces a persistent notification indicator even when the automation is informational and requires no user attention.
Requested behavior
Add an option for recurring automations or thread heartbeats to run silently, without creating an unread/completion badge. Possible designs:
- A per-automation
silentorsuppressUnreadBadgesetting. - A read-only/background mode that does not mark the parent thread unread on successful completion.
- Separate “needs attention” notifications from routine successful completion state.
Use case
A thread-naming officer heartbeat runs every 5 minutes across projects. Each successful run updates the thread and then leaves a new completion badge. The automation is working as intended, but the badge becomes notification noise.
Expected result
The automation continues to run and can still surface failures or requests for input, while successful routine runs do not create an unread/completion badge.
Related issues
- #20418 — archived automation runs stay unread/red (related read-state behavior)
- #3962 — completion notifications (related notification behavior)
- #25393 — Automations sidebar count badge behavior (opposite symptom)
Environment
Codex desktop app, recurring thread heartbeat/automation.