Видел такое же обращение два дня назад, вопрос так и не решили( я думаю так-же столкнулся бы с этой проблемой вчера, если бы вчера поставил новое обновление ). Странно , что через Visual Studio Code , происходит тоже самое и он перестаёт отвечать, а потом закрывается с ошибкой , а чат с ним не открывается вовсе ..
I saw the same request two days ago; the issue still hasn’t been resolved (I think I would have run into this problem yesterday as well if I had installed the new update yesterday). It’s strange that the same thing happens through Visual Studio Code—it stops responding and then closes with an error, and the chat with it doesn’t open at all..
Thanks for noting this detail.
I also use Codex, not the Windows Desktop app, with VSCode on Windows and VSCode and Codex are working fine for me.
In vscode .. reinstalling the codex extension does not work, restarting doesn’t and reinstalling leads to the same problem with the hanging page..
BUT: when i click on cursor app extension then and then click back on codex extension tab it works.
It seems like you have to tell it “if you don’t come up immediatly then I go to another thing…”
Sorry, I fully understand what this means to you .. we all have to finish stuff.
Take an hour or so and try again.. I am sure it will just go away. Do the other stuff you know you have to do. Call your mom and clean the dishes, do the laundry and take a shower and a walk!
Sam problem, happened after I did to update and has been broken since then. Does not open in Antigravity either. Been very frustrated with Claude code since opus 4.7 came out, made the decision to move everything to codex today and I can’t.
The problem is actually related to port 1455. If you are using that in VS Code or others (check port forwarding), and at the same time trying to authenticate using Codex, the browser tab that does the authentication doesn’t open. Make sure you release the port first and then try again. It should work.
For those looking to delete the ~/.codex directory, consider renaming the directory instead to something like ~./codex_original as Codex might create a new ~/.codex directory and you will not lose the valuable information in the directory.
If the new directory works, then do a diff or such and start to bring over the existing data until you possibly find the problem.
Also, I tried again this morning and same problem, I pulled up task manager and watch codex and the memory usage just continued to grow until I ended the process was using over 1Gb of ram when stopped it.