{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigqyso23hh6jdcrawcvlkfi5bpsq3lz2oha4dtygmpmjuzirh3dfe",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mkf3v4mujkf2"
  },
  "path": "/t/codex-vs-code-extension-appears-broken-while-opening-previous-chats/1379805#post_2",
  "publishedAt": "2026-04-26T08:05:07.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "OpenAI Codex GitHub Issues",
    "github.com/openai/codex",
    "Unable to open past conversation history in VS Code extension",
    "iamhenryhuang"
  ],
  "textContent": "Welcome to the forum!\n\nYou can discuss Codex-related issues here, but the official place to report them is the OpenAI Codex GitHub Issues.\n\nA quick search using ChatGPT surfaced several similar reports, for example:\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  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_\n\nIt’s worth searching existing issues to see if any match your case. If you find a relevant one, consider adding a  reaction to help increase its visibility.\n\nIf nothing aligns, you can open a new issue—just be sure to include clear and reproducible steps.",
  "title": "Codex VS Code extension appears broken while opening previous chats"
}