Feature request: Support pinning and custom sorting for Codex threads in the project sidebar

Open 💬 0 comments Opened Jun 6, 2026 by su6

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

26.602

What subscription do you have?

ChatGPT Plus

What platform is your computer?

macOS 14.4, arm64, Apple Silicon

What issue are you seeing?

I often create many Codex threads under the same project. The Codex App currently supports pinning threads, which is helpful, but pinned threads and regular threads still cannot be manually reordered.

When there are many threads under one project, I may have several important pinned threads at the same time. However, I cannot drag and reorder them based on my own priority. This makes it difficult to keep the most important or currently active thread in the exact position I want.

This is not a crash or blocking bug, but a usability issue for long-running development work with many threads.

What steps can reproduce the bug?

  1. Open Codex App.
  2. Open a project that has many existing threads.
  3. Pin several important threads under the same project.
  4. Observe the project sidebar.
  5. Try to manually drag and reorder the pinned threads or regular threads.

Current result:
Threads can be pinned, but there is no way to manually drag and reorder threads within the same project. When multiple threads are important, their order cannot be customized based on user priority.

What is the expected behavior?

I would like the Codex App sidebar to support manual ordering for threads under the same project.

Expected behavior:

  1. Allow users to drag and reorder pinned threads.
  2. Allow users to drag and reorder regular threads within the same project.
  3. Keep the custom order stable after restarting the app.
  4. Optionally support sorting by last updated time, created time, or task status.
  5. Optionally support grouping threads under the same project.

Since pinning already exists, manual ordering would make pinned threads more useful when multiple important threads are active at the same time.

Additional information

_No response_

View original on GitHub ↗