{"version":"2.1.232","anchor":"bridge-worker-processes-are-launched-with-a-resume-argument","canonical_anchor":"bridge-worker-processes-are-launched-with-a-resume-argument","heading":"Bridge worker processes are launched with a resume argument","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/bridge-worker-processes-are-launched-with-a-resume-argument","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Bridge worker processes are launched with a resume argument\n\nRemote bridge worker processes now start with a resume argument derived from the session URL.\n\n**What**\n\nThe child process started for a remote-control bridge session is now passed a `--resume=` argument derived from the session's SDK URL, in addition to the existing `--sdk-url`, `--session-id` and `--replay-user-messages` flags.\n\n**Evidence**\n\n`\"--replay-user-messages\"`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}