Slash commands not discovered in Gemini/Codex/Qwen (only speckit.constitution visible), while Claude Code shows all

[Scoheart]

Summary

When using Spec-Kit with Gemini CLI and Codex CLI, only the command speckit.constitution is discovered in the slash menu. Other core commands such as speckit.specify, speckit.plan, speckit.tasks, and speckit.implement are not shown, making it impossible to run the full Spec-Kit workflow with these tools.
In contrast, Claude Code correctly discovers and runs the full set of /speckit.* commands in the same project.

Output

gemini & qwen ...

> /speckit.implement

✕ Unknown command: /speckit.implement

Environment

 ~/ uv tool list
specify-cli v0.0.18
 ~/ gemini --version
0.8.1
 ~/ codex --version
codex-cli 0.46.0
 ~/ claude --version
2.0.11 (Claude Code)
 ~/ qwen --version
0.0.14

[outp1]

There could be a problem with how you initialized spec-kit.

Start a new project and initialyze spec-kit choosing claude code as a code agent.

Then you need to check output of the ls -a .claude/commands/ command ran from your project directory. If commands files are there, problem is likely to be with your code agent tool.

[bailiangcn]

Copy the commands below the existing normal .qwen\commands to the .qwen\commands of the newly created project, and start the qwen cli to see the commands

[frizikk]

I have the same problem in gemini / copilot

[lisovyk]

Similar problem for me, no commands are discovered in VS code in new project.

[hsin19]

Gemini slash commands are failing because \ in the generated TOML files are not escaped.

Quick workaround: replace \ to \\ in .gemini/commands/*.toml

[svrhovac]

This was cause in in my case.
Changing from '' to \' in .toml files solved it.

[localden]

Latest release fixes the TOML issue, so it should work.