Codex in VSCode never loads
Resolved 💬 5 comments Opened Jul 19, 2026 by BinaryLogicRo Closed Aug 23, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the IDE extension are you using?
26.715.31925
What subscription do you have?
ChatGPT Plus
Which IDE are you using?
VSCode 1.129.1
What platform is your computer?
Linux 6.1.0-51-amd64 x86_64 unknown
What issue are you seeing?
The Codex chat window does not load when activated. It was working perfectly a few days ago. From than until now, I have updated VSCode and the extensions have updated on their own.
What steps can reproduce the bug?
Just open the VSCode and try to open the Codex in sidebar. It shows the logo, but never loads. It does not matter how much you leave it like that.
What is the expected behavior?
Codex chat window opens in sidebar when activated.
Additional information
The OS is Debian 12 KDE.
What steps I have tried:
- uninstalled the extension, closed the VSCode, restart VSCode, retry opening the Codex chat window
- uninstalled the extension, closed the VSCode, I have deleted the
~/.codexfolder, restart VSCode, reinstall the Codex extension, retry opening the Codex chat window
What errors I get in the Output console of Codex:
2026-07-19 17:53:59.428 [info] Activating Codex extension
2026-07-19 17:53:59.428 [info] [CodexMcpConnection] Spawning codex app-server
2026-07-19 17:53:59.428 [info] [IpcRouter] I am the router
2026-07-19 17:53:59.428 [info] [CodexMcpConnection] Initialize received id=1
2026-07-19 17:53:59.428 [warning] [IpcClient] Received broadcast but no handler is configured method=client-status-changed
2026-07-19 17:53:59.428 [warning] [CodexMcpConnection] cli: message="codex_core_plugins::manager: failed to warm featured plugin ids cache error=remote featured plugin request to https://chatgpt.com/backend-api/plugins/featured failed with status 401 Unauthorized: {\"detail\":\"Unauthorized\"}"
2026-07-19 17:53:59.962 [error] [CodexMcpConnection] cli: message="2026-07-19T14:53:59.935567Z WARN codex_core_plugins::manifest: ignoring interface.defaultPrompt[0]: prompt must be at most 128 characters path=file:///home/user/.codex/.tmp/plugins/plugins/ngs-analysis/.codex-plugin/plugin.json\n2026-07-19T14:53:59.937799Z WARN codex_core_plugins::manifest: ignoring interface.defaultPrompt[0]: prompt must be at most 128 characters path=file:///home/user/.codex/.tmp/plugins/plugins/ngs-analysis/.codex-plugin/plugin.json"
If I'm accessing the https://chatgpt.com/backend-api/plugins/featured URL in browser (where I'm logged-in on ChatGPT), it returns valid JSON output:
[
"github@openai-curated",
"slack@openai-curated",
"notion@openai-curated",
"linear@openai-curated",
"datadog@openai-curated",
"statsig@openai-curated",
"gmail@openai-curated",
"google-calendar@openai-curated",
"google-docs@openai-curated",
"google-drive@openai-curated",
"google-sheets@openai-curated",
"google-slides@openai-curated",
"adobe-acrobat@openai-curated",
"teams@openai-curated",
"sharepoint@openai-curated",
"outlook-email@openai-curated",
"outlook-calendar@openai-curated",
"figma@openai-curated",
"datascience@openai-monorepo"
]
5 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
getting same issue on fedora linux VSCode extension
can you try the workaround on the issues i opened: https://github.com/openai/codex/issues/34308 (also https://github.com/microsoft/vscode/issues/326580)
I kept getting this error
[warning] [CodexMcpConnection] cli: message="codex_core_plugins::manager: failed to load recommended plugins error=failed to send remote plugin catalog request to https://chatgpt.com/backend-api/ps/plugins/suggested: error sending request for url (https://chatgpt.com/backend-api/ps/plugins/suggested?scope=GLOBAL)"What worked for me is to start with a clean VS profile, and disable apps and remote plugins in ~/.codex/config.toml:
and then starting from a clean slate:
tested on Linux Mint 22 Cinnamon, VS 1.129.1, Codex 26.5715.61943
After a few days of not working, it seems to have fixed itself. After thta, I no longer see this issue anymore.