Repository navigation
Closed as not planned
Labels
Description
Summary
OpenCode V2 has two issues with the /skills catalog:
- Skills deleted from
~/.agents/skillsremain visible after restartingopencode2and reopening the TUI. They disappear only after exiting and restarting WSL2. - Skills disabled through the
permissionssettings remain visible in the/skillscatalog after closing and reopening the TUI.
There are no other skill files or skill directories in this environment. All user skills are located under ~/.agents/skills.
Environment
- opencode version:
opencode2 v0.0.0-next-16953 - OS:
Linux 6.6.87.2-microsoft-standard-WSL2, x86_64 - Terminal:
TERM=xterm-256color;TERM_PROGRAMandCOLORTERMwere not set - Shell:
/bin/bash - Install/channel:
next - Active plugins:
/home/wuyao/.config/opencode/plugins/session-warming-opt-in.ts - Configured plugins: no plugins configured in
/home/wuyao/.config/opencode/opencode.json - Skill locations: all skills are under
~/.agents/skills; no other skill files or directories are present
Reproduction
Deleted skills remain visible
- Start
opencode2in a workspace. - Open
/skillsand verify that a skill from~/.agents/skillsis present. - Exit
opencode2. - Delete one or more skill directories from
~/.agents/skills. - Confirm that the deleted skill directories no longer exist.
- Start
opencode2again and open/skills. - Observe that the deleted skills are still listed.
- Exit WSL2 completely and restart WSL2.
- Start
opencode2again. - Observe that the deleted skills are no longer listed.
Permission-disabled skills remain visible
- Open the
permissionssettings. - Disable one or more skills.
- Close the TUI.
- Reopen the TUI and open
/skills. - Observe that the disabled skills are still listed.
Expected Behavior
- The
/skillscatalog should reflect the current contents of~/.agents/skillsafter restartingopencode2. - Deleted skills should no longer be listed without restarting the entire WSL2 environment.
- Skills disabled through
permissionsshould not appear in the/skillspicker, or their disabled state should be clearly represented. - A disabled skill should not be loadable or executable when its permission is denied.
Actual Behavior
- Skills deleted from
~/.agents/skillsremain visible after restartingopencode2and reopening the TUI. - The deleted skills disappear only after exiting and restarting WSL2.
- Skills disabled through
permissionsremain visible after closing and reopening the TUI. - It has not yet been confirmed whether permission-disabled skills can still be loaded or executed; the observed issue is that they remain visible in the catalog.
Additional Context
- The exact skill names and permission configuration are omitted from this report.
- The deleted-skill issue is reproducible across an
opencode2restart. - Restarting WSL2 clears the stale skills from the catalog.
- No logs or stack traces are currently available.
- The active plugin does not configure or provide skills.
- There are no project-local or alternative skill directories in this environment.
Reacted by Jeremy Murray and Jack Stringer
Activity
github-actions commentedon Aug 7, 2026
This issue might be a duplicate of existing issues. Please check:
/skillscatalogmurrayj426 commentedon Aug 8, 2026
Same need here — I run OpenCode alongside Claude Code, so ~70 plugin skills under
~/.claude/skillsget scanned and clutter the/skillspicker. Configpermission.skilldeny hides them from the model's context but not the selector. Filed #41288 before seeing this — happy to have it folded in. Askills.excludeglob (or having the selector honorpermission.skilldeny) would cover it.github-actions commentedon Oct 9, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.