[FEATURE] Built in slashes should appear before user slashes when keywords match

Resolved 💬 3 comments Opened Nov 9, 2025 by danielrosehill Closed Jan 11, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Users might credibly create slash commands that involve phrases that are part of the important ones built into the system.

E.g.:

/new-mcp-server

If you have a few of these they will tend to obscure the system slash of /mcp and it takes a bit of ... thinking to figure out that you need to scroll all the way past the auto-suggestions.

Proposed Solution

One idea (UI):

Different background shading for built in slashes to make them visually obvious as opposed to use added ones

Prefential ordering: as the system slashes (esp MCP) are very important they should always be shown before user slashes regardless of filtering logic

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗