ChatGPT desktop chats not showing on your phone or the web: why they don't sync and how to fix it

2 hours ago

9 min read

Last verified: November 15, 2026

You start a conversation in the ChatGPT desktop app on a Mac, Windows PC or Linux laptop, pick up your phone an hour later, and the chat is nowhere to be found. The web version at chatgpt.com shows the same gap, while chats you started on the phone appear on the desktop without trouble. Since the desktop app was rebuilt around separate Chat, Work and Codex modes, this one-way pattern has become one of the most common complaints on OpenAI's community forum, and in most of the reported cases nothing is broken. The conversation was started as a local task that lives on that computer, and the fix for new chats is to start them in regular Chat or in Work with Cloud selected.

The rule comes from OpenAI's own documentation of ChatGPT Work: when Cloud is selected in the desktop composer, eligible new conversations use cloud coordination and can continue on other devices, while Local keeps both coordination and execution on the computer. Users on macOS and Linux report seeing the local choice worded as "In this computer" or "On my computer" in the app. Two other causes produce the same symptom: chats created in Codex, which keeps a separate history that the phone and web sidebars do not show, and a smaller number of real sync faults that OpenAI support describes as unexpected and asks users to report.

··········

WHAT THE CHATGPT DESKTOP SYNC PROBLEM LOOKS LIKE.

The reports share a recognizable shape. New conversations created in the desktop app stay visible on that computer, survive a restart of the app, and can be continued there, but they never appear in the sidebar on the iPhone, Android or web versions. Traffic in the other direction keeps working, so a chat started on the phone shows up on the desktop. One user on the forum laid it out as a matrix in late October: iPhone to Mac and web to Mac worked, Mac to iPhone and Mac to web failed.

A second detail helps identify the cause. Several users noticed that the empty desktop composer read "Work with ChatGPT" while the phone showed "Ask a question to ChatGPT", which means the desktop app was opening new conversations in Work mode. A Linux user on desktop version 26.1027.51404 found that the missing conversations had all been created under Work with "In this computer" selected; existing conversations, and new messages added to them, synced normally.

The table below matches what you see to the most likely mode the conversation was created in.

........

What you see	Most likely mode on the desktop	Visible on phone and web
New desktop chats missing, phone chats appear on desktop	Work with Local ("In this computer")	No
Desktop chats missing from Projects on phone and web	Codex, or a local project	No
Chat visible on web but stale on the phone until reopened	Regular Chat, not refreshed	Yes, after refresh
Regular Chat or Cloud Work chat missing everywhere except the Mac	Sync fault	Should be yes
Some chats missing from the sidebar on every device	Archived or filtered view	Yes, in Archived chats

........

··········

CHATGPT DESKTOP CHATS NOT SYNCING: CAUSES, CHECKS AND FIXES.

Each row comes from OpenAI's documentation, an answer from OpenAI support on the community forum, or several independent user reports, as noted in the last column.

........

Cause	How to check	Fix	Basis
Conversation started as local Work	Composer shows Work with Local, "In this computer" or "On my computer"	Use Chat, or Work with Cloud, for new conversations	OpenAI docs, several user reports
Conversation created in Codex	Chat sits in the Codex section of the desktop app	Use Chat or Cloud Work; check Remote on mobile for supported Codex chats	OpenAI support answer, OpenAI docs
Different account or workspace	Profile menu shows a different email or workspace on each device	Sign in to the same account and workspace everywhere	OpenAI docs
Cloud Work or local access not enabled by the admin	No Cloud option in a Business, Enterprise or Edu workspace	Ask the workspace owner to enable Work Cloud and Allow local computer access	OpenAI docs
Stale screen on one device	Chat appears after a reload or after reopening it	Refresh before sending a new message	Several user reports
Archived or filtered sidebar	Chat found under Archived chats or in Chronological view	Unarchive it or change the sidebar filter	OpenAI docs
Real sync fault	Regular Chat or Cloud Work chat still missing after all checks	Report it through Help with app versions	OpenAI support answer, user reports

........

··········

FIX 1: STOP CREATING LOCAL WORK CHATS IN THE CHATGPT DESKTOP APP.

OpenAI's documentation describes two places a Work conversation can run. With Cloud, eligible new conversations use cloud coordination, which is what lets the same thread open on another device. With Local, both coordination and execution happen on the computer, so the thread belongs to that machine. The desktop app remembers the last choice, which is why one accidental switch can make every new conversation local for weeks.

1. Open the ChatGPT desktop app and look at the empty composer before you type.

2. If you only want to talk to ChatGPT, switch to the regular Chat mode. Users on Linux and macOS report that new chats then appear on the phone and the web right away.

3. If you need Work features and want the task on other devices, select Cloud in the composer instead of Local, "In this computer" or "On my computer".

4. Send a short test message and open the phone app or chatgpt.com to confirm the new chat is listed.

5. Restart the desktop app once and check that the mode you picked is still selected. The Linux user who documented the problem found the app kept the choice after a restart.

Existing conversations do not move. OpenAI's admin documentation states that existing tasks keep their original mode and that a new cloud task has to be started; users add that switching the selector does not convert old local Work chats into cloud chats. If those local conversations hold work you need, copy the important parts into a new Chat or Cloud Work conversation, and keep them on the computer until you have. The user report on Linux warns against resetting or uninstalling the app before backing them up.

··········

FIX 2: CHECK WHETHER THE CHATGPT CHATS WERE CREATED IN CODEX.

The new desktop app merged the former Codex app into ChatGPT, and Codex keeps its own history. In a July 2026 reply on the community forum, OpenAI support explained that chats created in Codex are not available in the normal web or mobile Projects view, that supported Codex chats may appear under Remote in the mobile app, and that Cloud Work chats should sync across desktop, web and mobile. OpenAI's documentation repeats that Codex history is separate from Work history.

1. In the desktop app, open the conversation that is missing on the phone and check which section of the sidebar it sits in.

2. If it is a Codex chat, look under Remote in the ChatGPT mobile app.

3. For future conversations that you want everywhere, start them in Chat or in Work with Cloud.

One user whose Mac had started defaulting to "On my computer" with a Codex-style layout reported on November 11 that switching to Codex and then back to standard Chat restored syncing with the iPhone and the web immediately. That is a single report, so treat it as something to try after the steps above.

If you want to follow a task running on your computer from your phone, OpenAI documents a separate feature for that. In the desktop app, Settings, Connections, "Control this Mac or PC" pairs the phone with a QR code, and the computer must stay awake, online and signed in to the same account and workspace. The phone then shows the computer's tasks for viewing, approving and reviewing; the work itself stays on the computer.

··········

FIX 3: CHATGPT ACCOUNT, WORKSPACE AND ADMIN SETTINGS.

OpenAI's troubleshooting page for Work conversations that do not appear on another device starts with the account: every device has to be signed in to the same account and the same workspace, and Work conversations are listed in Work history. A personal Plus or Pro account and a company Business workspace on the same email are different places, and a chat created in one will not appear in the other.

For Business, Enterprise and Edu workspaces, continuing local tasks across devices depends on the administrator. The documentation lists these requirements:

........

Requirement	Where it is set	Detail from OpenAI's documentation
Work Cloud enabled for the user	Admin Console, Permissions	Required before local access can be turned on
Allow local computer access	Admin Console, Permissions, under Work Cloud	Turned on by a workspace owner
Desktop app version	ChatGPT desktop app	26.929 or higher
No data residency enforcement	Agent Security cloud policies	enforce_residency disables local computer access
Computer online	The computer holding the files	Desktop app running and signed in to the same workspace

........

1. Open the profile menu on each device and confirm the email address and workspace name match.

2. In a workspace, ask the owner whether Work Cloud and Allow local computer access are enabled for your role.

3. Update the desktop app, then start a new Work task with Cloud selected. OpenAI's documentation says a task created before local access was available needs to be restarted this way.

When the computer is offline, OpenAI says an eligible new turn in a cloud task can run in a cloud container instead, without access to the computer's files or tools, so a task that looks broken on the phone may simply have lost its connection to the desktop.

··········

FIX 4: REFRESH, ARCHIVED CHATS AND THE SIDEBAR VIEW IN CHATGPT.

Some missing chats are a display problem. On a community thread with more than 11,000 views, users describe a desktop browser tab that kept showing an older version of a conversation after they had continued it on Android; sending a message from the stale tab replaced the newer messages on both devices. No official fix has been posted, and the users in that thread report that refreshing every device before sending is the only reliable prevention.

1. Before continuing a conversation on a second device, reload the page or close and reopen the chat.

2. If a chat is missing from the sidebar, select the filter icon next to Chats and choose Chronological, as OpenAI's documentation suggests.

3. Open Settings and check Archived chats. OpenAI says an unarchived chat returns to its original place in the sidebar.

··········

FIX 5: WHEN CHATGPT REGULAR CHATS REALLY DO NOT SYNC.

A smaller set of reports does not fit any of the causes above. A Plus user on macOS app 26.1007.71326 and iOS app 1.2026.279 described Mac conversations, mostly inside Projects, failing to reach the web, iPhone and Windows for more than three weeks, with two support cases open and no fix. A Business user on desktop 26.901.51231 reported Projects missing from the macOS app while the web showed them, reproduced by a colleague on another Mac. OpenAI support's position in the July thread is that missing sync for regular Chat or Work conversations is unexpected and should be reported through Help.

1. Confirm the conversation is a regular Chat or a Cloud Work chat, not Local and not Codex.

2. Note the desktop app version, the phone app version and the time you created the chat.

3. Report it from the Help menu in ChatGPT and include those details.

4. Until it is fixed, open important conversations on chatgpt.com in a browser on the computer, which keeps them in the same place as the phone.

··········

CHATGPT SYNC BEHAVIOR: DOCUMENTED BY OPENAI OR REPORTED BY USERS.

........

Statement	Status
Cloud lets eligible new Work conversations continue across devices; Local keeps coordination and execution on the computer	Documented by OpenAI
Existing tasks keep their original mode; a new cloud task is needed	Documented by OpenAI
Codex history is separate from Work history	Documented by OpenAI and stated by OpenAI support
Cloud Work chats should sync across desktop, web and mobile	Stated by OpenAI support
The local option appears as "In this computer" or "On my computer"	Reported by users on Linux and macOS
Switching the selector does not convert old local chats	Reported by users, consistent with the documentation
Switching to Codex and back to Chat restored sync	Reported by one user

........

The documentation also notes that local execution does not keep a conversation offline: prompts, file excerpts and tool results can still be sent to OpenAI to complete a task. Local describes where the task runs and who coordinates it, which is why it decides whether the thread shows up on your other devices.

··········

PREVENTING CHATGPT DESKTOP CHATS FROM GOING MISSING AFTER UPDATES.

The desktop app has changed several times since July, when the Codex and ChatGPT apps were merged, and on November 3 we covered OpenAI's plan to merge the Chat and Work tabs while keeping Codex separate. Each change can reset the default mode, so after an update look at the composer and confirm whether it says Chat, Cloud or Local before starting anything you will need elsewhere.

Keep a copy of conversations that matter. A data export of your account is one way to do that, and our page on a ChatGPT data export email that never arrives explains the waiting times and failures. If older chats appear in the list but refuse to open, the problem is different and is covered in our fixes for "Could not load this ChatGPT conversation".

··········

CHATGPT DESKTOP-TO-PHONE SYNC: WHAT TO DO FIRST.

When a desktop chat is missing on the phone or the web, the first thing to check is the composer mode on the computer. A conversation started as local Work stays on that machine by design, the same happens to Codex chats in the phone and web sidebars, and neither will be moved over by an update. New conversations created in regular Chat, or in Work with Cloud selected, appear on the other devices, and old local ones have to be restarted or copied by hand.

If the account, the workspace and the mode are all correct and a regular chat still does not reach the phone, the case belongs with OpenAI support, with app versions attached. Several of those reports from October and November remain open, and OpenAI has not published a fix or a cause for them as of November 15, 2026.

··········

·····

DATA STUDIOS

·····

datastudios.org