VS Code Codex conversation missing from sidebar but resumable by session ID in CLI
What version of the IDE extension are you using?
26.727.40816
What subscription do you have?
ChatGPT Plus
Which IDE are you using?
Visual Studio Code
What platform is your computer?
Windows 11, x64
What issue are you seeing?
A Codex conversation disappeared from the conversation history/sidebar in the Codex VS Code extension even though I did not delete or archive it.
The conversation still exists locally as a JSONL session and can be resumed successfully using the Codex CLI.
Session ID:
019fb023-24b8-7881-9119-509f078b610e
Local session folder:
C:\Users\ACCER\.codex\sessions\2026\07\30
Resume command:
codex resume 019fb023-24b8-7881-9119-509f078b610e
The complete conversation opens correctly in the terminal Codex interface. However, it does not appear in the Codex conversation panel inside Visual Studio Code.
The conversation disappeared after my Codex usage reached 0%. When my usage reset and I returned to VS Code, the conversation was no longer visible. I do not know whether the usage reset is related, but the local session was not deleted.
Feedback ID:
no-active-thread-019fbcf1-7d81-7072-bfd2-b1c446138f68
Possibly related issue:
#20131
What steps can reproduce the bug?
Feedback ID: no-active-thread-019fbcf1-7d81-7072-bfd2-b1c446138f68
What is the expected behavior?
A valid local Codex conversation that still exists on disk and can be resumed by the Codex CLI should remain visible and accessible in the Codex VS Code extension conversation panel.
The extension should also provide a way to re-index or restore local sessions that disappear from the sidebar.
Additional information
I already tried:
- Reloading the VS Code window
- Restarting Visual Studio Code
- Opening the original project folder
- Checking chronological conversation history
- Checking archived conversations
- Confirming that I am using the same ChatGPT account
- Resuming the session through the Codex CLI
The CLI successfully restores the full conversation, so the transcript does not appear to be corrupted or deleted.
Feedback ID:
no-active-thread-019fbcf1-7d81-7072-bfd2-b1c446138f68
Date of missing conversation:
July 30, 2026, approximately 7:08 AM
Time zone:
Asia/Manila, UTC+8
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I reviewed the suggested possible duplicates: #35784, #35585, and #36341.
They appear related, but my case is different because it affects the Codex VS Code extension on Windows, not the Codex desktop application.
In my case:
The closest extension-related report I found is #20131, although that issue concerns a visible session that opens blank, while mine is not visible in the sidebar at all.
I believe this issue should remain open as a VS Code extension session-indexing or sidebar-visibility problem unless maintainers confirm that it has the same root cause.
The useful part of this report is that the JSONL survives and the full conversation resumes by UUID in the CLI, while the VS Code sidebar cannot discover it. That cleanly separates transcript persistence from extension indexing.
I’m testing Codex Rescue as an independent local-session discovery path. It will not modify the extension index or source rollout, and it cannot force VS Code to render the chat. The goal is to verify that the hidden session is found and structurally safe.
If it still exists locally, could you run:
pipx install codex-rescue==0.1.0a3codex-rescue sessionscodex-rescue doctor --latestPlease share only sanitized output—no session IDs if you prefer, and no raw JSONL, databases, prompts, project contents, private paths, or secrets.
https://github.com/shleder/codex-rescue