Slash commands with their own interface now open in a panel you can dismiss to cancel cleanly.
What's wrong with this entry?
Commands that render an interactive interface are shown through a panel host on the tool-use context instead of being pushed into a single render slot. Dismissing the panel now cleanly ends the command with no messages produced, and a command can no longer resolve twice.
- The executor calls
localJsx.show(node, { commandName, immediate, hidesPrompt: !0 })and awaits the panel'sclosedpromise. - Two outcomes are recorded:
cmd_local_jsx_dismissedwhen the panel is closed, andcmd_local_jsx_no_panel_hostwhen the context has no panel host, which falls back to the same result as running the command with no interactive surface. - The prompt input no longer receives a separate flag saying such a command is active, and the old "hide the prompt input" check on the retired render slot is gone.
- Unconditional in this build; no flag guards it.
cmd_local_jsx_no_panel_host
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
A crashing slash command now tells you it crashed
Both mention slash command
-
v2.1.234
A command can decide from its arguments whether it counts as sensitive
Both mention slash command
-
v2.1.234
A slash-command grouping for a command that does not exist
Both mention slash command