openai / openai/codex

[macOS][ChatGPT Desktop][Cloud Projects] Web-created Chats stay out of last-active order and omit unread dots

Open
#40,731 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

app bug session
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of the Codex App are you using (from the About dialog / installed app)?

ChatGPT desktop app 26.820.60940 (build 7119)

What platform is your computer?

macOS 26.6.2 (25G83), Darwin 25.6.0 arm64

What issue are you seeing?

Ordinary Chat conversations created or continued on chatgpt.com inside a ChatGPT Cloud Project do not present correctly in the macOS desktop app's nested Project Chats list.

This report is specifically about Chat, not ChatGPT Work tasks, Scheduled Tasks, or Codex tasks.

On the same account and same Cloud Project:

  • chatgpt.com orders the Chats by current/latest activity;
  • chatgpt.com shows the small unread indicator for a Chat with a new unread response;
  • the desktop app leaves the same Chat in a stale position instead of moving it according to latest activity; and
  • the desktop app does not show the unread-dot indicator on that Chat.

The conversations remain accessible. The problem appears limited to desktop ordering and unread-state presentation.

What steps can reproduce the bug?
  1. Open chatgpt.com and enter an existing ChatGPT Cloud Project.
  2. Create or continue an ordinary Chat inside that Project.
  3. Let the Chat become the most recently active item, or let it receive a response while it is not open.
  4. In the web Project Chats list, confirm that the Chat moves according to current activity and shows as unread when applicable.
  5. Open the same Cloud Project in the macOS ChatGPT desktop app.
  6. Compare the same Project's Chat ordering and unread indicator.
  7. Observe that the desktop Project list can retain the older order and omit the unread dot.
What is the expected behavior?

For the same Cloud Project Chat, the desktop app should reflect current last-active ordering and unread state, consistent with the same-account web view.

Actual behavior

The desktop Project Chats list can remain out of last-active order and omit the small unread indicator even though the web view has the current order and unread state.

Additional information
  • A read-only desktop host inventory exposes current updatedAt values for the affected ordinary Chat records and distinguishes them from Codex tasks and Work tasks.
  • That inventory returns current chat metadata, while the nested Project list remains visibly stale. This supports a desktop presentation/state-subscription issue rather than conversation data loss.
  • The unread value is not exposed by that inventory, so the missing dot is a direct cross-surface UI observation.
  • Projectless Chat has not been tested and is NOT_PROVED.
  • No restart, account change, permission change, trace upload, or private attachment was used.

Official documentation says Chat and Work both appear as chats in a Project's Chats section, and that Activity view can include unread Chat items:

Related but not exact duplicates:

  • #35090 - stale normal-sidebar recency after pin/unpin for a Codex thread
  • #36300 - stale ordering inside Activity view
  • #37266 - stale project thread ordering on Windows
  • #36699 - stale Codex conversation order repaired by toggling Activity

This report differs because it concerns web-created ordinary ChatGPT Cloud Project Chats on macOS desktop, requires no pin/unpin trigger, and includes both stale last-active ordering and a missing unread-dot indicator.

Feedback submitted via /feedback:

  • Feedback ID: 01a03b23-9107-73f3-9619-d50052f15de4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The payload names no repository files, tests, or entry points; begin by locating the macOS desktop Project Chats list and its ordering and unread-state data flow. Reproduce with a web-created ordinary Chat in a Cloud Project, compare desktop with web, and consider the work done when ordering and unread dots match.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, rust
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.