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
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?
codex resume --last/quitActual Results:
What is the expected behavior?
Bonus Points:
Additional information
No response