{"version":"2.1.265","anchor":"local-slash-command-execution-unified-between-direct-and-bri","canonical_anchor":"local-slash-command-execution-unified-between-direct-and-bri","heading":"Local slash-command execution unified and simplified","tier":"internal","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/local-slash-command-execution-unified-between-direct-and-bri","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Local slash-command execution unified and simplified\n\nLocal slash commands now run through one shared path and skip the dialog\/panel host entirely\n\n**What**\n\nRunning a local slash command and appending its result has been factored into one shared function, now used both for normal command invocation and for commands dispatched over a remote\/bridge connection. Bridge-originated commands are tagged with `dispatchedOverBridge: true` so they can be distinguished.\n\nCommand dispatch now special-cases commands of type `local` to run directly through this shared path and log a `tengu_immediate_command_executed` telemetry event, without ever opening a panel or going through the dialog-host's JSX-building step. Only `local-jsx` commands (ones that render their own interactive UI) still go through the dialog-host path.\n\n**Why**\n\nThis removes duplicated logic between direct and bridge-originated command execution and avoids unnecessary UI\/panel overhead for plain local commands that don't need one.\n\n- Area: Slash Commands\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}