Repository navigation
ChatGPT mobile SSH sessions do not live-sync back to Codex App and can conflict with active macOS app sessions #29094
Description
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.616.32156
What subscription do you have?
ChatGPT Pro
What platform is your computer?
Darwin 25.5.0 arm64 arm
What issue are you seeing?
When connecting ChatGPT mobile to an SSH-accessible Codex computer, existing session history loads correctly. However, new conversation turns created after the SSH/mobile connection do not appear in the Codex App on macOS until the app is restarted.
The new turns appear to be routed through or persisted by the Codex CLI/terminal session instead of being live-synced into the Codex App UI.
What steps can reproduce the bug?
Open an existing Codex session in Codex App on macOS.
From ChatGPT mobile, connect to the same Codex computer over SSH.
Open or continue the same Codex session.
Send new messages from the mobile/SSH side.
Check the same session in Codex App on macOS without restarting the app.
What is the expected behavior?
Actual Behavior
Prior session history loads correctly on mobile/SSH.
New mobile/SSH conversation turns do not appear in Codex App until the macOS app is restarted.
The new turns seem to be associated with the Codex CLI/terminal path.
If both Codex App and mobile/SSH are active in the same session, conflicting conversation state can occur.
Expected Behavior
Conversation turns from ChatGPT mobile over SSH should sync live into the Codex App session.
Codex App and Codex CLI/mobile should show a consistent shared session state.
If simultaneous writes to the same session are unsupported, the app should detect this and prevent or clearly warn about conflicts.
Additional information
Impact
This makes cross-device Codex usage unreliable. It can cause users to miss messages, operate on stale state, or create conflicting turns in the same session when using Codex App and SSH/mobile concurrently.
Suggested Fix
Add live session synchronization between Codex CLI/SSH sessions and Codex App
Activity
github-actions commentedon Jun 19, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
codex exec resumecan append to a Desktop session transcript without updating the Desktop session index/UI reliably #28259Powered by Codex Action
Necmttn commentedon Jun 21, 2026
Cross-surface continuation needs a shared append stream or lease record.
Each writer can stamp surface id, session id, append sequence, last seen sequence, and active writer lease. The macOS app can then live-apply external SSH/mobile appends or show a conflict if both surfaces write past the same sequence.
Restarting the app should not be the first sync mechanism.
Generated with ax.
johncowley commentedon Aug 28, 2026
Same issue here on macOS + ChatGPT mobile over SSH. Existing history loads, but new turns stop live-updating across devices unless Codex Desktop is quit/reopened. This used to work reliably, so it appears to be a regression. +1 for fixing this — it materially breaks the mobile continuation workflow.
bobfang1992 commentedon Aug 31, 2026
+1. Live consistency between mobile/SSH, CLI, and the Codex App is critical. A remote client that can read history but not reliably propagate new turns back into the active app/session creates stale-state and conflict risks.