Feature Request: Separate /-prefix (commands) from skills/agents picker (Codex-style)
Resolved 💬 3 comments Opened May 13, 2026 by danwan Closed May 17, 2026
Motivation
Currently, the / prefix in Claude Code shows a mixed list of:
- Built-in slash commands (
/help,/clear,/config,/loop, …) - User-defined slash commands
- Skills (auto-installed + plugin-provided)
- Agents / subagents
With many plugins/skills installed (superpowers, pr-review-toolkit, coderabbit, memsearch, frontend-design, skill-creator, …) the / menu becomes very long and hard to scan. Finding a built-in command means scrolling past dozens of skills.
The wording in claude --help reinforces that skills and slash commands share the same pipeline:
--disable-slash-commandsis documented as "Disable all skills"--baresays "Skills still resolve via/skill-name"
That is a deliberate design choice — but as the skill ecosystem grows it becomes a discoverability problem.
Proposed Solution
Adopt a prefix separation similar to OpenAI Codex CLI:
/→ only built-in + user-defined slash commands$(or another prefix like@@) → Skills and/or agent picker (own namespace)
The @ prefix is already taken in Claude Code (file references), so $ is the obvious free key.
Benefits
- Clean, predictable
/menu — easy to find built-ins again - Faster category-based discovery
- Clearer mental model: commands vs extensions
- Plugin authors still get a first-class entry point (just under a different prefix)
Alternatives considered
skillOverrides: "off"per skill — works, but is opt-out per skill and removes them entirely (no picker entry at all). Doesn't solve discoverability; it solves clutter only by deletion.- Disabling whole plugins via
enabledPlugins— same issue, all-or-nothing. - A simple toggle / settings flag (e.g.
skillsInSlashPicker: false) would already be enough — doesn't have to be a new prefix.
Example
/ → /help, /clear, /config, /loop, /review, /plugin, …
$ → memsearch:memory-recall, coderabbit:code-review, superpowers:*, …
Environment
- Claude Code CLI
- macOS 15.5.0
- Many plugins installed via the official marketplace
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗