anomalyco / anomalyco/opencode

Desktop app shows all skills in the / command menu - unlike terminal TUI

Open
#41,643 1 comment 1 reaction 1 assignee View on GitHub

@Hona is already working on this.

Since Aug 11, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

In the desktop app (@opencode-aidesktop, v1.18.16), pressing / shows every registered skill as a command (e.g. /using-godot-prompter, each with a Skill badge). The terminal TUI already filters these out, so this is a desktop-only behavior.

Expected behavior

Skills should not appear in the / command menu - they are meant to be invoked by the agent via the native skill tool, not manually by the user. This matches the terminal TUI behavior.

How to reproduce

  1. Install any plugin that registers skills (e.g. via skills.paths or a plugin's config hook)
  2. Open the desktop app and press /
  3. See all skills listed as commands with a Skill badge

Evidence / investigation

  • The terminal TUI explicitly skips skill commands in the autocomplete menu: packages/tui/src/component/prompt/autocomplete.tsx - if (serverCommand.source === skill) continue;
  • In the desktop app's bundle, the v1 legacy path contains a commented-out filter (// source: command.source === skill ? undefined : command.source), suggesting the intent existed but was not enabled.
  • The permission.skill mechanism only offers allow/ask/deny; deny also hides skills from the agent, so there is no way to hide them from the menu while keeping them available to the agent.
  • No config option (in opencode.json schema) controls skill visibility in the desktop command menu.

Suggested fix

Apply the same source === skill filter to the desktop app's command list loading (the api.list() path), mirroring the terminal TUI. Skills would remain discoverable/invocable by the agent via the skill tool; they would simply not clutter the user-facing / menu.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.