{"version":"2.1.265","anchor":"local-slash-command-results-can-now-be-patched-into-an-alrea","canonical_anchor":"local-slash-command-results-can-now-be-patched-into-an-alrea","heading":"Local slash-command results can now be patched into an already-queued message (deferred slash commands)","tier":"notice","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/local-slash-command-results-can-now-be-patched-into-an-alrea","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Local slash-command results can now be patched into an already-queued message (deferred slash commands)\n\nSlash commands can now finish their output after being queued and patch it into your queued message\n\n**What**\n\nWhen a local slash command's output isn't ready yet but you've already queued a message containing it, Claude Code can now go back and patch the queued message once the result arrives, rather than requiring the result up front. This works by finding a queued message that starts with `<local-command-stdout>` or `<local-command-stderr>` and rewriting its contents in place, paired with new internal helpers that build the initial placeholder message and track it by a `deferredSlashUuid`.\n\n**Why**\n\nThis lets a local slash command's result show up correctly even if it finishes after the message using it has already been queued for sending, instead of the message being stuck with stale or missing output.\n\n- Area: Slash Commands\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}