Codex sidebar fails to open in TRAE: missing command workbench.view.extension.codexSecondaryViewContainer
Resolved 💬 5 comments Opened Mar 25, 2026 by stephenlzc Closed Apr 4, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
Codex IDE extension from OpenAI (@ext:openai.chatgpt) in TRAE (VS Code fork).
Which model are you using?
N/A (UI fails before usable thread/sidebar interaction).
What operating system are you using?
macOS
Reproduction steps
- Install the official OpenAI Codex extension in TRAE.
- Open Command Palette and run
Codex: Open Codex Sidebar. - Observe no sidebar opens (no visible UI response).
- Check extension output/logs.
Expected behavior
Codex sidebar should be focused/opened successfully.
Actual behavior
No sidebar opens. Logs repeatedly show IPC warnings and explicit view-focus errors:
[warning] [IpcClient] Received broadcast but no handler is configured method=thread-stream-state-changed
[error] Failed to focus Codex view error="command 'workbench.view.extension.codexSecondaryViewContainer' not found"
Logs
Key errors (timestamps in Asia/Shanghai, UTC+8):
2026-03-26T00:01:01.936+08:00 [error] Failed to focus Codex view error="command 'workbench.view.extension.codexSecondaryViewContainer' not found"
2026-03-26T00:01:04.904+08:00 [error] Failed to focus Codex view error="command 'workbench.view.extension.codexSecondaryViewContainer' not found"
2026-03-26T00:04:02.332+08:00 [error] Failed to focus Codex view error="command 'workbench.view.extension.codexSecondaryViewContainer' not found"
2026-03-26T00:04:18.067+08:00 [error] Failed to focus Codex view error="command 'workbench.view.extension.codexSecondaryViewContainer' not found"
2026-03-26T00:05:14.963+08:00 [error] Failed to focus Codex view error="command 'workbench.view.extension.codexSecondaryViewContainer' not found"
2026-03-26T00:05:33.884+08:00 [error] Failed to focus Codex view error="command 'workbench.view.extension.codexSecondaryViewContainer' not found"
Also repeated throughout:
[warning] [IpcClient] Received broadcast but no handler is configured method=thread-stream-state-changed
Notes
This appears to be an IDE-compatibility issue in a VS Code fork where the extension expects a command id that is not available.
5 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Triage note after duplicate check:\n- Potentially related: #15397 (same broadcast warnings), but that report is focused on event-storm/high CPU in VS Code.\n- Potentially related historical UI regression: #14705 (closed; sidebar icon disappearance after VS Code 1.111.0).\n\nI am keeping this issue open for now because the core failure here is distinct and reproducible in TRAE: , which prevents opening/focusing the Codex sidebar at all.
Correction (previous comment had shell-escaping artifacts):
Triage after duplicate check:
thread-stream-state-changedbroadcast warnings), but that report focuses on event-storm/high CPU in VS Code.Keeping this issue open for now because the core failure here is distinct and reproducible in TRAE:
command 'workbench.view.extension.codexSecondaryViewContainer' not foundwhich prevents opening/focusing the Codex sidebar at all.
Reproduced here as well on Linux in Trae.
Environment:
What I verified locally:
Relevant logs from Trae:
From renderer.log:
From Codex.log:
Manifest details from the installed extension show that it contributes both:
This strongly suggests a compatibility issue with Trae's handling of
secondarySidebarcontainers. In this environment, the extension should probably fall back to the normal sidebar/activitybar path whensecondarySidebaris unavailable.I also tested a local patch that forces the extension down the non-secondary-sidebar path, and that appears consistent with the root cause. So this does not look like a failed install or failed Codex process startup; it looks specifically like a view-container compatibility problem in Trae.
The Codex IDE Extension installs and works fine in VS Code and other forks thereof (including Cursor, Windsurf, and Codium). If it's not working in TRAE, then it's likely due to some incompatibility in that fork. Please work with the maintainers of TRAE to diagnose the issue.