{"version":"2.1.217","anchor":"remote-workflow-launch-via-server-events-ccr","canonical_anchor":"remote-workflow-launch-via-server-events-ccr","heading":"Remote Workflow Launch via Server Events (CCR)","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.217\/e\/remote-workflow-launch-via-server-events-ccr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.217","markdown":"### Remote Workflow Launch via Server Events (CCR)\n\nClaude Code Remote sessions can now receive `workflow_launch` SSE events from the server, which trigger automatic workflow execution. This enables server-initiated multi-agent workflows in remote sessions without requiring a user to type a command.\n\nThe flow:\n\n- Server pushes a `workflow_launch` event with a signed workflow bundle (filestore path + SHA256)\n- Claude Code fetches the bundle, verifies the SHA256, and validates the format (version byte, script frame, args frame)\n- If all checks pass, the script is executed via the workflow engine\n- Results are posted back to the server as a `workflow_launch_result` system event\n\nPolicy gates:\n\n- Blocked entirely if `disableWorkflows` is set in managed settings (separate message from org policy block)\n- Blocked if org policy `allow_workflows` is false\n- At most one `workflow_launch` event per session is permitted\n\nThe `CLAUDE_CODE_REMOTE_SESSION_ORIGIN` env var (set to `\"review\"`) bypasses the org policy check for server-authored carriers.\n\n**Evidence**\n\nLaunch handler (search for `\"workflow_launch received outside a remote (CCR) session\"`) and bundle validation (search for `\"unsupported bundle format version\"`)"}