Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix chatgpt.newChat always opens the primary sidebar even when Codex has been moved to the secondary sidebar in Cursor [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19273•Fetched 2026-04-24 10:39:35
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
tylr2017tylr2017
Participants
tylr2017tylr2017
Timeline (top)
labeled ×2subscribed ×1unsubscribed ×1

In Cursor, after moving the Codex view from the Primary Side Bar to the Secondary Side Bar (right side, same area as Cursor Chat), triggering chatgpt.newChat still opens the left primary sidebar.

This makes the command behave as if Codex were still located in the primary sidebar.

Root Cause

In Cursor, after moving the Codex view from the Primary Side Bar to the Secondary Side Bar (right side, same area as Cursor Chat), triggering chatgpt.newChat still opens the left primary sidebar.

This makes the command behave as if Codex were still located in the primary sidebar.

RAW_BUFFERClick to expand / collapse

What version of the IDE extension are you using?

3.1.15

What subscription do you have?

Cursor Pro

Which IDE are you using?

Cursor

What platform is your computer?

Windows11

What issue are you seeing?

Summary

In Cursor, after moving the Codex view from the Primary Side Bar to the Secondary Side Bar (right side, same area as Cursor Chat), triggering chatgpt.newChat still opens the left primary sidebar.

This makes the command behave as if Codex were still located in the primary sidebar.

Expected behavior

chatgpt.newChat should create a new Codex thread in the existing Codex sidebar location. If Codex is currently in the Secondary Side Bar, it should stay there and should not open the left primary sidebar.

Actual behavior

chatgpt.newChat opens the left primary sidebar, even though Codex has already been moved to the right secondary sidebar.

Environment

  • Cursor
  • OpenAI Codex extension
  • Windows
  • Codex view manually moved to Secondary Side Bar

What steps can reproduce the bug?

  1. Open Cursor.
  2. Move the Codex view from the Primary Side Bar to the Secondary Side Bar.
  3. Make sure Codex is already visible in the right sidebar.
  4. Trigger the chatgpt.newChat command, for example via a custom keybinding like: Ctrl+Alt+N

What is the expected behavior?

chatgpt.newChat should create a new Codex thread in the existing Codex sidebar location. If Codex is currently in the Secondary Side Bar, it should stay there and should not open the left primary sidebar.

Additional information

This appears to be tied to the implementation of chatgpt.newChat, which seems to explicitly open/focus the Codex sidebar container before sending the new-chat action, instead of respecting the current visible location of the Codex view.

extent analysis

TL;DR

The issue can be resolved by modifying the chatgpt.newChat command to respect the current location of the Codex view instead of explicitly opening the primary sidebar.

Guidance

  • Verify that the Codex view is correctly moved to the Secondary Side Bar and visible before triggering the chatgpt.newChat command.
  • Check the implementation of chatgpt.newChat to see if it can be modified to respect the current visible location of the Codex view.
  • Consider adding a conditional statement to check the current location of the Codex view before opening the sidebar.
  • Test the modified chatgpt.newChat command to ensure it creates a new Codex thread in the correct location.

Example

// Pseudo-code example, actual implementation may vary
if (codexViewLocation === 'Secondary Side Bar') {
  // Create new Codex thread in Secondary Side Bar
} else {
  // Create new Codex thread in Primary Side Bar
}

Notes

The exact implementation of the fix will depend on the specific code and functionality of the chatgpt.newChat command and the Codex view.

Recommendation

Apply a workaround by modifying the chatgpt.newChat command to respect the current location of the Codex view, as the issue appears to be tied to the implementation of this command.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

chatgpt.newChat should create a new Codex thread in the existing Codex sidebar location. If Codex is currently in the Secondary Side Bar, it should stay there and should not open the left primary sidebar.

#autograd error#model save/load#optimization#mixed precision#training loop

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix chatgpt.newChat always opens the primary sidebar even when Codex has been moved to the secondary sidebar in Cursor [1 participants]