What version of the IDE extension are you using?
openai.chatgpt-26.417.40842-darwin-x64
What subscription do you have?
ChatGPT Plus account
Which IDE are you using?
VS Code
What platform is your computer?
No response
What issue are you seeing?
An existing Codex chat thread can become stuck (infinite spinner / unable to load or send) in one workspace, while other chats still work normally.
The same broken thread can be opened successfully in another workspace. If I send a new message there and receive a response, then returning to the original workspace makes the thread work again.
This suggests a thread state / workspace binding / rehydration bug rather than a full extension failure.
What steps can reproduce the bug?
Extension Version
openai.chatgpt-26.417.40842-darwin-x64
Environment
OS: macOS
IDE: VS Code
ChatGPT Plus account
Local workspace folders
What happens
Example scenario:
Chat A originally used in Project X
Chat B originally used in Project Y
Symptoms:
Open Project X + Chat A -> broken (spinner / cannot send / fails to load properly)
Open Project X + Chat B -> works
Open Project Y + Chat B -> broken
Open Project Y + Chat A -> works
Then:
Open Project Y
Open Chat A
Send a message and receive a successful response
Return to Project X
Open Chat A again
Result:
Chat A now works normally in Project X
What is the expected behavior?
Expected behavior
Any existing thread should load consistently in any workspace without entering a stuck state.
Actual behavior
A thread may become unusable only in one workspace until it is "refreshed" by getting a new response in another workspace.
Additional information
Steps to reproduce
I cannot guarantee deterministic reproduction, but the pattern observed was:
Use multiple long-running chats across different projects
Reopen an older chat in its usual workspace
Thread gets stuck loading or sending
Open same thread in another workspace
Send one new message successfully
Return to original workspace
Thread works again
What I already tested
Reload Window
Restart VS Code
Open same project in new VS Code window
Clone project to new path
Uninstall/reinstall extension
These did not permanently fix it.
Suspected cause
Possibly one of:
stale thread/workspace state cache
failed conversation rehydration tied to workspace context
thread metadata mismatch
session state not refreshed until new assistant response arrives
Useful note
Creating a brand new chat in the affected workspace worked normally. Only specific older threads were affected.
What version of the IDE extension are you using?
openai.chatgpt-26.417.40842-darwin-x64
What subscription do you have?
ChatGPT Plus account
Which IDE are you using?
VS Code
What platform is your computer?
No response
What issue are you seeing?
An existing Codex chat thread can become stuck (infinite spinner / unable to load or send) in one workspace, while other chats still work normally.
The same broken thread can be opened successfully in another workspace. If I send a new message there and receive a response, then returning to the original workspace makes the thread work again.
This suggests a thread state / workspace binding / rehydration bug rather than a full extension failure.
What steps can reproduce the bug?
Extension Version
openai.chatgpt-26.417.40842-darwin-x64
Environment
OS: macOS
IDE: VS Code
ChatGPT Plus account
Local workspace folders
What happens
Example scenario:
Chat A originally used in Project X
Chat B originally used in Project Y
Symptoms:
Open Project X + Chat A -> broken (spinner / cannot send / fails to load properly)
Open Project X + Chat B -> works
Open Project Y + Chat B -> broken
Open Project Y + Chat A -> works
Then:
Open Project Y
Open Chat A
Send a message and receive a successful response
Return to Project X
Open Chat A again
Result:
Chat A now works normally in Project X
What is the expected behavior?
Expected behavior
Any existing thread should load consistently in any workspace without entering a stuck state.
Actual behavior
A thread may become unusable only in one workspace until it is "refreshed" by getting a new response in another workspace.
Additional information
Steps to reproduce
I cannot guarantee deterministic reproduction, but the pattern observed was:
Use multiple long-running chats across different projects
Reopen an older chat in its usual workspace
Thread gets stuck loading or sending
Open same thread in another workspace
Send one new message successfully
Return to original workspace
Thread works again
What I already tested
Reload Window
Restart VS Code
Open same project in new VS Code window
Clone project to new path
Uninstall/reinstall extension
These did not permanently fix it.
Suspected cause
Possibly one of:
stale thread/workspace state cache
failed conversation rehydration tied to workspace context
thread metadata mismatch
session state not refreshed until new assistant response arrives
Useful note
Creating a brand new chat in the affected workspace worked normally. Only specific older threads were affected.