{"version":"2.1.268","anchor":"sdkprint-mode-result-event-gains-a-local-command-field","canonical_anchor":"sdkprint-mode-result-event-gains-a-local-command-field","heading":"Local slash-command results can now surface a localCommand field","tier":"use","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/sdkprint-mode-result-event-gains-a-local-command-field","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Local slash-command results can now surface a localCommand field\n\nBoth the SDK's final result event and local slash-command dispatch can now include a localCommand field in their output.\n\n**Unclear.** What triggers the condition for including local_command, and what value it carries, is not specified in the evidence.\n\n**What**\n\n- The final \"success\" result event emitted at the end of an SDK\/print-mode query can now optionally include a `local_command` field, built from a helper call, alongside its existing fields.\n\n- The command-dispatch return object also gained a conditional `localCommand` field, included only when the engine did not defer the slash command to the model (i.e. `engineDeferredSlash` is false).\n\n**Why** This surfaces which local slash command handled a request directly in the result output, useful for SDK consumers and tooling that need to know a command was resolved locally rather than by the model.\n\n- Area: SDK\n- Names: `local_command`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}