Cannot unbind cmd+shift+P "enable plan" command?

Open 💬 8 comments Opened Feb 13, 2026 by gussmith23

What version of the IDE extension are you using?

1.109.2 591199df409fbf59b4b52d5ad4ee0470152a9b31 arm64

What subscription do you have?

plus

Which IDE are you using?

VSCode

What platform is your computer?

Darwin 23.6.0 arm64 arm

What issue are you seeing?

When focused on a Codex window, Cmd+shift+P toggles the "plan" mode. But this is a quite unhelpful binding to override (it opens the command palette normally). I would like a way to disable the keybinding. It doesn't seem to appear in the list of Codex keybindings:

What steps can reproduce the bug?

Create a new Codex agent, focus on the window, and press cmd+shift+P. It will enable the "Plan" setting. I would like to be able to disable or change this to instead open the command palette.

What is the expected behavior?

Allow me to disable/change the shortcut.

Additional information

Thanks so much!

View original on GitHub ↗

8 Comments

justinTM · 5 months ago

Yeah the extension page doesn't even list this under Features > Commands, which is mad annoying since it's THE number one most-used keyboard shortcut in VS Code :/

nicholasjconn · 5 months ago

I have the same issue. It should not reuse by default a prominent VSCode command.

nos1609 · 5 months ago

Same on Windows, and not present in key bindings.
On VSCode this is a highly undesirable behavior, as it intercepts one of the basic keystroke to access Quick Commands palette, thus breaking the "host" UX basic patterns.

billtonium · 4 months ago

Repro confirmed on my setup as well:

VS Code: 1.109.5 (macOS)
Codex extension: 0.4.76
OS: macOS 26.3

Behavior:

With focus inside the Codex panel, Cmd+Shift+P triggers Plan mode instead of opening the VS Code Command Palette.
This shortcut does not appear in VS Code Keyboard Shortcuts, so it cannot be remapped/disabled via normal settings.

Impact:

It blocks a core VS Code workflow in the panel context.
In my case, I needed Command Palette actions (ESLint: Restart ESLint Server, TypeScript: Restart TS Server) and ended up restarting VS Code to recover from stale diagnostics.

Request:

Do not override Cmd+Shift+P by default in the Codex webview/panel, or make the binding discoverable/remappable in VS Code keybindings.

yguedidi · 4 months ago

Same issue for me on Windows.
@codex-maintainers I think this should be a bug, not an enhancement, as it degrades the VS Code usual experience.
Thank you

python273 · 3 months ago

@shijie-oai can you fix this?

CoryLR · 3 months ago

This is indeed a frustrating issue, especially when shift+tab does the exact same thing and is consistent with other agent harnesses.

I’ve tried clobbering Codex’s keybinding by adding to the VS Code keyboard shortcuts JSON with various “when” conditions, including true, but no luck. I’m thinking Codex captures the keypress event and doesn’t even let VS Code see it. Does anyone know a workaround until this issue gets fixed?

yguedidi · 3 months ago

I discovered that F1 also opens the palette, so I started to use it in my dev workflow, as it's a single key in the end