[FEATURE]: Allow plugins to register slash commands #10262

Activity

1. nsoufian

   added

   discussionUsed for feature requests, proposals, ideas, etc. Open discussionUsed for feature requests, proposals, ideas, etc. Open discussion

   on Jan 23, 2026
2. github-actions

   assigned

   thdxr

   on Jan 23, 2026
3. github-actions commented on Jan 23, 2026

   

   github-actionsBot

   on Jan 23, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • [FEATURE]: Plugin Hook for Instant TUI Commands #5305: [FEATURE]: Plugin Hook for Instant TUI Commands - Proposes allowing plugins to register instant commands that execute without agent involvement
   • [FEATURE]: Plugin Hooks for spawning dialogs #9911: [FEATURE]: Plugin Hooks for spawning dialogs - Requests plugin hooks for creating custom modals and dialogs for native feeling interactions
   • [FEATURE]: Plugin Support for Modal Human-in-the-loop Interactions  #5147: [FEATURE]: Plugin Support for Modal Human-in-the-loop Interactions - Proposes exposing modal infrastructure to plugins for interactive capabilities
   • [FEATURE]: Generic UI Intent Channel for cross-client plugin-driven UX #6330: [FEATURE]: Generic UI Intent Channel for cross-client plugin-driven UX - Suggests a comprehensive UI intent system that would enable plugins to drive interactions

   These issues explore similar concepts of extending plugin capabilities for user interaction. Feel free to ignore if your specific use case differs from these.
4. nsoufian

   changed the title [-][FEATURE]: Allow plugins to register slash commands for user interaction[/-] [+][FEATURE]: Allow plugins to register slash commands[/+] on Jan 23, 2026
5. pablontiv commented on Jan 29, 2026

   

   pablontiv

   on Jan 29, 2026

   More actions

   Use Case: Claude Code Compatibility Plugin

   I'm building a plugin (claude-compat) that reads .claude/skills/ and exposes user-invocable skills as slash commands in OpenCode, without file duplication.

   Current Workaround Limitation

   Today, I can expose skills as tools via the tool hook, but this requires agent mediation. The user must say "use the investigar skill" instead of typing /investigar directly.

   What I Need

   The proposed command hook would allow:

   export const ClaudeCompatPlugin: Plugin = async ({ worktree }) => {
     const skills = await discoverClaudeSkills(path.join(worktree, ".claude/skills"))
     
     const commands: Record<string, CommandDef> = {}
     for (const skill of skills.filter(s => s.userInvocable !== false)) {
       commands[skill.name] = {
         template: skill.content,
         description: skill.description,
         hints: skill.argumentHint ? ["$ARGUMENTS"] : [],
       }
     }
     
     return { command: commands }
   }

   Benefits

   • Zero file duplication (reads directly from .claude/)
   • Users migrating from Claude Code get the same /skill-name UX
   • Plugin can handle $ARGUMENTS substitution matching Claude Code behavior

   Happy to help implement this if the design is approved.
6. grota commented on Feb 4, 2026

   

   grota

   on Feb 4, 2026

   Contributor

   More actions

   Wouldn't an approach like this one fit the need?
   Admittedly, since it seems too easy, I might have misunderstood the scope of the request.

   ❤️React with ❤️1Reacted by Jacob Daitzman

   🚀React with 🚀1Reacted by Jacob Daitzman
7. github-actions commented on Apr 6, 2026

   

   github-actionsBot

   on Apr 6, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
8. github-actions

   closed this as completedon Apr 6, 2026