openai / openai/codex

Remote work chats are not syncing between Windows PC and remote devices

Open
#45,280 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Summary

Remote chats used for work are not syncing between the Windows PC and remote devices. This prevents reliable continuity when moving between the PC and remote access.

Environment

  • Host: Codex desktop app on Windows PC.
  • Remote clients: remote devices; exact device models, OS versions and client versions have not been captured for this report.
  • Reported on: 13 September 2026.
  • Exact desktop app version: not captured.

Actual behavior

Work chats are not syncing between the PC and remote devices. The current report does not yet establish whether the failure affects chat listing, new messages within existing chats, or both, nor whether synchronization fails in one direction or both.

Expected behavior

Work chats and their latest conversation state should be consistently available when switching between the PC and connected remote devices.

Reproduction context

The issue occurs in the user's PC/remote-device work-chat workflow. A controlled reproduction and diagnostic logs have not yet been collected; this is a user-reported issue, not an independently reproduced diagnosis.

Impact

The user cannot reliably continue their work chats across devices.

Possibly related

  • #41470 describes Windows desktop projects/threads not appearing in Android Remote. It may involve related discovery/synchronization behavior, but the same root cause has not been established.

Please investigate cross-device chat synchronization and advise which diagnostics are needed to identify the failure.

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 reviewing related issue #41470 and collecting the missing device, client-version, desktop-version, reproduction, and diagnostic-log details. Done means the affected synchronization scope and direction are reproduced and the failing component or next investigation path is identified.

Written by the indexing model from the issue text.

Assessment

Domain
desktop-dev, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.