I’ve been using the Codex extension for VS Code inside a Docker container, so it is not installed on my local machine. After updating to version 26.825.51511, I could no longer open the Codex tab in the VS Code window. The tab would appear, but it would not start properly.
After a quick search and testing, I found that downgrading the extension resolved the issue. I reverted to the previous version and the Codex tab started working normally again.
This may be helpful for anyone else who encounters the same problem after updating the extension in a containerized VS Code environment. If the tab fails to launch after an update, downgrading is a practical workaround until the issue is fixed in a newer release.
You are welcome to discuss Codex issues here. However, the official place to report and track Codex bugs is the OpenAI Codex GitHub issue tracker.
I asked ChatGPT to search for the closest related issue, and it identified:
If that issue describes the same problem you are experiencing, consider adding a reaction to the GitHub issue itself, rather than only reacting to this forum topic. GitHub reactions can help the maintainers gauge how many users are affected.
If it does not match your problem closely enough, search the existing Codex issues for a better match. If you cannot find one, consider opening a new issue and include as much relevant information as possible, such as your Codex version, operating system, environment, reproduction steps, expected behavior, actual behavior, and any relevant logs or error messages.
Experiencing the same issue, codex extension fails to boot in latest cursor versions
Remote activation fails with SyntaxError: Unexpected identifier 'p' at generated code using using p, because Cursor’s remote server runs embedded Node v22.22.1. The container’s system Node is newer, but is not used by the remote extension host. Rebuilding the container does not help because ~/.cursor-server is persisted via the host-mounted ~/.cursor directory. Stable and prerelease Codex packages show the same failure.
Hi @joanna.sousa, welcome and thanks for the report! The error you shared matches an issue we’re working on a fix for, and I’m sorry for the disruption.
In the meantime, we highly recommend updating Cursor. If you can’t update, or updating doesn’t help, roll back the Codex extension to stable version 26.825.51511 (released August 30, 2026). Make the change in the connected dev container window. You don’t need to change the container’s system Node.
We’ll post updates in GitHub issue #42663.
reaction to the GitHub issue itself, rather than only reacting to this forum topic. GitHub reactions can help the maintainers gauge how many users are affected.