claude-code - 💡(How to fix) Fix [FEATURE] Wrap slash command picker description to a second line instead of truncating it mid-sentence. [1 participants]

Preflight Checklist

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

Problem Statement

Problem

The slash command picker truncates long descriptions at terminal width with an ellipsis, often cutting off mid-word. This hides information the description was specifically written to convey.

Example

Typing / and scrolling to /clear shows:

/clear Start a new session with empty context; previous session stays on disk (resumabl…

<img width="2627" height="113" alt="Image" src="https://github.com/user-attachments/assets/cb5572fd-5474-449a-8250-025273a3b2d3" />

The truncation hides that the previous session can be resumed using the /resume command, which is precisely what a user deciding whether to run /clear needs to know.

Impact

• Users make decisions based on incomplete information, or abandon the picker to look up the command elsewhere. - The problem worsens on narrow terminals, split panes, and IDE-embedded terminals, where truncation can happen after only a few words.
• Command authors have no way to know where their description will be cut, so they can't write around it.

Proposed Solution

Wrap long descriptions onto a second (or additional) line within the picker, rather than truncating with … . Wrapping preserves the information the description was written to convey and is standard in most modern CLI autocomplete UIs (fzf, gh, etc.).

Alternative Solutions

No response

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

I'm mid-session working through a tricky refactor. The context window is getting full and Claude's responses are slowing down, so I want to start fresh, but I also want to be sure I can come back to this conversation later if I need to reference what we discussed.

1. I type / to open the slash command picker.
2. I scroll to /clear and see:
   /clear Start a new session with empty context; previous session stays on disk (resumabl…
3. I stop. The description tells me the previous session "stays on disk" but cuts off mid-word right where it matters. Does "stays on disk" mean it's archived and gone, or does it mean I can get it back? I can't tell.
4. Not wanting to lose my work, I close the picker and Google "claude code clear command resumable" to find the docs.
5. The docs confirm the session is resumable via /resume. I go back and run /clear.

Having to leave the tool to confirm what a built-in command does defeats the purpose of having descriptions in the picker at all.

Additional Context

No response