openai / openai/codex

Desktop app does not sync latest conversation turns after continuing the same chat on mobile

Open
#43,749 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug Linux 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 “About Codex” dialog)?

Version 26.901.31953

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Linux 7.1.12-200.fc44.x86_64 x86_64 Fedore

What issue are you seeing?

When I continue an existing conversation on the ChatGPT mobile app, the desktop app frequently remains stuck on an older version of the same conversation.
A typical case is:
I have a conversation open/use it on the desktop app, then continue the same conversation from my mobile device and add several additional user/assistant turns. When I later return to the desktop app, those newer mobile turns are not present.
The desktop conversation remains at the state it was in before I continued it on mobile. Switching to another conversation and reopening the affected conversation does not reliably fetch the latest state, and there appears to be no manual "Refresh", "Sync", or "Reload conversation from server" action available.
I have experienced this repeatedly across multiple conversations, so it does not appear to be a one-time synchronization failure.
The mobile

What steps can reproduce the bug?

Feedback ID: no-active-thread-01a07ffd-8001-7ff3-bd5a-e5bd6143ed15

What is the expected behavior?

When a conversation has been updated from another device, the desktop app should automatically retrieve and reconcile the latest conversation state.
At minimum, this should happen when:

  • the desktop app regains focus,
  • the conversation is reopened,
  • the user switches away from the conversation and comes back.
    If automatic synchronization cannot be completed, the app should expose a clear Refresh / Sync conversation action.
    The user should never unknowingly continue writing from a stale local version of a conversation when newer turns already exist on another device.
Additional information

This is particularly problematic because there is currently no clear indication that the desktop conversation is stale.
From the user's perspective, both devices are signed into the same account and are displaying the same conversation, so there is no reason to expect one device to contain an outdated snapshot.
The issue also creates a risk that the user continues the conversation from the stale desktop state, potentially creating conflicting conversation branches or losing continuity.
A simple fallback such as "Reload latest conversation" would make the problem substantially less disruptive even if real-time cross-device synchronization cannot always be guaranteed.
This has happened to me many times during normal desktop ↔ mobile usage.

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

Start by reproducing the stale conversation state across the desktop app and ChatGPT mobile app using the reported feedback scenario. Trace what happens when the desktop app regains focus, reopens the conversation, or switches away and back; done means the latest mobile turns are retrieved or a clear refresh action is available.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.