Under the hood
Telemetry no longer records a session_id when Claude Code was started via a remote trigger
What
A 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).
Why
This 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.