[FEATURE] Prioritize /status over /stop in autocomplete for /st

Status Open
Maintainer reply None cached
Activity 0 comments · opened Sep 17, 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

I'm used to typing /st and pressing Enter to check my status. Autocomplete shows two options, /stop and /status, with /stop always first. Pressing Enter accepts /stop, which has stopped all my running programs when I only wanted to check status.

I understand that autocomplete is executing the selected command as implemented. This is a usability request: the default ordering makes a familiar, quick status check unexpectedly disruptive, and it is frustrating to keep running into it.

Proposed Solution

Please prioritize /status over /stop when the input is /st, so typing /st and pressing Enter opens status. /stop should still be available by selecting it deliberately or typing the full command.

The goal is to make checking status convenient without accidentally stopping running work.

Alternative Solutions

Incorporating another key word for /stop.

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

  1. I have programs running through Claude Code.
  2. I want to check status, so I type /st.
  3. The suggestions are /stop first and /status second.
  4. Out of habit, I press Enter, which accepts /stop and stops my programs.
  5. With the requested ordering, the same keystrokes would open /status and my programs would keep running.

Additional Context

_No response_

View original on GitHub ↗