[Feature Request] Show custom Slash Commands at the top of the "/" picker, before built-in sections

Resolved 💬 1 comment Opened May 3, 2026 by info-codelta Closed Jun 2, 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

[Feature Request] Show custom Slash Commands at the top of the "/" picker, before built-in sections

Summary

When opening the / command picker in the Claude Code VSCode Extension, built-in sections (Context, Model, Customize) always appear above custom Slash Commands. There is no way to reorder sections or surface custom commands without typing filter characters first. This creates unnecessary friction for users who rely heavily on custom slash commands as their primary workflow interface.

---

Current behavior

Clicking / in the chat input opens a picker with the following fixed order:

  1. Context — Attach file, Mention file, Clear conversation, Rewind
  2. Model — Switch model, Effort, Thinking, Account & usage
  3. Customize — Hooks, Output styles, Agents, Memory, Permissions
  4. Slash Commands ← custom user commands always appear last

To reach a custom command without scrolling, users must type 2–4 characters of a known prefix (e.g., /01, /03ADH, /00FUSE). There is no built-in way to pin, reorder, or prioritize custom commands.

---

Expected behavior / Feature request

Please consider one or more of the following improvements:

  • Option A: Add a user setting ("commandPicker.customCommandsFirst": true) that moves the Slash Commands section above the built-in sections.
  • Option B: Support a "pinned" or "favorites" list (configurable in settings.json) so specific custom commands always appear at the top of the picker.
  • Option C: Allow users to hide built-in sections from the picker for users who prefer to access them via other UI elements.
  • Option D: Show recently used custom commands at the very top of the picker, similar to VS Code's command palette behavior.

---

Why this matters

Power users with many custom slash commands (project workflows, daily routines, CI operations) use them as their primary interaction pattern with Claude Code. The current UX forces them to scroll past built-in options on every invocation, even though those built-in options are rarely used by comparison.

---

Workaround (current)

Typing a known prefix narrows the list:

| Type | Filters to |
|------|-----------|
| /01 | All 01DLY-* commands |
| /03 | All 03ADH-* commands |
| /00 | All 00FUSE-* commands |

This works but requires memorizing prefixes and doesn't help on cold open.

---

Environment

  • Tool: Claude Code VSCode Extension
  • Platform: Windows 11 Pro
  • Behavior: Confirmed in latest extension version as of 2026-05-03

---

Related

Custom slash commands are loaded from .claude/commands/ and displayed alphabetically — ordering within the section already works well. The request is only about section ordering in the picker UI.

Proposed Solution

Please consider one or more of the following improvements:

  • Option A: Add a user setting ("commandPicker.customCommandsFirst": true) that moves the Slash Commands section above the built-in sections.
  • Option B: Support a "pinned" or "favorites" list (configurable in settings.json) so specific custom commands always appear at the top of the picker.
  • Option C: Allow users to hide built-in sections from the picker for users who prefer to access them via other UI elements.
  • Option D: Show recently used custom commands at the very top of the picker, similar to VS Code's command palette behavior.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗