openai / openai/codex

[Remote Control][Android/Windows] Remote loads stale Codex session state instead of latest progress

Open
#46,084 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What issue are you seeing?

Since September 16, 2026, Codex Remote Control repeatedly fails to synchronize the latest state of an active Codex session.

When connecting remotely from the ChatGPT Android app to Codex work running on the Windows host, Remote Control loads a significantly older state of the conversation/work and then remains on that stale state instead of updating to the latest progress.

The Codex work on the host may continue, but the remote client does not reflect the current session state. This has been occurring repeatedly since yesterday and makes remote monitoring/control unreliable.

This appears to be a session/thread state synchronization or stale-state/cache problem rather than simply a one-time connection failure.

Steps to reproduce
  1. Run an active Codex development session on the Windows host and continue working so the session accumulates new progress/messages.
  2. Connect to that session remotely using ChatGPT/Codex Remote Control on Android.
  3. Open the active session.
  4. Observe that Remote Control may load a much older portion/state of the session rather than the latest state.
  5. Wait for synchronization/refresh.
  6. The remote view remains stale and does not catch up to the latest host-side progress.
  7. Repeating the connection has reproduced the issue since September 16, 2026.
Expected behavior

Remote Control should synchronize to the authoritative latest state of the selected active Codex session and continue receiving subsequent progress/messages from the host.

If synchronization cannot complete, the client should surface an explicit sync/reconnect error rather than silently presenting an old state as current.

Actual behavior

A significantly older session/work state is loaded and remains displayed without catching up to current host-side progress.

Impact

High. Long-running Codex development work cannot be reliably monitored or controlled remotely because the remote UI may silently display stale state.

Environment
  • Remote client: ChatGPT Android app / Codex Remote Control
  • Host: Windows Codex environment
  • Subscription: ChatGPT Pro
  • First repeatedly observed: September 16, 2026
  • Still occurring: September 17, 2026
Additional context

The same user has previously experienced Remote Control connection instability, but this report is specifically about a different symptom: the connection can present session content while failing to load/synchronize the latest state.

Potential areas to inspect include remote thread/session authoritative-state selection, pagination/cursor handling, stale cache invalidation, reconnect replay/resume boundaries, and host-to-mobile incremental update subscription.

No private repository names, account identifiers, or project content are included in this public report.

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

Start by reproducing the Android-to-Windows Remote Control flow with an active session, then inspect remote thread/session authoritative-state selection and pagination or cursor handling. Check stale-cache invalidation, reconnect replay/resume boundaries, and host-to-mobile incremental update subscription. Done means the remote view reaches the latest session state and continues receiving updates, or shows an explicit synchronization error.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, rust
Domain
distributed-systems, mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.