Android remote control session list stays stale while Codex Desktop has newer sessions

Description

The ChatGPT Android remote-control session list for Codex Desktop appears stale. Recent Codex Desktop sessions exist locally and are visible from desktop/iOS, but the Android remote-control session list only shows old sessions, around 4 days behind. Android can still resume/control older sessions, so the remote-control channel is not completely broken.

I am filing this on behalf of a user who is currently controlling Codex from the Android app.

Expected behavior

The Android remote-control session list should show the same recent Codex Desktop sessions as the desktop app / iOS remote-control view.

Actual behavior

As of 2026-05-25 23:26 Asia/Shanghai, the local Codex Desktop thread DB contains fresh sessions, including:

• 019e5fb5-... updated 2026-05-25 23:26, title starts with 最新的session是哪一个？为什么我这里看不到？
• 019e5ddc-... updated 2026-05-25 23:20, title starts with 我在手机，安卓手机上远程连接你...

However, the Android app's remote-control session list only shows sessions from around 4 days ago. Reinstalling the Android app, restarting the phone, switching accounts away/back, and reauthorizing remote control did not refresh the list.

The user also reports that deleting the device/list entry from Android is not a viable workaround because it removes the device across all devices.

Diagnostics from the desktop machine

Environment:

• Codex Desktop app version observed in logs: 0.133.0-alpha.1
• Codex CLI: codex-cli 0.130.0
• macOS: 26.5 build 25F71
• Android remote client name/version observed in logs: codex_chatgpt_android_remote, version dev
• iOS remote client version observed separately in logs: 1.2026.132

Local thread storage is up to date:

• ~/.codex/state_5.sqlite threads table lists multiple sessions updated on 2026-05-25, including the two above.
• ~/.codex/sessions/2026/05/25/...019e5fb5...jsonl exists for the latest session.

Remote-control enrollment/state looks suspicious:

• remote_control_enrollments has a current local environment ID ending in ...dc91, server name appledeMacBook-Pro-3.local, last updated 2026-05-19 12:57:32 local time.
• ~/.codex/.codex-global-state.json has electron-local-remote-control-environment-id ending in ...dc91, but selected-remote-host-id, added-remote-control-env-ids, and remote-connection-auto-connect-by-host-id point to a different environment ID ending in ...3115.

Logs suggest the Android client is not refreshing the session list from the current desktop server:

• Recent Android remote logs show thread/resume calls for older thread IDs.
• No recent Android-originated thread/list request was found.
• The only recent thread/list requests observed were from Codex Desktop, not from codex_chatgpt_android_remote.
• Remote/plugin sync logs complete successfully, so the remote-control transport itself appears to be working.

Steps already tried by the user

• Android app uninstall/reinstall
• Phone reboot
• Switch account away, then switch back
• Reauthorize remote control
• Resume older sessions from Android still works

Suspected area

This looks like either:

1. Android remote-control session list/backfill is stuck on an old cursor or old remote environment, or
2. Android is selecting an old remote host/environment even though the current desktop enrollment points to a newer environment, or
3. Android remote-control list refresh is not issuing thread/list against the active desktop app-server.

I did not include account email, account ID, or complete internal IDs in this report.