{"version":"2.1.280","anchor":"session-telemetry-gains-remote-control-lane-and-projects-ses","canonical_anchor":"session-telemetry-gains-remote-control-lane-and-projects-ses","heading":"Session telemetry gains remote_control_lane and projects_session fields","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/session-telemetry-gains-remote-control-lane-and-projects-ses","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Session telemetry gains remote_control_lane and projects_session fields\n\nSession-start telemetry can now include remote_control_lane and projects_session fields\n\n**Unclear.** The finding doesn't say what values these fields take or when they're populated.\n\n**What**\n\nThe telemetry event sent when a session starts can now optionally carry two new fields, `remote_control_lane` and `projects_session`, in addition to the existing `subscription_type`, `parent_agent_id`, `cc_prompt_id`, and `desktop_app_version` fields.\n\n**Why**\n\nThis gives more context about how and where a session was started, useful for distinguishing sessions started via remote control or as part of a project.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}