Not show command on codex

[joaosantanadev]

Hello,

After restarting VS Code today, the OpenSpec commands are no longer appearing (see the attached screenshot).

I’ve already tried removing and reinstalling the OpenSpec extension, but the issue persists.

Before the restart, everything was working normally.

Steps already tried:

Restarted VS Code

Uninstalled and reinstalled the OpenSpec extension

Please let me know if there’s anything else I can check or if additional information is needed.

[TabishB]

@joaosantanadev Hmm yeah sometimes slash command loading by a lot of the tools (even claude code) is a little flaky.

A few things that can help:

• just waiting a few seconds after restarting vs code, the extensions like codex can sometimes load these at weird times.
• checking the global codex directory to inspect to see if the commands exist
• creating a temporary slash command in codex to see if this comes up

[TabishB]

@joaosantanadev If you still end up having issues, just ping me on discord to take a closer look. (Hopping on a 14hr flight soon so might take a while to get resolved, sorry!)

[joaosantanadev]

@TabishB

The error persisted because VS Code was still attempting to register a stale claude-code chat participant, likely coming from cached data in globalStorage / workspaceStorage.

To fully resolve the issue, I had to:

Delete Code/User/globalStorage

Delete Code/User/workspaceStorage

Delete the project-level .vscode/settings.json

After removing the project .vscode/settings.json as well, the chatParticipant must be declared in package.json: claude-code error stopped appearing, and slash commands (including OpenSpec) started working again.

This seems to be a VS Code Chat API caching/state issue rather than an OpenSpec or workspace configuration problem.