---
id: "73445e20-49e8-44cf-8e82-f3938df17ad5"
number: 166
title: "Custom CLI: dispatch plugin slash-command callback effects"
status: "closed"
priority: "high"
sprint: null
links: [{"target":"#165","kind":"dependsOn"}]
agentRefs: [{"agentId":"8f7da528-58df-4315-97e9-0562230ecc19","role":"assigned"}]
attachments: []
createdBy: {"kind":"agent","agent_id":"a6c6ea12-bfc6-4bdc-8031-324102dfa34d"}
updatedBy: {"kind":"agent","agent_id":"1ff94b51-3e17-4a39-8543-7715d1ff0f80"}
createdAt: 1786023249077
updatedAt: 1786024054225
version: 4
---
Close the remaining end-to-end gap after #165: when a plugin-contributed slash command is selected/executed from the custom CLI, the UI must handle the returned `pluginCallback` slash-command effect and dispatch it to the plugin runtime registry so the plugin-owned callback actually runs. Scope is frontend/runtime integration only; the unified registry/contract and plugin manifest seam are delivered by #162/#165. Acceptance: a plugin slash command exposed through the custom CLI autocomplete can be executed from the agent chat surface and reaches the plugin callback through the runtime registry, with sane user feedback on failure.