Problems using the CODEX extension in Visual Studio Code
What version of the IDE extension are you using?
4,182,663
What subscription do you have?
Chatgpt Pro Plan
Which IDE are you using?
VC Code
What platform is your computer?
Windows 11 Pro | 26200.7840 | 64-bit operating system, ARM-based processor
What issue are you seeing?
<img width="1822" height="971" alt="Image" src="https://github.com/user-attachments/assets/a15b0bca-f4c8-4ae5-b87f-777dec29b453" />
The extension in VS Code simply stopped working after I closed VS Code and reopened it; nothing appears, it just keeps loading and shows nothing.
I joined a forum where many people are complaining about the same problem.
What steps can reproduce the bug?
I used it for three days straight, day and night, writing code. I reproduced three chats, and they became quite large. Then I closed VC Code, and it stopped working.
I've already tried uninstalling the CODEX agent extension and reinstalling it. I uninstalled VC Code and cleared the entire CODEX and VC Code data folder twice, but it didn't work. The error persists.
What is the expected behavior?
I just wants to open it please with you guys please can help me
Additional information
_No response_
3 Comments
You said that you cleared the codex folder. Is that the
.codexdirectory you're referring to? Deleting (or at least temporarily renaming) that directory is the first thing I'd try.You could also try downgrading to an earlier version to see if this is a regression. You can do this by clicking on the gear icon in the Codex tile of the extensions panel and selecting the "Install Specific Version...".
You mentioned that other users are reporting this in a forum. Is it a public forum? I'm wondering if there might be additional clues to help us figure out the cause.
We are also having issues after the most recent VSCode update yesterday..
For example clicking the Codex: Add to Thread (or any other F1 command related to codex) results in a windows dialogue box along the lines of:
Command 'chatgpt.addToThread' not found.
@a1ultima, can you clarify which version of the extension you are seeing this in? We publish both prerelease and release versions, and it's important that we pinpoint which version where this problem started. Also, the problem you're describing (command not found) doesn't sound like the problem described by the OP in this thread. Why do you think they're related? I recommend that you open a new bug report with full details.