dv-pipecat-flows 0.0.22.dev2200__tar.gz → 0.0.22.dev2300__tar.gz

{dv_pipecat_flows-0.0.22.dev2200/src/dv_pipecat_flows.egg-info → dv_pipecat_flows-0.0.22.dev2300}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dv-pipecat-flows
-Version: 0.0.22.dev2200
+Version: 0.0.22.dev2300
 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.22.dev2200 → dv_pipecat_flows-0.0.22.dev2300/src/dv_pipecat_flows.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dv-pipecat-flows
-Version: 0.0.22.dev2200
+Version: 0.0.22.dev2300
 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.22.dev2200 → dv_pipecat_flows-0.0.22.dev2300}/src/pipecat_flows/actions.py

@@ -25,6 +25,7 @@ Actions are used to perform side effects during conversations, such as:
 
 import asyncio
 import inspect
+import re
 from dataclasses import dataclass
 from typing import TYPE_CHECKING, Callable, Dict, List, Optional, Tuple
 
@@ -56,6 +57,48 @@ if TYPE_CHECKING:
 ONGOING_ACTIONS_WAIT_TIMEOUT_S = 60.0
 
 
+# Router/Agent-extracted variable token: ``[{name}]`` (distinct from custom
+# ``{{name}}`` on the FE — see VariableSelect.tsx). Resolved at TTS time from
+# ``flow_manager.state``, where ``_run_router_node`` (and the flattened
+# agent_node→llm_router path) writes the LLM's extracted args. Backend
+# lowering only substitutes compile-time vars (custom_args, api_responses);
+# anything a router extracts at runtime needs this pass to reach TTS.
+#
+# Pattern matches BOTH the FE's dominant mention form ``@[{var}]`` (the
+# ``@``-prefixed visible text inside a Tiptap mention span) AND the raw
+# ``[{var}]`` form — mirrors how ``replace_custom_variables`` handles both
+# ``@{{var}}`` and ``{{var}}`` for custom_args.
+_EXTRACT_VAR_RE = re.compile(
+    r"@?\[\{\s*([A-Za-z_][A-Za-z0-9_.]*)\s*\}\]"
+)
+
+
+def _substitute_extract_vars(text: str, state: dict) -> str:
+    """Replace ``[{var}]`` / ``@[{var}]`` occurrences with ``state[var]``.
+
+    Supports dotted paths (``[{user.name}]``). Unknown variables (key not
+    in state, or any path segment missing) are LEFT LITERAL — the marker
+    survives so downstream debugging can spot the misconfigured extract.
+    """
+    if not text or "[{" not in text or not isinstance(state, dict):
+        return text
+
+    def _resolve(key: str):
+        cur = state
+        for seg in key.split("."):
+            if isinstance(cur, dict) and seg in cur:
+                cur = cur[seg]
+            else:
+                return None
+        return cur
+
+    def _repl(match: "re.Match[str]") -> str:
+        value = _resolve(match.group(1))
+        return str(value) if value is not None else match.group(0)
+
+    return _EXTRACT_VAR_RE.sub(_repl, text)
+
+
 @dataclass
 class FunctionActionFrame(ControlFrame):
     """Frame containing a function action to be executed.
@@ -432,6 +475,16 @@ class ActionManager:
             logger.error("TTS action missing 'text' / 'text_variants' field")
             return
 
+        # Runtime resolution of [{var}] / @[{var}] tokens against
+        # flow_manager.state. Backend lowering substitutes {{var}} (custom
+        # args) and ((tool.field)) (pre-call outputs) at compile time, but
+        # router/agent-extracted vars only exist at runtime — without this
+        # pass, the bot speaks literals like "@[{user_name}]" verbatim.
+        # text_raw stays unrendered so the split-cache's prefix derivation
+        # remains stable across calls.
+        state = self._flow_manager.state if isinstance(self._flow_manager.state, dict) else {}
+        text = _substitute_extract_vars(text, state)
+
         await self._maybe_switch_tts_service_for_action(action)
 
         use_cache = action.get("use_cache", False)