Feature: Trigger slash command picker mid-line and via keybinding

Problem

The slash command picker (autocomplete) only activates when / is typed at the beginning of a line in the input field. Users who want to embed commands mid-line (e.g., "fix this bug and then /commit") or who have many custom skills/plugins (40+) cannot trigger the picker without starting a new line.

Current workaround: Press Enter to create a new line, type / at the beginning, then select the command.

Proposed Solutions

A. chat:openCommandPicker keybinding action (Recommended)

Add a new keybinding action that opens the slash command picker at the current cursor position, regardless of where the cursor is in the input.

Example configuration:

{
  "context": "Chat",
  "bindings": {
    "ctrl+/": "chat:openCommandPicker"
  }
}

Why this approach:

• Explicit and intentional — requires deliberate action, zero false positives
• Follows established precedent — VS Code (Cmd+Shift+P), Sublime Text, and other developer tools use keybinding-triggered command palettes
• No conflicts — avoids clashing with file path input (/usr/local/bin) or internal prompt routing
• Fits existing architecture — Claude Code already has 66 keybinding actions across 19 contexts; this naturally extends the chat: context

B. Mid-line / trigger (Alternative)

Like Slack, Notion, and Discord, activate the command picker when / is typed anywhere in the input, not just at line start.

Tradeoffs to consider:

• Risk of false positives — developers frequently type file paths containing / (e.g., ls /usr/local/bin, cat ./config/routes.rb), which would incorrectly trigger the picker
• Potential heuristic: only trigger after whitespace + / to reduce false positives
• Could be gated behind a setting (opt-in)

Use Cases

1. Inline command embedding — "investigate this error and /commit the fix" with autocomplete for the command
2. Discoverability of large plugin/skill sets — users with 40+ custom skills need efficient browsing without navigating to line start
3. Keyboard-driven workflows — power users who avoid breaking their typing flow

Environment & Research

• Reviewed the full list of available keybinding actions via official documentation
• Confirmed that chat:openCommandPicker does not currently exist as an action
• Existing autocomplete context only supports accept, dismiss, previous, next — no action to open the picker
• Precedent exists: Esc+Esc is already mapped to invoke /rewind, proving the input field can handle key-sequence-triggered commands

Suggested Default Keybinding

| Platform | Keybinding | Rationale |
|:---|:---|:---|
| macOS | Cmd+/ | Mirrors VS Code comment toggle convention, intuitive for "slash" |
| Linux/Windows | Ctrl+/ | Cross-platform equivalent |

These are suggestions — the keybinding should be user-configurable via keybindings.json as with all other actions.