openai
VScode codex extension sidebar issue "To continue, return to the window where this conversation started"
What version of the VS Code extension are you using?
v0.4.51
What subscription do you have?
Plus
Which IDE are you using?
VScode 1.107.0
What platform is your computer?
Ubuntu 24.04
What issue are you seeing?
VScode codex extension sidebar issue "To continue, return to the window where this conversation started"
(reverting from v0.4.51, back to v0.4.50, issue not present, although I note that GPT 5.2, only seems available in v0.4.51)
Behaviour up to and including 0.4.50:
- start 2 VScode windows (2 separate Profiles - I have a 'planner' and a 'coder' window)
- start a chat in one VScode window A (profile 'a'), then reload VScode window B (profile 'b'), to continue the chat.
No issues.
Behaviour on v0.4.51:
- start 2 VScode windows (2 separate Profiles - I have a 'planner' and a 'coder' window)
- start a chat in one VScode window A (profile 'a'), then reload VScode window B (profile 'b'), to continue the chat.
- unable to focus the 'ASk for follow-up changes' chat box.
- vscode codex extension sidebar issue "To continue, return to the window where this conversation started"
What steps can reproduce the bug?
Behaviour on v0.4.51:
- start 2 VScode windows (2 separate Profiles - I have a 'planner' and a 'coder' window)
- start a chat in one VScode window A (profile 'a'), then reload VScode window B (profile 'b'), to continue the chat.
- vscode codex extension sidebar issue "To continue, return to the window where this conversation started"
What is the expected behavior?
Behaviour up to and including 0.4.50:
- start 2 VScode windows (2 separate Profiles - I have a 'planner' and a 'coder' window)
- start a chat in one VScode window A (profile 'a'), then reload VScode window B (profile 'b'), to continue the chat.
No issues.
Additional information
VScode:
Version: 1.107.0 Commit: 618725e67565b290ba4da6fe2d29f8fa1d4e3622 Date: 2025-12-10T07:43:47.883Z Electron: 39.2.3 ElectronBuildId: 12895514 Chromium: 142.0.7444.175 Node.js: 22.21.1 V8: 14.2.231.21-electron.0 OS: Linux x64 6.14.0-37-generic
Codex Extension:
Installation Identifier openai.chatgpt Version 0.4.50 Last Updated 1 minute ago Size 84.13MB
System Details Report
Report details
- Date generated: 2025-12-12 13:44:00
Hardware Information:
- Hardware Model: Gigabyte Technology Co., Ltd. X870E AORUS ELITE WIFI7
- Memory: 128.0 GiB
- Processor: AMD Ryzen™ 9 7900X × 24
- Graphics: AMD Ryzen™ 9 7900X
- Graphics 1: AMD Radeon™ Pro WX 3200 Series
- Disk Capacity: 13.0 TB
Software Information:
- Firmware Version: FA6d
- OS Name: Ubuntu 24.04.3 LTS
- OS Build: (null)
- OS Type: 64-bit
- GNOME Version: 46
- Windowing System: X11
- Kernel Version: Linux 6.14.0-37-generic
Side note: I 'think' my VScode also updated today, so not 100% sure if this issue related solely to the extension ~ although it seems like rolling back to extension v0.4.50 on my current version of VScode works fine, so.
If I understand correctly, it sounds like you want to use the same conversation across two separate windows, is that right? If so, I'm somewhat surprised this was working well for you before because once each window opened the conversation, they wouldn't know about subsequent messages sent in the other and would likely start clobbering each other's messages. Did you experience that or am I misunderstanding something?
"If I understand correctly, it sounds like you want to use the same conversation across two separate windows, is that right?":
- yes, that's right, both windows running, but not using the 'same chat' simultaneously in both windows. 2 separate VScode windows, each with it's own Profile. One for 'Planning Tasks/Ideation' (so, primarily GPT 5.1), one for 'Codex/coding' (so primarily GPT 5.1 Codex Max). Slightly different workspace layouts/ pinned files maybe, but mainly for my own sanity and not having to remember to choose which Model I'm tasking all the time.
"If so, I'm somewhat surprised this was working well for you before because once each window opened the conversation, they wouldn't know about subsequent messages sent in the other":
- correct, so a reload of VScode window is required to then bring in the chat to Window 2 (if started in Window 1) and vice versa.
"and would likely start clobbering each other's messages. Did you experience that or am I misunderstanding something?":
- no, I did not experience that (until the VScode update a couple days back, now I've noticed (not the subject of this ticket, but related to your question) chats are simply 'duplicated' for some reason. Not a deal breaker, but inconvenient.
But aside from that, workflow still functions reasonably well as 'planning tasks' and documentation etc on one screen with Kanbn board / GPT 5.1, and code / changes / Codex 5.1 Codex Max on screen 2. Only real bugbear is having to 'reload the window', but that's a quick 'Super+R' keystroke. Benefit for me, is that I don't suddenly realise that Codex Max has been running for 5 minutes....only, it wasn't codex max, it was GPT 5.1....because I forgot to choose the right bloody Model again....;-)
Got it. We're in the process of making this better across the board so that you will be able to maintain both and they will stay in sync. For now, if you reload both windows, the first one will relinquish control and you will be able to resume the conversation from either. Does that work for you for now? I think this will be net-better once the conversation stays fully in sync across both (targeting January)
"Does that work for you for now?":
- Yes, it's working now that I reverted to Extension v0.4.50. The issue is, afaik, only with the extension v0.4.51. I might try updating when there is a v0.4.52 maybe see if it's ironed out then (I see in a quick google search 0.4.52 released yesterday on the 15th, but not yet seeing it available in VScode extension manager).
It will be a few more releases before this exact issue is resolved. For now, if you want to upgrade and use the same conversation in two windows, reload the first one you interacted with the conversation with. We now restrict conversations to be used by a single window so they don't clobber each other but a subsequent update will allow other windows to delegate things like new messages through that first window to work around this.