Skip to content

Cannot access chats #45259

Open
Open

Description

@Right2Rebel

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

Version 26.908.40834

What subscription do you have?

Pro

What platform is your computer?

macOs

What issue are you seeing?

I receive errors and am not given access too my latest chats. I have tried browser and desktop. Logged in and out. Now I cannot add images in "what steps can reproduce the bug" and I cannot write a message in that box, just an automated message that cannot be deleted.

Image Image

What steps can reproduce the bug?

Feedback ID: no-active-thread-01a09ba9-816a-78d2-b8d0-c3e0abbacc63

What is the expected behavior?

That I can continue my conversation and access my chat. This has happened in the last 20 minutes.

Additional information

No response

Activity

  1. added
    appIssues related to the Codex desktop app
    on Sep 13, 2026
  2. added
    bugSomething isn't working
    sessionIssues involving session (thread) management, resuming, forking, naming, archiving
    on Sep 13, 2026
  3. Right2Rebel commented on Sep 13, 2026

    @Right2Rebel
    Author

    Subject: Two conversations in White Rabbit Project inaccessible — conversation metadata visible but underlying chats fail to load
    Date observed: 13 September 2026, approximately 18:41–18:42 CEST
    Project: White Rabbit
    Account: Same ChatGPT account in both Chrome and ChatGPT macOS desktop app
    Two conversations in my White Rabbit Project have become inaccessible:

    1. Recover White Rabbit Chat
    2. Third Way Proposal Chat
      The conversations have not apparently disappeared from the Project. They are still represented/listed in the ChatGPT interface, but their underlying conversation content cannot be opened.
      Chrome behaviour
      When accessing the White Rabbit Project in Chrome, the Project itself loads and its conversation list is visible. Attempting to access the affected conversation produces:
      “You don’t have access to this conversation. Make sure you’re logged in to the right account, or ask the conversation owner to send you a share link.”
      I am already logged into the account that owns/created the Project and conversations.
      ChatGPT macOS desktop app behaviour
      The same conversation is visible in the White Rabbit Project sidebar. Attempting to open it produces:
      “Could not load this ChatGPT conversation”
      This therefore reproduces across both the web application and native macOS application, but with different error messages.
      Additional diagnostic
      I opened a separate functioning ChatGPT conversation and asked ChatGPT to search the ChatGPT conversation/Library retrieval available to it for the two affected conversations.
      Neither “Recover White Rabbit Chat” nor “Third Way Proposal Chat”, nor their underlying conversation content, could be retrieved.
      Other White Rabbit material stored in my ChatGPT Library was successfully retrieved. This suggests the retrieval mechanism itself is functioning, while these specific conversation objects are inaccessible.
      Observed state
      Project metadata/listing → accessible
      Conversation name/listing → accessible
      Underlying conversation → inaccessible
      ChatGPT Library/file retrieval → functioning
      Retrieval of affected conversation content → inaccessible
      This appears potentially consistent with an authorization, conversation-object, or indexing/reference issue rather than ordinary connectivity or the conversations simply having been deleted.
      Important: These conversations contain work that I need to recover. Please do not delete or reset the affected conversation records as part of troubleshooting. I would specifically like the underlying conversation contents recovered/restored if possible.
  4. Right2Rebel commented on Sep 13, 2026

    @Right2Rebel
    Author

    UPDATE — 13 September 2026, 20:00 CEST
    The problem is no longer confined to the White Rabbit Project.
    In the ChatGPT macOS desktop application, a conversation in a separate Project (AI → “Trilogy: Rave Life Philosophy”) has now become stuck during processing.
    The UI remains on “Thinking”, with an apparently failed/blank response area and the stop-generation control still active. The Outputs panel shows a generated Word document (Trilogy - Rave Life Philosophy.docx), but the conversation does not complete/render normally.
    Screenshot attached: Screenshot 2026-09-13 at 20.00.46.png
    This is significant because the earlier failures affected two conversations in the White Rabbit Project (“Recover White Rabbit Chat” and “Third Way Proposal”). This new failure is occurring in an entirely separate Project, suggesting the issue may be account/session/conversation-processing related rather than corruption isolated to the White Rabbit Project.
    Please correlate these failures against my account/server logs around 18:41–18:42 CEST and 19:59–20:00 CEST on 13 September 2026.

    Image
  5. oyatek commented on Sep 17, 2026

    @oyatek

    Same for me for the last 3 days; I often get "Could not load this ChatGPT conversation."
    Sometimes reloading the page helps, but most of the time it doesn't.

  6. SIMON-WORLD commented on Sep 24, 2026

    @SIMON-WORLD

    Additional cross-surface reproduction from 2026-09-24:

    Environment:

    • ChatGPT Plus
    • Windows
    • ChatGPT Web
    • ChatGPT Windows desktop: Powered by Codex & OWL, version 26.917.71314, released Sep 23, 2026

    I have now observed the same visible error on both ChatGPT Web and the Windows desktop app:

    Could not load this ChatGPT conversation

    The failure is selective rather than account-wide:

    • some existing conversations continue to open and work normally;
    • other existing conversations fail to load;
    • affected conversations remain visible in the sidebar / Project list.

    On Web, at least one affected conversation recovered without any account, browser, network, or configuration change: after several minutes, refreshing the same conversation URL loaded it successfully again.

    Later the same day, additional conversations intermittently showed the same error.

    I am also attaching a Web screenshot showing the failure state.

    This is occurring during the current redesigned ChatGPT Web UI rollout, whose interaction surface appears increasingly aligned with the desktop app. I am not claiming that the UI rollout caused the failure; I mention the timing only because the same conversation-loading error is now observable across both Web and Windows desktop surfaces.

    In this reproduction the affected conversation was therefore not permanently deleted or permanently inaccessible. The behavior is consistent with an intermittent conversation-loading / retrieval failure, but I do not have evidence for the underlying failure layer.

    Image
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 workingsessionIssues involving session (thread) management, resuming, forking, naming, archiving

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions