Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Slash command autocomplete misses /terminal-setup on partial prefix /terminal-setu [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#56111•Fetched 2026-05-05 05:57:55
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
khaled0fareskhaled0fares
Participants
khaled0fareskhaled0fares
Timeline (top)
labeled ×4

Error Message

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

The only way to learn whether Shift+Enter is wired up — or whether it even needs to be wired up in the current terminal — is to run /terminal-setup and read its output. On iTerm2 the response is "Shift+Enter is natively supported, no configuration needed", which is useful information that's currently hidden behind a command invocation.

For new users (and anyone debugging a multi-line prompt issue) the question is "is my terminal set up correctly?" — and there's no way to answer it at a glance.

What Should Happen?

Surface terminal-setup status passively, in one of these places:

  • A /doctor (or similar) command that lists environment checks, including: terminal detected, Shift+Enter status (native / configured / not configured / unsupported), Claude Code version, etc.
  • A one-time toast on first launch confirming the terminal status (e.g. "iTerm2 detected — Shift+Enter works natively").
  • Inline annotation on /terminal-setup in the autocomplete menu showing current status (e.g. /terminal-setup — iTerm2 (native, no setup needed)).

Any of these would let users confirm setup without invoking the command.

Error Messages/Logs

Steps to Reproduce

  1. Open a fresh Claude Code session in iTerm2 (Claude Code 2.1.118, macOS Darwin 25.0.0).
  2. In the prompt, type /terminal-setu (one character short of the full command name).
  3. Observe the autocomplete suggestion list — /terminal-setup does not appear.
  4. Type the final character so the input reads /terminal-setup.
  5. Observe the autocomplete suggestion list — /terminal-setup now appears.

The same behavior can be checked with shorter prefixes like /terminal or /term to confirm the command is missed at every prefix shorter than the full name.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.118

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

<img width="1713" height="259" alt="Image" src="https://github.com/user-attachments/assets/4958728f-d7c8-4c02-b77b-de4365ca5c7b" />

extent analysis

TL;DR

To address the issue, consider adding a passive status indicator for terminal setup, such as a /doctor command or a one-time toast on first launch, to help users confirm their setup without invoking the /terminal-setup command.

Guidance

  • Introduce a /doctor command that lists environment checks, including terminal detected, Shift+Enter status, and Claude Code version, to provide users with a clear overview of their setup.
  • Implement a one-time toast on first launch to confirm the terminal status, such as "iTerm2 detected — Shift+Enter works natively", to inform users about their setup.
  • Add inline annotation on /terminal-setup in the autocomplete menu to show the current status, allowing users to confirm their setup at a glance.
  • Consider enhancing the autocomplete suggestion list to include /terminal-setup even when the input prefix is shorter than the full command name.

Example

No code snippet is provided as the issue focuses on the desired functionality rather than a specific code implementation.

Notes

The proposed solutions aim to improve the user experience by providing a clear and passive indication of the terminal setup status, addressing the issue without requiring users to invoke the /terminal-setup command.

Recommendation

Apply a workaround by introducing a /doctor command or a one-time toast on first launch, as these solutions can be implemented without requiring significant changes to the existing codebase, and they address the core issue of providing users with a clear indication of their terminal setup status.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#response parsing#generation error#database connection#prompt issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Slash command autocomplete misses /terminal-setup on partial prefix /terminal-setu [1 participants]