Bug: Desktop and iOS show different chat state and “Recent” lists

ChatGPT Bugs
,
1

Environment

  • Surfaces: ChatGPT Web/Desktop and ChatGPT iOS app
  • Desktop OS: Windows 10
  • Desktop browser: Microsoft Edge / Chromium-based
  • Mobile device: iPhone XS Max
  • Exact browser / iOS / app versions at the time: not recorded
  • Affected feature: Cross-device synchronization / conversation state / Recent chat list

Bug

Chat state and conversation indexing can diverge between desktop and iOS.

Two related symptoms were observed.

Case A – New mobile input is not reflected on an already-open desktop chat

A conversation is open on both mobile and desktop.

New content is entered on mobile, including voice-based input.

The mobile conversation updates correctly, but the already-open desktop version can remain stale.

A reload or reopening of the conversation may be required before the desktop reflects the newer state.

This behavior is intermittent. Cross-device synchronization has also worked correctly on other occasions.

Case B – Active desktop chat missing completely from iPhone “Recent”

A conversation called “PRIVATE EINREICHUNG” was recently active and visible at the top of the desktop Recent list.

On the iPhone, the same conversation was completely absent from Recent.

The iPhone app was restarted twice, but the conversation still did not appear.

The conversation had not been deleted and remained available on desktop.

Sidebar Search was not tested during this incident, so it is not known whether the chat was missing only from Recent indexing or from mobile discovery more generally.

Expected behavior

Conversation state should converge automatically across devices.

If a chat is active and current on one device:

  • new messages should propagate to other open instances
  • the conversation should appear consistently in Recent
  • manual reloads, logout/login or app restarts should not be required

A stale local state should automatically reconcile with the authoritative server state.

Reproduction

Case A

  1. Open the same conversation on mobile and desktop.
  2. Leave the desktop conversation open.
  3. Add new content on mobile.
  4. Return to desktop.
  5. Observe that the desktop view may still show the older state.
  6. Reload or reopen the conversation.
  7. The newer state may then appear.

Case B

  1. Use a conversation actively on desktop.
  2. Confirm that it appears near the top of desktop Recent.
  3. Open ChatGPT on iPhone.
  4. Check the Recent conversation list.
  5. The active conversation may be absent.
  6. Restart the iOS app.
  7. The conversation may still remain missing from Recent.

Impact

This creates uncertainty about which device shows the authoritative conversation state.

It can lead to:

  • duplicated work
  • continued work from an outdated conversation state
  • unnecessary reloads or restarts
  • difficulty locating an active conversation on another device
  • uncertainty about whether content was actually synchronized or persisted

Diagnostics

The issue appears related to synchronization and conversation indexing rather than deletion.

Potential layers involved:

mobile state
→ server persistence
→ cross-device synchronization
→ desktop open-chat refresh
→ Recent/sidebar indexing

One positive counter-observation is important:

On 14 Sep 2026, phone-to-desktop synchronization worked cleanly.

The issue therefore appears intermittent rather than universal.

For future occurrences, useful diagnostics would include:

  • exact timestamp and timezone
  • app and browser versions
  • Wi-Fi / cellular state
  • whether the chat appears in Sidebar Search even when missing from Recent
  • whether direct opening succeeds before restarting the app

Acceptance criteria

  1. New messages synchronize automatically between open devices.
  2. An already-open desktop chat refreshes when newer server state exists.
  3. Recently active conversations appear consistently in Recent across devices.
  4. Missing Recent entries are automatically reconciled without app restart.
  5. The UI clearly distinguishes stale local state from current server-confirmed state.
3

Feature Request: Use ChatGPT as a direct cross-device file handoff

Feature Request

ChatGPT could become a much more useful cross-device workspace if files uploaded on one device could be handed off directly to another device through the same conversation.

Example workflow:

Smartphone
→ capture photo / upload file
→ ChatGPT conversation
→ open same chat on desktop
→ download original file
→ continue working locally

At the moment, this workflow is incomplete.

A file or image uploaded on mobile may be visible inside the conversation on desktop, but there is not always a clear and reliable way to retrieve the original file itself.

In one concrete case, a generated “download” link only opened the raw image asset in the browser on a dark page.

There was:

  • no clear “Save as…” action
  • no visible original filename
  • no file size
  • no obvious download control
  • no indication whether the original uploaded asset or only a rendered representation was being shown

Desired behavior

Every user-uploaded file should offer a clear action such as:

  • Download original
  • Save as…
  • Open original file

The UI should also show:

  • original filename
  • file type
  • file size
  • upload source where useful

For multiple files:

  • multi-select
  • Download all
  • optional handoff to a project/library folder

Why this matters

ChatGPT already sits naturally between devices.

The phone is often the capture/input device.

The desktop is often the editing/output device.

The conversation can become the transfer layer between both.

This would remove the need for separate temporary transfer tools, email-to-self workflows, cloud-folder detours or repeated uploads.

The desired model is:

Mobile capture
→ ChatGPT context
→ Desktop retrieval
→ continued production

This is closely related to cross-device synchronization, but it is a distinct workflow requirement:

Synchronization keeps conversation state aligned.

File handoff makes the actual working asset directly transferable between devices.

Acceptance criteria

  1. A file uploaded on mobile can be downloaded as the original file on desktop.
  2. The original filename and file size are visible.
  3. “Download original” is clearly distinguishable from simply opening a rendered asset.
  4. Multi-file transfer is possible without downloading files one by one.
  5. The workflow works consistently across mobile and desktop surfaces.
4

In August, active Project chats were missing from my global iOS Recent list. I could still find them through Projects > Project > chat, but pins weren’t a practical replacement.

I’d like Recent to include those chats, with the Project name and any unread result shown.

A Refresh/Sync button would help too, especially if it could update the list without stopping an active Work run.