{"version":"2.1.300","anchor":"queued-prompts-slash-command-filtering-now-bypassed-by-a-fl","canonical_anchor":"queued-prompts-slash-command-filtering-now-bypassed-by-a-fl","heading":"Queued slash commands can now be run in a batch with other prompts","tier":"notice","area":"Input Queue","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/queued-prompts-slash-command-filtering-now-bypassed-by-a-fl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Queued slash commands can now be run in a batch with other prompts\n\nSlash commands you queue while Claude is busy can now be included when queued prompts run together, where before they were always kept out\n\n**Unclear.** What decides whether a queued slash command joins the batch is not shown.\n\n**What**\n\nMessages you type while Claude is still working are queued and can be run together as one batch. A slash command (a command starting with `\/`) used to be kept out of that batch every time. Now it is kept out only when a check says so, so in some cases it runs along with the other queued prompts.\n\nQueued messages also carry some extra information through to the step that processes your input.\n\n**Why**\n\nThis changes how queued slash commands are handled, so a command you queue may run together with your other waiting messages.\n\n- Area: Input Queue\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}