{"version":"2.1.247","anchor":"cloud-sessions-now-report-turn-activity-to-the-environment-m","canonical_anchor":"cloud-sessions-now-report-turn-activity-to-the-environment-m","heading":"Cloud sessions now report turn activity to the environment manager","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/cloud-sessions-now-report-turn-activity-to-the-environment-m","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Cloud sessions now report turn activity to the environment manager\n\nCloud sessions now report turn start, progress and end to the environment manager.\n\n**What**\n\nThe hook that drives a remote (cloud) session builds an environment-manager driver and notifies it as frames arrive from the stream: turn-in-flight on assistant, stream-event and requesting-status frames and on every tool-progress frame, worker-init on the init frame, and turn-ended on a result frame.\n\n**Details**\n\n- These lifecycle notifications already existed in 2.1.246; what is new is that the remote session stream drives them, so the cloud environment manager sees turn activity.\n- The driver is only constructed when two conditions pass and the session is not viewer-only. The two conditions are not tied to any named flag or setting in the build, so whether the driver exists for a given cloud session is decided by that unnamed logic.\n\n**Evidence**\n\n`onTurnInFlight`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}