Group of 2 Under the hood
No documentation found
The fork_conversation RPC's availability checks were reworked to require two new gate functions and a direct bridge session ID check
What
- The
fork_conversationRPC'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. - On top of the existing
sdkUrl-based check,fork_conversationnow returns "unsupported" if either of these two additional gate checks fails.
Why This tightens up when conversation forking is considered available, and adds conditions under which the RPC now reports itself unsupported instead of proceeding.
Names in the bundlefork_conversation