{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigclqupexis3k6hmlarpn4cgki7tzbd45fw2qvlwsv5myixacniia",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mm4mrvhsqsv2"
  },
  "path": "/t/codex-previous-chat-disappears-in-vs-code-after-restart/1381210#post_2",
  "publishedAt": "2026-05-18T08:47:42.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "github.com/openai/codex",
    "Unable to open past conversation history in VS Code extension",
    "iamhenryhuang"
  ],
  "textContent": "Welcome to the forum!\n\nevaxes:\n\n> Has anyone else experienced this issue?\n\nYes, this is has been reported in many topics.\n\nPlease see:\n\ngithub.com/openai/codex\n\n####  Unable to open past conversation history in VS Code extension\n\nopened 03:12PM - 22 Apr 26 UTC\n\n\n\n          iamhenryhuang\n        \n\nbug  extension  regression  session\n\n### What version of the IDE extension are you using? 1.117.0 ### What subscrip…tion do you have? plus ### Which IDE are you using? vs code ### What platform is your computer? Microsoft Windows NT 10.0.26200.0 x64 ### What issue are you seeing? Recently, I have been unable to open any past conversation records. When I click on a history item in the sidebar, the interface does not respond, and the previous chat content fails to load. There are no explicit error pop-ups, but the chat window remains blank or stuck. ### What steps can reproduce the bug? What steps can reproduce the bug?* Open VS Code and ensure the GPT Codex extension is logged in. Click on the \"History\" icon/tab to view past conversations. Click on any specific historical conversation title from the list. Observe that the chat interface does not update or display the selected history. ### What is the expected behavior? What is the expected behavior? The extension should correctly fetch and display the full chat history of the selected conversation when clicked. ### Additional information _No response_",
  "title": "Codex - Previous chat disappears in VS Code after restart"
}