{"version":"2.1.305","anchor":"bash-command-events-carry-stream-timestamps","canonical_anchor":"bash-command-events-carry-stream-timestamps","heading":"Shell command events now carry timing information","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/bash-command-events-carry-stream-timestamps","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Shell command events now carry timing information\n\nEvents for shell commands now copy their creation and processing times into the data they send, including when the session stream started\n\n**What**\n\nWhen Claude Code reports that a shell command ran, the report now copies two times into the data it sends: when the event was created and when processing began. They go under keys that include `session_stream_started_at`. If either value is not text, it is left out.\n\n**Why**\n\nShell command events in remote sessions now include timing data, so it is possible to see when commands happened relative to the session.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}