Qwen CLI slash commands

[mhenke]

The Qwen Code CLI v1.1.1 the slash commands don't match the notes from openspec init

 mhenke@IdeaPad  ~/Projects/start-spec-driving   main  openspec --version
1.1.1

OpenSpec Installation

OpenSpec Setup Complete

Created: Qwen Code
10 skills and 10 commands in .qwen/
Config: openspec/config.yaml (exists)

Getting started:
  /opsx:new       Start a new change
  /opsx:continue  Create the next artifact
  /opsx:apply     Implement tasks

Learn more: https://github.com/Fission-AI/OpenSpec
Feedback:   https://github.com/Fission-AI/OpenSpec/issues

Restart your IDE for slash commands to take effect.

Using Qwen CLI

mhenke@IdeaPad  ~/Projects/start-spec-driving   main  qwen


   ▄▄▄▄▄▄  ▄▄     ▄▄ ▄▄▄▄▄▄▄ ▄▄▄    ▄▄   ╭──────────────────────────────────────────────────────────╮
  ██╔═══██╗██║    ██║██╔════╝████╗  ██║  │ >_ Qwen Code (v0.9.1)                                    │
  ██║   ██║██║ █╗ ██║█████╗  ██╔██╗ ██║  │                                                          │
  ██║▄▄ ██║██║███╗██║██╔══╝  ██║╚██╗██║  │ Qwen OAuth | coder-model (/auth to change)               │
  ╚██████╔╝╚███╔███╔╝███████╗██║ ╚████║  │ ~/Projects/start-spec-driving                            │
   ╚══▀▀═╝  ╚══╝╚══╝ ╚══════╝╚═╝  ╚═══╝  ╰──────────────────────────────────────────────────────────╯

  Tips: Switch auth type quickly with /auth.
  ℹ[workspace] Successfully migrated 10 command files to Markdown format. Original files backed up as
    .toml.backup

───────────────────────────────────────────────────────────────────────────────────────────────────────────────
> /opsx
───────────────────────────────────────────────────────────────────────────────────────────────────────────────
  opsx-verify        Verify implementation matches change artifacts before archiving
  opsx-sync          Sync delta specs from a change to main specs
  opsx-onboard       Guided onboarding - walk through a complete OpenSpec workflow cycle with narration
  opsx-new           Start a new change using the experimental artifact workflow (OPSX)
  opsx-ff            Create a change and generate all artifacts needed for implementation in one go
  opsx-explore       Enter explore mode - think through ideas, investigate problems, clarify requirements
  opsx-continue      Continue working on a change - create the next artifact (Experimental)
  opsx-bulk-archive  Archive multiple completed changes at once

[1code-async]

Task completed.

The enrichment comment has been posted on issue #680. Here's a summary of what was found:

Two problems identified:

1. Command naming mismatch — The openspec init success message (src/core/init.ts:574-576) and welcome screen (src/ui/welcome-screen.ts:28-30) always show colon-separated commands (/opsx:new), but Qwen CLI uses hyphenated names (opsx-new). A transformToHyphenCommands() utility exists but is only applied for the opencode tool, not Qwen.

2. Missing opsx-apply — The command template exists in the codebase but doesn't appear in the user's Qwen CLI output, suggesting either a file write issue or a Qwen CLI loading issue.

6 related issues were linked, including the previously closed #591 which addressed the same category of tool-specific command naming problems.

---

View full conversation

Powered by 1Code

[1code-async]

Issue Analysis

There are two distinct problems reported here:

1. Command naming mismatch: /opsx:new vs opsx-new

The openspec init success message always displays colon-separated commands (/opsx:new, /opsx:continue, /opsx:apply), but Qwen CLI renders them with hyphens (opsx-new, opsx-continue, etc.).

Root cause: The success message in displaySuccessMessage() is hardcoded with colon syntax and does not adapt to the target tool's naming convention.

• Hardcoded output — src/core/init.ts:574-576:

  /opsx:new       Start a new change
  /opsx:continue  Create the next artifact
  /opsx:apply     Implement tasks
  

• Welcome screen also hardcodes colon syntax — src/ui/welcome-screen.ts:28-30

Meanwhile, the Qwen adapter generates files as opsx-<id>.toml (hyphen-separated) — src/core/command-generation/adapters/qwen.ts:19:

return path.join('.qwen', 'commands', `opsx-${commandId}.toml`);

A transformToHyphenCommands() utility exists at src/utils/command-references.ts:18-20 that converts /opsx: → /opsx-, but it is currently only used for the opencode tool (src/core/init.ts:445, src/core/update.ts:122), not for Qwen or other tools that use hyphenated command filenames.

The post-init success message and welcome screen don't account for the selected tool at all — they always show colon syntax regardless of which tool(s) were configured.

2. Missing opsx-apply command

The user's Qwen CLI output shows 8 commands but opsx-apply is not listed among them, despite being generated by the command system. The command template exists in src/core/shared/skill-generation.ts:74 and the full template is at src/core/templates/skill-templates.ts:1851-1900. This may be a Qwen CLI-side issue where the command was not loaded, or there could have been a file write failure during init that went unreported.

Additional observation

The issue title mentions "Qwen CLI v1.1.1" but the Qwen CLI banner in the screenshot shows v0.9.1. This version discrepancy may be relevant.

---

Related issues

• Bug: OpenSpec generates unsupported commands/opsx for Windsurf/Cursor #591 (closed) — "OpenSpec generates unsupported commands/opsx for Windsurf/Cursor" — same category of tool-specific command naming issues
• Bug Report: Copilot-CLI doesn't recognize slash commands #362 — "Copilot-CLI doesn't recognize slash commands"
• Factory Droid doesn't respect the slash command #232 — "Factory Droid doesn't respect the slash command"
• Slash command are not installed in Claude Code init #143 — "Slash commands are not installed in Claude Code init"
• /opsx-explore behavior #668 — /opsx-explore behavior issues
• Agent does not ask for /ospx-continue #663 — Agent does not ask for /ospx-continue (note: also contains a typo ospx vs opsx, suggesting naming confusion)

Suggested fix approach

1. Make displaySuccessMessage() in src/core/init.ts tool-aware: when the configured tool(s) use hyphenated commands, display the matching format (or show both if multiple tools with different conventions are configured).
2. Apply the same logic to getWelcomeText() in src/ui/welcome-screen.ts.
3. Consider whether transformToHyphenCommands should be applied to Qwen skill content (currently only applied for opencode), since Qwen also uses hyphenated file names.