Codex could not start: “The extension couldn't load its resources”
Codex IDE extension (VS Code) — wording from user reports on the openai/codex tracker, not from the docs: the IDE extension is not open source, so there is no source string to quote. A Codex team member did explain it and announce a fix in the closed issue below, and that is what this page relies on.
The message
“The extension couldn't load its resources”
What it means
In issue #37458 users reported that the Codex panel in VS Code failed to start with “Codex could not start. The extension couldn't load its resources.” On 2026-08-11 a Codex team member (alexr-oai) wrote that “a recent change exposed an existing bug that was previously masked” and that a fix was in progress. On 2026-08-13 the same person announced an update that “fixes the startup watchdog issue”, adding that you should no longer see “The extension couldn’t load its resources” simply because application initialization takes longer than 30 seconds.
What you can do
- Update the extension. The team said that after updating you should no longer get this message just because startup is slow, and on 2026-10-27 added that Windows users on Open VSX can now get a version with the startup fix too; check for extension updates in your editor.
- If the extension is still stuck after updating, the team's advice was: “If the extension remains stuck after you update, please check your proxy and VPN settings, and then file a bug report.” The same reply warns that “if an underlying networking or authentication problem was preventing initialization from completing, that will likely still be the case.”
- A different message, “Codex could not start The extension could not start its user interface.”, appears in two open user reports from October 2026 (#57600 and #57762, the second on Windows). As of 2026-11-09 neither had a Codex-team reply, only an automated duplicate-finder comment, so this page cannot say what causes it.
On this site: install Codex CLI · check your Codex usage · did Codex reset today? · OpenAI status
Also searched as
People look this message up in several ways. These are search wordings, not OpenAI's text:
- Codex could not start. The extension couldn't load its resources.
- Codex could not start The extension could not start its user interface.
The first is how issue #37458's report words the failure. The second is the title of open user report #57600 and is a separate message.
Sources
- openai/codex issue #37458 (a user report, closed, with Codex-team replies) — fetched 2026-11-09
- openai/codex issue #37517 (a user report, closed as a duplicate of #37458) — fetched 2026-11-09
- openai/codex issue #57600 (a user report, open) — fetched 2026-11-09
- openai/codex issue #57762 (a user report, open) — fetched 2026-11-09
This site is not affiliated with OpenAI. Where a statement above comes from a user report or a reply on the openai/codex issue tracker rather than documentation, it says so.
Frequently asked questions
Why does Codex say “could not start” and “The extension couldn't load its resources”?
In the closed issue #37458 a Codex team member said a recent change exposed an existing bug and later said the startup watchdog issue was fixed, so the message no longer appears just because initialization takes longer than 30 seconds. The same reply says a networking or authentication problem that stops initialization from finishing may still be there.
How do I fix “Codex could not start” in VS Code?
Update the Codex extension first; the team said the fix shipped in an update. If it is still stuck, the team's advice was to check proxy and VPN settings and then file a bug report on the openai/codex tracker. No docs page covers this message.
Is “The extension could not start its user interface” the same Codex error?
It is a different message. It appears in open user reports (#57600 and #57762) that had no Codex-team reply as of 2026-11-09, so its cause is not stated anywhere official.