Skip to content

The /highlights command returns "No matching commands" after upgrading to v2.1.1 #57608

Open

Description

@HoseaChern

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 -g triggers an EPERM warning during cleanup. It fails to unlink the old opencode.exe file, 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 -g process completes without any warnings or permission errors. However, the /highlights command is still missing, indicating that the issue is not solely caused by the Windows file lock.

Screenshots & Logs

  • v2.1.0 (Working): /highlights is available and displayed in the autocomplete list.
  • v2.1.1 (Failing): Typing /highlights shows "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

  1. Install OpenCode v2.1.0 globally via npm:
    npm install -g [email protected]
  2. Open the OpenCode TUI and verify the command is available by typing /high. The /highlights command appears in the autocomplete list and works as expected.
  3. Upgrade to OpenCode v2.1.1 using the global update command:
    npm update -g
    (Note: On Windows 11, this step throws an EPERM warning during cleanup, but the installation still completes. On Ubuntu 24.04, it completes without warnings.)
  4. Open the OpenCode TUI again.
  5. Type /highlights in the input field and press Enter.
  6. Observe that the TUI displays a "No matching commands" message, and the command cannot be executed.

Screenshot

Image Image Image

Operating System

Ubuntu 24.04 and Windows 11

Terminal

Kitty on Ubuntu / WindowsTerminal on Windows

Activity

  1. opencode-agent commented on Oct 21, 2026

    @opencode-agent
    Contributor

    Thanks for the detailed report, with screenshots from both platforms!

    This looks like intended behaviour rather than a regression. /highlights is only registered when the installed build has release highlights embedded in it. They come from the ### Highlights section 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 Windows EPERM cleanup warning from npm update -g is unrelated.

    I'll treat this as a feature request: keep /highlights available 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:

  2. bacigal commented on Oct 27, 2026

    @bacigal

    2.2.0 same problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions