### What issue are you seeing? Sessions don't stay in sync when used across cli/desktop/mobile. ### What steps can reproduce the bug? 1. Start cli, launch some subagents 2. While running/once finished, send followup/steer from mobile (android) remotely connected to your host 3. Check cli and see no update made to the session 4. Check codex desktop && vscode extension, and you might see updates for the session, but also might not ### What is the expected behavior? Sending a message from one

Potential duplicates detected. Please review them and close your issue if it is a duplicate. - #29094 - #29390 - #29096 - #28259 *Powered by [Codex Action](https://github.com/openai/codex-action)*

Severe session sync issues between tui/desktop/mobile

Open 💬 2 comments Opened Jun 23, 2026 by RickDavis404

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What issue are you seeing?

Sessions don't stay in sync when used across cli/desktop/mobile.

What steps can reproduce the bug?

Start cli, launch some subagents
While running/once finished, send followup/steer from mobile (android) remotely connected to your host
Check cli and see no update made to the session
Check codex desktop && vscode extension, and you might see updates for the session, but also might not

What is the expected behavior?

Sending a message from one client should trigger updates to other sessions, ideally when messages are sent, but at the very least when responses are sent (a little lag is fine, but not completely lost msgs/tui never updating).

Additional information

Codex Feedback/thread ID: 019ef531-0938-7220-afbf-d5dbb802ba9a

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 2 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

#29094
#29390
#29096
#28259

Powered by Codex Action

hm8526-ops · 15 days ago

Additional confirmed reproduction on 2026-08-13 involving the Windows desktop app and ChatGPT mobile Remote:

The mobile client and Windows desktop were viewing the same Codex thread on the same connected host (confirmed from the thread/host header).
Multiple user turns and completed assistant responses were visible on mobile but did not appear in the Windows desktop thread.
The desktop appeared unresponsive, so the user had to create a new thread.
Later inspection of the stored thread history showed that the supposedly missing turns were present and marked completed; one final response completed in about 40 seconds.
This rules out complete message loss and strongly suggests cross-client event/state reconciliation or desktop rendering/refresh failure.
It was not a different ChatGPT conversation, project, thread, or host.

Impact is severe: the user cannot tell whether a prompt was received or a response completed, may repeat instructions, and may abandon the original task even though work finished successfully.

Expected behavior: once a turn is accepted or completed through Remote, every client viewing that thread should reconcile to the authoritative thread state. If live updates fail, reopening or refreshing the thread should recover the missing turns and surface a clear reconnect/stale-state indicator.

Screenshots and the private thread identifier are intentionally not posted publicly because they contain project and conversation details.