Add a command to jump to the latest unread thread in Codex App

Open 💬 1 comment Opened May 15, 2026 by patrick-fu

What variant of Codex are you using?

App

What feature would you like to see?

When running multiple Codex App threads in parallel, I rely on unread / waiting-for-user indicators to know which thread needs attention next. Today, I can switch between recent threads with existing navigation shortcuts, but I do not see a command that jumps directly to the latest unread thread.

Please add a command such as Open latest unread thread or Jump to latest unread thread, available from the command palette / Keyboard Shortcuts. It should be possible to bind this command to a shortcut.

Problem:

  • Multiple Codex threads can finish or ask for input while I am working in another thread.
  • The unread / waiting-for-user indicator is useful, but locating the newest unread thread still requires scanning the sidebar manually.
  • Recent-thread navigation is not enough because the thread that needs attention next may not be the most recently viewed thread.

Proposed behavior:

  • A command opens the latest unread / waiting-for-user thread in the current Codex App window.
  • If no unread thread exists, the command should do nothing or show a lightweight "No unread threads" message.
  • The command should be bindable in Keyboard Shortcuts.

Why this matters:

This makes parallel Codex workflows easier to manage. When several agents are running at once, the user needs a fast way to jump to the next thread requiring attention without visually scanning the sidebar.

Related but distinct issues:

  • #14597 requests a recent-thread quick switcher.
  • #10459, #13115, and #14452 discuss unread-state behavior.
  • This request is specifically for navigation to the latest unread / waiting-for-user thread.

Additional information

Codex App version: 26.513.20950 (2816)

Platform:

Darwin 25.4.0 arm64 arm

I checked the current Keyboard Shortcuts list and did not see an existing command for jumping to the latest unread thread.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗