{"version":"2.1.274","anchor":"slash-command-local-command-output-can-be-patched-in-place","canonical_anchor":"slash-command-local-command-output-can-be-patched-in-place","heading":"Slash-command \/ local-command output can be patched in place after the fact","tier":"internal","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/slash-command-local-command-output-can-be-patched-in-place","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Slash-command \/ local-command output can be patched in place after the fact\n\nSlash-command output can now be edited in place after it's already been produced\n\n**What**\n\nA new internal function can update the output of an already-completed slash command or local command (such as its stdout or stderr text) with new content, and can also replace related context entries. This only happens if the current turn hasn't already moved on, such as by querying further, advancing to the next input, or finishing.\n\n**Why**\n\nThis allows command output to be corrected or supplemented after the fact, as long as the turn is still in a state where that update can safely apply.\n\n- Area: Slash Commands\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}