{"version":"2.1.271","anchor":"command-execution-now-records-a-commandrun-marker-on-transcr","canonical_anchor":"command-execution-now-records-a-commandrun-marker-on-transcr","heading":"Command execution now records a commandRun marker on transcript messages","tier":"internal","area":"Transcript","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/command-execution-now-records-a-commandrun-marker-on-transcr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Command execution now records a commandRun marker on transcript messages\n\nCommand execution now attaches a commandRun marker to transcript messages\n\n**Unclear.** What consumes this new field, and how it changes what a user sees, is not specified in the finding.\n\n**What**\n\nWhen a command is run, whether immediately in the local session or via a bridge, the resulting transcript message now carries a `commandRun` field alongside its existing text and error content.\n\n**Why**\n\nThis appears to record which command produced a given transcript entry, likely for tracking or displaying command-run history more precisely.\n\n- Area: Transcript\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}