[BUG] Desktop app (macOS): pasted slash command is silently swallowed — neither executed nor sent as text

Environment

• Client: Claude Code desktop app on macOS
• CLI version (reported by claude --version): 2.1.139
• Note: the changelog for v2.1.132 lists a fix titled "Fixed pasting text starting with / silently swallowing the input or triggering an unknown-command reply". The behavior below appears to be a regression of that fix, or a case the fix did not cover (skill invocation in the desktop app).

Summary

In the macOS desktop app, pasting a slash-command/skill invocation into the prompt input (instead of typing it) results in the input being silently dropped: the skill is not executed, and no message is sent to Claude either. The user is left with the impression that nothing happened.

Steps to reproduce

1. Open the Claude Code desktop app on macOS.
2. Copy a slash-command/skill invocation to the clipboard, e.g. /kb-scaffold entity app/models/expense.rb (copied from within the same desktop app — e.g. from an assistant message).
3. Paste it into the prompt input with Cmd+V.
4. Press Enter.

Expected

Either:

• the skill is recognized and executed (ideal), or
• the text is sent as a normal user message and the assistant can respond.

Actual

• The UI does not mark the pasted text as a recognized skill (no blue "chip" the way typing /kb + selecting from autocomplete would).
• Pressing Enter does nothing visible: no skill execution, no user message added to the transcript, and the assistant receives no input.
• A subsequent unrelated user message confirms that the pasted invocation never reached the model.

Why this matters

The current behavior is the worst of both worlds: the UI recognizes the input enough to suppress it as a plain text message, but not enough to execute it as a skill. Users who paste commands (a very common case — copying from docs, chats, or assistant messages) silently lose their input with no feedback that anything went wrong.

Suggested fix

Either:

1. Execute the pasted skill/slash command as if it had been typed and selected from autocomplete, or
2. Insert the pasted text into the prompt as literal text (matching the post-2.1.132 CLI behavior described in #56885) so the user can edit/send it manually.

Falling back silently to "do nothing" should not be an option.

Related

• #56885 — docs issue noting the pre-2.1.132 CLI behavior (silent swallow) was fixed.
• Changelog v2.1.132: "Fixed pasting text starting with / silently swallowing the input or triggering an unknown-command reply".