openai / openai/codex

Remote access from both desktop and phone will cause a fetch of conversation, lost context, and broken envirement

Open
#39,842 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug remote session
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of the Codex App are you using (From “About Codex” dialog)?

Powered by Codex & OWL Version 26.803.41515

What subscription do you have?

Pro 5x

What platform is your computer?

Desktop: Mac OS Server: Linux x64 Phone: Android

What issue are you seeing?

When I use the method mentioned in #23200 to connect my desktop to the server, i can successfully control it. However, if I get a push notif on my phone about a update and reply it, the new thread on phone will be fetched, Codex lost the latest message context, and the envirement is broken such as file not found.

What steps can reproduce the bug?

Start a codex cli session on server, connect to it using both phone and desktop. start a few messages on the desktop and switch to phone to continue,

What is the expected behavior?

Per my understanding, this is expected when two window open to a chat at the same time, that is why when the cli is open on server, the desktop cannot control it. However, seems like the phone app does not have this gate and it will allow the conversation to be continued

Additional information

No response

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 with the remote Codex CLI session flow described in #23200 and reproduce it using a server session opened from both desktop and Android phone, including a push-notification reply. Done means switching clients either preserves the latest conversation context and working environment or prevents the conflicting continuation, with the observed file-not-found failure addressed.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.