Cursor 3.0.4 on macOS: OpenAI Codex sidebar works on primary sidebar but becomes blank/invisible after Move View to Secondary Sidebar

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Issue
After the Cursor update, the Codex sidebar panel no longer works correctly in the Secondary Sidebar.

What happens

If I run View: Reset View Locations, the Codex panel appears normally in the primary (left) sidebar.
However, if I use Move View to move Codex into the Secondary Sidebar (right side), the panel becomes blank / invisible.
Sometimes the right side turns white, but the actual Codex UI does not render.
Reinstalling the Codex extension does not fix it.

Codex only works in the primary sidebar. Moving it to the Secondary Sidebar causes a blank / invisible panel.

Steps to Reproduce

1.Install / enable the OpenAI Codex extension (openai.chatgpt)
2.Open Codex in Cursor
3.Run View: Reset View Locations
4.Confirm Codex displays correctly in the left sidebar
5.Use Move View to move Codex to the Secondary Sidebar
6.Observe that the panel becomes blank / invisible

Expected Behavior

Codex should render normally in the Secondary Sidebar after using Move View.

Operating System

MacOS

Version Information

Cursor Version: 3.0.4 (Stable)
VSCode Version: 1.105.1
Commit: 63715ffc1807793ce209e935e5c3ab9b79fddc80
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
OS: macOS Darwin arm64 25.3.0
Extension: openai.chatgpt
Extension Version: 26.325.31654

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, this is a known issue. The Secondary Sidebar doesn’t correctly support third-party extensions right now. Extensions like OpenAI Codex show up blank when moved there.

For now, the workaround is to use Codex from the primary sidebar (Activity Bar, left panel). The extension itself still works, it’s only the location that’s affected.

Main thread: Secondary Sidebar not supported

The team is aware. There’s no timeline yet, but your report helps with prioritization.

8

Thanks for your reply, I’m happy to known that this is not my own problem, and I really look forward to you having time to fix this issue.