Activity view: snooze chats from Priority

Open 💬 2 comments Opened Aug 5, 2026 by kendonB

What variant of Codex are you using?

App

What feature would you like to see?

Add a Snooze action to chats in the Activity view’s Priority section.

Snoozing should remove the chat from Priority until a selected time. When the snooze expires, it should return if it still requires attention.

This would let users defer chats they cannot act on yet without archiving or resolving them.

This differs from #22837, which requests general chat reminders. This request is specifically for managing the Priority queue.

View original on GitHub ↗

2 Comments

lifan-builds · 16 days ago

A key use case for this is blocked work: a task may still need attention, but the user cannot act until later. Please let the user choose the snooze duration or an exact date/time, then provide a clear reminder or system notification when the snooze expires, rather than only silently reordering the Activity view. This would help prevent blocked tasks from being forgotten. Related general reminder request: #22837.

lifan-builds · 16 days ago

One concrete workflow behind this request: I often have an Activity/Priority chat that still matters but is temporarily outside my control—a feature waiting for deployment, or a pushed commit waiting for reviewer comments. There is nothing useful to do in the chat right now, but archiving it makes it too easy to forget.

For me, the smallest useful Snooze behavior would be:

From a Priority row, choose Snooze… and pick In 1 hour, Tomorrow, Next week, or Pick date & time…. Relative choices should show the resolved wake time.
The chat moves to a collapsed Snoozed section, where its wake time is visible. Change snooze… and Unsnooze should always be available.
The rule is: return at the chosen time, or sooner if new activity arrives. New activity should end the snooze and return the chat to Priority using the normal new-activity indication; it should not be muted.
At the scheduled time, return the chat to Priority and show Snooze ended in-app. If Codex is backgrounded or closed, send a system notification instead.
Snoozes should survive an app restart. Completing, resolving, or archiving the chat should cancel its wake-up rather than resurrecting finished work.

This is about managing the live Priority queue, not adding a general task/calendar system. The attached sketch shows the entry point and the Snoozed row actions.

Would maintainers prefer Activity Snooze to share the reminder primitive discussed in #22837, if one is built, or remain an Activity-specific state?