When will this get fixed??
Anybody solved this problem yet?? Still getting this…
With CLI (WSL), I can sign in but eventually it fails to connect to anything on localhost:1445 and returns 404…
Any one solved this problem?
I have encountered the same error after clicking the [Sign in with ChatGPT] button :
failed to start login server: An attempt was made to access a socket in a way forbidden by its access permissions. (os error 10013)
2 Likes
Today, when I tried to resume working with my current workflow — with the CHATGPT macOS app and the VSCode extension connected via SSH to the dev server — I couldn’t get it to sync. I’m getting the ‘No workspace available’ error. Has anyone figured this out? Tx in advance!
1 Like
It’s really disappointing that there’s no support for JetBrains IDEs yet.
IntelliJ, PyCharm, WebStorm and the rest of the suite are massively popular and widely used by developers worldwide. Leaving them out feels like a huge gap, especially since so many teams and companies rely heavily on JetBrains tools for their daily workflows.
Hopefully official support comes soon, because this is too big of a platform to overlook.
3 Likes
This worked for me… finally
npm uninstall -g @openai/codex
npm install -g @openai/codex@0.1.2505172129
- This allowed me to login under codex in a windows terminal, after clearing the blocked port (1455 in my case). If you have a blocked port - open cmd as admin
netstat -ano | findstr :1455
response: TCP 0.0.0.0:1455 0.0.0.0:0 LISTENING 5588 –> this is the task I had to kill
kill the task to release the port OpenAI needs:
taskkill /PID 5588 /F
After that I was able to login to the old version of Codex in a windows terminal.
Then when I opened the new Codex extension in VSCode - I was already logged in / authenticated.
I believe the problem was the req login port was blocked and OpenAI just didn’t say it needed that port. I had to jump through these hoops to figure that out, kill the process using the port, then login w/ the terminal version, and after that was authenticated I was free to use the extension.
1 Like
We need IntelliJ plugin !
4 Likes
How do we get websearch to work for the ide extension? I’ve tested it and indeed the config.toml works to enable it for the cli version, and changing from gpt-5-codex to gpt-5 changes the toml. However no matter how hard i try to prompt it, it won’t use any tool calling for search.
After more than a month, codex still doesn’t work for me (both VSCode extension and CLI in WSL). Keep getting the error when trying to login. And I don’t have anything listening on 1455… (ran netstat to check).
I also encountered the same problem and would like to ask for advice. Has this problem been solved
Is there a plan for a Codex extension in Visual Studio? Would be amazing to see Visual Studio get the same kind of extension support as our VS Code pals