Magic Context extension slash commands are consumed but show no feedback

[imaGPT-sol]

Summary

Magic Context extension slash commands such as /ctx-status and /ctx-wrapup appear to be consumed by PI-Desktop's chat input, but they do not show any feedback and do not appear to dispatch to the extension command handler.

Environment

• App: PI-Desktop on Windows
• Repository inferred from local source copy: vastsa/pi-desktop
• GitHub account used for this report: imaGPT-sol
• Magic Context plugin id: imported.magic-context
• Current session id where reproduced: b654c21a-a811-4ad8-834c-3219a0621a06
• Model during reproduction: gpt-5.5

Reproduction

1. Ensure Magic Context is installed/enabled in PI-Desktop.
2. Open an Agent session.
3. Type or select /ctx-status in the chat input.
4. Press Enter.

I also tried /ctx-wrapup with the same behavior.

Actual behavior

• The input box becomes empty, so the slash command appears to be consumed by the UI.
• No status card, overlay, notification, or chat message is shown.
• No visible error is shown.
• The session continues normally afterward.

Expected behavior

/ctx-status should display Magic Context status information, and /ctx-wrapup should show a Magic Wrapup status/result message. These commands are Magic Context Pi extension commands registered via pi.registerCommand() and are intended to be non-LLM commands (triggerTurn: false).

Local evidence

Magic Context itself appears to be loaded and partly working:

• imported.magic-context is loaded successfully according to logs/app/plugin.log.
• Magic Context tools are available: ctx_search executed successfully in the same session.
• The local plugin source contains registrations for the relevant commands:
  • pi.registerCommand("ctx-status", ...)
  • pi.registerCommand("ctx-wrapup", ...)
• The Magic Context package README lists /ctx-status and /ctx-wrapup [messages_to_keep] as supported Pi slash commands.

However, after trying /ctx-status and /ctx-wrapup:

• The current session JSONL contains only normal user messages; it does not contain /ctx-status or /ctx-wrapup.
• logs/app/session.log shows normal prompt.accepted events for my explanatory messages, but no command execution signal for /ctx-status or /ctx-wrapup.
• logs/app/plugin.log has plugin load/reload entries but no /ctx-status, /ctx-wrapup, wrapup, or historian/status activity corresponding to the attempted command.
• I saw no evidence that the Magic Context command handler ran.

This makes it look like PI-Desktop consumes the extension slash command at the input layer, but does not dispatch it to the pi.registerCommand() handler or does not display the handler's UI/status feedback.

Related upstream context

This may be related to known Pi/ACP behavior around extension slash commands that do not start an agent loop:

• svkozak/pi-acp#84: session/prompt never resolves for extension slash commands that don't start an agent loop.
• earendil-works/pi#1782: extension commands registered with pi.registerCommand() do not emit agent_end / command completion events under the old architecture.

Magic Context's /ctx-status is exactly this kind of command: an extension slash command that should not trigger an LLM turn.

Request

Please check whether PI-Desktop correctly routes plugin-provided slash commands registered via pi.registerCommand() to the extension handler, especially commands that do not trigger an agent loop and only return UI/status feedback.

If PI-Desktop already has a command palette or command registry view, it would also be helpful to verify whether ctx-status / ctx-wrapup are visible there after plugin load.