{"version":"2.1.247","anchor":"more-than-one-interactive-slash-command-can-be-on-screen-at-","canonical_anchor":"more-than-one-interactive-slash-command-can-be-on-screen-at-","heading":"More than one interactive slash command can be on screen at once","tier":"notice","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/more-than-one-interactive-slash-command-can-be-on-screen-at-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### More than one interactive slash command can be on screen at once\n\nSeveral interactive slash commands can now be on screen at once and closed individually.\n\n**What**\n\nInteractive command output is now tracked in a registry that gives each render its own id rather than sharing one slot, so several such commands can be displayed together and closed individually.\n\n**Details**\n\n- Each render gets an id of the form `local-jsx-N`; the manager exposes `close()` and `closeAll()` and resolves each render as either `\"closed\"` or `\"dismissed\"`.\n- The REPL call site now shows a command with `{ commandName, immediate: !0, hidesPrompt: !1 }`.\n\n**Evidence**\n\n`local-jsx-`\n\n- Area: Slash Commands\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}