Update broke Codex IDE extension in codeserver environment

Resolved 💬 1 comment Opened Feb 10, 2026 by WhammyLeaf Closed Feb 10, 2026

What version of the IDE extension are you using?

0.4.71

What subscription do you have?

API access token

Which IDE are you using?

VS Code

What platform is your computer?

Linux 5.15.0-305.176.4.el8uek.x86_64 x86_64 x86_64

What issue are you seeing?

The Codex extension does not currently seem to work in a codeserver environment. The extension gets stuck during initialization and the output panel produces the following:

2026-02-10 16:38:34.682 [info] Activating Codex extension
2026-02-10 16:38:34.682 [info] [CodexMcpConnection] Spawning codex app-server
2026-02-10 16:38:34.682 [info] [IpcRouter] I am the router
2026-02-10 16:38:42.180 [error] [persisted-atom] host did not respond to sync request; continuing with legacy state only
2026-02-10 16:38:45.957 [info] [CodexMcpConnection] Initialize received (id=1)
2026-02-10 16:38:45.958 [error] [CodexMcpConnection] CLI: string(len=449)

This error was introduced with version 0.4.69 of the Codex extension. Everything works as expected with version 0.4.68

What steps can reproduce the bug?

  1. inside a codeserver environment install codex with npm i -g @openai/codex
  2. setup access via access API key.
  3. install Codex extension with version > 0.4.68
  4. observe Codex extension being stuck during initialization

What is the expected behavior?

For the Codex extension to start up normally and provide the user with an interface to type, manage conversations, etc.

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗