dv-pipecat-flows 0.0.26.dev142__tar.gz → 0.0.26.dev145__tar.gz

{dv_pipecat_flows-0.0.26.dev142/src/dv_pipecat_flows.egg-info → dv_pipecat_flows-0.0.26.dev145}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dv-pipecat-flows
-Version: 0.0.26.dev142
+Version: 0.0.26.dev145
 Summary: Conversation Flow management for Pipecat AI applications
 License: BSD 2-Clause License
 Project-URL: Source, https://github.com/pipecat-ai/pipecat-flows

{dv_pipecat_flows-0.0.26.dev142 → dv_pipecat_flows-0.0.26.dev145/src/dv_pipecat_flows.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dv-pipecat-flows
-Version: 0.0.26.dev142
+Version: 0.0.26.dev145
 Summary: Conversation Flow management for Pipecat AI applications
 License: BSD 2-Clause License
 Project-URL: Source, https://github.com/pipecat-ai/pipecat-flows

dv_pipecat_flows-0.0.26.dev145/src/dv_pipecat_flows.egg-info/scm_version.json

@@ -0,0 +1,8 @@
+{
+  "tag": "0.0.25",
+  "distance": 145,
+  "node": "g056447d2",
+  "dirty": false,
+  "branch": "dv-stage",
+  "node_date": "2026-10-08"
+}

{dv_pipecat_flows-0.0.26.dev142 → dv_pipecat_flows-0.0.26.dev145}/src/pipecat_flows/manager.py

@@ -53,6 +53,9 @@ from utils.collect_prompts import collect_prompt
 from pipecat.frames.frames import (
     DTMFUpdateSettingsFrame,
     FunctionCallResultProperties,
+    InterruptionFrame,
+    LLMFullResponseEndFrame,
+    LLMFullResponseStartFrame,
     LLMMessagesAppendFrame,
     LLMMessagesUpdateFrame,
     LLMRunFrame,
@@ -265,6 +268,11 @@ def extract_conversation_messages(
 # drained the terminal frame. Coarse on purpose — nothing waits on it.
 _CALL_END_POLL_INTERVAL_S = 5.0
 
+# How long a RESET_WITH_CONVERSATION carry waits for the reply in flight to be
+# saved (see FlowManager._wait_for_reply_saved). In a chat session the end frame
+# lands within milliseconds of the transition.
+_REPLY_SAVE_TIMEOUT_S = 1.5
+
 # How long to let an utterance that straddled the wait ceiling finish
 # committing. The caller started speaking just before the ceiling fired, so STT
 # has a final in flight; deciding anything before it lands means classifying
@@ -453,6 +461,20 @@ class FlowManager:
         # Signature:  is_injected(message) -> bool
         self.injected_message_filter: Optional[Callable[[Any], bool]] = None
 
+        # Chat sessions: before RESET_WITH_CONVERSATION carries the conversation into
+        # the next node, wait for the assistant aggregator to save the reply in flight,
+        # so text the LLM wrote alongside the transition is carried too (see
+        # `_wait_for_reply_saved`). Off by default: in a voice call the reply is saved
+        # only once it has been spoken, so waiting would hold the hop for the speech.
+        self.carry_waits_for_reply: bool = False
+        # Replies the assistant aggregator has started but not yet saved, counted from
+        # its own frame events (`_track_assistant_reply`); `_reply_saved` is set while
+        # there are none.
+        self._replies_in_flight = 0
+        self._reply_saved = asyncio.Event()
+        self._reply_saved.set()
+        self._watch_assistant_replies()
+
         # Wired in `initialize()` once the pipeline is up. Tracks the timestamp
         # of the latest UserStoppedSpeakingFrame so router-mode nodes can gate
         # their LLM classification on "user has actually replied" instead of
@@ -5078,6 +5100,54 @@ In all of these cases, you can provide a `name` in your new node's config for de
             resolved.append(message)
         return resolved
 
+    def _watch_assistant_replies(self) -> None:
+        """Follow the assistant aggregator's replies through its on_after_process_frame event."""
+        assistant = self._context_aggregator.assistant() if self._context_aggregator else None
+        add_event_handler = getattr(assistant, "add_event_handler", None)
+        if add_event_handler is None:
+            return
+        try:
+            add_event_handler("on_after_process_frame", self._track_assistant_reply)
+        except Exception as exc:  # never let reply tracking break flow setup
+            logger.debug(f"Not tracking assistant replies: {exc}")
+
+    async def _track_assistant_reply(self, _aggregator: Any, frame: Any) -> None:
+        """Count replies in flight. The aggregator saves a reply's text to the context
+        while processing its LLMFullResponseEndFrame, so after that frame it is saved."""
+        if isinstance(frame, LLMFullResponseStartFrame):
+            self._replies_in_flight += 1
+            self._reply_saved.clear()
+        elif isinstance(frame, (LLMFullResponseEndFrame, InterruptionFrame)):
+            if isinstance(frame, InterruptionFrame):
+                self._replies_in_flight = 0
+            else:
+                self._replies_in_flight = max(0, self._replies_in_flight - 1)
+            if not self._replies_in_flight:
+                self._reply_saved.set()
+
+    async def _wait_for_reply_saved(self) -> None:
+        """Wait, briefly, until the assistant aggregator has saved the reply in flight.
+
+        A transition fires on its function-call result, a SystemFrame that overtakes
+        the reply's queued text and its LLMFullResponseEndFrame. The aggregator adds
+        that text to the context only at the end frame, so a carry taken before it
+        leaves out what the LLM wrote alongside the transition ("Plans that work well
+        for NRIs -") and the LLMMessagesUpdateFrame then erases it from the live
+        context: the customer saw it, the LLM never does, and the next node re-routes
+        on a turn that was already answered (Policybazaar chat, Oct 2026).
+
+        Capped, so a lost end frame only delays the hop.
+        """
+        if self._reply_saved.is_set():
+            return
+        try:
+            await asyncio.wait_for(self._reply_saved.wait(), timeout=_REPLY_SAVE_TIMEOUT_S)
+        except asyncio.TimeoutError:
+            logger.warning(
+                f"Reply still in flight after {_REPLY_SAVE_TIMEOUT_S}s; carrying the "
+                "conversation without it"
+            )
+
     async def _update_llm_context(
         self,
         role_messages: Optional[List[dict]],
@@ -5156,6 +5226,8 @@ In all of these cases, you can provide a `name` in your new node's config for de
                 # prompt and tool-call/tool-result logs are dropped. Placed after
                 # role_messages (the new system instruction) and before task
                 # messages, mirroring the RESET_WITH_SUMMARY layout.
+                if self.carry_waits_for_reply:
+                    await self._wait_for_reply_saved()
                 carried = extract_conversation_messages(
                     self._without_injected(
                         self._context_aggregator.user()._context.get_messages()

dv_pipecat_flows-0.0.26.dev142/src/dv_pipecat_flows.egg-info/scm_version.json

@@ -1,8 +0,0 @@
-{
-  "tag": "0.0.25",
-  "distance": 142,
-  "node": "g5494275d",
-  "dirty": false,
-  "branch": "dv-stage",
-  "node_date": "2026-10-07"
-}