{"version":"2.1.277","anchor":"fork-conversation-gains-extra-availability-gates","canonical_anchor":"fork-conversation-precondition-check-reworked","heading":"fork_conversation precondition checks reworked","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/fork-conversation-gains-extra-availability-gates","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### fork_conversation precondition checks reworked\n\nThe fork_conversation RPC's availability checks were reworked to require two new gate functions and a direct bridge session ID check\n\n**Unclear.** What conditions the two new checks (`Un()` and `At()`) actually test is not stated in the finding.\n\n**What**\n\n- The `fork_conversation` RPC's early bail-out conditions changed from four checks to three: it now checks two gate functions plus a freshly computed bridge session ID for being undefined, rather than relying on a separately tracked variable.\n\n- On top of the existing `sdkUrl`-based check, `fork_conversation` now returns \"unsupported\" if either of these two additional gate checks fails.\n\n**Why** This tightens up when conversation forking is considered available, and adds conditions under which the RPC now reports itself unsupported instead of proceeding.\n\n- Area: Remote Control\n- Names: `fork_conversation`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}