{"version":"2.1.299","anchor":"local-command-run-event-can-carry-a-plugin-name-chrome-brid","canonical_anchor":"local-command-run-event-can-carry-a-plugin-name-chrome-brid","heading":"Local command runs record the plugin, plus new diagnostic events","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/local-command-run-event-can-carry-a-plugin-name-chrome-brid","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Local command runs record the plugin, plus new diagnostic events\n\nThe record of a local command run now includes the plugin it came from, and new diagnostic events cover the Chrome bridge and remote sessions\n\n**What**\n\nWhen Claude Code records that a local command ran, the record now includes the plugin's name if the command came from a plugin (an add-on package). Before, it held only the command and its arguments.\n\nClaude Code also gains new diagnostic events, including ones for:\n\n- a Chrome bridge tool call that disconnected or was lost\n\n- a shell line queued in a remote session\n\n- agents cut off in a cloud session\n\n- the calling session in a cloud session\n\n- a hold on IDE changes that have not been seen yet\n\n**Why**\n\nThese are small diagnostic changes with little effect on how Claude Code behaves for you.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}