Codex panel stays loading indefinitly

Resolved 💬 3 comments Opened Jun 19, 2026 by AFCMS Closed Jul 6, 2026

What version of the IDE extension are you using?

26.616.32156

What subscription do you have?

Plus

Which IDE are you using?

VSCode 1.125.1

What platform is your computer?

Linux 7.0.12-201.fc44.x86_64 x86_64 unknown

What issue are you seeing?

The Codex panel stays loading indefinitely with a horizontal overflow (scrollbar).

It started to happen within the last few days. I have tried using the pre-release version of the extension as well as the insider version of VSCode without sucess. I have also tried clearing my .codex folder.

It's not a remote only scenario like other similar reported issues.

<img width="1202" height="801" alt="Image" src="https://github.com/user-attachments/assets/b017086d-81be-42dd-832c-85708ec83a11" />

The output logs (same after and before clearing .codex):

2026-06-19 21:50:51.500 [info] Activating Codex extension
2026-06-19 21:50:51.500 [info] [CodexMcpConnection] Spawning codex app-server
2026-06-19 21:50:51.500 [info] [IpcRouter] I am the router
2026-06-19 21:50:51.500 [info] [IpcRouter] I am the router
2026-06-19 21:50:51.500 [info] [IpcRouter] I am the router
2026-06-19 21:50:51.500 [warning] [IpcClient] Received broadcast but no handler is configured method=client-status-changed
2026-06-19 21:50:51.555 [info] [CodexMcpConnection] Initialize received id=1
2026-06-19 21:50:52.013 [error] [CodexMcpConnection] cli: message="2026-06-19T19:50:51.956197Z  WARN codex_core_plugins::manifest: ignoring interface.defaultPrompt[0]: prompt must be at most 128 characters path=/home/afcm/.codex/.tmp/plugins/plugins/ngs-analysis/.codex-plugin/plugin.json\n2026-06-19T19:50:51.956907Z  WARN codex_core_plugins::manifest: ignoring interface.defaultPrompt[0]: prompt must be at most 128 characters path=/home/afcm/.codex/.tmp/plugins/plugins/ngs-analysis/.codex-plugin/plugin.json"

What steps can reproduce the bug?

Install the latest VSCode and the latest version of the extension (?)

What is the expected behavior?

I would expect the extension to work properly.

Additional information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗