[FEATURE]: expose the plugin manager as a /plugins slash command #47345

Activity

1. github-actions

   assigned

   simonklee

   on Sep 4, 2026
2. eloyred commented on Oct 16, 2026

   

   eloyred

   on Oct 16, 2026

   More actions

   Hi! I'd like to pick this up — clean two-line change.

   Plan:

   • Base branch dev per CONTRIBUTING.md.

   • Add slashName: "plugins" and slashAliases: ["plugin"] to plugins.list in packages/tui/src/feature-plugins/system/plugins.tsx.

   • Add slashName: "plugin-install" to plugins.install in the same file.

   • Confirm useCommandSlashes in packages/tui/src/keymap.tsx picks up the new fields without further changes.

   • Add a focused test in packages/tui/test/feature-plugins/plugins-commands.test.ts mirroring the precedent from feat(tui): expose plugin manager as /plugins slash command #47347 (closed by automated cleanup, not by rejection).

   • Run:

     cd packages/tui
     bun test
     bun typecheck
     

   • Open PR against dev linking this issue.

   Scope: ~50 LOC diff, doc note in specs/tui-plugins.md, no UI or API change.

   Could you assign this to me, or let me know if the team is already working on it so I don't duplicate effort?
3. eloyred commented on Oct 16, 2026

   

   eloyred

   on Oct 16, 2026

   More actions

   Update after reading the code on dev: the API in the issue is stale for v2 — the real fields are slash: { name, aliases?, arguments? } on each keymap command (no slashName/slashAliases). plugins.list at packages/tui/src/feature-plugins/system/plugins.tsx:334 already declares slash: { name: "plugins" } (only name, no alias), and plugins.install does not exist as a separate command — install is triggered from inside the PluginsDialog via keymap, not via slash.

   So the in-scope fix is the alias on the existing slash:

   slash: { name: "plugins", aliases: ["plugin"] }

   One line in plugins.tsx. Tests live in packages/tui/test/cli/tui/plugins-dialog.test.tsx; I'll add a focused case there asserting that typing /plugin resolves to the plugins.list command alongside /plugins.

   Out of scope here (would need design review per CONTRIBUTING.md): a separate /plugin-install slash that bypasses the dialog. I'm leaving that for now unless you want it in the same PR.

   Plan:

   • Branch plugins-slash (renamed from my earlier branch to match the v2 branch-naming rule in AGENTS.md).
   • Apply the alias change in plugins.tsx.
   • Add the test in plugins-dialog.test.tsx.
   • Run bun test and bun typecheck from packages/tui, plus bun run check from the repo root.
   • Open PR against dev linking #47345.

   Can you confirm the scope is OK before I start, or do you want /plugin-install folded in as well?
4. opencodejr commented on Oct 28, 2026

   

   opencodejrBot

   on Oct 28, 2026

   More actions

   Thanks for the detailed write-up, @rsmets!

   The code you're describing (slashName, the plugins.install command and the keybind defaults in config/keybind.ts) is from OpenCode v1 (opencode-ai, versions 0.x/1.x). v1 now only gets critical fixes such as data loss, security problems or crashes, so this change is unlikely to be made there.

   In v2 (@opencode/cli, versions 2.x) the plugin manager already has a slash command: /plugins opens it and shows up in slash autocomplete. It has been there since v2.0.0. v2 has no separate install-plugin command, and there is no /plugin alias right now. If you'd like either of those in v2, please open a new issue that mentions v2.

   We'd recommend upgrading to v2. If you think this is critical for v1, or you see the same gap in v2, please reply here.

   Related: #28696 (plugin marketplace/registry), #23800, #7716, #44452.
5. opencodejr

   added

   pending close

   triaging

   on Oct 28, 2026
6. opencodejr

   closed this as not plannedon Oct 29, 2026
7. opencodejr commented on Oct 29, 2026

   

   opencodejrBot

   on Oct 29, 2026

   More actions

   Closing this as not planned. The request is about v1, which now only gets critical fixes, and nobody has replied since.

   In v2 (@opencode/cli), /plugins already opens the plugin manager. If you'd like a /plugin alias or an install-plugin command in v2, please open a new issue that mentions v2. If you think this is critical for v1, reply here and we can take another look. Thanks again, @rsmets!