Autocomplete popup renders clipped for the second command when stacking slash commands

Status Open
Maintainer reply None cached
Activity 0 comments · opened Aug 25, 2026

Summary

When stacking slash commands (/skill-a /skill-b), the autocomplete popup for the second
command renders as a small clipped box instead of the normal command list. Typing the first command
at position 1 shows the list correctly, so the defect is specific to the stacked position.

Command parsing is unaffected — typing the full name still expands both skills as documented. This
is a UI rendering issue only.

Environment

  • Claude Code 2.1.243 (Claude Code) (desktop app, macOS)
  • macOS 26.6.2
  • Reproduced by the reporter on their own machine; the discriminator below was run.

Steps to reproduce

  1. Type /experience-distillation (a valid user skill, followed by a space).
  2. Begin typing a second command: /session-en.
  3. Observe the autocomplete.

Actual

A small dark rounded box appears above and to the left of the input. It contains a clipped fragment
of the input line rather than a list of matching commands. No usable suggestion list is shown.

Expected

The same autocomplete list that appears when /session-en is typed at position 1 — matching
/session-end, selectable.

Discriminator already run

  • /session- typed at position 1 → list renders normally.
  • /session- typed after another command → clipped box.

So the trigger is the stacked position, not the skill itself.

Ruled out

  • skillOverrides is not the cause. session-end is set to name-only, and the documented

behaviour for name-only is In / menu: Yes. Only "off" hides a skill from the menu, and the
configuration in question contains no "off" entries.

  • Not a no-such-command case. An earlier screenshot with a genuine typo (/session-ion, which

prefixes nothing) correctly shows no popup at all — a different, correct behaviour.

Docs note

Command stacking is documented at
https://code.claude.com/docs/en/skills ("You can also stack several skills at the start of one
message", available since v2.1.199). The docs do not describe autocomplete behaviour at the second
position, so it is unclear whether the list is intended to appear there at all. If it is not
intended, the clipped box is still wrong — it should render nothing, as it does for an unmatched
prefix.

View original on GitHub ↗