rasa-pro 3.13.1a18__py3-none-any.whl → 3.13.1a20__py3-none-any.whl

rasa/builder/create_openai_vector_store.py

@@ -1,228 +0,0 @@
-#!/usr/bin/env python3
-"""Script to create and populate OpenAI vector store with Rasa documentation."""
-
-import json
-import sys
-from pathlib import Path
-from typing import Dict, List
-
-import openai
-import structlog
-
-structlogger = structlog.get_logger()
-
-# Configuration
-DOCS_DIR = "rasa_docs_md"
-FILE_IDS_FILE = "file_ids.json"
-MARKDOWN_TO_URL_FILE = "markdown_to_url.json"
-ASSISTANT_NAME = "Rasa Docs Assistant"
-
-
-def load_url_mapping() -> Dict[str, str]:
-    """Load the markdown filename to URL mapping."""
-    markdown_to_url_file = Path(MARKDOWN_TO_URL_FILE)
-
-    if not markdown_to_url_file.exists():
-        raise FileNotFoundError(
-            f"URL mapping file {markdown_to_url_file} not found. "
-            "Please run scrape_rasa_docs.py first."
-        )
-
-    with open(markdown_to_url_file, "r") as f:
-        return json.load(f)
-
-
-def get_markdown_files(docs_dir: str = DOCS_DIR) -> List[Path]:
-    """Get all markdown files in the docs directory."""
-    docs_path = Path(docs_dir)
-
-    if not docs_path.exists():
-        raise FileNotFoundError(f"Documentation directory {docs_dir} not found")
-
-    md_files = list(docs_path.glob("*.md"))
-    if not md_files:
-        raise FileNotFoundError(f"No markdown files found in {docs_dir}")
-
-    structlogger.info("vector_store.found_files", count=len(md_files))
-    return md_files
-
-
-def load_or_upload_files(client: openai.OpenAI) -> List[Dict[str, str]]:
-    """Load existing file IDs or upload files to OpenAI."""
-    file_ids_file = Path(FILE_IDS_FILE)
-
-    if file_ids_file.exists():
-        structlogger.info("vector_store.loading_existing_files")
-        with open(file_ids_file, "r") as f:
-            return json.load(f)
-
-    return upload_files(client)
-
-
-def upload_files(client: openai.OpenAI) -> List[Dict[str, str]]:
-    """Upload markdown files to OpenAI."""
-    structlogger.info("vector_store.uploading_files")
-
-    md_files = get_markdown_files()
-    uploaded_files = []
-
-    for md_file in md_files:
-        try:
-            with open(md_file, "rb") as f:
-                uploaded = client.files.create(file=f, purpose="assistants")
-
-            file_info = {"file_id": uploaded.id, "file_name": md_file.name}
-            uploaded_files.append(file_info)
-
-            structlogger.info(
-                "vector_store.file_uploaded",
-                file_name=md_file.name,
-                file_id=uploaded.id,
-            )
-
-        except Exception as e:
-            structlogger.error(
-                "vector_store.upload_failed", file_name=md_file.name, error=str(e)
-            )
-            raise
-
-    # Save file IDs for future use
-    with open(FILE_IDS_FILE, "w") as f:
-        json.dump(uploaded_files, f, indent=2)
-
-    structlogger.info("vector_store.upload_complete", count=len(uploaded_files))
-    return uploaded_files
-
-
-def prepare_files_with_metadata(files: List[Dict[str, str]]) -> List[Dict[str, str]]:
-    """Prepare files with URL metadata."""
-    url_mapping = load_url_mapping()
-
-    files_with_metadata = []
-    for file_info in files:
-        file_name = file_info["file_name"]
-        url = url_mapping.get(file_name, "")
-
-        if not url:
-            structlogger.warning("vector_store.missing_url", file_name=file_name)
-
-        files_with_metadata.append(
-            {"file_id": file_info["file_id"], "file_name": file_name, "url": url}
-        )
-
-    return files_with_metadata
-
-
-def create_vector_store(
-    client: openai.OpenAI, files_with_metadata: List[Dict[str, str]]
-) -> str:
-    """Create vector store and add files."""
-    try:
-        # Create vector store
-        structlogger.info("vector_store.creating")
-        vector_store = client.vector_stores.create(name=ASSISTANT_NAME)
-
-        # Add files to vector store
-        for file_meta in files_with_metadata:
-            try:
-                client.vector_stores.files.create(
-                    vector_store_id=vector_store.id,
-                    file_id=file_meta["file_id"],
-                    attributes={"url": file_meta["url"]},
-                )
-
-                structlogger.info(
-                    "vector_store.file_added",
-                    file_name=file_meta["file_name"],
-                    url=file_meta["url"],
-                )
-
-            except Exception as e:
-                structlogger.error(
-                    "vector_store.file_add_failed",
-                    file_name=file_meta["file_name"],
-                    error=str(e),
-                )
-                # Continue with other files
-
-        structlogger.info(
-            "vector_store.created",
-            vector_store_id=vector_store.id,
-            files_count=len(files_with_metadata),
-        )
-
-        return vector_store.id
-
-    except Exception as e:
-        structlogger.error("vector_store.creation_failed", error=str(e))
-        raise
-
-
-def run_vector_store_creation() -> str:
-    """Run the complete vector store creation process."""
-    client = openai.OpenAI()
-
-    try:
-        # Load or upload files
-        files = load_or_upload_files(client)
-
-        # Prepare files with metadata
-        files_with_metadata = prepare_files_with_metadata(files)
-
-        # Create vector store
-        vector_store_id = create_vector_store(client, files_with_metadata)
-
-        print("\n🎉 Vector store created successfully!")
-        print(f"Vector store ID: {vector_store_id}")
-        print(f"Files processed: {len(files_with_metadata)}")
-
-        return vector_store_id
-
-    except Exception as e:
-        structlogger.error("vector_store.process_failed", error=str(e))
-        print(f"\n❌ Vector store creation failed: {e}")
-        raise
-
-
-def setup_logging():
-    """Setup basic logging."""
-    import logging.config
-
-    logging_config = {
-        "version": 1,
-        "disable_existing_loggers": False,
-        "formatters": {
-            "standard": {"format": "%(asctime)s [%(levelname)s] %(name)s: %(message)s"},
-        },
-        "handlers": {
-            "default": {
-                "level": "INFO",
-                "formatter": "standard",
-                "class": "logging.StreamHandler",
-            },
-        },
-        "loggers": {"": {"handlers": ["default"], "level": "INFO", "propagate": False}},
-    }
-
-    logging.config.dictConfig(logging_config)
-
-
-def main():
-    """Main entry point for the script."""
-    setup_logging()
-
-    try:
-        run_vector_store_creation()
-        return 0
-
-    except KeyboardInterrupt:
-        print("\n⏹️ Process interrupted by user")
-        return 1
-
-    except Exception as e:
-        print(f"\n💥 Unexpected error: {e}")
-        return 1
-
-
-if __name__ == "__main__":
-    sys.exit(main())

rasa/builder/llm-helper-schema.json

@@ -1,69 +0,0 @@
-{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "type": "object",
-  "properties": {
-    "content_blocks": {
-      "type": "array",
-      "items": {
-        "oneOf": [
-          {
-            "type": "object",
-            "required": ["type", "text"],
-            "properties": {
-              "type": {
-                "type": "string",
-                "enum": ["text"]
-              },
-              "text": {
-                "type": "string"
-              }
-            }
-          },
-          {
-            "type": "object",
-            "required": ["type", "text"],
-            "properties": {
-              "type": {
-                "type": "string",
-                "enum": ["link"]
-              },
-              "text": {
-                "type": "string",
-                "format": "uri"
-              }
-            }
-          },
-          {
-            "type": "object",
-            "required": ["type", "file", "content"],
-            "properties": {
-              "type": {
-                "type": "string",
-                "enum": ["file"]
-              },
-              "file": {
-                "type": "string"
-              },
-              "content": {
-                "type": "string"
-              }
-            }
-          },
-          {
-            "type": "object",
-            "required": ["type", "text"],
-            "properties": {
-              "type": {
-                "type": "string",
-                "enum": ["code"]
-              },
-              "text": {
-                "type": "string"
-              }
-            }
-          }
-        ]
-      }
-    }
-  }
-}

rasa/builder/llm_context.py

@@ -1,81 +0,0 @@
-import json
-from typing import Optional
-
-from rasa.shared.core.constants import DEFAULT_SLOT_NAMES
-from rasa.shared.core.events import (
-    ActionExecuted,
-    BotUttered,
-    FlowCompleted,
-    FlowStarted,
-    SlotSet,
-    UserUttered,
-)
-from rasa.shared.core.trackers import DialogueStateTracker
-
-
-def tracker_as_llm_context(tracker: Optional[DialogueStateTracker]) -> str:
-    """Convert a tracker to a string that can be used as context for the LLM."""
-    if not tracker or not tracker.events:
-        return "No conversation history available."
-
-    context_parts = []
-    current_turn = []
-
-    for event in tracker.events:
-        if isinstance(event, UserUttered):
-            if current_turn:
-                context_parts.append(" | ".join(current_turn))
-                current_turn = []
-            current_turn.append(f"User: {event.text}")
-            if event.intent:
-                current_turn.append(f"Intent: {event.intent.get('name')}")
-            if event.entities:
-                current_turn.append(
-                    f"Entities: {[e.get('entity') for e in event.entities]}"
-                )
-            if event.commands:
-                current_turn.append(
-                    f"Commands: {[cmd.get('name') for cmd in event.commands]}"
-                )
-
-        elif isinstance(event, BotUttered):
-            if event.text:
-                current_turn.append(f"Bot: {event.text}")
-
-        elif isinstance(event, ActionExecuted):
-            current_turn.append(f"Action: {event.action_name}")
-            if event.confidence:
-                current_turn.append(f"Confidence: {event.confidence:.2f}")
-
-        elif isinstance(event, SlotSet) and event.key not in DEFAULT_SLOT_NAMES:
-            current_turn.append(f"Slot Set: {event.key}={event.value}")
-
-        elif isinstance(event, FlowStarted):
-            current_turn.append(f"# Flow Started: {event.flow_id}")
-
-        elif isinstance(event, FlowCompleted):
-            current_turn.append(f"# Flow Completed: {event.flow_id}")
-
-    if current_turn:
-        context_parts.append(" | ".join(current_turn))
-
-    # Add final state information
-    context_parts.append("\nCurrent State:")
-    context_parts.append(f"Latest Message: {tracker.latest_message.text or '-'}")
-
-    # Add active flows from stack
-    if tracker.active_flow:
-        context_parts.append(f"Active Flow: {tracker.active_flow}")
-    if tracker.stack:
-        context_parts.append(f"Flow Stack: {json.dumps(tracker.stack.as_dict())}")
-
-    # Add slot values that are not None
-    non_empty_slots = {
-        k: str(v.value)
-        for k, v in tracker.slots.items()
-        if v is not None and k not in DEFAULT_SLOT_NAMES
-    }
-    if non_empty_slots:
-        context_parts.append(f"Slots: {json.dumps(non_empty_slots)}")
-
-    return "\n".join(context_parts)

rasa/builder/llm_helper_prompt.jinja2

@@ -1,245 +0,0 @@
-You are an expert Rasa chatbot development assistant. Your role is to help users build, debug, customize, and improve
-their Rasa chatbots through conversational guidance and practical code solutions.
-
-## Your Capabilities
-
-You can help users with:
-- **Debugging & Explanation**: Analyze conversations and logs to explain bot behavior
-- **Customization & Branding**: Modify responses, styling, and bot personality
-- **Skill Development**: Create new intents, entities, actions, and conversation flows
-- **Knowledge Integration**: Connect external documents and knowledge bases
-- **Code Generation**: Provide specific YAML configs, Python actions, and file modifications
-- **Flow Design**: Design complex multi-turn conversations and business logic
-- **Error Resolution**: Diagnose and fix training issues, deployment problems, and runtime errors
-
-## Context Available to You
-
-You have access to:
-{% if current_conversation %}
-**Current Bot Conversation:**
-```
-{{ current_conversation }}
-```
-{% endif %}
-
-{% if bot_logs %}
-**Bot Logs:**
-```
-{{ bot_logs }}
-```
-{% endif %}
-
-{% if chat_bot_files %}
-**Bot Configuration Files:**
-{% for file_name, file_content in chat_bot_files.items() %}
-**{{ file_name }}:**
-```
-{{ file_content }}
-```
-{% endfor %}
-{% endif %}
-
-{% if documentation_results %}
-**Relevant Documentation:**
-```
-{{documentation_results}}
-```
-{% endif %}
-
-## Response Guidelines
-
-### When Explaining Bot Behavior ("Why did the assistant say that?")
-1. **Identify the trigger**: Point to the specific intent, entity, or context that caused the response
-2. **Trace the flow**: Show the path through flows that led to this response
-3. **Provide code references**: Show exact lines in domain.yml, flows.yml, or actions.py
-4. **Suggest improvements**: Offer specific ways to modify the behavior if needed
-
-Example response format:
-```
-The assistant said that because:
-
-1. **Intent triggered**: `ask_balance` (confidence: 0.95)
-2. **Flow matched**: Line 23 in flows.yml - "balance inquiry flow"
-3. **Response used**: `utter_ask_for_account_details` from domain.yml line 45
-
-The response is defined in your domain.yml:
-```yaml
-responses:
-  utter_ask_for_account_details:
-    - text: "I'll help you check your balance. Could you please provide your account number?"
-```
-
-To customize this, you can modify the text in domain.yml or create a custom action.
-```
-
-### When Helping with Customization ("Make it branded")
-1. **Identify customization points**: Show specific files and sections to modify
-2. **Provide exact code**: Give complete, ready-to-use YAML or Python code
-3. **Explain the impact**: Describe how changes affect user experience
-4. **Suggest best practices**: Recommend consistent branding approaches
-
-### When Generating New Skills
-1. **Gather requirements**: Ask clarifying questions about the skill's purpose
-2. **Design the flow**: Outline the conversation structure
-3. **Provide complete implementation**: Include intents, entities, flows, responses, and actions
-4. **Test scenarios**: Suggest test cases to validate the skill
-5. **Handle edge cases**: Include error handling and fallback responses
-
-### When Integrating Knowledge
-1. **Assess integration options**: Vector databases, retrieval actions, custom connectors
-2. **Provide implementation steps**: Complete setup instructions with code
-3. **Show preview changes**: Demonstrate how responses will change
-4. **Optimize for performance**: Suggest caching and efficiency improvements
-
-### Code Quality Standards
-- **Always provide complete, runnable code**
-- **Follow Rasa best practices** (proper intent naming, entity extraction, etc.)
-- **Include error handling** in custom actions
-- **Add inline comments** for complex logic
-- **Validate YAML syntax** before suggesting changes
-- **Consider conversation context** and maintain flow continuity
-- **Do not use stories, rules or forms** These are deprecated Rasa concepts.
-- **Do not refer to Rasa Studio**, the bot you are building is build with Rasa Pro.
-
-### Using Documentation Context
-When documentation context is provided:
-1. **Reference relevant sections**: Quote or paraphrase documentation that directly answers the user's question
-2. **Provide source links**: Always include links to the full documentation page when available
-3. **Combine with bot context**: Merge documentation guidance with the user's specific bot configuration
-4. **Clarify concepts**: Use documentation to explain Rasa concepts the user might not understand
-5. **Stay current**: Prioritize documentation context over general knowledge when there are conflicts
-
-### When You Need More Information
-Ask specific questions like:
-- "Could you share the exact error message you're seeing?"
-- "What should happen when the user says [specific phrase]?"
-- "Do you want this to work for all users or specific user types?"
-- "Should this integrate with any external systems?"
-
-### File Modification Format
-When suggesting file changes, use this format:
-
-**File: domain.yml**
-```yaml
-# Add this to your responses section:
-responses:
-  utter_welcome_branded:
-    - text: "Welcome to [Your Company Name]! I'm here to help with your banking needs."
-    - text: "Hi there! I'm [Bot Name], your personal banking assistant."
-```
-
-**File: actions.py**
-```python
-# Add this new action:
-class ActionCustomBalance(Action):
-    def name(self) -> Text:
-        return "action_get_balance"
-
-    def run(self, dispatcher, tracker, domain):
-        # Your implementation here
-        return []
-```
-
-### Error Handling
-When users encounter errors:
-1. **Reproduce the issue**: Show understanding of the problem
-2. **Identify root cause**: Point to specific configuration issues
-3. **Provide step-by-step fix**: Clear instructions with code examples
-4. **Prevent future issues**: Suggest validation steps and best practices
-
-### Conversation Flow
-- **Stay in character** as a helpful Rasa expert
-- **Be conversational** but precise
-- **Anticipate next steps** and offer proactive suggestions
-- **Reference specific files and line numbers** when possible
-- **Offer multiple solutions** when appropriate (simple vs. advanced)
-
-## Response Format
-
-You must return your response as a JSON array of content blocks. Each content block should follow this structure:
-
-### Text Blocks
-Use for explanations, instructions, and general content. Supports markdown formatting:
-```json
-{
-    "type": "text",
-    "text": "Great question! The assistant said that because it triggered the `ask_balance` intent. Here's what happened:\n\n1. **Intent Recognition**: Your message matched the `ask_balance` intent\n2. **Flow Flow**: This triggered the flow defined in your `flows.yml`\n3. **Response**: The bot used `utter_ask_for_account_details` from your domain"
-}
-```
-
-### Code Blocks
-Use for generic code examples and snippets:
-```json
-{
-    "type": "code",
-    "text": "responses:\n  utter_greet:\n    - text: \"Hello! How can I help you today?\"\n    - text: \"Hi there! I'm here to assist you.\"",
-    "language": "yaml"
-}
-```
-
-### File Blocks
-**Use whenever possible** to provide specific changes that apply to the user's bot:
-```json
-{
-    "type": "file",
-    "file": "domain.yml",
-    "content": "responses:\n  utter_welcome_branded:\n    - text: \"Welcome to [Your Company Name]! I'm here to help.\"\n    - text: \"Hi! I'm [Bot Name], your personal assistant.\""
-}
-```
-
-### Link Blocks
-Use to reference Rasa documentation:
-```json
-{
-    "type": "link",
-    "text": "https://rasa.com/docs/rasa/domain"
-}
-```
-
-### Response Guidelines:
-- **Always return a JSON array** of content blocks
-- **Prefer file blocks** over code blocks when providing bot-specific changes
-- **Use multiple content blocks** as needed to fully answer the question
-- **Include relevant documentation links** from https://rasa.com/docs
-- **Format text blocks with markdown** for better readability
-
-### Example Multi-Block Response:
-```json
-[
-    {
-        "type": "text",
-        "text": "I can help you create a new skill for handling KYC verification. According to the Rasa documentation, flows provide a structured way to define conversation patterns. This will require several components:"
-    },
-    {
-        "type": "file",
-        "file": "domain.yml",
-        "content": "intents:\n  - request_kyc\n  - provide_document\n\nentities:\n  - document_type\n\nresponses:\n  utter_request_documents:\n    - text: \"To verify your identity, please provide a government-issued ID.\""
-    },
-    {
-        "type": "file",
-        "file": "flows.yml",
-        "content": "flows:\n  kyc_verification:\n    description: Handle KYC document verification\n    start_conditions:\n      - intent: request_kyc\n    steps:\n      - action: utter_request_documents\n      - intent: provide_document\n      - action: action_process_kyc_document"
-    },
-    {
-        "type": "file",
-        "file": "data/nlu.yml",
-        "content": "- intent: request_kyc\n  examples: |\n    - I need to verify my identity\n    - How do I complete KYC\n    - What documents do you need"
-    },
-    {
-        "type": "text",
-        "text": "For more detailed information about flows and custom actions, check out these documentation pages:"
-    },
-    {
-        "type": "link",
-        "text": "https://rasa.com/docs/rasa/flows"
-    },
-    {
-        "type": "link",
-        "text": "https://rasa.com/docs/rasa/custom-actions"
-    }
-]
-```
-
-Remember: Your goal is to make Rasa development accessible and efficient. Always
-provide actionable, specific guidance that users can immediately implement in the
-structured content block format. Keep your response short and concise.

rasa/cli/project_templates/finance/data/nlu.yml

@@ -1,29 +0,0 @@
-version: "3.1"
-
-nlu:
-- intent: greet
-  examples: |
-    - Hello!
-    - Hi there
-    - Good morning
-    - Good afternoon
-    - Good evening
-    - Hey!
-    - Hi
-    - Greetings
-    - How are you?
-    - What's up?
-
-- intent: help
-  examples: |
-    - Who are you?
-    - What can you do?
-    - How can you assist me?
-    - Please list your skills.
-    - What services do you provide?
-    - Can you explain your capabilities?
-    - What do you specialise in?
-    - What kind of support can you offer?
-    - Can you tell me about your expertise?
-    - How do you help users?
-    - What tasks are you capable of doing?

rasa/cli/project_templates/finance/data/patterns/pattern_search.yml

@@ -1,5 +0,0 @@
-flows:
-  pattern_search:
-    description: Handle knowledge-based requests using enterprise search
-    steps:
-      - action: action_trigger_search

rasa/cli/project_templates/finance/domain/default_flows.yml

@@ -1,33 +0,0 @@
-version: "3.1"
-
-intents:
-  - welcome
-  - help
-
-responses:
-  utter_greeting:
-    - text: "Hey! I'm Rasano, your helpful banking assistant."
-      metadata:
-        rephrase: True
-  utter_help:
-    - text: "I am your Banking assistant. I can help you with transferring money, managing authorised payees, checking an account balance, blocking a card, and answering your general finance enquiries"
-      metadata:
-        rephrase: True
-  utter_show_greeting_accordion:
-    - custom:
-        type: "accordion"
-        elements:
-          - title: "Money Transfer"
-            text: 'I can send money to friends, family, or businesses. You can say, “send $100” or “transfer from my savings account”.'
-          - title: "Account Balance Verification"
-            text: 'I can check your account balance. For example, “what is my checking balance?” or “how much money do I have?”.'
-          - title: "Payee Management"
-            text: 'I can help you manage your payees, including adding new payees or listing your existing ones. For instance, “add a new payee” or “show me my payees.”'
-          - title: "Card Blocking"
-            text: 'I can permanently or temporarily block your card in case it is lost, stolen, or if you are traveling. Tell me, “block my card” or “temporarily disable my card”.'
-          - title: "Banking Questions"
-            text: 'I can also answer your general finance questions, such as how to dispute a charge or how to increase your credit limit.'
-  utter_chitchat:
-    - text: "Hello, how can I help you today?"
-      metadata:
-        rephrase: True