[Bug] `/clear` command matches wrong terminal option instead of exact match
Status Fixed / completed
Reported on v2.1.12
Maintainer reply None cached
Activity 4 comments · opened Jan 19, 2026 · closed Jan 19, 2026
Title
/clear command selects wrong terminal option (prefers /code-refactor over exact match) since ~2 releases ago
Summary
In the Claude Code terminal (within VS Code on macOS), typing /clear incorrectly selects a different command/skill option (e.g., /code-refactor) even though /clear is an exact match. This regression began approximately two updates ago.
Expected Behavior
When the user types /clear, the command palette/autocomplete should select /clear as the top/active option because it is an exact match.
Actual Behavior
Typing /clear results in a different option being selected (observed: /code-refactor skill). The exact-match /clear is not prioritized.
Regression
- This behavior started roughly two updates ago (prior versions matched
/clearcorrectly).
Steps to Reproduce
- Open VS Code on macOS (darwin).
- Open the Claude Code terminal.
- Type
/clear. - Observe the selected command/option in the UI (it selects something other than
/clear, e.g.,/code-refactor).
Environment
- Platform:
darwin - Terminal:
vscode - Version:
2.1.12 - Feedback ID:
8b3adec3-1a0b-4f25-bce6-c74329ee0973
<img width="1393" height="220" alt="Image" src="https://github.com/user-attachments/assets/45523e53-c51e-4c09-af1d-deb4335b192f" />
4 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Hello, I have the same issue in v2.1.12 but it selects /compact for me instead of /clear :
<img width="928" height="99" alt="Image" src="https://github.com/user-attachments/assets/8395e54c-58b4-45c9-acc7-7bb2c00d9b0f" />
Closing as this bug has now been widely reported. All three recommendations but github-actions describe my same issue.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.