Slash-prefixed input gets stuck on "No matching items" instead of sending plain text #37010

Description

Describe the bug

When typing into the chat input, if the first character is /, OpenCode treats it as a command/function trigger. If the entered text does not match any available slash command, the UI shows No matching items and blocks normal text sending behavior.

Expected behavior: when / does not match any command/function option, the input should be treated as plain text, and pressing Enter should send the message normally.

Steps to reproduce

1. Focus the chat input box.
2. Type a string that starts with / but is not a valid slash command, for example:
   /tmp/test
   or
   /abc
3. Observe that the dropdown shows No matching items.
4. Press Enter.

Actual behavior

The input is interpreted as a slash-command search state, shows No matching items, and does not fall back to normal text sending behavior.

Expected behavior

If the input starting with / does not match any slash command or function option, it should be handled as normal text input.
Pressing Enter should send the original text message as typed.

Example

Input:
/tmp/test

Expected result:
The message /tmp/test is sent as plain text.

Actual result:
The UI shows No matching items, and the text cannot be sent normally.

Plugins

opencode-tui

OpenCode version

1.17.20

Steps to reproduce

Input:
/tmp/test

Expected result:
The message /tmp/test is sent as plain text.

Actual result:
The UI shows No matching items, and the text cannot be sent normally.

Screenshot and/or share link

Operating System

macOS26.5.6

Terminal

terminal