VScode codex extension sidebar issue "To continue, return to the window where this conversation started"

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.

Just came here to say I am affected by the same issue, but under slightly different circumstances...

• I was working within a Folder in VSCode, on a monorepo with three sub-projects. For each sub-project, I had quite an extensive conversation history.
• Since then, I've created a .code-workspace file, to create a Workspace.
• At the same time, I also created a .vscode/devcontainer.json file to launch the project within a Dev Container
• The Dev Container shows two chats, but not the ones related to this workspace.
• Going back to the workspace shows the error "To continue, return to the window where this conversation started"
• I've just closed the workspace and re-opened as a Folder, but am still seeing the same error.

So, now I'm in a situation where I can't continue my chats within VS Code at all, which is a shame because I had some pretty massive chats...

Oh, it looks like the chat got hijacked by the new Codex app, which I installed yesterday. I can continue with my chats there, but not within VS Code. I guess this is expected behaviour until this Issue is addressed?

I was able to work around the issue by downgrading the VS Code extension from 0.4.71/0.4.72 to 0.4.69. Hopefully the Codex team can address this in a future release.

This issue still persists with most recent update 0.4.73.

Same issue here.

Closing as resolved in current releases.