{"version":"2.1.273","anchor":"remote-bridge-repl-sessions-gain-fork-conversation-and-pendi","canonical_anchor":"remote-bridge-repl-sessions-gain-fork-conversation-and-pendi","heading":"Remote-bridge REPL sessions gain fork-conversation and pending-prompt-count hooks","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/remote-bridge-repl-sessions-gain-fork-conversation-and-pendi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Remote-bridge REPL sessions gain fork-conversation and pending-prompt-count hooks\n\nRemote-bridge REPL sessions gain hooks for forking a conversation and checking for pending prompts\n\n**Unclear.** What feature uses these hooks, and what effect they have for someone using Remote Control, isn't established by the evidence.\n\n**What**\n\nThe session builder used for remote and headless REPL sessions (the Remote Control v2 transport handler) now passes two new items into each connection's configuration: an `onForkConversation` callback, and a `hasPendingPrompts()` function that reports whether there are prompts still waiting to be handled. These sit alongside the existing `onMcpSetServers`, `outboundOnly`, and `writeFrame` fields.\n\n**Why**\n\nThe finding doesn't say what calls these new hooks or what user-facing feature they support, only that the plumbing for forking a conversation and checking pending-prompt state is now in place for remote sessions.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}