You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE]: desktop: show project-level skills in Settings → Extensions → Skills #53716
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Summary
In OpenCode Desktop, Settings → Extensions → Skills only shows global skills under "Available to all projects". Project-scoped skills (.opencode/skills/, .agents/skills/, .claude/skills/) are not displayed anywhere in Settings, leading users to believe project skills are unsupported or failed to load.
Problem
OpenCode correctly discovers and advertises project skills during sessions, but the main Settings UI gives no indication they exist. Users checking Settings → Extensions to verify their skills see only global skills ("Available to all projects") and may conclude their project-level configuration is broken.
Proposed Solution
Add a "Project Skills" section to Settings → Extensions → Skills showing skills discovered for the active project, alongside the existing "Available to all projects" global section.
Alternatively, provide a project selector dropdown (similar to OpenChamber's approach) or link directly from the global Settings → Extensions → Skills page to the project-specific extensions view under Settings → Projects → [project] → Extensions → Skills.
Thanks for the detailed report! I couldn't test this myself because the Desktop app isn't available in my environment, so a maintainer with Desktop will need to confirm it.
From the 2.0.24 code, Settings → Extensions → Skills is meant to list only skills available to every project, which is why your project skills don't appear there. Each project also has its own settings page: Settings → Projects → (your project) → Extensions → Skills. It has an "Added to this project" section for skills found in that project's directory (e.g. .opencode/skills/, .agents/skills/, .claude/skills/), followed by "Shared with all projects".
Could you check whether your project skills show up there? If they don't, or if you think the global Skills page should point to the project page, please reply here.
changed the title [-]desktop: show project-level skills in Settings → Extensions → Skills[/-][+][FEATURE]: desktop: show project-level skills in Settings → Extensions → Skills[/+]on Oct 7, 2026
Regarding @opencode-agent's note on Settings → Projects → [project] → Extensions → Skills:
Thank you for pointing that out! The project skills are indeed listed under that project-specific path. However, because the top-level Settings → Extensions → Skills page only shows "Available to all projects" without any pointer or hint that project-scoped skills are located under Projects, it creates the impression that project skills were missed or unsupported. Adding a link/pointer to the project extensions page or a project switcher in that view would clear up the confusion.
As a follow-up observation after navigating to Settings → Projects → [project] → Extensions:
The skills do show up under the Skills tab ("Added to this project"), but the landing experience compounds the confusion:
Navigating to Extensions always defaults to the MCPs tab.
The MCPs tab displays a prominent "No MCPs yet" / "MCPs available to OpenCode will appear here" empty state directly above the active "Shared with all projects" list.
Clarifying the empty state wording (e.g., "No project-specific MCPs configured") and/or unifying global and project extensions into a single view with a project switcher would make the state of extensions much more intuitive.
Activity
github-actions commentedon Oct 7, 2026
This issue does not fully meet our contributing guidelines.
What needs to be fixed:
Please edit this issue to address the above within 72 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
If you believe this was flagged incorrectly, please let a maintainer know.
opencode-agent commentedon Oct 7, 2026
Thanks for the detailed report! I couldn't test this myself because the Desktop app isn't available in my environment, so a maintainer with Desktop will need to confirm it.
From the 2.0.24 code, Settings → Extensions → Skills is meant to list only skills available to every project, which is why your project skills don't appear there. Each project also has its own settings page: Settings → Projects → (your project) → Extensions → Skills. It has an "Added to this project" section for skills found in that project's directory (e.g.
.opencode/skills/,.agents/skills/,.claude/skills/), followed by "Shared with all projects".Could you check whether your project skills show up there? If they don't, or if you think the global Skills page should point to the project page, please reply here.
[-]desktop: show project-level skills in Settings → Extensions → Skills[/-][+][FEATURE]: desktop: show project-level skills in Settings → Extensions → Skills[/+]milesbuckton commentedon Oct 7, 2026
Compliance updates applied:
[FEATURE]:prefix.Regarding the flagged potential duplicates:
/skillscommand and picker.This request is specifically about UX discoverability in the existing Settings → Extensions → Skills view.
Regarding @opencode-agent's note on
Settings → Projects → [project] → Extensions → Skills:Thank you for pointing that out! The project skills are indeed listed under that project-specific path. However, because the top-level Settings → Extensions → Skills page only shows "Available to all projects" without any pointer or hint that project-scoped skills are located under Projects, it creates the impression that project skills were missed or unsupported. Adding a link/pointer to the project extensions page or a project switcher in that view would clear up the confusion.
github-actions commentedon Oct 7, 2026
Thanks for updating the issue!
milesbuckton commentedon Oct 7, 2026
As a follow-up observation after navigating to Settings → Projects → [project] → Extensions:
The skills do show up under the Skills tab ("Added to this project"), but the landing experience compounds the confusion:
Clarifying the empty state wording (e.g., "No project-specific MCPs configured") and/or unifying global and project extensions into a single view with a project switcher would make the state of extensions much more intuitive.