Repository navigation
Description
Description
1. Common Issue
After upgrading OpenCode from v2.1.0 to v2.1.1, the /highlights slash command is no longer recognized. In the TUI, typing /highlights returns a "No matching commands" error. This is a regression from v2.1.0, where the command worked correctly and was displayed in the autocomplete dropdown (as shown in the screenshots below).
2. Environment
- OS: Windows 11 (x64) & Ubuntu 24.04 LTS
- OpenCode Version: v2.1.1 (upgraded from v2.1.0)
- Installation Method:
npm(global)
3. Platform Difference
While the core issue (/highlights command missing) is reproducible on both Windows 11 and Ubuntu 24.04, there is a platform-specific difference during the upgrade process:
- Windows 11: Running
npm update -gtriggers anEPERMwarning during cleanup. It fails to unlink the oldopencode.exefile, which may indicate a file lock or permission issue during the upgrade:npm warn cleanup Failed to remove some directories [ npm warn cleanup 'D:\\npm-global\\node_modules\\@opencode\\.cli-xqxTodHT', npm warn cleanup ... npm warn cleanup [Error: EPERM: operation not permitted, unlink '...\\opencode.exe'] npm warn cleanup ]
- Ubuntu 24.04: The
npm update -gprocess completes without any warnings or permission errors. However, the/highlightscommand is still missing, indicating that the issue is not solely caused by the Windows file lock.
Screenshots & Logs
- v2.1.0 (Working):
/highlightsis available and displayed in the autocomplete list. - v2.1.1 (Failing): Typing
/highlightsshows "No matching commands". - Windows EPERM Log: Attached above.
Additional Context
The /highlights command was introduced in PR #54969. Given it's a stable release, it should be present. The fact that it's missing on both platforms suggests a potential build issue (missing embedded data) or a TUI autocomplete logic bug in v2.1.1.
Plugins
windows-controller (p.s. this plugin is only uesd on Windows and does not exist on Ubuntu)
OpenCode version
TUI 2.1.1
Steps to reproduce
- Install OpenCode v2.1.0 globally via npm:
npm install -g [email protected]
- Open the OpenCode TUI and verify the command is available by typing
/high. The/highlightscommand appears in the autocomplete list and works as expected. - Upgrade to OpenCode v2.1.1 using the global update command:
(Note: On Windows 11, this step throws an
npm update -g
EPERMwarning during cleanup, but the installation still completes. On Ubuntu 24.04, it completes without warnings.) - Open the OpenCode TUI again.
- Type
/highlightsin the input field and pressEnter. - Observe that the TUI displays a "No matching commands" message, and the command cannot be executed.
Screenshot
Operating System
Ubuntu 24.04 and Windows 11
Terminal
Kitty on Ubuntu / WindowsTerminal on Windows
Activity
opencode-agent commentedon Oct 21, 2026
Thanks for the detailed report, with screenshots from both platforms!
This looks like intended behaviour rather than a regression.
/highlightsis only registered when the installed build has release highlights embedded in it. They come from the### Highlightssection of that release's notes, and the release process leaves that section out when a release has nothing that qualifies. v2.1.0 had highlights. v2.1.1 is a small patch release and most likely shipped without any, so the command doesn't appear and the autocomplete shows "No matching commands". The WindowsEPERMcleanup warning fromnpm update -gis unrelated.I'll treat this as a feature request: keep
/highlightsavailable even when the current release has no highlights, for example by showing the most recent release that had some, or a clear "no highlights for this release" message instead of "No matching commands". Maintainers will consider it.Related:
/highlightsbacigal commentedon Oct 27, 2026
2.2.0 same problem