{"version":"2.1.261","anchor":"resume-can-now-adoptaccept-custom-non-uuid-session-id","canonical_anchor":"resume-can-now-adoptaccept-custom-non-uuid-session-id","heading":"--resume can now adopt\/accept custom (non-UUID) session IDs when used with SDK URL sessions","tier":"use","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/resume-can-now-adoptaccept-custom-non-uuid-session-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### `--resume` can now adopt\/accept custom (non-UUID) session IDs when used with SDK URL sessions\n\n--resume can now accept custom, non-UUID session IDs for SDK URL sessions.\n\nA new helper decides whether a resumed session ID is adopted and whether the resume is effectively a fork. `--resume` now accepts custom, non-UUID session IDs specifically when `d.sdkUrl` is set, for SDK URL sessions. The returned message bundle now also reports `resumedAsFork`.\n\n- Area: Sessions\n- Names: `--resume`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}