{"version":"2.1.277","anchor":"session-id-telemetry-suppressed-for-remote-trigger-entrypoin","canonical_anchor":"session-id-telemetry-suppressed-for-remote-trigger-entrypoin","heading":"session_id telemetry suppressed for remote-trigger entrypoints","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/session-id-telemetry-suppressed-for-remote-trigger-entrypoin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### session_id telemetry suppressed for remote-trigger entrypoints\n\nTelemetry no longer records a session_id when Claude Code was started via a remote trigger\n\n**What**\n\nA telemetry helper that used to attach the current `session_id` to outgoing telemetry whenever one was available now leaves it out if the process was launched through a remote trigger entrypoint (a way of starting Claude Code programmatically rather than by hand).\n\n**Why**\n\nThis means telemetry from remotely-triggered runs is harder to tie back to a specific session, which matters mainly for diagnosing issues in automated or remotely-started Claude Code runs.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}