rasa-pro 3.12.0rc1__py3-none-any.whl → 3.12.0rc3__py3-none-any.whl

rasa/dialogue_understanding/commands/start_flow_command.py

@@ -141,7 +141,9 @@ class StartFlowCommand(Command):
     def regex_pattern() -> str:
         mapper = {
             CommandSyntaxVersion.v1: r"StartFlow\(['\"]?([a-zA-Z0-9_-]+)['\"]?\)",
-            CommandSyntaxVersion.v2: r"^[^\w]*start flow ['\"]?([a-zA-Z0-9_-]+)['\"]?",
+            CommandSyntaxVersion.v2: (
+                r"""^[\s\W\d]*start flow ['"`]?([a-zA-Z0-9_-]+)['"`]*"""
+            ),
         }
         return mapper.get(
             CommandSyntaxManager.get_syntax_version(),

rasa/dialogue_understanding/commands/utils.py

@@ -1,14 +1,11 @@
-from typing import TYPE_CHECKING, Any, List, Optional, Tuple, Union
+from typing import TYPE_CHECKING, List, Optional, Tuple, Union
 
 import structlog
 
 from rasa.dialogue_understanding.patterns.validate_slot import (
     ValidateSlotPatternFlowStackFrame,
 )
-from rasa.shared.constants import (
-    ACTION_ASK_PREFIX,
-    UTTER_ASK_PREFIX,
-)
+from rasa.shared.constants import ACTION_ASK_PREFIX, UTTER_ASK_PREFIX
 from rasa.shared.core.events import Event, SlotSet
 from rasa.shared.core.slots import Slot
 from rasa.shared.core.trackers import DialogueStateTracker
@@ -100,7 +97,6 @@ def create_validate_frames_from_slot_set_events(
     events: List[Event],
     validate_frames: List[ValidateSlotPatternFlowStackFrame] = [],
     should_break: bool = False,
-    update_corrected_slots: bool = False,
 ) -> Tuple[DialogueStateTracker, List[ValidateSlotPatternFlowStackFrame]]:
     """Process SlotSet events and create validation frames.
 
@@ -111,8 +107,6 @@ def create_validate_frames_from_slot_set_events(
             if True, break out of the event loop as soon as the first non-SlotSet
             event is encountered.
             if False, continue processing the events until the end.
-        update_corrected_slots: whether or not corrected slots in the last
-            correction frame need to be updated.
 
     Returns:
         Tuple of (updated tracker, list of validation frames).
@@ -130,29 +124,5 @@ def create_validate_frames_from_slot_set_events(
 
         if frame:
             validate_frames.append(frame)
-            if update_corrected_slots:
-                tracker = update_corrected_slots_in_correction_frame(
-                    tracker, event.key, event.value
-                )
 
     return tracker, validate_frames
-
-
-def update_corrected_slots_in_correction_frame(
-    tracker: DialogueStateTracker, slot_name: str, slot_value: Any
-) -> DialogueStateTracker:
-    """Update the corrected_slots and new_slot_values of the
-    CorrectionPatternFlowStackFrame with only valid values.
-    """
-    stack = tracker.stack
-    top_frame = stack.top()
-    del top_frame.corrected_slots[slot_name]  # type: ignore[union-attr]
-    top_frame.new_slot_values.remove(slot_value)  # type: ignore[union-attr]
-
-    # since we can't directly modify a stack we have to pop first
-    # and then push back the updated frame
-    stack.pop()
-    stack.push(top_frame)
-    new_events = tracker.create_stack_updated_events(stack)
-    tracker.update_with_events(new_events)
-    return tracker

rasa/dialogue_understanding/generator/command_parser.py

@@ -1,4 +1,5 @@
 import re
+import sys
 from functools import lru_cache
 from typing import Any, Callable, Dict, List, Optional, Type, Union
 
@@ -78,6 +79,44 @@ def _get_additional_parsing_logic(
     return command_to_parsing_fn_mapper.get(command_clz)
 
 
+def validate_custom_commands(command_classes: List[Type[PromptCommand]]) -> None:
+    clz_not_inheriting_from_command_clz = [
+        command_clz
+        for command_clz in command_classes
+        if not issubclass(command_clz, Command)
+    ]
+
+    if clz_not_inheriting_from_command_clz:
+        structlogger.error(
+            "command_parser.validate_custom_commands.invalid_command",
+            invalid_commands=clz_not_inheriting_from_command_clz,
+            event_info=(
+                "The additional command classes must be a subclass of the 'Command' "
+                "class. Please refer to the class in "
+                "`rasa.dialogue_understanding.commands.command.Command`"
+            ),
+        )
+        sys.exit(1)
+
+    clz_not_adhering_to_prompt_command_protocol = [
+        command_clz
+        for command_clz in command_classes
+        if not isinstance(command_clz, PromptCommand)
+    ]
+
+    if clz_not_adhering_to_prompt_command_protocol:
+        structlogger.error(
+            "command_parser.validate_custom_commands.invalid_command",
+            invalid_commands=clz_not_adhering_to_prompt_command_protocol,
+            event_info=(
+                "The additional command classes must adhere to the 'PromptCommand' "
+                "protocol. Please refer to the protocol in "
+                "`rasa.dialogue_understanding.commands.prompt_command.PromptCommand`"
+            ),
+        )
+        sys.exit(1)
+
+
 def parse_commands(
     actions: Optional[str],
     flows: FlowsList,
@@ -93,6 +132,8 @@ def parse_commands(
         return []
 
     commands: List[Command] = []
+    validate_custom_commands(additional_commands or [])
+
     default_commands = DEFAULT_COMMANDS
     if default_commands_to_remove:
         default_commands = _create_default_commands(default_commands_to_remove)

rasa/dialogue_understanding/generator/constants.py

@@ -1,7 +1,9 @@
 from rasa.shared.constants import (
+    MAX_TOKENS_CONFIG_KEY,
     MODEL_CONFIG_KEY,
     OPENAI_PROVIDER,
     PROVIDER_CONFIG_KEY,
+    TEMPERATURE_CONFIG_KEY,
     TIMEOUT_CONFIG_KEY,
 )
 from rasa.shared.utils.llm import (
@@ -12,8 +14,8 @@ from rasa.shared.utils.llm import (
 DEFAULT_LLM_CONFIG = {
     PROVIDER_CONFIG_KEY: OPENAI_PROVIDER,
     MODEL_CONFIG_KEY: DEFAULT_OPENAI_CHAT_MODEL_NAME_ADVANCED,
-    "temperature": 0.0,
-    "max_tokens": DEFAULT_OPENAI_MAX_GENERATED_TOKENS,
+    TEMPERATURE_CONFIG_KEY: 0.0,
+    MAX_TOKENS_CONFIG_KEY: DEFAULT_OPENAI_MAX_GENERATED_TOKENS,
     TIMEOUT_CONFIG_KEY: 7,
 }
 
@@ -28,3 +30,6 @@ FLOW_RETRIEVAL_FLOW_THRESHOLD = 20
 
 COMMAND_PROMPT_FILE_NAME = "command_prompt.jinja2"
 LLM_BASED_COMMAND_GENERATOR_CONFIG_FILE = "config.json"
+
+MODEL_NAME_GPT_4O_2024_11_20 = "gpt-4o-2024-11-20"
+MODEL_NAME_CLAUDE_3_5_SONNET_20240620 = "claude-3-5-sonnet-20240620"

rasa/dialogue_understanding/generator/llm_based_command_generator.py

@@ -175,7 +175,7 @@ class LLMBasedCommandGenerator(
         """
         self.perform_llm_health_check(
             self.config.get(LLM_CONFIG_KEY),
-            DEFAULT_LLM_CONFIG,
+            self.get_default_llm_config(),
             "llm_based_command_generator.train",
             LLMBasedCommandGenerator.__name__,
         )
@@ -332,7 +332,9 @@ class LLMBasedCommandGenerator(
         Raises:
             ProviderClientAPIException: If an error occurs during the LLM API call.
         """
-        llm = llm_factory(self.config.get(LLM_CONFIG_KEY), DEFAULT_LLM_CONFIG)
+        llm = llm_factory(
+            self.config.get(LLM_CONFIG_KEY), self.get_default_llm_config()
+        )
         try:
             return await llm.acompletion(prompt)
         except Exception as e:
@@ -619,3 +621,8 @@ class LLMBasedCommandGenerator(
             )
         )
         return prior_commands, filtered_commands
+
+    @staticmethod
+    def get_default_llm_config() -> Dict[str, Any]:
+        """Get the default LLM config for the command generator."""
+        return DEFAULT_LLM_CONFIG

rasa/dialogue_understanding/generator/multi_step/multi_step_llm_command_generator.py

@@ -226,7 +226,7 @@ class MultiStepLLMCommandGenerator(LLMBasedCommandGenerator):
             # be completed, "predict" the ErrorCommand
             commands = [ErrorCommand()]
 
-        if not commands:
+        if not commands and not prior_commands:
             # if for any reason the final list of commands is empty,
             # "predict" CannotHandle
             commands = [CannotHandleCommand()]

rasa/dialogue_understanding/generator/prompt_templates/command_prompt_v2_claude_3_5_sonnet_20240620_template.jinja2

@@ -1,77 +1,58 @@
+## Task Description
 Your task is to analyze the current conversation context and generate a list of actions to start new business processes that we call flows, to extract slots, or respond to small talk and knowledge requests.
 
+--
+
 ## Available Actions:
-* `start flow flow_name`: Starting a flow. For example, `start flow transfer_money` or `start flow list_contacts`
-* `set slot slot_name slot_value`: Slot setting. For example, `set slot transfer_money_recipient Freddy`. Can be used to correct and change previously set values
-* `cancel flow`: Cancelling the current flow
+* `start flow flow_name`: Starting a flow. For example, `start flow transfer_money` or `start flow list_contacts`.
+* `set slot slot_name slot_value`: Slot setting. For example, `set slot transfer_money_recipient Freddy`. Can be used to correct and change previously set values.
+* `cancel flow`: Cancelling the current flow.
 * `disambiguate flows flow_name1 flow_name2 ... flow_name_n`: Disambiguate which flow should be started when user input is ambiguous by listing the potential flows as options. For example, `disambiguate flows list_contacts add_contact remove_contact ...` if the user just wrote "contacts".
-* `provide info`: Responding to the user's questions by supplying relevant information, such as answering FAQs or explaining services
+* `provide info`: Responding to the user's questions by supplying relevant information, such as answering FAQs or explaining services.
 * `offtopic reply`: Responding to casual or social user messages that are unrelated to any flows, engaging in friendly conversation and addressing off-topic remarks.
-* `hand over`: Handing over to a human, in case the user seems frustrated or explicitly asks to speak to one
+* `hand over`: Handing over to a human, in case the user seems frustrated or explicitly asks to speak to one.
 
+--
 
 ## General Tips
 * Do not fill slots with abstract values or placeholders.
+* For categorical slots try to match the user message with allowed slot values. Use "other" if you cannot match it.
+* Set the boolean slots based on the user response. Map positive responses to `True`, and negative to `False`.
+* Always refer to the slot description to determine what information should be extracted and how it should be formatted.
+* For text slots, extract values exactly as provided by the user unless the slot description specifies otherwise. Preserve formatting and avoid rewording, truncation, or making assumptions.
 * Only use information provided by the user.
 * Use clarification in ambiguous cases.
 * Multiple flows can be started. If a user wants to digress into a second flow, you do not need to cancel the current flow.
+* Do not cancel the flow unless the user explicitly requests it.
 * Strictly adhere to the provided action format.
-* For categorical slots try to match the user message with potential slot values. Use "other" if you cannot match it
 * Focus on the last message and take it one step at a time.
 * Use the previous conversation steps only to aid understanding.
 
+--
 
-## Available Flows:
-Use the following structured date:
-```xml
-<flows>
-    {% for flow in available_flows %}<flow>
-        <name>{{ flow.name }}</name>
-        <description>{{ flow.description }}</description>
-        <slots>{% for slot in flow.slots %}
-            <slot>
-                <name>{{ slot.name }}</name>
-                <description>{{ slot.description }}</description>
-                <allowed_values>{{ slot.allowed_values }}</allowed_values>
-            </slot>{% endfor %}
-        </slots>
-    </flow>
-    {% endfor %}
-</flows>
+## Available Flows and Slots
+Use the following structured data:
+```json
+{"flows":[{% for flow in available_flows %}{"name":"{{ flow.name }}","description":"{{ flow.description }}"{% if flow.slots %},"slots":[{% for slot in flow.slots %}{"name":"{{ slot.name }}"{% if slot.description %},"description":"{{ slot.description }}"{% endif %}{% if slot.allowed_values %},"allowed_values":{{ slot.allowed_values }}{% endif %}}{% if not loop.last %},{% endif %}{% endfor %}]{% endif %}}{% if not loop.last %},{% endif %}{% endfor %}]}
 ```
 
+--
+
 ## Current State
-{% if current_flow != None %}
-Use the following structured date:
-```xml
-<current_state>
-    <active_flow>{{ current_flow }}</active_flow>
-    <current_step>
-        <requested_slot>{{ current_slot }}</requested_slot>
-        <requested_slot_description>{{ current_slot_description }}</requested_slot_description>
-    </current_step>
-    <slots>
-        {% for slot in flow_slots %}<slot>
-            <name>{{ slot.name }}</name>
-            <value>{{ slot.value }}</value>
-            <type>{{ slot.type }}</type>
-            <description>{{ slot.description }}</description>{% if slot.allowed_values %}
-            <allowed_values>{{ slot.allowed_values }}</allowed_values>{% endif %}
-        </slot>
-        {% endfor %}
-    </slots>
-</current_state>
-```
-{% else %}
-You are currently not inside any flow.
-{% endif %}
+{% if current_flow != None %}Use the following structured data:
+```json
+{"active_flow":"{{ current_flow }}","current_step":{"requested_slot":"{{ current_slot }}","requested_slot_description":"{{ current_slot_description }}"},"slots":[{% for slot in flow_slots %}{"name":"{{ slot.name }}","value":"{{ slot.value }}","type":"{{ slot.type }}"{% if slot.description %},"description":"{{ slot.description }}"{% endif %}{% if slot.allowed_values %},"allowed_values":"{{ slot.allowed_values }}"{% endif %}}{% if not loop.last %},{% endif %}{% endfor %}]}
+```{% else %}
+You are currently not inside any flow.{% endif %}
 
+---
 
 ## Conversation History
 {{ current_conversation }}
 
+---
 
 ## Task
-Create an action list with one action per line in response to the users last message: """{{ user_message }}""".
+Create an action list with one action per line in response to the user's last message: """{{ user_message }}""".
 
 Your action list:

rasa/dialogue_understanding/generator/prompt_templates/command_prompt_v2_fallback_other_models_template.jinja2

@@ -0,0 +1,57 @@
+## Task Description
+Your task is to analyze the current conversation context and generate a list of actions to start new business processes that we call flows, to extract slots, or respond to small talk and knowledge requests.
+
+---
+
+## Available Flows and Slots
+Use the following structured data:
+```json
+{"flows":[{% for flow in available_flows %}{"name":"{{ flow.name }}","description":"{{ flow.description }}"{% if flow.slots %},"slots":[{% for slot in flow.slots %}{"name":"{{ slot.name }}"{% if slot.description %},"description":"{{ slot.description }}"{% endif %}{% if slot.allowed_values %},"allowed_values":{{ slot.allowed_values }}{% endif %}}{% if not loop.last %},{% endif %}{% endfor %}]{% endif %}}{% if not loop.last %},{% endif %}{% endfor %}]}
+```
+
+---
+
+## Available Actions:
+* `start flow flow_name`: Starting a flow. For example, `start flow transfer_money` or `start flow list_contacts`.
+* `set slot slot_name slot_value`: Slot setting. For example, `set slot transfer_money_recipient Freddy`. Can be used to correct and change previously set values.
+* `cancel flow`: Cancelling the current flow.
+* `disambiguate flows flow_name1 flow_name2 ... flow_name_n`: Disambiguate which flow should be started when user input is ambiguous by listing the potential flows as options. For example, `disambiguate flows list_contacts add_contact remove_contact ...` if the user just wrote "contacts".
+* `provide info`: Responding to the user's questions by supplying relevant information, such as answering FAQs or explaining services.
+* `offtopic reply`: Responding to casual or social user messages that are unrelated to any flows, engaging in friendly conversation and addressing off-topic remarks.
+* `hand over`: Handing over to a human, in case the user seems frustrated or explicitly asks to speak to one.
+
+---
+
+## General Tips
+* Do not fill slots with abstract values or placeholders.
+* For categorical slots try to match the user message with allowed slot values. Use "other" if you cannot match it.
+* Set the boolean slots based on the user response. Map positive responses to `True`, and negative to `False`.
+* Extract text slot values exactly as provided by the user. Avoid assumptions, format changes, or partial extractions.
+* Only use information provided by the user.
+* Use clarification in ambiguous cases.
+* Multiple flows can be started. If a user wants to digress into a second flow, you do not need to cancel the current flow.
+* Do not cancel the flow unless the user explicitly requests it.
+* Strictly adhere to the provided action format.
+* Focus on the last message and take it one step at a time.
+* Use the previous conversation steps only to aid understanding.
+
+---
+
+## Current State
+{% if current_flow != None %}Use the following structured data:
+```json
+{"active_flow":"{{ current_flow }}","current_step":{"requested_slot":"{{ current_slot }}","requested_slot_description":"{{ current_slot_description }}"},"slots":[{% for slot in flow_slots %}{"name":"{{ slot.name }}","value":"{{ slot.value }}","type":"{{ slot.type }}"{% if slot.description %},"description":"{{ slot.description }}"{% endif %}{% if slot.allowed_values %},"allowed_values":"{{ slot.allowed_values }}"{% endif %}}{% if not loop.last %},{% endif %}{% endfor %}]}
+```{% else %}
+You are currently not inside any flow.{% endif %}
+
+---
+
+## Conversation History
+{{ current_conversation }}
+
+---
+
+## Task
+Create an action list with one action per line in response to the user's last message: """{{ user_message }}""".
+
+Your action list:

rasa/dialogue_understanding/generator/prompt_templates/command_prompt_v2_gpt_4o_2024_11_20_template.jinja2

@@ -1,73 +1,46 @@
 ## Task Description
 Your task is to analyze the current conversation context and generate a list of actions to start new business processes that we call flows, to extract slots, or respond to small talk and knowledge requests.
 
---
+---
+
+## Available Flows and Slots
+Use the following structured data:
+```json
+{"flows":[{% for flow in available_flows %}{"name":"{{ flow.name }}","description":"{{ flow.description }}"{% if flow.slots %},"slots":[{% for slot in flow.slots %}{"name":"{{ slot.name }}"{% if slot.description %},"description":"{{ slot.description }}"{% endif %}{% if slot.allowed_values %},"allowed_values":{{ slot.allowed_values }}{% endif %}}{% if not loop.last %},{% endif %}{% endfor %}]{% endif %}}{% if not loop.last %},{% endif %}{% endfor %}]}
+```
+
+---
 
 ## Available Actions:
-* `start flow flow_name`: Starting a flow. For example, `start flow transfer_money` or `start flow list_contacts`
-* `set slot slot_name slot_value`: Slot setting. For example, `set slot transfer_money_recipient Freddy`. Can be used to correct and change previously set values
-* `cancel flow`: Cancelling the current flow
+* `start flow flow_name`: Starting a flow. For example, `start flow transfer_money` or `start flow list_contacts`.
+* `set slot slot_name slot_value`: Slot setting. For example, `set slot transfer_money_recipient Freddy`. Can be used to correct and change previously set values.
+* `cancel flow`: Cancelling the current flow.
 * `disambiguate flows flow_name1 flow_name2 ... flow_name_n`: Disambiguate which flow should be started when user input is ambiguous by listing the potential flows as options. For example, `disambiguate flows list_contacts add_contact remove_contact ...` if the user just wrote "contacts".
-* `provide info`: Responding to the user's questions by supplying relevant information, such as answering FAQs or explaining services
+* `provide info`: Responding to the user's questions by supplying relevant information, such as answering FAQs or explaining services.
 * `offtopic reply`: Responding to casual or social user messages that are unrelated to any flows, engaging in friendly conversation and addressing off-topic remarks.
-* `hand over`: Handing over to a human, in case the user seems frustrated or explicitly asks to speak to one
+* `hand over`: Handing over to a human, in case the user seems frustrated or explicitly asks to speak to one.
 
---
+---
 
 ## General Tips
 * Do not fill slots with abstract values or placeholders.
+* For categorical slots try to match the user message with allowed slot values. Use "other" if you cannot match it.
+* Set the boolean slots based on the user response. Map positive responses to `True`, and negative to `False`.
+* Extract text slot values exactly as provided by the user. Avoid assumptions, format changes, or partial extractions.
 * Only use information provided by the user.
 * Use clarification in ambiguous cases.
 * Multiple flows can be started. If a user wants to digress into a second flow, you do not need to cancel the current flow.
+* Do not cancel the flow unless the user explicitly requests it.
 * Strictly adhere to the provided action format.
-* For categorical slots try to match the user message with potential slot values. Use "other" if you cannot match it
 * Focus on the last message and take it one step at a time.
 * Use the previous conversation steps only to aid understanding.
 
---
-
-## Available Flows and Slots
-Use the following structured date:
-```json
-{
-    "flows": [
-        {% for flow in available_flows %}{
-            "name": "{{ flow.name }}",
-            "description": "{{ flow.description }}"{% if flow.slots %},
-            "slots": [{% for slot in flow.slots %}
-                {
-                    "name": "{{ slot.name }}"{% if slot.description %},
-                    "description": "{{ slot.description }}"{% endif %}{% if slot.allowed_values %},
-                    "allowed_values": {{ slot.allowed_values }}{% endif %}
-                }{% if not loop.last %},{% endif %}{% endfor %}
-            ]{% endif %}
-        }{% if not loop.last %},
-        {% endif %}{% endfor %}
-    ]
-}
-```
-
---
+---
 
 ## Current State
-{% if current_flow != None %}Use the following structured date:
+{% if current_flow != None %}Use the following structured data:
 ```json
-{
-    "active_flow": "{{ current_flow }}",
-    "current_step": {
-        "requested_slot": "{{ current_slot }}",
-        "requested_slot_description": "{{ current_slot_description }}"
-    },
-    "slots": [{% for slot in flow_slots %}
-        {
-            "name": "{{ slot.name }}",
-            "value": "{{ slot.value }}",
-            "type": "{{ slot.type }}"{% if slot.description %},
-            "description": "{{ slot.description }}"{% endif %}{% if slot.allowed_values %},
-            "allowed_values": "{{ slot.allowed_values }}"{% endif %}
-        }{% if not loop.last %},{% endif %}{% endfor %}
-    ]
-}
+{"active_flow":"{{ current_flow }}","current_step":{"requested_slot":"{{ current_slot }}","requested_slot_description":"{{ current_slot_description }}"},"slots":[{% for slot in flow_slots %}{"name":"{{ slot.name }}","value":"{{ slot.value }}","type":"{{ slot.type }}"{% if slot.description %},"description":"{{ slot.description }}"{% endif %}{% if slot.allowed_values %},"allowed_values":"{{ slot.allowed_values }}"{% endif %}}{% if not loop.last %},{% endif %}{% endfor %}]}
 ```{% else %}
 You are currently not inside any flow.{% endif %}
 
@@ -79,6 +52,6 @@ You are currently not inside any flow.{% endif %}
 ---
 
 ## Task
-Create an action list with one action per line in response to the users last message: """{{ user_message }}""".
+Create an action list with one action per line in response to the user's last message: """{{ user_message }}""".
 
 Your action list: