Remote task completion leaves conversation text stale on other machines
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Summary
Remote task completion does not update the conversation text on other machines using the same account.
User-reported behavior
When a task is worked on and completed remotely, the conversation text on other machines does not keep up or show the completed task's latest response. This makes it difficult to tell whether work has finished and to follow progress across devices.
Reproduction scenario
- Use a Codex task remotely.
- Allow the task to finish on the remote side.
- View the same task on another machine.
- Observe that the conversation text does not reflect the latest remote completion.
Expected behavior
The latest messages and completion state should synchronize to other connected clients viewing the same task, without requiring another user message to discover the result.
Actual behavior
The other machines continue displaying stale conversation text after remote completion.
Environment and evidence
- Product: Codex remote / cross-device task experience.
- Reported September 7, 2026.
- Local host available to the reporting assistant: macOS 26.5.
- Exact app builds, other device operating systems, frequency, and whether reopening the task or restarting the app resolves it are not yet established.
- This report captures the user's observed behavior; the reporting assistant has not independently reproduced the cross-device failure.
- No private repository contents, conversation transcript, credentials, or diagnostic logs are attached.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or code entry points are identified in the report. Start by reproducing the remote-completion scenario on two machines with the same account, then investigate why the second client retains stale conversation text; done means the latest messages and completion state appear without another user message.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100