openai / openai/codex

Windows-to-mobile chat synchronization is unacceptable and makes the desktop app unusable

Open
#40,265 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app enhancement session windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

I am uninstalling the Windows ChatGPT/Codex desktop app because a chat started there does not automatically appear in the ChatGPT mobile app.

Users should not have to discover and configure Remote, pair devices with a QR code, keep the PC online, and search through a separate Remote task list merely to continue the same conversation on their phone.

Actual behavior:

  • Start a projectless chat in the Windows desktop app.
  • Open the ChatGPT mobile app using the same account and workspace.
  • The chat is absent from the normal chat history.
  • The suggested workaround is to configure Remote and use a separate interface.

Expected behavior:

  • Conversations should synchronize automatically across devices signed into the same account.
  • If a local task cannot be synchronized, the desktop app must clearly warn the user before the first message.
  • The app should provide a simple one-click option to make the conversation available on other devices.

This caused lost continuity, wasted time, and the impression that the conversation had disappeared. Remote is not an acceptable replacement for ordinary cross-device chat synchronization.

Please treat this as a core product and UX problem, not merely a documentation issue.

Nota bene: This should not be dismissed as a mere “enhancement.” A user should not need to know whether a conversation is “local” or “cloud,” nor should they be chained to the computer on which it began. They should be able to close the computer, pick up their phone, and continue from the very next message.

If the product cannot provide that basic continuity, then its internal architecture has been made the user’s problem. That burden belongs to the product—not to the customer.

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

No files, tests, or entry points are named. Start by tracing how a projectless Windows chat is stored and whether it enters the normal cross-device history, then compare that path with the Remote task flow. Done means a same-account conversation appears in mobile history automatically, or the desktop app clearly warns and offers a simple sharing option when synchronization is unavailable.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
backend-api-design, desktop, mobile-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.