VS Code extension slash skill picker only works once per message, unlike Codex app
Resolved 💬 4 comments Opened Mar 19, 2026 by liqiang311 Closed Mar 26, 2026
What version of the IDE extension are you using?
openai.chatgpt-26.313.41514
What subscription do you have?
Enterprise
Which IDE are you using?
VS Code
What platform is your computer?
Darwin 25.3.0 arm64 arm
What issue are you seeing?
Summary
In the Codex VS Code extension, I can use / to select one skill, but after inserting the first skill, typing / again in the same message does not open the skill picker anymore.
This is inconsistent with the Codex app, where I can select multiple skills in the same message using /.
Environment
- Product: Codex VS Code extension
- Extension version: openai.chatgpt-26.313.41514
- IDE: VS Code / Cursor
- Date observed: March 19, 2026
- Workspace type: local project
- Account: same account used in both Codex app and VS Code extension
What steps can reproduce the bug?
Steps to reproduce
- Open the Codex panel in the VS Code extension.
- Start a new message in the composer.
- Type
/and select a skill. - Continue typing in the same message.
- Type
/again to select a second skill.
What is the expected behavior?
Expected behavior
- The slash skill picker should open again, so I can insert a second skill in the same message.
- Behavior should match the Codex app.
Actual behavior
- After the first skill is inserted, typing
/again does not show the skill picker. - As a result, I cannot select a second skill via slash in the same message.
Additional information
Notes
- This appears to be specific to the VS Code extension UI/composer behavior.
- The same workflow works in the Codex app with the same account and skill set.
- Skills themselves are available; the issue seems to be with repeated slash-triggered selection in the extension composer.
Impact
- Multi-skill prompting is harder in the VS Code extension.
- This creates inconsistent behavior between Codex app and Codex IDE extension.
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗