What happened?
When typing / to bring up slash command suggestions and selecting a custom command (e.g., /qc:create-issue), the @ file search feature no longer works. Typing @ after the slash command on the same line does not show any file search suggestions.
Steps to reproduce:
- Start Qwen Code interactive CLI
- Type
/ to bring up slash command suggestions
- Select a custom slash command such as
/qc:create-issue
- On the same line, type
@ followed by a partial filename
- No file search suggestions appear
What did you expect to happen?
After completing a slash command, typing @ should still trigger file search suggestions as normal, allowing me to reference files in the command arguments.
Client information
Client Information
Run qwen to enter the interactive CLI, then run the /about command.
$ qwen /about
# paste output here
Anything else we need to know?
The @ file search works fine when no slash command is present on the line. The issue only occurs when @ is typed after a /command on the same line.
What happened?
When typing
/to bring up slash command suggestions and selecting a custom command (e.g.,/qc:create-issue), the@file search feature no longer works. Typing@after the slash command on the same line does not show any file search suggestions.Steps to reproduce:
/to bring up slash command suggestions/qc:create-issue@followed by a partial filenameWhat did you expect to happen?
After completing a slash command, typing
@should still trigger file search suggestions as normal, allowing me to reference files in the command arguments.Client information
Client Information
Run
qwento enter the interactive CLI, then run the/aboutcommand.Anything else we need to know?
The
@file search works fine when no slash command is present on the line. The issue only occurs when@is typed after a/commandon the same line.