Skip to content

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

Open

Description

@hergameworld

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

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

Activity

  1. added
    bugSomething isn't working
    appIssues related to the Codex desktop app
    windows-osIssues related to Codex on Windows systems
    sessionIssues involving session (thread) management, resuming, forking, naming, archiving
    on Sep 13, 2026
  2. github-actions commented on Sep 13, 2026

    @github-actions
    Contributor

    Potential duplicates detected. Please review them and close your issue if it is a duplicate.

    Powered by Codex Action

  3. hergameworld commented on Sep 13, 2026

    @hergameworld
    Author

    Follow-up: project structure remains stale on iPad and iPhone even when chat messages sync

    This adds more specific observations to the original report. The problem is not a complete failure of message synchronisation: a newly started chat successfully synced between the PC and a connected remote device, while the remote project list and displayed organisation remained inconsistent with the PC.

    Environment

    • Host: a fully updated Windows PC running the Codex desktop app.
    • Remote devices: Apple iPad (iPadOS) and iPhones (iOS), all fully updated, including the apps used for this workflow, as reported by the user.
    • Windows app version identified earlier on 13 September from the running application's installation path: 26.908.4834.0.
    • Exact Windows, iOS/iPadOS and mobile app version numbers and device models have not been recorded.
    • Observations reported on 13 September 2026.

    Important clarification: the PC setup looks correct

    The user moved project folders and chats around inside ChatGPT on the PC and double-checked the folder associations at the time. The project folders and chat arrangements visible on the PC are correct. The user is not reporting visibly incorrect working-folder settings on the PC. The problem is that the connected remote devices do not reflect that current PC setup.

    Observed behaviour

    1. A new project on the PC did not appear on the connected remote device.
    2. After starting a new chat inside that project on the PC, the project appeared remotely and that chat's messages synced successfully between the two devices.
    3. After moving existing chats between projects and archiving the old projects on the PC, the remote devices continued to show the older project/chat arrangements.
    4. The user could not find a way to remove those obsolete project entries on the remote devices.
    5. The remote lists appear to retain arrangements from when those chats/projects were previously used on each device, rather than consistently reflecting the current PC setup. This is the user's observed pattern, not a confirmed caching mechanism.

    Separate, unverified metadata observation from the assistant

    During read-only inspection through app tools, the assistant saw differences between project associations and recorded working-directory paths for some threads. These were tool-returned metadata, not a visible settings problem identified by the user. The assistant has not established whether those fields are historical records, stale metadata, expected behaviour, or relevant to the remote-list issue. They do not establish that the user's PC configuration is wrong or that a chat actually edits files in the wrong location. No incorrect file writes have been demonstrated.

    Expected behaviour and impact

    Connected remote devices should reflect the current PC project list, chat membership and archive state without requiring a new chat to make a project appear.

    The stale remote arrangements make it difficult to locate ongoing work and distinguish current projects from archived ones, despite the PC organisation being correct. Please investigate project discovery, project/chat reassignment and archive-state propagation between Windows and iOS/iPadOS, separately from message synchronisation. Please advise which diagnostics would help; this is a user-observed sequence, not a controlled engineering reproduction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingremotesessionIssues involving session (thread) management, resuming, forking, naming, archivingwindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions