Bug:Vscode Keyboard Shortcut "chatgpt.sidebarView.focus" work badly on the newest version of Codex plugin

Resolved 💬 12 comments Opened Jan 30, 2026 by mistcoversmyeyes Closed Feb 18, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the VS Code extension are you using?

v0.4.68

What subscription do you have?

GPT Teams

Which IDE are you using?

VsCode

What platform is your computer?

Linux 6.6.87.2-microsoft-standard-WSL2 x86_64 x86_64

What issue are you seeing?

As Soon as I've updated to v0.4.68, when i use keyboard shortcut focus on the sidebar of codex, it can't automatically display the cursor in the input box (exactly can't type anything until I click the input box) appear like this:

<img width="626" height="290" alt="Image" src="https://github.com/user-attachments/assets/a0cc5729-55da-4f08-8f3a-c70e69c375f9" />

The right response should appear like this:

<img width="639" height="273" alt="Image" src="https://github.com/user-attachments/assets/8828cb72-0b95-4833-a4b9-3632f17c4672" />

As soon as I downgrade the version of plugins to v0.4.47 , the bug don't appear anymore.

What steps can reproduce the bug?

Use the vscode plugin v0.4.68 , and put codex view to the right sidebar. Then close the right sidebar and use Vscode commant User View Container: Focus on Codex View trying to open the sidebar view of codex. Then try to enter some chapter , you will find out that no chapter was entered into the input box and cursor don't appear in the input box.

What is the expected behavior?

It works the same as v0.4.67.

Additional information

_No response_

View original on GitHub ↗

12 Comments

github-actions[bot] contributor · 5 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #7925

Powered by Codex Action

pmallek · 5 months ago

I have the same problem. It's pretty annoying. Hopefully it can be resolve soon, thanks.

d-w-d · 5 months ago

This has completely broken my workflow! I had keybindings nicely set up, I was jumping back and forth between the text editor and codex-chat really fluently, and now I have to mess with the mouse EVERY TIME I want to jump into codex on vscode!

Please sort out the keybindings and then NEVER touch them again! Having to get back into the mental space of re-setting up keybindings is so deflating to a developer's sanity!

shijie-oai contributor · 5 months ago

Hi all! Thanks for reporting! I have a fix in the pipeline and I will report back when that is fixed. Sorry about the inconvenience.

emilaxelsson · 5 months ago

I noticed that "Codex: Focus on Codex View" usually causes the plus button (add files) to be focused. During a few days I was able to get by by pressing Shift+Tab to get to the input box. However, now there seems to be a different key binding at play: Shift+Tab toggles planning mode, so it's no longer possible to use it to jump back to the input box.

rammah-cmc · 5 months ago

Any updates? I'm still facing this issue

pmallek · 5 months ago

still not fixed...

d-w-d · 5 months ago

I'm surprised how little attention this is getting from the community. Am I the only developer in the world who uses codex in VSCode? Am I missing something? Perhaps there is afresh updated guide on how to set up keybindings so that one can jump between the codex chat and the text editor panes just like one can easily do in Windsurf, Cursor, etc.

I hate having to switch IDEs all the time, but I will have to consider going back to windsurf, etc. soon.

etraut-openai contributor · 5 months ago

The fix was merged and will be included in the next release, hopefully later today.

shijie-oai contributor · 5 months ago

Hi all! Just a quick update - the fix has been merged and should be included in the next release.

shijie-oai contributor · 5 months ago

Thanks for your patience! We have just released 0.4.76 and that includes the fix. Please let us know if there is any more issues.

d-w-d · 4 months ago

Is there no longer an explicit do-not-make-edits/planning mode?