Oops, an error has occurred, Try again*
What version of the VS Code extension are you using?
Cursor Version: 2.2.43 VSCode Version: 1.105.1 Electron: 37.7.0 Chromium: 138.0.7204.251 Node.js: 22.20.0 V8: 13.8.258.32-electron.0 OS:
What subscription do you have?
pro
Which IDE are you using?
Cursor
What platform is your computer?
Darwin arm64 25.1.0
What issue are you seeing?
Dear community and Open AI stuff, we need your help, please do not close the issue until we collect enough information from the users to catch the bug that is really annoying. I understand, that your goal is to close issues as fast as you can, but we have not enough info to prepare complete bug report.
"Oops, an error has occurred" and "Try again" button on white background
What steps can reproduce the bug?
When using Codex Extension, regular development and tasks, as usual, some times small, some times bigger getting "Oops, an error has occurred" and "Try again" button on the white background.
It is not clear enough how to reproduce the bug, but it happen to me 3-4 times yesterday and 2 times already today,
What is the expected behavior?
"Try again" button reload the extension properly without reloading IDE completely
Additional information
How to resolve? completely reload IDE only helps
Which is really annoying as far we are using different free and paid CLI and extensions, and some times you need to wait till accomplish the task within that particular CLI (aka Claude).
This is causing next thing - when you are waiting for Claude to reload, you work with Codex, then Codex crashed, and whole progress stops, because you can not reload IDE, as far. you would lose the progress you made with Claude, and Codex is stack on this "Oops, an error has occurred" state.
and "Try again" button literally do nothing
If this is something that Open AI do to "help developers" to not use other AI's, this is not a fair for developers. You have to fight different way.
If you could instruct me where to get logs, i would gladly provide them, if they even exist.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗