Refresh conversation history when switching/resuming conversation in same VSCode session
Resolved 💬 5 comments Opened Dec 3, 2025 by remygendron Closed Mar 20, 2026
💡 Likely answer: A maintainer (ccy-oai, contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
codex-cli 0.64.0
What subscription do you have?
PRO
Which model were you using?
gpt-5.1-codex-max
What platform is your computer?
Darwin 23.6.0 arm64 arm
What issue are you seeing?
Thank you for an incredible platform.
Assume that my setup has 'CODEX_HOME' set to the same location for both Codex VSCode and Codex CLI. Verified and confirmed anyway be steps below.
What steps can reproduce the bug?
- Have an agent conversation in Codex VSCode extension.
- Continue conversation in Codex CLI with
codex resume --last - Have a few conversation turns
- Quit Codex CLI with
/quit - Go back to VSCode Codex
- Start new conversation, then open conversation history, and select previous conversation
Actual Results:
- The conversation turns in Codex CLI are not appended to the conversation
- Need to shut down VSCode, restart, and open the previous conversation
- Then, the Codex CLI conversation turns are visible from Codex VSCode
What is the expected behavior?
- Open a conversation
- See all messages nonewithstansd their origin (Codex CLI or Codex VSCode)
- Assume user has defined CODEX_HOME to share ".codex/sessions" storage
Bonus Points:
- Add a refresh button to the chat panel to refresh a conversation, to prevent the need to re-enter a conversation
- Extra bonus points: Codex VSCode should, on window re-activate, check for new messages appended to the conversation from external sources (e.g. Codex CLI)
Additional information
_No response_
5 Comments
The extension doesn't support refreshing CLI conversations currently. The workaround will be to restart your extension.
You can use https://github.com/milisp/codexia
+1 to request refreshing conversations in the extension. (Still an issue with v0.92.0 CLI and v0.4.68 vscode extension.) A form of this bug/missing feature is that if I start a new codex conversation through Codex CLI, then go back to the vscode extension, there is no way to see it in the "task history".
The workaround command seems to be "Developer: Restart Extension Host" which restarts all extensions and is pretty heavyweight. I don't see any way to restart a specific extension (unless it has auto-updated itself and needs a restart, but when there are no updates nothing in the right-click menu looks relevant). I tried to disable-enable it but then I just got a blank screen in the codex panel and had to restart vscode anyway.
This feature request hasn't received enough upvotes, so closing.
upvote. Refreshing(or auto refreshing) should be a basic feature.