@elizaos/core 2.0.0-alpha.92 → 2.0.0-alpha.93

package/dist/prompts.d.ts

@@ -1,8 +1,8 @@
 export declare const shouldRespondTemplate = "<task>Decide on behalf of {{agentName}} whether they should respond to the message, ignore it or stop the conversation.</task>\n\n<providers>\n{{providers}}\n</providers>\n\n<instructions>Decide if {{agentName}} should respond to or interact with the conversation.\n\nIMPORTANT RULES FOR RESPONDING:\n- If YOUR name ({{agentName}}) is directly mentioned \u2192 RESPOND\n- If someone uses a DIFFERENT name (not {{agentName}}) \u2192 IGNORE (they're talking to someone else)\n- If you're actively participating in a conversation and the message continues that thread \u2192 RESPOND\n- If someone tells you to stop or be quiet \u2192 STOP\n- Otherwise \u2192 IGNORE\n\nThe key distinction is:\n- \"Talking TO {{agentName}}\" (your name mentioned, replies to you, continuing your conversation) \u2192 RESPOND\n- \"Talking ABOUT {{agentName}}\" or to someone else \u2192 IGNORE\n</instructions>\n\n<output>\nDo NOT include any thinking, reasoning, or <think> sections in your response.\nGo directly to the XML response format without any preamble or explanation.\n\nRespond using XML format like this:\n<response>\n  <name>{{agentName}}</name>\n  <reasoning>Your reasoning here</reasoning>\n  <action>RESPOND | IGNORE | STOP</action>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.\n</output>";
-export declare const messageHandlerTemplate = "<task>Generate dialog and actions for the character {{agentName}}.</task>\n\n<providers>\n{{providers}}\n</providers>\n\n<instructions>\nWrite a thought and plan for {{agentName}} and decide what actions to take. Also include the providers that {{agentName}} will use to have the right context for responding and acting, if any.\n\nIMPORTANT ACTION ORDERING RULES:\n- Actions are executed in the ORDER you list them - the order MATTERS!\n- REPLY should come FIRST to acknowledge the user's request before executing other actions\n- Common patterns:\n  - For requests requiring tool use: REPLY,CALL_MCP_TOOL (acknowledge first, then gather info)\n  - For task execution: REPLY,SEND_MESSAGE or REPLY,EVM_SWAP_TOKENS (acknowledge first, then do the task)\n  - For multi-step operations: REPLY,ACTION1,ACTION2 (acknowledge first, then complete all steps)\n- REPLY is used to acknowledge and inform the user about what you're going to do\n- Follow-up actions execute the actual tasks after acknowledgment\n- Use IGNORE only when you should not respond at all\n- If you use IGNORE, do not include any other actions. IGNORE should be used alone when you should not respond or take any actions.\n\nIMPORTANT ACTION PARAMETERS:\n- Some actions accept input parameters that you should extract from the conversation\n- When an action has parameters listed in its description, include a <params> block for that action\n- Extract parameter values from the user's message and conversation context\n- Required parameters MUST be provided; optional parameters can be omitted if not mentioned\n- If you cannot determine a required parameter value, ask the user for clarification in your <text>\n\nEXAMPLE (action parameters):\nUser message: \"Send a message to @dev_guru on telegram saying Hello!\"\nActions: REPLY,SEND_MESSAGE\nParams:\n<params>\n    <SEND_MESSAGE>\n        <targetType>user</targetType>\n        <source>telegram</source>\n        <target>dev_guru</target>\n        <text>Hello!</text>\n    </SEND_MESSAGE>\n</params>\n\nIMPORTANT PROVIDER SELECTION RULES:\n- Only include providers if they are needed to respond accurately.\n- If the message mentions images, photos, pictures, attachments, or visual content, OR if you see \"(Attachments:\" in the conversation, you MUST include \"ATTACHMENTS\" in your providers list\n- If the message asks about or references specific people, include \"ENTITIES\" in your providers list  \n- If the message asks about relationships or connections between people, include \"RELATIONSHIPS\" in your providers list\n- If the message asks about facts or specific information, include \"FACTS\" in your providers list\n- If the message asks about the environment or world context, include \"WORLD\" in your providers list\n- If no additional context is needed, you may leave the providers list empty.\n\nIMPORTANT CODE BLOCK FORMATTING RULES:\n- If {{agentName}} includes code examples, snippets, or multi-line code in the response, ALWAYS wrap the code with ``` fenced code blocks (specify the language if known, e.g., ```python).\n- ONLY use fenced code blocks for actual code. Do NOT wrap non-code text, instructions, or single words in fenced code blocks.\n- If including inline code (short single words or function names), use single backticks (`) as appropriate.\n- This ensures the user sees clearly formatted and copyable code when relevant.\n</instructions>\n\n<keys>\n\"thought\" should be a short description of what the agent is thinking about and planning.\n\"actions\" should be a comma-separated list of the actions {{agentName}} plans to take based on the thought, IN THE ORDER THEY SHOULD BE EXECUTED (if none, use IGNORE, if simply responding with text, use REPLY)\n\"providers\" should be a comma-separated list of the providers that {{agentName}} will use to have the right context for responding and acting (NEVER use \"IGNORE\" as a provider - use specific provider names like ATTACHMENTS, ENTITIES, FACTS, KNOWLEDGE, etc.)\n\"text\" should be the text of the next message for {{agentName}} which they will send to the conversation.\n\"params\" (optional) should contain action parameters when actions require input. Format as nested XML with action name as wrapper.\n</keys>\n\n<output>\n\nRespond using XML format like this:\n<response>\n    <thought>Your thought here</thought>\n    <actions>ACTION1,ACTION2</actions>\n    <providers>PROVIDER1,PROVIDER2</providers>\n    <text>Your response text here</text>\n    <params>\n        <ACTION1>\n            <paramName1>value1</paramName1>\n            <paramName2>value2</paramName2>\n        </ACTION1>\n        <ACTION2>\n            <paramName1>value1</paramName1>\n        </ACTION2>\n    </params>\n</response>\n\nThe <params> block is optional - only include when actions require input parameters.\nIf an action has no parameters or you're only using REPLY/IGNORE, omit <params> entirely.\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.\n</output>";
-export declare const postCreationTemplate = "# Task: Create a post in the voice and style and perspective of {{agentName}} @{{xUserName}}.\n\nExample task outputs:\n1. A post about the importance of AI in our lives\n<response>\n  <thought>I am thinking about writing a post about the importance of AI in our lives</thought>\n  <post>AI is changing the world and it is important to understand how it works</post>\n  <imagePrompt>A futuristic cityscape with flying cars and people using AI to do things</imagePrompt>\n</response>\n\n2. A post about dogs\n<response>\n  <thought>I am thinking about writing a post about dogs</thought>\n  <post>Dogs are man's best friend and they are loyal and loving</post>\n  <imagePrompt>A dog playing with a ball in a park</imagePrompt>\n</response>\n\n3. A post about finding a new job\n<response>\n  <thought>Getting a job is hard, I bet there's a good post in that</thought>\n  <post>Just keep going!</post>\n  <imagePrompt>A person looking at a computer screen with a job search website</imagePrompt>\n</response>\n\n{{providers}}\n\nWrite a post that is {{adjective}} about {{topic}} (without mentioning {{topic}} directly), from the perspective of {{agentName}}. Do not add commentary or acknowledge this request, just write the post.\nYour response should be 1, 2, or 3 sentences (choose the length at random).\nYour response should not contain any questions. Brief, concise statements only. The total character count MUST be less than 280. No emojis. Use \\n\\n (double spaces) between statements if there are multiple statements in your response.\n\nYour output should be formatted in XML like this:\n<response>\n  <thought>Your thought here</thought>\n  <post>Your post text here</post>\n  <imagePrompt>Optional image prompt here</imagePrompt>\n</response>\n\nThe \"post\" field should be the post you want to send. Do not including any thinking or internal reflection in the \"post\" field.\nThe \"imagePrompt\" field is optional and should be a prompt for an image that is relevant to the post. It should be a single sentence that captures the essence of the post. ONLY USE THIS FIELD if it makes sense that the post would benefit from an image.\nThe \"thought\" field should be a short description of what the agent is thinking about before responding, including a brief justification for the response. Includate an explanation how the post is relevant to the topic but unique and different than other posts.\n\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.";
+export declare const messageHandlerTemplate = "<task>Generate dialog and actions for the character {{agentName}}.</task>\n\n<providers>\n{{providers}}\n</providers>\n\n<instructions>\nWrite a thought and plan for {{agentName}} and decide what actions to take. Also include the providers that {{agentName}} will use to have the right context for responding and acting, if any.\n\nIMPORTANT ACTION ORDERING RULES:\n- Actions are executed in the ORDER you list them - the order MATTERS!\n- REPLY should come FIRST to acknowledge the user's request before executing other actions\n- Common patterns:\n  - For requests requiring tool use: REPLY,CALL_MCP_TOOL (acknowledge first, then gather info)\n  - For task execution: REPLY,MAIN_TASK_ACTION (acknowledge first, then do the task)\n  - For multi-step operations: REPLY,ACTION1,ACTION2,REPLY (acknowledge first, then complete all steps, then acknowledge all done)\n- REPLY is used to acknowledge and inform the user about what you're going to do\n- Follow-up actions execute the actual tasks after acknowledgment\n- Use IGNORE only when you should not respond at all\n- If you use IGNORE, do not include any other actions. IGNORE should be used alone when you should not respond or take any actions.\n\nIMPORTANT ACTION PARAMETERS:\n- When an action has parameters listed in its description, include a <params> block for that action\n- Extract parameter values from the user's message and conversation context\n- Required parameters MUST be provided; optional parameters can be omitted if not mentioned\n- If you cannot determine a required parameter value, ask the user for clarification in your <text>\n\nEXAMPLE (action parameters):\nUser message: \"Send a message to @dev_guru on telegram saying Hello!\"\n<actions>\n  <action>\n    <name>REPLY</name>\n  </action>\n  <action>\n    <name>SEND_MESSAGE</name>\n    <params>\n      <targetType>user</targetType>\n      <source>telegram</source>\n      <target>dev_guru</target>\n      <text>Hello!</text>\n    </params>\n  </action>\n</actions>\n\nIMPORTANT PROVIDER SELECTION RULES:\n- Only include providers if they are needed to respond accurately.\n- If the message mentions images, photos, pictures, attachments, or visual content, OR if you see \"(Attachments:\" in the conversation, you MUST include \"ATTACHMENTS\" in your providers list\n- If the message asks about or references specific people, include \"ENTITIES\" in your providers list  \n- If the message asks about relationships or connections between people, include \"RELATIONSHIPS\" in your providers list\n- If the message asks about facts or specific information, include \"FACTS\" in your providers list\n- If the message asks about the environment or world context, include \"WORLD\" in your providers list\n- If no additional context is needed, you may leave the providers list empty.\n\nIMPORTANT CODE BLOCK FORMATTING RULES:\n- If {{agentName}} includes code examples, snippets, or multi-line code in the response, ALWAYS wrap the code with ``` fenced code blocks (specify the language if known, e.g., ```python).\n- ONLY use fenced code blocks for actual code. Do NOT wrap non-code text, instructions, or single words in fenced code blocks.\n- If including inline code (short single words or function names), use single backticks (`) as appropriate.\n- This ensures the user sees clearly formatted and copyable code when relevant.\n</instructions>\n\n<keys>\n\"thought\" should be a short description of what the agent is thinking about and planning.\n\"actions\" should be a list of <action> elements IN THE ORDER THEY SHOULD BE EXECUTED (if none, use a single <action><name>IGNORE</name></action>, if simply responding with text, use <action><name>REPLY</name></action>). Each action that requires parameters should include a <params> child element.\n\"providers\" should be a comma-separated list of the providers that {{agentName}} will use to have the right context for responding and acting (NEVER use \"IGNORE\" as a provider - use specific provider names like ATTACHMENTS, ENTITIES, FACTS, KNOWLEDGE, etc.)\n\"text\" should be the text of the next message for {{agentName}} which they will send to the conversation.\n</keys>\n\n<output>\nDo NOT include any thinking, reasoning, or <think> sections in your response.\nGo directly to the XML response format without any preamble or explanation.\n\nRespond using XML format like this:\n<response>\n    <thought>Your thought here</thought>\n    <actions>\n        <action>\n            <name>ACTION1</name>\n            <params>\n                <paramName1>value1</paramName1>\n                <paramName2>value2</paramName2>\n            </params>\n        </action>\n        <action>\n            <name>ACTION2</name>\n            <params>\n                <paramName1>value1</paramName1>\n            </params>\n        </action>\n    </actions>\n    <providers>PROVIDER1,PROVIDER2</providers>\n    <text>Your response text here</text>\n</response>\n\nThe <params> block inside each <action> is optional - only include it when that action requires input parameters.\nIf an action has no parameters (e.g. REPLY or IGNORE), omit the <params> child entirely.\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.\n</output>";
+export declare const postCreationTemplate = "# Task: Create a post in the voice and style and perspective of {{agentName}} @{{xUserName}}.\n\nExample task outputs:\n1. A post about the importance of AI in our lives\n<response>\n  <thought>I am thinking about writing a post about the importance of AI in our lives</thought>\n  <post>AI is changing the world and it is important to understand how it works</post>\n  <imagePrompt>A futuristic cityscape with flying cars and people using AI to do things</imagePrompt>\n</response>\n\n2. A post about dogs\n<response>\n  <thought>I am thinking about writing a post about dogs</thought>\n  <post>Dogs are man's best friend and they are loyal and loving</post>\n  <imagePrompt>A dog playing with a ball in a park</imagePrompt>\n</response>\n\n3. A post about finding a new job\n<response>\n  <thought>Getting a job is hard, I bet there's a good post in that</thought>\n  <post>Just keep going!</post>\n  <imagePrompt>A person looking at a computer screen with a job search website</imagePrompt>\n</response>\n\n{{providers}}\n\nWrite a post that is {{adjective}} about {{topic}} (without mentioning {{topic}} directly), from the perspective of {{agentName}}. Do not add commentary or acknowledge this request, just write the post.\nYour response should be 1, 2, or 3 sentences (choose the length at random).\nYour response should not contain any questions. Brief, concise statements only. The total character count MUST be less than 280. No emojis. Use \\n\\n (double spaces) between statements if there are multiple statements in your response.\n\nYour output should be formatted in XML like this:\n<response>\n  <thought>Your thought here</thought>\n  <post>Your post text here</post>\n  <imagePrompt>Optional image prompt here</imagePrompt>\n</response>\n\nThe \"post\" field should be the post you want to send. Do not including any thinking or internal reflection in the \"post\" field.\nThe \"imagePrompt\" field is optional and should be a prompt for an image that is relevant to the post. It should be a single sentence that captures the essence of the post. ONLY USE THIS FIELD if it makes sense that the post would benefit from an image.\nThe \"thought\" field should be a short description of what the agent is thinking about before responding, including a brief justification for the response. Includate an explanation how the post is relevant to the topic but unique and different than other posts.\n\nDo NOT include any thinking, reasoning, or <think> sections in your response.\nGo directly to the XML response format without any preamble or explanation.\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.";
 export declare const booleanFooter = "Respond with only a YES or a NO.";
-export declare const imageDescriptionTemplate = "<task>Analyze the provided image and generate a comprehensive description with multiple levels of detail.</task>\n\n<instructions>\nCarefully examine the image and provide:\n1. A concise, descriptive title that captures the main subject or scene\n2. A brief summary description (1-2 sentences) highlighting the key elements\n3. An extensive, detailed description that covers all visible elements, composition, lighting, colors, mood, and any other relevant details\n\nBe objective and descriptive. Focus on what you can actually see in the image rather than making assumptions about context or meaning.\n</instructions>\n\n<output>\n\nRespond using XML format like this:\n<response>\n  <title>A concise, descriptive title for the image</title>\n  <description>A brief 1-2 sentence summary of the key elements in the image</description>\n  <text>An extensive, detailed description covering all visible elements, composition, lighting, colors, mood, setting, objects, people, activities, and any other relevant details you can observe in the image</text>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.\n</output>";
+export declare const imageDescriptionTemplate = "<task>Analyze the provided image and generate a comprehensive description with multiple levels of detail.</task>\n\n<instructions>\nCarefully examine the image and provide:\n1. A concise, descriptive title that captures the main subject or scene\n2. A brief summary description (1-2 sentences) highlighting the key elements\n3. An extensive, detailed description that covers all visible elements, composition, lighting, colors, mood, and any other relevant details\n\nBe objective and descriptive. Focus on what you can actually see in the image rather than making assumptions about context or meaning.\n</instructions>\n\n<output>\nDo NOT include any thinking, reasoning, or <think> sections in your response.\nGo directly to the XML response format without any preamble or explanation.\n\nRespond using XML format like this:\n<response>\n  <title>A concise, descriptive title for the image</title>\n  <description>A brief 1-2 sentence summary of the key elements in the image</description>\n  <text>An extensive, detailed description covering all visible elements, composition, lighting, colors, mood, setting, objects, people, activities, and any other relevant details you can observe in the image</text>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.\n</output>";
 export declare const multiStepDecisionTemplate = "<task>\nDetermine the next step the assistant should take in this conversation to help the user reach their goal.\n</task>\n\n{{recentMessages}}\n\n# Multi-Step Workflow\n\nIn each step, decide:\n\n1. **Which providers (if any)** should be called to gather necessary data.\n2. **Which action (if any)** should be executed after providers return.\n3. Decide whether the task is complete. If so, set `isFinish: true`. Do not select the `REPLY` action; replies are handled separately after task completion.\n\nYou can select **multiple providers** and at most **one action** per step.\n\nIf the task is fully resolved and no further steps are needed, mark the step as `isFinish: true`.\n\n---\n\n{{actionsWithDescriptions}}\n\n{{providersWithDescriptions}}\n\nThese are the actions or data provider calls that have already been used in this run. Use this to avoid redundancy and guide your next move.\n\n{{actionResults}}\n\n<keys>\n\"thought\" Clearly explain your reasoning for the selected providers and/or action, and how this step contributes to resolving the user's request.\n\"action\"  Name of the action to execute after providers return (can be empty if no action is needed).\n\"providers\" List of provider names to call in this step (can be empty if none are needed).\n\"isFinish\" Set to true only if the task is fully complete.\n</keys>\n\n\u26A0\uFE0F IMPORTANT: Do **not** mark the task as `isFinish: true` immediately after calling an action. Wait for the action to complete before deciding the task is finished.\n\n<output>\n<response>\n  <thought>Your thought here</thought>\n  <action>ACTION</action>\n  <providers>PROVIDER1,PROVIDER2</providers>\n  <isFinish>true | false</isFinish>\n</response>\n</output>";
 export declare const multiStepSummaryTemplate = "<task>\nSummarize what the assistant has done so far and provide a final response to the user based on the completed steps.\n</task>\n\n# Context Information\n{{bio}}\n\n---\n\n{{system}}\n\n---\n\n{{messageDirections}}\n\n# Conversation Summary\nBelow is the user's original request and conversation so far:\n{{recentMessages}}\n\n# Execution Trace\nHere are the actions taken by the assistant to fulfill the request:\n{{actionResults}}\n\n# Assistant's Last Reasoning Step\n{{recentMessage}}\n\n# Instructions\n\n - Review the execution trace and last reasoning step carefully\n\n - Your final output MUST be in this XML format:\n<output>\n<response>\n  <thought>Your thought here</thought>\n  <text>Your final message to the user</text>\n</response>\n</output>\n";
 export declare const replyTemplate = "# Task: Generate dialog for the character {{agentName}}.\n\n{{providers}}\n\n# Instructions: Write the next message for {{agentName}}.\n\"thought\" should be a short description of what the agent is thinking about and planning.\n\"text\" should be the next message for {{agentName}} which they will send to the conversation.\n\nIMPORTANT CODE BLOCK FORMATTING RULES:\n- If {{agentName}} includes code examples, snippets, or multi-line code in the response, ALWAYS wrap the code with ``` fenced code blocks (specify the language if known, e.g., ```python).\n- ONLY use fenced code blocks for actual code. Do NOT wrap non-code text, instructions, or single words in fenced code blocks.\n- If including inline code (short single words or function names), use single backticks (`) as appropriate.\n- This ensures the user sees clearly formatted and copyable code when relevant.\n\nDo NOT include any thinking, reasoning, or <think> sections in your response.\nGo directly to the XML response format without any preamble or explanation.\n\nRespond using XML format like this:\n<response>\n    <thought>Your thought here</thought>\n    <text>Your message here</text>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.";
@@ -13,10 +13,10 @@ export declare const updateSettingsTemplate = "# Task: Update settings based on
 export declare const updateEntityTemplate = "# Task: Update entity information.\n\n{{providers}}\n\n# Current Entity Information:\n{{entityInfo}}\n\n# Instructions:\nBased on the request, determine what information about the entity should be updated.\nOnly update fields that the user has explicitly requested to change.\n\nRespond using XML format like this:\n<response>\n    <thought>Your reasoning for the entity update</thought>\n    <entity_id>The entity ID to update</entity_id>\n    <updates>\n        <field>\n            <name>field_name</name>\n            <value>new_value</value>\n        </field>\n    </updates>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above.";
 export declare const optionExtractionTemplate = "# Task: Extract selected task and option from user message\n\n# Available Tasks:\n{{tasks}}\n\n# Recent Messages:\n{{recentMessages}}\n\n# Instructions:\n1. Review the user's message and identify which task and option they are selecting\n2. Match against the available tasks and their options, including ABORT\n3. Return the task ID (shortened UUID) and selected option name exactly as listed above\n4. If no clear selection is made, return null for both fields\n\n\nReturn in XML format:\n<response>\n  <taskId>string_or_null</taskId>\n  <selectedOption>OPTION_NAME_or_null</selectedOption>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.";
 export declare const SHOULD_RESPOND_TEMPLATE = "<task>Decide on behalf of {{agentName}} whether they should respond to the message, ignore it or stop the conversation.</task>\n\n<providers>\n{{providers}}\n</providers>\n\n<instructions>Decide if {{agentName}} should respond to or interact with the conversation.\n\nIMPORTANT RULES FOR RESPONDING:\n- If YOUR name ({{agentName}}) is directly mentioned \u2192 RESPOND\n- If someone uses a DIFFERENT name (not {{agentName}}) \u2192 IGNORE (they're talking to someone else)\n- If you're actively participating in a conversation and the message continues that thread \u2192 RESPOND\n- If someone tells you to stop or be quiet \u2192 STOP\n- Otherwise \u2192 IGNORE\n\nThe key distinction is:\n- \"Talking TO {{agentName}}\" (your name mentioned, replies to you, continuing your conversation) \u2192 RESPOND\n- \"Talking ABOUT {{agentName}}\" or to someone else \u2192 IGNORE\n</instructions>\n\n<output>\nDo NOT include any thinking, reasoning, or <think> sections in your response.\nGo directly to the XML response format without any preamble or explanation.\n\nRespond using XML format like this:\n<response>\n  <name>{{agentName}}</name>\n  <reasoning>Your reasoning here</reasoning>\n  <action>RESPOND | IGNORE | STOP</action>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.\n</output>";
-export declare const MESSAGE_HANDLER_TEMPLATE = "<task>Generate dialog and actions for the character {{agentName}}.</task>\n\n<providers>\n{{providers}}\n</providers>\n\n<instructions>\nWrite a thought and plan for {{agentName}} and decide what actions to take. Also include the providers that {{agentName}} will use to have the right context for responding and acting, if any.\n\nIMPORTANT ACTION ORDERING RULES:\n- Actions are executed in the ORDER you list them - the order MATTERS!\n- REPLY should come FIRST to acknowledge the user's request before executing other actions\n- Common patterns:\n  - For requests requiring tool use: REPLY,CALL_MCP_TOOL (acknowledge first, then gather info)\n  - For task execution: REPLY,SEND_MESSAGE or REPLY,EVM_SWAP_TOKENS (acknowledge first, then do the task)\n  - For multi-step operations: REPLY,ACTION1,ACTION2 (acknowledge first, then complete all steps)\n- REPLY is used to acknowledge and inform the user about what you're going to do\n- Follow-up actions execute the actual tasks after acknowledgment\n- Use IGNORE only when you should not respond at all\n- If you use IGNORE, do not include any other actions. IGNORE should be used alone when you should not respond or take any actions.\n\nIMPORTANT ACTION PARAMETERS:\n- Some actions accept input parameters that you should extract from the conversation\n- When an action has parameters listed in its description, include a <params> block for that action\n- Extract parameter values from the user's message and conversation context\n- Required parameters MUST be provided; optional parameters can be omitted if not mentioned\n- If you cannot determine a required parameter value, ask the user for clarification in your <text>\n\nEXAMPLE (action parameters):\nUser message: \"Send a message to @dev_guru on telegram saying Hello!\"\nActions: REPLY,SEND_MESSAGE\nParams:\n<params>\n    <SEND_MESSAGE>\n        <targetType>user</targetType>\n        <source>telegram</source>\n        <target>dev_guru</target>\n        <text>Hello!</text>\n    </SEND_MESSAGE>\n</params>\n\nIMPORTANT PROVIDER SELECTION RULES:\n- Only include providers if they are needed to respond accurately.\n- If the message mentions images, photos, pictures, attachments, or visual content, OR if you see \"(Attachments:\" in the conversation, you MUST include \"ATTACHMENTS\" in your providers list\n- If the message asks about or references specific people, include \"ENTITIES\" in your providers list  \n- If the message asks about relationships or connections between people, include \"RELATIONSHIPS\" in your providers list\n- If the message asks about facts or specific information, include \"FACTS\" in your providers list\n- If the message asks about the environment or world context, include \"WORLD\" in your providers list\n- If no additional context is needed, you may leave the providers list empty.\n\nIMPORTANT CODE BLOCK FORMATTING RULES:\n- If {{agentName}} includes code examples, snippets, or multi-line code in the response, ALWAYS wrap the code with ``` fenced code blocks (specify the language if known, e.g., ```python).\n- ONLY use fenced code blocks for actual code. Do NOT wrap non-code text, instructions, or single words in fenced code blocks.\n- If including inline code (short single words or function names), use single backticks (`) as appropriate.\n- This ensures the user sees clearly formatted and copyable code when relevant.\n</instructions>\n\n<keys>\n\"thought\" should be a short description of what the agent is thinking about and planning.\n\"actions\" should be a comma-separated list of the actions {{agentName}} plans to take based on the thought, IN THE ORDER THEY SHOULD BE EXECUTED (if none, use IGNORE, if simply responding with text, use REPLY)\n\"providers\" should be a comma-separated list of the providers that {{agentName}} will use to have the right context for responding and acting (NEVER use \"IGNORE\" as a provider - use specific provider names like ATTACHMENTS, ENTITIES, FACTS, KNOWLEDGE, etc.)\n\"text\" should be the text of the next message for {{agentName}} which they will send to the conversation.\n\"params\" (optional) should contain action parameters when actions require input. Format as nested XML with action name as wrapper.\n</keys>\n\n<output>\n\nRespond using XML format like this:\n<response>\n    <thought>Your thought here</thought>\n    <actions>ACTION1,ACTION2</actions>\n    <providers>PROVIDER1,PROVIDER2</providers>\n    <text>Your response text here</text>\n    <params>\n        <ACTION1>\n            <paramName1>value1</paramName1>\n            <paramName2>value2</paramName2>\n        </ACTION1>\n        <ACTION2>\n            <paramName1>value1</paramName1>\n        </ACTION2>\n    </params>\n</response>\n\nThe <params> block is optional - only include when actions require input parameters.\nIf an action has no parameters or you're only using REPLY/IGNORE, omit <params> entirely.\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.\n</output>";
-export declare const POST_CREATION_TEMPLATE = "# Task: Create a post in the voice and style and perspective of {{agentName}} @{{xUserName}}.\n\nExample task outputs:\n1. A post about the importance of AI in our lives\n<response>\n  <thought>I am thinking about writing a post about the importance of AI in our lives</thought>\n  <post>AI is changing the world and it is important to understand how it works</post>\n  <imagePrompt>A futuristic cityscape with flying cars and people using AI to do things</imagePrompt>\n</response>\n\n2. A post about dogs\n<response>\n  <thought>I am thinking about writing a post about dogs</thought>\n  <post>Dogs are man's best friend and they are loyal and loving</post>\n  <imagePrompt>A dog playing with a ball in a park</imagePrompt>\n</response>\n\n3. A post about finding a new job\n<response>\n  <thought>Getting a job is hard, I bet there's a good post in that</thought>\n  <post>Just keep going!</post>\n  <imagePrompt>A person looking at a computer screen with a job search website</imagePrompt>\n</response>\n\n{{providers}}\n\nWrite a post that is {{adjective}} about {{topic}} (without mentioning {{topic}} directly), from the perspective of {{agentName}}. Do not add commentary or acknowledge this request, just write the post.\nYour response should be 1, 2, or 3 sentences (choose the length at random).\nYour response should not contain any questions. Brief, concise statements only. The total character count MUST be less than 280. No emojis. Use \\n\\n (double spaces) between statements if there are multiple statements in your response.\n\nYour output should be formatted in XML like this:\n<response>\n  <thought>Your thought here</thought>\n  <post>Your post text here</post>\n  <imagePrompt>Optional image prompt here</imagePrompt>\n</response>\n\nThe \"post\" field should be the post you want to send. Do not including any thinking or internal reflection in the \"post\" field.\nThe \"imagePrompt\" field is optional and should be a prompt for an image that is relevant to the post. It should be a single sentence that captures the essence of the post. ONLY USE THIS FIELD if it makes sense that the post would benefit from an image.\nThe \"thought\" field should be a short description of what the agent is thinking about before responding, including a brief justification for the response. Includate an explanation how the post is relevant to the topic but unique and different than other posts.\n\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.";
+export declare const MESSAGE_HANDLER_TEMPLATE = "<task>Generate dialog and actions for the character {{agentName}}.</task>\n\n<providers>\n{{providers}}\n</providers>\n\n<instructions>\nWrite a thought and plan for {{agentName}} and decide what actions to take. Also include the providers that {{agentName}} will use to have the right context for responding and acting, if any.\n\nIMPORTANT ACTION ORDERING RULES:\n- Actions are executed in the ORDER you list them - the order MATTERS!\n- REPLY should come FIRST to acknowledge the user's request before executing other actions\n- Common patterns:\n  - For requests requiring tool use: REPLY,CALL_MCP_TOOL (acknowledge first, then gather info)\n  - For task execution: REPLY,MAIN_TASK_ACTION (acknowledge first, then do the task)\n  - For multi-step operations: REPLY,ACTION1,ACTION2,REPLY (acknowledge first, then complete all steps, then acknowledge all done)\n- REPLY is used to acknowledge and inform the user about what you're going to do\n- Follow-up actions execute the actual tasks after acknowledgment\n- Use IGNORE only when you should not respond at all\n- If you use IGNORE, do not include any other actions. IGNORE should be used alone when you should not respond or take any actions.\n\nIMPORTANT ACTION PARAMETERS:\n- When an action has parameters listed in its description, include a <params> block for that action\n- Extract parameter values from the user's message and conversation context\n- Required parameters MUST be provided; optional parameters can be omitted if not mentioned\n- If you cannot determine a required parameter value, ask the user for clarification in your <text>\n\nEXAMPLE (action parameters):\nUser message: \"Send a message to @dev_guru on telegram saying Hello!\"\n<actions>\n  <action>\n    <name>REPLY</name>\n  </action>\n  <action>\n    <name>SEND_MESSAGE</name>\n    <params>\n      <targetType>user</targetType>\n      <source>telegram</source>\n      <target>dev_guru</target>\n      <text>Hello!</text>\n    </params>\n  </action>\n</actions>\n\nIMPORTANT PROVIDER SELECTION RULES:\n- Only include providers if they are needed to respond accurately.\n- If the message mentions images, photos, pictures, attachments, or visual content, OR if you see \"(Attachments:\" in the conversation, you MUST include \"ATTACHMENTS\" in your providers list\n- If the message asks about or references specific people, include \"ENTITIES\" in your providers list  \n- If the message asks about relationships or connections between people, include \"RELATIONSHIPS\" in your providers list\n- If the message asks about facts or specific information, include \"FACTS\" in your providers list\n- If the message asks about the environment or world context, include \"WORLD\" in your providers list\n- If no additional context is needed, you may leave the providers list empty.\n\nIMPORTANT CODE BLOCK FORMATTING RULES:\n- If {{agentName}} includes code examples, snippets, or multi-line code in the response, ALWAYS wrap the code with ``` fenced code blocks (specify the language if known, e.g., ```python).\n- ONLY use fenced code blocks for actual code. Do NOT wrap non-code text, instructions, or single words in fenced code blocks.\n- If including inline code (short single words or function names), use single backticks (`) as appropriate.\n- This ensures the user sees clearly formatted and copyable code when relevant.\n</instructions>\n\n<keys>\n\"thought\" should be a short description of what the agent is thinking about and planning.\n\"actions\" should be a list of <action> elements IN THE ORDER THEY SHOULD BE EXECUTED (if none, use a single <action><name>IGNORE</name></action>, if simply responding with text, use <action><name>REPLY</name></action>). Each action that requires parameters should include a <params> child element.\n\"providers\" should be a comma-separated list of the providers that {{agentName}} will use to have the right context for responding and acting (NEVER use \"IGNORE\" as a provider - use specific provider names like ATTACHMENTS, ENTITIES, FACTS, KNOWLEDGE, etc.)\n\"text\" should be the text of the next message for {{agentName}} which they will send to the conversation.\n</keys>\n\n<output>\nDo NOT include any thinking, reasoning, or <think> sections in your response.\nGo directly to the XML response format without any preamble or explanation.\n\nRespond using XML format like this:\n<response>\n    <thought>Your thought here</thought>\n    <actions>\n        <action>\n            <name>ACTION1</name>\n            <params>\n                <paramName1>value1</paramName1>\n                <paramName2>value2</paramName2>\n            </params>\n        </action>\n        <action>\n            <name>ACTION2</name>\n            <params>\n                <paramName1>value1</paramName1>\n            </params>\n        </action>\n    </actions>\n    <providers>PROVIDER1,PROVIDER2</providers>\n    <text>Your response text here</text>\n</response>\n\nThe <params> block inside each <action> is optional - only include it when that action requires input parameters.\nIf an action has no parameters (e.g. REPLY or IGNORE), omit the <params> child entirely.\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.\n</output>";
+export declare const POST_CREATION_TEMPLATE = "# Task: Create a post in the voice and style and perspective of {{agentName}} @{{xUserName}}.\n\nExample task outputs:\n1. A post about the importance of AI in our lives\n<response>\n  <thought>I am thinking about writing a post about the importance of AI in our lives</thought>\n  <post>AI is changing the world and it is important to understand how it works</post>\n  <imagePrompt>A futuristic cityscape with flying cars and people using AI to do things</imagePrompt>\n</response>\n\n2. A post about dogs\n<response>\n  <thought>I am thinking about writing a post about dogs</thought>\n  <post>Dogs are man's best friend and they are loyal and loving</post>\n  <imagePrompt>A dog playing with a ball in a park</imagePrompt>\n</response>\n\n3. A post about finding a new job\n<response>\n  <thought>Getting a job is hard, I bet there's a good post in that</thought>\n  <post>Just keep going!</post>\n  <imagePrompt>A person looking at a computer screen with a job search website</imagePrompt>\n</response>\n\n{{providers}}\n\nWrite a post that is {{adjective}} about {{topic}} (without mentioning {{topic}} directly), from the perspective of {{agentName}}. Do not add commentary or acknowledge this request, just write the post.\nYour response should be 1, 2, or 3 sentences (choose the length at random).\nYour response should not contain any questions. Brief, concise statements only. The total character count MUST be less than 280. No emojis. Use \\n\\n (double spaces) between statements if there are multiple statements in your response.\n\nYour output should be formatted in XML like this:\n<response>\n  <thought>Your thought here</thought>\n  <post>Your post text here</post>\n  <imagePrompt>Optional image prompt here</imagePrompt>\n</response>\n\nThe \"post\" field should be the post you want to send. Do not including any thinking or internal reflection in the \"post\" field.\nThe \"imagePrompt\" field is optional and should be a prompt for an image that is relevant to the post. It should be a single sentence that captures the essence of the post. ONLY USE THIS FIELD if it makes sense that the post would benefit from an image.\nThe \"thought\" field should be a short description of what the agent is thinking about before responding, including a brief justification for the response. Includate an explanation how the post is relevant to the topic but unique and different than other posts.\n\nDo NOT include any thinking, reasoning, or <think> sections in your response.\nGo directly to the XML response format without any preamble or explanation.\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.";
 export declare const BOOLEAN_FOOTER = "Respond with only a YES or a NO.";
-export declare const IMAGE_DESCRIPTION_TEMPLATE = "<task>Analyze the provided image and generate a comprehensive description with multiple levels of detail.</task>\n\n<instructions>\nCarefully examine the image and provide:\n1. A concise, descriptive title that captures the main subject or scene\n2. A brief summary description (1-2 sentences) highlighting the key elements\n3. An extensive, detailed description that covers all visible elements, composition, lighting, colors, mood, and any other relevant details\n\nBe objective and descriptive. Focus on what you can actually see in the image rather than making assumptions about context or meaning.\n</instructions>\n\n<output>\n\nRespond using XML format like this:\n<response>\n  <title>A concise, descriptive title for the image</title>\n  <description>A brief 1-2 sentence summary of the key elements in the image</description>\n  <text>An extensive, detailed description covering all visible elements, composition, lighting, colors, mood, setting, objects, people, activities, and any other relevant details you can observe in the image</text>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.\n</output>";
+export declare const IMAGE_DESCRIPTION_TEMPLATE = "<task>Analyze the provided image and generate a comprehensive description with multiple levels of detail.</task>\n\n<instructions>\nCarefully examine the image and provide:\n1. A concise, descriptive title that captures the main subject or scene\n2. A brief summary description (1-2 sentences) highlighting the key elements\n3. An extensive, detailed description that covers all visible elements, composition, lighting, colors, mood, and any other relevant details\n\nBe objective and descriptive. Focus on what you can actually see in the image rather than making assumptions about context or meaning.\n</instructions>\n\n<output>\nDo NOT include any thinking, reasoning, or <think> sections in your response.\nGo directly to the XML response format without any preamble or explanation.\n\nRespond using XML format like this:\n<response>\n  <title>A concise, descriptive title for the image</title>\n  <description>A brief 1-2 sentence summary of the key elements in the image</description>\n  <text>An extensive, detailed description covering all visible elements, composition, lighting, colors, mood, setting, objects, people, activities, and any other relevant details you can observe in the image</text>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.\n</output>";
 export declare const MULTI_STEP_DECISION_TEMPLATE = "<task>\nDetermine the next step the assistant should take in this conversation to help the user reach their goal.\n</task>\n\n{{recentMessages}}\n\n# Multi-Step Workflow\n\nIn each step, decide:\n\n1. **Which providers (if any)** should be called to gather necessary data.\n2. **Which action (if any)** should be executed after providers return.\n3. Decide whether the task is complete. If so, set `isFinish: true`. Do not select the `REPLY` action; replies are handled separately after task completion.\n\nYou can select **multiple providers** and at most **one action** per step.\n\nIf the task is fully resolved and no further steps are needed, mark the step as `isFinish: true`.\n\n---\n\n{{actionsWithDescriptions}}\n\n{{providersWithDescriptions}}\n\nThese are the actions or data provider calls that have already been used in this run. Use this to avoid redundancy and guide your next move.\n\n{{actionResults}}\n\n<keys>\n\"thought\" Clearly explain your reasoning for the selected providers and/or action, and how this step contributes to resolving the user's request.\n\"action\"  Name of the action to execute after providers return (can be empty if no action is needed).\n\"providers\" List of provider names to call in this step (can be empty if none are needed).\n\"isFinish\" Set to true only if the task is fully complete.\n</keys>\n\n\u26A0\uFE0F IMPORTANT: Do **not** mark the task as `isFinish: true` immediately after calling an action. Wait for the action to complete before deciding the task is finished.\n\n<output>\n<response>\n  <thought>Your thought here</thought>\n  <action>ACTION</action>\n  <providers>PROVIDER1,PROVIDER2</providers>\n  <isFinish>true | false</isFinish>\n</response>\n</output>";
 export declare const MULTI_STEP_SUMMARY_TEMPLATE = "<task>\nSummarize what the assistant has done so far and provide a final response to the user based on the completed steps.\n</task>\n\n# Context Information\n{{bio}}\n\n---\n\n{{system}}\n\n---\n\n{{messageDirections}}\n\n# Conversation Summary\nBelow is the user's original request and conversation so far:\n{{recentMessages}}\n\n# Execution Trace\nHere are the actions taken by the assistant to fulfill the request:\n{{actionResults}}\n\n# Assistant's Last Reasoning Step\n{{recentMessage}}\n\n# Instructions\n\n - Review the execution trace and last reasoning step carefully\n\n - Your final output MUST be in this XML format:\n<output>\n<response>\n  <thought>Your thought here</thought>\n  <text>Your final message to the user</text>\n</response>\n</output>\n";
 export declare const REPLY_TEMPLATE = "# Task: Generate dialog for the character {{agentName}}.\n\n{{providers}}\n\n# Instructions: Write the next message for {{agentName}}.\n\"thought\" should be a short description of what the agent is thinking about and planning.\n\"text\" should be the next message for {{agentName}} which they will send to the conversation.\n\nIMPORTANT CODE BLOCK FORMATTING RULES:\n- If {{agentName}} includes code examples, snippets, or multi-line code in the response, ALWAYS wrap the code with ``` fenced code blocks (specify the language if known, e.g., ```python).\n- ONLY use fenced code blocks for actual code. Do NOT wrap non-code text, instructions, or single words in fenced code blocks.\n- If including inline code (short single words or function names), use single backticks (`) as appropriate.\n- This ensures the user sees clearly formatted and copyable code when relevant.\n\nDo NOT include any thinking, reasoning, or <think> sections in your response.\nGo directly to the XML response format without any preamble or explanation.\n\nRespond using XML format like this:\n<response>\n    <thought>Your thought here</thought>\n    <text>Your message here</text>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.";

package/dist/prompts.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"prompts.d.ts","sourceRoot":"","sources":["../src/prompts.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,qBAAqB,49CAgCxB,CAAC;AAEX,eAAO,MAAM,sBAAsB,siKAwFzB,CAAC;AAEX,eAAO,MAAM,oBAAoB,omFA0C+M,CAAC;AAEjP,eAAO,MAAM,aAAa,qCAAqC,CAAC;AAEhE,eAAO,MAAM,wBAAwB,4yCAqB3B,CAAC;AAEX,eAAO,MAAM,yBAAyB,isDA4C5B,CAAC;AAEX,eAAO,MAAM,wBAAwB,kwBAqCpC,CAAC;AAGF,eAAO,MAAM,aAAa,64CAuBsN,CAAC;AAEjP,eAAO,MAAM,oBAAoB,8hBAiBqD,CAAC;AAEvF,eAAO,MAAM,uBAAuB,ojBAiBkD,CAAC;AAEvF,eAAO,MAAM,kBAAkB,6xBAuBuD,CAAC;AAEvF,eAAO,MAAM,sBAAsB,2lBAsBmD,CAAC;AAEvF,eAAO,MAAM,oBAAoB,+qBAuBqD,CAAC;AAEvF,eAAO,MAAM,wBAAwB,o1BAqB2M,CAAC;AAGjP,eAAO,MAAM,uBAAuB,49CAAwB,CAAC;AAC7D,eAAO,MAAM,wBAAwB,siKAAyB,CAAC;AAC/D,eAAO,MAAM,sBAAsB,omFAAuB,CAAC;AAC3D,eAAO,MAAM,cAAc,qCAAgB,CAAC;AAC5C,eAAO,MAAM,0BAA0B,4yCAA2B,CAAC;AACnE,eAAO,MAAM,4BAA4B,isDAA4B,CAAC;AACtE,eAAO,MAAM,2BAA2B,kwBAA2B,CAAC;AACpE,eAAO,MAAM,cAAc,64CAAgB,CAAC;AAC5C,eAAO,MAAM,sBAAsB,8hBAAuB,CAAC;AAC3D,eAAO,MAAM,yBAAyB,ojBAA0B,CAAC;AACjE,eAAO,MAAM,mBAAmB,6xBAAqB,CAAC;AACtD,eAAO,MAAM,wBAAwB,2lBAAyB,CAAC;AAC/D,eAAO,MAAM,sBAAsB,+qBAAuB,CAAC;AAC3D,eAAO,MAAM,0BAA0B,o1BAA2B,CAAC;AAGnE,eAAO,MAAM,wBAAwB,ytCA6B2M,CAAC;AAEjP,eAAO,MAAM,kBAAkB,muCA2BiN,CAAC;AAEjP,eAAO,MAAM,sBAAsB,i+BAuB6M,CAAC;AAEjP,eAAO,MAAM,qBAAqB,6yBAmB8M,CAAC;AAEjP,eAAO,MAAM,qBAAqB,mrCA4B8M,CAAC;AAGjP,eAAO,MAAM,wBAAwB,qmBAWJ,CAAC;AAElC,eAAO,MAAM,0BAA0B,+kBAWN,CAAC;AAElC,eAAO,MAAM,sBAAsB,qgBAYF,CAAC;AAElC,eAAO,MAAM,wBAAwB,kkBAWJ,CAAC;AAGlC,eAAO,MAAM,wBAAwB,snBAqBzB,CAAC;AAGb,eAAO,MAAM,kBAAkB,6kBAkBuD,CAAC;AAGvF,eAAO,MAAM,4BAA4B,25BA6B9B,CAAC;AAEZ,eAAO,MAAM,2BAA2B,0/BA+B7B,CAAC;AAEZ,eAAO,MAAM,0BAA0B,osBAuB3B,CAAC;AAEb,eAAO,MAAM,yBAAyB,6rCAoChB,CAAC;AAGvB,eAAO,MAAM,2BAA2B,ytCAA2B,CAAC;AACpE,eAAO,MAAM,oBAAoB,muCAAqB,CAAC;AACvD,eAAO,MAAM,wBAAwB,i+BAAyB,CAAC;AAC/D,eAAO,MAAM,uBAAuB,6yBAAwB,CAAC;AAC7D,eAAO,MAAM,uBAAuB,mrCAAwB,CAAC;AAC7D,eAAO,MAAM,2BAA2B,qmBAA2B,CAAC;AACpE,eAAO,MAAM,6BAA6B,+kBAA6B,CAAC;AACxE,eAAO,MAAM,yBAAyB,qgBAAyB,CAAC;AAChE,eAAO,MAAM,2BAA2B,kkBAA2B,CAAC;AAEpE,eAAO,MAAM,oBAAoB,qmBAA2B,CAAC;AAC7D,eAAO,MAAM,sBAAsB,+kBAA6B,CAAC;AACjE,eAAO,MAAM,kBAAkB,qgBAAyB,CAAC;AACzD,eAAO,MAAM,oBAAoB,kkBAA2B,CAAC;AAC7D,eAAO,MAAM,0BAA0B,snBAA2B,CAAC;AACnE,eAAO,MAAM,oBAAoB,6kBAAqB,CAAC;AACvD,eAAO,MAAM,8BAA8B,25BAA+B,CAAC;AAC3E,eAAO,MAAM,6BAA6B,0/BAA8B,CAAC;AACzE,eAAO,MAAM,6BAA6B,osBAA6B,CAAC;AACxE,eAAO,MAAM,2BAA2B,6rCAA4B,CAAC;AAErE,eAAO,MAAM,2BAA2B,+4DAsDwM,CAAC;AAEjP,eAAO,MAAM,6BAA6B,+4DAA8B,CAAC;AAGzE,eAAO,MAAM,wBAAwB,ioCAgCiD,CAAC;AAGvF,eAAO,MAAM,iBAAiB,24BA8BwD,CAAC;AAGvF,eAAO,MAAM,uBAAuB,wuBAgB4B,CAAC;AAEjE,eAAO,MAAM,uBAAuB,41BAyBkC,CAAC;AAEvE,eAAO,MAAM,qBAAqB,shBAemC,CAAC;AAEtE,eAAO,MAAM,0BAA0B,4rBAoB6B,CAAC;AAGrE,eAAO,MAAM,0BAA0B,ioCAA2B,CAAC;AACnE,eAAO,MAAM,kBAAkB,24BAAoB,CAAC;AACpD,eAAO,MAAM,yBAAyB,wuBAA0B,CAAC;AACjE,eAAO,MAAM,yBAAyB,41BAA0B,CAAC;AACjE,eAAO,MAAM,uBAAuB,shBAAwB,CAAC;AAC7D,eAAO,MAAM,4BAA4B,4rBAA6B,CAAC;AAGvE,eAAO,MAAM,+BAA+B,seAUkC,CAAC;AAE/E,eAAO,MAAM,kCAAkC,2gBAYkB,CAAC;AAElE,eAAO,MAAM,yBAAyB,ulBAWmC,CAAC;AAE1E,eAAO,MAAM,4BAA4B,6nBAaoB,CAAC;AAG9D,eAAO,MAAM,kCAAkC,seACd,CAAC;AAClC,eAAO,MAAM,qCAAqC,2gBACd,CAAC;AACrC,eAAO,MAAM,4BAA4B,ulBAA4B,CAAC;AACtE,eAAO,MAAM,+BAA+B,6nBAA+B,CAAC"}
+{"version":3,"file":"prompts.d.ts","sourceRoot":"","sources":["../src/prompts.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,qBAAqB,49CAgCxB,CAAC;AAEX,eAAO,MAAM,sBAAsB,uxKAiGzB,CAAC;AAEX,eAAO,MAAM,oBAAoB,gwFA4C+M,CAAC;AAEjP,eAAO,MAAM,aAAa,qCAAqC,CAAC;AAEhE,eAAO,MAAM,wBAAwB,w8CAuB3B,CAAC;AAEX,eAAO,MAAM,yBAAyB,isDA4C5B,CAAC;AAEX,eAAO,MAAM,wBAAwB,kwBAqCpC,CAAC;AAGF,eAAO,MAAM,aAAa,64CAuBsN,CAAC;AAEjP,eAAO,MAAM,oBAAoB,8hBAiBqD,CAAC;AAEvF,eAAO,MAAM,uBAAuB,ojBAiBkD,CAAC;AAEvF,eAAO,MAAM,kBAAkB,6xBAuBuD,CAAC;AAEvF,eAAO,MAAM,sBAAsB,2lBAsBmD,CAAC;AAEvF,eAAO,MAAM,oBAAoB,+qBAuBqD,CAAC;AAEvF,eAAO,MAAM,wBAAwB,o1BAqB2M,CAAC;AAGjP,eAAO,MAAM,uBAAuB,49CAAwB,CAAC;AAC7D,eAAO,MAAM,wBAAwB,uxKAAyB,CAAC;AAC/D,eAAO,MAAM,sBAAsB,gwFAAuB,CAAC;AAC3D,eAAO,MAAM,cAAc,qCAAgB,CAAC;AAC5C,eAAO,MAAM,0BAA0B,w8CAA2B,CAAC;AACnE,eAAO,MAAM,4BAA4B,isDAA4B,CAAC;AACtE,eAAO,MAAM,2BAA2B,kwBAA2B,CAAC;AACpE,eAAO,MAAM,cAAc,64CAAgB,CAAC;AAC5C,eAAO,MAAM,sBAAsB,8hBAAuB,CAAC;AAC3D,eAAO,MAAM,yBAAyB,ojBAA0B,CAAC;AACjE,eAAO,MAAM,mBAAmB,6xBAAqB,CAAC;AACtD,eAAO,MAAM,wBAAwB,2lBAAyB,CAAC;AAC/D,eAAO,MAAM,sBAAsB,+qBAAuB,CAAC;AAC3D,eAAO,MAAM,0BAA0B,o1BAA2B,CAAC;AAGnE,eAAO,MAAM,wBAAwB,ytCA6B2M,CAAC;AAEjP,eAAO,MAAM,kBAAkB,muCA2BiN,CAAC;AAEjP,eAAO,MAAM,sBAAsB,i+BAuB6M,CAAC;AAEjP,eAAO,MAAM,qBAAqB,6yBAmB8M,CAAC;AAEjP,eAAO,MAAM,qBAAqB,mrCA4B8M,CAAC;AAGjP,eAAO,MAAM,wBAAwB,qmBAWJ,CAAC;AAElC,eAAO,MAAM,0BAA0B,+kBAWN,CAAC;AAElC,eAAO,MAAM,sBAAsB,qgBAYF,CAAC;AAElC,eAAO,MAAM,wBAAwB,kkBAWJ,CAAC;AAGlC,eAAO,MAAM,wBAAwB,snBAqBzB,CAAC;AAGb,eAAO,MAAM,kBAAkB,6kBAkBuD,CAAC;AAGvF,eAAO,MAAM,4BAA4B,25BA6B9B,CAAC;AAEZ,eAAO,MAAM,2BAA2B,0/BA+B7B,CAAC;AAEZ,eAAO,MAAM,0BAA0B,osBAuB3B,CAAC;AAEb,eAAO,MAAM,yBAAyB,6rCAoChB,CAAC;AAGvB,eAAO,MAAM,2BAA2B,ytCAA2B,CAAC;AACpE,eAAO,MAAM,oBAAoB,muCAAqB,CAAC;AACvD,eAAO,MAAM,wBAAwB,i+BAAyB,CAAC;AAC/D,eAAO,MAAM,uBAAuB,6yBAAwB,CAAC;AAC7D,eAAO,MAAM,uBAAuB,mrCAAwB,CAAC;AAC7D,eAAO,MAAM,2BAA2B,qmBAA2B,CAAC;AACpE,eAAO,MAAM,6BAA6B,+kBAA6B,CAAC;AACxE,eAAO,MAAM,yBAAyB,qgBAAyB,CAAC;AAChE,eAAO,MAAM,2BAA2B,kkBAA2B,CAAC;AAEpE,eAAO,MAAM,oBAAoB,qmBAA2B,CAAC;AAC7D,eAAO,MAAM,sBAAsB,+kBAA6B,CAAC;AACjE,eAAO,MAAM,kBAAkB,qgBAAyB,CAAC;AACzD,eAAO,MAAM,oBAAoB,kkBAA2B,CAAC;AAC7D,eAAO,MAAM,0BAA0B,snBAA2B,CAAC;AACnE,eAAO,MAAM,oBAAoB,6kBAAqB,CAAC;AACvD,eAAO,MAAM,8BAA8B,25BAA+B,CAAC;AAC3E,eAAO,MAAM,6BAA6B,0/BAA8B,CAAC;AACzE,eAAO,MAAM,6BAA6B,osBAA6B,CAAC;AACxE,eAAO,MAAM,2BAA2B,6rCAA4B,CAAC;AAErE,eAAO,MAAM,2BAA2B,+4DAsDwM,CAAC;AAEjP,eAAO,MAAM,6BAA6B,+4DAA8B,CAAC;AAGzE,eAAO,MAAM,wBAAwB,ioCAgCiD,CAAC;AAGvF,eAAO,MAAM,iBAAiB,24BA8BwD,CAAC;AAGvF,eAAO,MAAM,uBAAuB,wuBAgB4B,CAAC;AAEjE,eAAO,MAAM,uBAAuB,41BAyBkC,CAAC;AAEvE,eAAO,MAAM,qBAAqB,shBAemC,CAAC;AAEtE,eAAO,MAAM,0BAA0B,4rBAoB6B,CAAC;AAGrE,eAAO,MAAM,0BAA0B,ioCAA2B,CAAC;AACnE,eAAO,MAAM,kBAAkB,24BAAoB,CAAC;AACpD,eAAO,MAAM,yBAAyB,wuBAA0B,CAAC;AACjE,eAAO,MAAM,yBAAyB,41BAA0B,CAAC;AACjE,eAAO,MAAM,uBAAuB,shBAAwB,CAAC;AAC7D,eAAO,MAAM,4BAA4B,4rBAA6B,CAAC;AAGvE,eAAO,MAAM,+BAA+B,seAUkC,CAAC;AAE/E,eAAO,MAAM,kCAAkC,2gBAYkB,CAAC;AAElE,eAAO,MAAM,yBAAyB,ulBAWmC,CAAC;AAE1E,eAAO,MAAM,4BAA4B,6nBAaoB,CAAC;AAG9D,eAAO,MAAM,kCAAkC,seACf,CAAC;AACjC,eAAO,MAAM,qCAAqC,2gBACf,CAAC;AACpC,eAAO,MAAM,4BAA4B,ulBAA4B,CAAC;AACtE,eAAO,MAAM,+BAA+B,6nBAA+B,CAAC"}

package/dist/providers/sessionKeys.d.ts

@@ -0,0 +1,24 @@
+/**
+ * Bridges Milady session keys with ElizaOS rooms.
+ *
+ * Milady keys: agent:{agentId}:main (DMs), agent:{agentId}:{channel}:group:{id} (groups)
+ * ElizaOS rooms: per-agent UUIDs via createUniqueUuid(runtime, channelId)
+ */
+import { type Provider, type Room } from "../types";
+/**
+ * Resolve an Milady session key from an ElizaOS room.
+ *
+ * DMs -> agent:{agentId}:main
+ * Groups -> agent:{agentId}:{channel}:group:{groupId}
+ * Channels -> agent:{agentId}:{channel}:channel:{channelId}
+ * Threads append :thread:{threadId}
+ */
+export declare function resolveSessionKeyFromRoom(agentId: string, room: Room, meta?: {
+    threadId?: string;
+    groupId?: string;
+    channel?: string;
+}): string;
+export declare function createSessionKeyProvider(options?: {
+    defaultAgentId?: string;
+}): Provider;
+//# sourceMappingURL=sessionKeys.d.ts.map

package/dist/providers/sessionKeys.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sessionKeys.d.ts","sourceRoot":"","sources":["../../src/providers/sessionKeys.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,OAAO,EAIL,KAAK,QAAQ,EAEb,KAAK,IAAI,EAEV,MAAM,UAAU,CAAC;AA6ClB;;;;;;;GAOG;AACH,wBAAgB,yBAAyB,CACvC,OAAO,EAAE,MAAM,EACf,IAAI,EAAE,IAAI,EACV,IAAI,CAAC,EAAE;IAAE,QAAQ,CAAC,EAAE,MAAM,CAAC;IAAC,OAAO,CAAC,EAAE,MAAM,CAAC;IAAC,OAAO,CAAC,EAAE,MAAM,CAAA;CAAE,GAC/D,MAAM,CAiBR;AAED,wBAAgB,wBAAwB,CAAC,OAAO,CAAC,EAAE;IACjD,cAAc,CAAC,EAAE,MAAM,CAAC;CACzB,GAAG,QAAQ,CAoDX"}

package/dist/request-context.d.ts

@@ -0,0 +1,143 @@
+/**
+ * Request context management for per-entity settings in multi-tenant deployments.
+ *
+ * Follows the OpenTelemetry ContextManager pattern (same as streaming-context.ts):
+ * - Interface for context management
+ * - Platform-specific implementations (Node.js AsyncLocalStorage, Browser Stack)
+ * - Global singleton configured at startup
+ *
+ * This enables sharing a single agent runtime across multiple users while ensuring
+ * each user's API keys, OAuth tokens, and configuration are used for their specific requests.
+ *
+ * @example
+ * ```typescript
+ * // Before processing a user's message
+ * const entitySettings = await prefetchEntitySettings(userId, agentId);
+ *
+ * await runWithRequestContext({
+ *   entityId: userId,
+ *   agentId: agentId,
+ *   entitySettings: new Map([
+ *     ['OPENAI_API_KEY', 'sk-user-specific-key'],
+ *     ['TWITTER_ACCESS_TOKEN', 'oauth-token-for-user'],
+ *   ]),
+ *   requestStartTime: Date.now(),
+ * }, async () => {
+ *   // All getSetting() calls here check entitySettings first
+ *   await runtime.handleMessage(message);
+ * });
+ * ```
+ */
+import type { UUID } from "./types";
+/**
+ * The value types that can be stored in entity settings.
+ * Matches the return type of getSetting().
+ */
+export type EntitySettingValue = string | boolean | number | null;
+/**
+ * Request-scoped context containing per-entity settings.
+ * Used to isolate user settings across concurrent requests sharing the same runtime.
+ */
+export interface RequestContext {
+    /**
+     * The entity (user) ID for this request.
+     * Used to identify which user's settings should be used.
+     */
+    entityId: UUID;
+    /**
+     * The agent ID for this request.
+     * Used for agent-specific entity settings lookup.
+     */
+    agentId: UUID;
+    /**
+     * Pre-fetched entity-specific settings.
+     * These take highest priority in getSetting() resolution chain.
+     *
+     * The Map contains setting keys and their values:
+     * - string/boolean/number: The actual setting value to use
+     * - null: Explicitly unset (use agent default)
+     * - undefined (key not present): Fall through to agent settings
+     */
+    entitySettings: Map<string, EntitySettingValue>;
+    /**
+     * Request start timestamp for observability and debugging.
+     * Useful for tracking request duration and timeout handling.
+     */
+    requestStartTime: number;
+    /**
+     * Optional trace ID for distributed tracing.
+     * Can be passed from incoming request headers (e.g., X-Trace-Id).
+     */
+    traceId?: string;
+    /**
+     * Optional organization ID for multi-tenant deployments.
+     * Used for logging and auditing purposes.
+     */
+    organizationId?: string;
+}
+/**
+ * Interface for request context managers.
+ * Different implementations exist for Node.js (AsyncLocalStorage) and Browser (fallback).
+ */
+export interface IRequestContextManager {
+    /**
+     * Run a function with a request context.
+     * The context will be available to all nested async calls via `active()`.
+     *
+     * @param context - The request context to make available, or undefined to clear context
+     * @param fn - The function to run within the context
+     * @returns The result of the function
+     */
+    run<T>(context: RequestContext | undefined, fn: () => T): T;
+    /**
+     * Get the currently active request context.
+     * Returns undefined if no context is active (e.g., during plugin init).
+     *
+     * @returns The current request context or undefined
+     */
+    active(): RequestContext | undefined;
+}
+/**
+ * Set the global request context manager.
+ * Called during initialization by platform-specific entry points.
+ *
+ * @param manager - The context manager to use globally
+ */
+export declare function setRequestContextManager(manager: IRequestContextManager): void;
+/**
+ * Get the global request context manager.
+ * Useful for testing or advanced use cases.
+ *
+ * @returns The current global request context manager
+ */
+export declare function getRequestContextManager(): IRequestContextManager;
+/**
+ * Run a function with a request context.
+ * All getSetting() calls within this function will check entitySettings first.
+ *
+ * @example
+ * ```typescript
+ * const result = await runWithRequestContext({
+ *   entityId: userId as UUID,
+ *   agentId: agentId as UUID,
+ *   entitySettings: new Map([['API_KEY', 'user-specific-key']]),
+ *   requestStartTime: Date.now(),
+ * }, async () => {
+ *   // Inside here, runtime.getSetting('API_KEY') returns 'user-specific-key'
+ *   return await runtime.processMessage(message);
+ * });
+ * ```
+ *
+ * @param context - The request context with entitySettings
+ * @param fn - The function to run with request context
+ * @returns The result of the function
+ */
+export declare function runWithRequestContext<T>(context: RequestContext | undefined, fn: () => T): T;
+/**
+ * Get the currently active request context.
+ * Called by getSetting() to check for entity-specific settings.
+ *
+ * @returns The current request context or undefined if not in a request
+ */
+export declare function getRequestContext(): RequestContext | undefined;
+//# sourceMappingURL=request-context.d.ts.map

package/dist/request-context.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"request-context.d.ts","sourceRoot":"","sources":["../src/request-context.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,OAAO,KAAK,EAAE,IAAI,EAAE,MAAM,SAAS,CAAC;AAEpC;;;GAGG;AACH,MAAM,MAAM,kBAAkB,GAAG,MAAM,GAAG,OAAO,GAAG,MAAM,GAAG,IAAI,CAAC;AAElE;;;GAGG;AACH,MAAM,WAAW,cAAc;IAC7B;;;OAGG;IACH,QAAQ,EAAE,IAAI,CAAC;IAEf;;;OAGG;IACH,OAAO,EAAE,IAAI,CAAC;IAEd;;;;;;;;OAQG;IACH,cAAc,EAAE,GAAG,CAAC,MAAM,EAAE,kBAAkB,CAAC,CAAC;IAEhD;;;OAGG;IACH,gBAAgB,EAAE,MAAM,CAAC;IAEzB;;;OAGG;IACH,OAAO,CAAC,EAAE,MAAM,CAAC;IAEjB;;;OAGG;IACH,cAAc,CAAC,EAAE,MAAM,CAAC;CACzB;AAED;;;GAGG;AACH,MAAM,WAAW,sBAAsB;IACrC;;;;;;;OAOG;IACH,GAAG,CAAC,CAAC,EAAE,OAAO,EAAE,cAAc,GAAG,SAAS,EAAE,EAAE,EAAE,MAAM,CAAC,GAAG,CAAC,CAAC;IAE5D;;;;;OAKG;IACH,MAAM,IAAI,cAAc,GAAG,SAAS,CAAC;CACtC;AAqBD;;;;;GAKG;AACH,wBAAgB,wBAAwB,CACtC,OAAO,EAAE,sBAAsB,GAC9B,IAAI,CAEN;AAED;;;;;GAKG;AACH,wBAAgB,wBAAwB,IAAI,sBAAsB,CAEjE;AAED;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,wBAAgB,qBAAqB,CAAC,CAAC,EACrC,OAAO,EAAE,cAAc,GAAG,SAAS,EACnC,EAAE,EAAE,MAAM,CAAC,GACV,CAAC,CAEH;AAED;;;;;GAKG;AACH,wBAAgB,iBAAiB,IAAI,cAAc,GAAG,SAAS,CAE9D"}

package/dist/security/sandbox-token-manager.d.ts

@@ -0,0 +1,33 @@
+/**
+ * Sandbox secret token manager.
+ *
+ * Maps real secrets to opaque `stok_` prefixed tokens. Plugins see tokens;
+ * the fetch proxy resolves them to real values at the network boundary.
+ */
+export declare const SANDBOX_TOKEN_PREFIX = "stok_";
+export interface SecretTokenMetadata {
+    settingKey: string;
+    secretType: "api_key" | "oauth_token" | "password" | "private_key" | "other";
+    createdAt: number;
+    owner?: string;
+}
+export declare class SandboxTokenManager {
+    private tokenToEntry;
+    private realValueToToken;
+    private settingKeyToToken;
+    /** Register a secret, returning its stable token. Idempotent per key. */
+    registerSecret(settingKey: string, realValue: string, metadata?: Partial<SecretTokenMetadata>): string;
+    resolveToken(token: string): string | null;
+    getTokenForKey(settingKey: string): string | null;
+    getTokenForValue(realValue: string): string | null;
+    getMetadata(token: string): SecretTokenMetadata | null;
+    /** Replace tokens → real values (outbound). */
+    detokenizeString(input: string): string;
+    /** Replace real values → tokens (inbound). Longest-first to avoid partial matches. */
+    tokenizeString(input: string): string;
+    static isToken(value: string): boolean;
+    get size(): number;
+    clear(): void;
+    listKeys(): string[];
+}
+//# sourceMappingURL=sandbox-token-manager.d.ts.map

package/dist/security/sandbox-token-manager.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sandbox-token-manager.d.ts","sourceRoot":"","sources":["../../src/security/sandbox-token-manager.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAIH,eAAO,MAAM,oBAAoB,UAAU,CAAC;AAE5C,MAAM,WAAW,mBAAmB;IAClC,UAAU,EAAE,MAAM,CAAC;IACnB,UAAU,EAAE,SAAS,GAAG,aAAa,GAAG,UAAU,GAAG,aAAa,GAAG,OAAO,CAAC;IAC7E,SAAS,EAAE,MAAM,CAAC;IAClB,KAAK,CAAC,EAAE,MAAM,CAAC;CAChB;AAQD,qBAAa,mBAAmB;IAC9B,OAAO,CAAC,YAAY,CAAiC;IACrD,OAAO,CAAC,gBAAgB,CAA6B;IACrD,OAAO,CAAC,iBAAiB,CAA6B;IAEtD,yEAAyE;IACzE,cAAc,CACZ,UAAU,EAAE,MAAM,EAClB,SAAS,EAAE,MAAM,EACjB,QAAQ,CAAC,EAAE,OAAO,CAAC,mBAAmB,CAAC,GACtC,MAAM;IAgCT,YAAY,CAAC,KAAK,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI;IAI1C,cAAc,CAAC,UAAU,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI;IAIjD,gBAAgB,CAAC,SAAS,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI;IAIlD,WAAW,CAAC,KAAK,EAAE,MAAM,GAAG,mBAAmB,GAAG,IAAI;IAItD,+CAA+C;IAC/C,gBAAgB,CAAC,KAAK,EAAE,MAAM,GAAG,MAAM;IAWvC,sFAAsF;IACtF,cAAc,CAAC,KAAK,EAAE,MAAM,GAAG,MAAM;IAcrC,MAAM,CAAC,OAAO,CAAC,KAAK,EAAE,MAAM,GAAG,OAAO;IAItC,IAAI,IAAI,IAAI,MAAM,CAEjB;IAED,KAAK,IAAI,IAAI;IAMb,QAAQ,IAAI,MAAM,EAAE;CAGrB"}

package/dist/services/action-filter.d.ts

@@ -0,0 +1,195 @@
+/**
+ * ActionFilterService — dynamically filters which actions are shown to the LLM
+ * based on relevance to the current message.
+ *
+ * Two-tier ranking:
+ *   1. Vector search: embed action descriptions + similes at registration time.
+ *      At message time, embed the query (user message + context). Use cosine
+ *      similarity to get the top candidates.
+ *   2. BM25 reranking: rerank the vector-search candidates using BM25
+ *      (term-frequency * inverse-document-frequency). BM25 is especially good
+ *      at matching specific keywords that vector search might miss.
+ *
+ * Graceful degradation:
+ *   - If the embedding model is unavailable → BM25-only ranking.
+ *   - If BM25 also fails → return all actions (same as before).
+ */
+import type { Action, IAgentRuntime, Memory, Provider } from "../types/index.ts";
+import { Service } from "../types/service.ts";
+import type { State } from "../types/state.ts";
+declare module "../types/service.ts" {
+    interface ServiceTypeRegistry {
+        ACTION_FILTER: "action_filter";
+    }
+}
+export interface RankedAction {
+    action: Action;
+    /** Cosine similarity against the query embedding (0-1 range, 0 if unavailable). */
+    vectorScore: number;
+    /** BM25 score against the query text (0+ range, 0 if unavailable). */
+    bm25Score: number;
+    /** Weighted combination of vectorScore and bm25Score, plus momentum boost. */
+    combinedScore: number;
+}
+export interface FilterConfig {
+    /** Master switch — if false the service is a no-op. */
+    enabled: boolean;
+    /** Minimum registered action count before filtering kicks in. */
+    threshold: number;
+    /** How many candidates to pull from the vector search stage. */
+    vectorTopK: number;
+    /** Final number of actions returned after reranking. */
+    finalTopK: number;
+    /** Weight for the normalized vector score in the combined score (0-1). */
+    vectorWeight: number;
+    /** Weight for the normalized BM25 score in the combined score (0-1). */
+    bm25Weight: number;
+    /** Action names that always bypass filtering (in addition to per-action alwaysInclude). */
+    alwaysIncludeActions: string[];
+    /** Time window (ms) for conversation momentum decay. */
+    momentumDecayMs: number;
+    /** Score boost for recently used actions (0-1). */
+    momentumBoost: number;
+}
+export interface FilterMetrics {
+    /** Total number of filter() invocations. */
+    filterCalls: number;
+    /** How many times filtering was actually applied (vs. passthrough). */
+    filteredCalls: number;
+    /** How many times we fell back to BM25-only (embedding unavailable). */
+    bm25OnlyFallbacks: number;
+    /** How many times we fell back to returning all actions (complete failure). */
+    fullFallbacks: number;
+    /** Reported misses — actions that were filtered out but then selected by the LLM. */
+    missCount: number;
+    /** Names of missed actions for debugging (bounded ring buffer). */
+    missedActions: string[];
+    /** Average combined-score of returned actions (last call). */
+    lastAvgScore: number;
+    /** Number of actions in the embedding index. */
+    indexedActionCount: number;
+    /** Number of actions whose embedding failed during buildIndex or addAction. */
+    embedFailureCount: number;
+}
+/**
+ * Build a rich text blob from an action's metadata, suitable for both
+ * embedding and BM25 indexing.
+ */
+export declare function getActionEmbeddingText(action: Action): string;
+/**
+ * Build a text blob from a provider's metadata for BM25 indexing.
+ * Includes name, description, and relevanceKeywords.
+ */
+export declare function getProviderIndexText(provider: Provider): string;
+/**
+ * Build the query text used for vector + BM25 matching against the action
+ * index. Includes the user message, recent conversation context, and any
+ * detected intent keywords.
+ */
+export declare function buildQueryText(message: Memory, state: State): string;
+/**
+ * Normalize an array of scores to [0, 1] using min-max normalization.
+ * Returns an array of the same length. If all values are the same,
+ * returns an array of 1s (or 0s if all are 0).
+ *
+ * NaN and Infinity values are sanitized to 0 before normalization.
+ */
+export declare function minMaxNormalize(scores: number[]): number[];
+export declare class ActionFilterService extends Service {
+    static serviceType: "action_filter";
+    capabilityDescription: string;
+    private actionEmbeddings;
+    private bm25Index;
+    /** Separate BM25 index for provider descriptions, used by filterProviders(). */
+    private providerBM25Index;
+    private filterConfig;
+    private recentActions;
+    private readonly maxRecentActions;
+    private lastFilteredByRoom;
+    private readonly maxTrackedRooms;
+    private metrics;
+    private embeddingAvailable;
+    constructor(runtime?: IAgentRuntime, config?: Partial<FilterConfig>);
+    /** Start the service. Reads ACTION_FILTER_* from runtime settings, then builds indices. */
+    static start(runtime: IAgentRuntime): Promise<Service>;
+    stop(): Promise<void>;
+    /**
+     * Build (or rebuild) the vector + BM25 index for all registered actions.
+     * Also builds the provider BM25 index for dynamic provider filtering.
+     */
+    buildIndex(runtime: IAgentRuntime): Promise<void>;
+    /**
+     * Add a single action to the index at runtime (e.g. when a plugin
+     * registers a new action after startup).
+     */
+    addAction(action: Action, runtime: IAgentRuntime): Promise<void>;
+    /**
+     * Remove an action from both indices (e.g. when a plugin is unloaded).
+     */
+    removeAction(actionName: string): void;
+    /**
+     * Filter the registered actions to the most relevant subset for this message.
+     *
+     * Flow:
+     *  1. If action count <= threshold → return all (same as validate-all path).
+     *  2. Always-include actions bypass filtering and are prepended to results.
+     *  3. Vector search: embed query → cosine similarity → top vectorTopK.
+     *  4. BM25 rerank: score vectorTopK candidates → combine scores.
+     *  5. Apply momentum boost for recently used actions.
+     *  6. Return top finalTopK actions.
+     *
+     * The returned actions have NOT been validated — the caller (actionsProvider)
+     * is responsible for running `validate()` on the returned set.
+     */
+    filter(runtime: IAgentRuntime, message: Memory, state: State): Promise<Action[]>;
+    /**
+     * Score providers by relevance to the current message using BM25.
+     * Returns provider names sorted by relevance score, highest first.
+     * Only scores providers that have been indexed (i.e. have a description).
+     *
+     * This is used by composeState() to auto-include dynamic providers
+     * that are relevant to the current message, without requiring explicit
+     * relevanceKeywords on each provider.
+     *
+     * @param providers - The candidate providers to score (typically dynamic providers).
+     * @param message - The current message being processed.
+     * @param state - The current state (used to build query context).
+     * @param topK - Maximum number of provider names to return (default: 5).
+     * @returns Provider names sorted by descending BM25 relevance score.
+     */
+    filterProviders(providers: Provider[], message: Memory, state: State, topK?: number): string[];
+    /**
+     * Record that an action was used, so future queries in the same room
+     * receive a momentum boost for that action.
+     */
+    recordActionUse(actionName: string, roomId: string): void;
+    getMetrics(): FilterMetrics;
+    reportMiss(actionName: string): void;
+    hasAction(actionName: string): boolean;
+    getConfig(): Readonly<FilterConfig>;
+    /**
+     * Check whether an action was in the most recent filtered set for a room.
+     * Returns `true` if filtering was active for that room and the action
+     * WAS in the filtered set, `false` if it was filtered OUT, or `null` if
+     * filtering wasn't active for that room (so the caller should skip
+     * false-negative reporting).
+     */
+    wasActionInFilteredSet(actionName: string, roomId: string): boolean | null;
+    /**
+     * Override the tracked action set for a room with the exact list that was
+     * presented in the prompt. This keeps miss detection accurate when callers
+     * use filter() for ranking but still include additional actions.
+     */
+    setRoomActionSet(roomId: string, actionNames: Iterable<string>): void;
+    /**
+     * Run the full two-tier ranking pipeline on a set of candidate actions.
+     * Returns RankedAction[] sorted by combinedScore descending.
+     */
+    private rankActions;
+    /**
+     * Compute per-action momentum boosts based on recently used actions
+     * in the same room as the current message.
+     */
+    private computeMomentumBoosts;
+}
+//# sourceMappingURL=action-filter.d.ts.map

package/dist/services/action-filter.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"action-filter.d.ts","sourceRoot":"","sources":["../../src/services/action-filter.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;GAeG;AAGH,OAAO,KAAK,EACV,MAAM,EACN,aAAa,EACb,MAAM,EACN,QAAQ,EACT,MAAM,mBAAmB,CAAC;AAE3B,OAAO,EAAE,OAAO,EAAE,MAAM,qBAAqB,CAAC;AAC9C,OAAO,KAAK,EAAE,KAAK,EAAE,MAAM,mBAAmB,CAAC;AAI/C,OAAO,QAAQ,qBAAqB,CAAC;IACnC,UAAU,mBAAmB;QAC3B,aAAa,EAAE,eAAe,CAAC;KAChC;CACF;AAED,MAAM,WAAW,YAAY;IAC3B,MAAM,EAAE,MAAM,CAAC;IACf,mFAAmF;IACnF,WAAW,EAAE,MAAM,CAAC;IACpB,sEAAsE;IACtE,SAAS,EAAE,MAAM,CAAC;IAClB,8EAA8E;IAC9E,aAAa,EAAE,MAAM,CAAC;CACvB;AAED,MAAM,WAAW,YAAY;IAC3B,uDAAuD;IACvD,OAAO,EAAE,OAAO,CAAC;IACjB,iEAAiE;IACjE,SAAS,EAAE,MAAM,CAAC;IAClB,gEAAgE;IAChE,UAAU,EAAE,MAAM,CAAC;IACnB,wDAAwD;IACxD,SAAS,EAAE,MAAM,CAAC;IAClB,0EAA0E;IAC1E,YAAY,EAAE,MAAM,CAAC;IACrB,wEAAwE;IACxE,UAAU,EAAE,MAAM,CAAC;IACnB,2FAA2F;IAC3F,oBAAoB,EAAE,MAAM,EAAE,CAAC;IAC/B,wDAAwD;IACxD,eAAe,EAAE,MAAM,CAAC;IACxB,mDAAmD;IACnD,aAAa,EAAE,MAAM,CAAC;CACvB;AAED,MAAM,WAAW,aAAa;IAC5B,4CAA4C;IAC5C,WAAW,EAAE,MAAM,CAAC;IACpB,uEAAuE;IACvE,aAAa,EAAE,MAAM,CAAC;IACtB,wEAAwE;IACxE,iBAAiB,EAAE,MAAM,CAAC;IAC1B,+EAA+E;IAC/E,aAAa,EAAE,MAAM,CAAC;IACtB,qFAAqF;IACrF,SAAS,EAAE,MAAM,CAAC;IAClB,mEAAmE;IACnE,aAAa,EAAE,MAAM,EAAE,CAAC;IACxB,8DAA8D;IAC9D,YAAY,EAAE,MAAM,CAAC;IACrB,gDAAgD;IAChD,kBAAkB,EAAE,MAAM,CAAC;IAC3B,+EAA+E;IAC/E,iBAAiB,EAAE,MAAM,CAAC;CAC3B;AA2CD;;;GAGG;AACH,wBAAgB,sBAAsB,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,CAW7D;AAED;;;GAGG;AACH,wBAAgB,oBAAoB,CAAC,QAAQ,EAAE,QAAQ,GAAG,MAAM,CAO/D;AAED;;;;GAIG;AACH,wBAAgB,cAAc,CAAC,OAAO,EAAE,MAAM,EAAE,KAAK,EAAE,KAAK,GAAG,MAAM,CAsCpE;AAED;;;;;;GAMG;AACH,wBAAgB,eAAe,CAAC,MAAM,EAAE,MAAM,EAAE,GAAG,MAAM,EAAE,CAqB1D;AAED,qBAAa,mBAAoB,SAAQ,OAAO;IAC9C,MAAM,CAAC,WAAW,EAAG,eAAe,CAAU;IAC9C,qBAAqB,SACmD;IAExE,OAAO,CAAC,gBAAgB,CAAoC;IAE5D,OAAO,CAAC,SAAS,CAA8B;IAE/C,gFAAgF;IAChF,OAAO,CAAC,iBAAiB,CAA8B;IAEvD,OAAO,CAAC,YAAY,CAAe;IAEnC,OAAO,CAAC,aAAa,CAA2B;IAChD,OAAO,CAAC,QAAQ,CAAC,gBAAgB,CAAO;IAExC,OAAO,CAAC,kBAAkB,CAAuC;IACjE,OAAO,CAAC,QAAQ,CAAC,eAAe,CAAO;IAEvC,OAAO,CAAC,OAAO,CAAiC;IAEhD,OAAO,CAAC,kBAAkB,CAAS;gBAEvB,OAAO,CAAC,EAAE,aAAa,EAAE,MAAM,CAAC,EAAE,OAAO,CAAC,YAAY,CAAC;IAKnE,2FAA2F;WAC9E,KAAK,CAAC,OAAO,EAAE,aAAa,GAAG,OAAO,CAAC,OAAO,CAAC;IAgCtD,IAAI,IAAI,OAAO,CAAC,IAAI,CAAC;IAa3B;;;OAGG;IACG,UAAU,CAAC,OAAO,EAAE,aAAa,GAAG,OAAO,CAAC,IAAI,CAAC;IAiFvD;;;OAGG;IACG,SAAS,CAAC,MAAM,EAAE,MAAM,EAAE,OAAO,EAAE,aAAa,GAAG,OAAO,CAAC,IAAI,CAAC;IA8BtE;;OAEG;IACH,YAAY,CAAC,UAAU,EAAE,MAAM,GAAG,IAAI;IAMtC;;;;;;;;;;;;;OAaG;IACG,MAAM,CACV,OAAO,EAAE,aAAa,EACtB,OAAO,EAAE,MAAM,EACf,KAAK,EAAE,KAAK,GACX,OAAO,CAAC,MAAM,EAAE,CAAC;IA2FpB;;;;;;;;;;;;;;OAcG;IACH,eAAe,CACb,SAAS,EAAE,QAAQ,EAAE,EACrB,OAAO,EAAE,MAAM,EACf,KAAK,EAAE,KAAK,EACZ,IAAI,GAAE,MAA+B,GACpC,MAAM,EAAE;IA6BX;;;OAGG;IACH,eAAe,CAAC,UAAU,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,GAAG,IAAI;IAYzD,UAAU,IAAI,aAAa;IAO3B,UAAU,CAAC,UAAU,EAAE,MAAM,GAAG,IAAI;IAepC,SAAS,CAAC,UAAU,EAAE,MAAM,GAAG,OAAO;IAItC,SAAS,IAAI,QAAQ,CAAC,YAAY,CAAC;IAInC;;;;;;OAMG;IACH,sBAAsB,CAAC,UAAU,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,GAAG,OAAO,GAAG,IAAI;IAQ1E;;;;OAIG;IACH,gBAAgB,CAAC,MAAM,EAAE,MAAM,EAAE,WAAW,EAAE,QAAQ,CAAC,MAAM,CAAC,GAAG,IAAI;IAUrE;;;OAGG;YACW,WAAW;IAyIzB;;;OAGG;IACH,OAAO,CAAC,qBAAqB;CA6B9B"}

package/dist/services/bm25.d.ts

@@ -0,0 +1,51 @@
+/**
+ * BM25 index with incremental add/remove support.
+ *
+ * Uses the shared Tokenizer from search.ts as the primary text processor
+ * (Unicode normalization, optional Porter2 stemming, configurable stopwords).
+ * Falls back to a unicode-aware regex tokenizer for scripts the shared
+ * Tokenizer doesn't cover (Cyrillic, Arabic, etc.).
+ *
+ * Scoring formula:
+ *   score(q, d) = Σ IDF(qi) * (f(qi, d) * (k1 + 1)) / (f(qi, d) + k1 * (1 - b + b * |d| / avgdl))
+ */
+import { type TokenizerOptions } from "../search.ts";
+export interface BM25Result {
+    id: string;
+    score: number;
+}
+/**
+ * BM25 index for text documents with incremental add/remove.
+ *
+ * Primary tokenization: shared Tokenizer (stemming, Unicode normalization).
+ * Fallback: unicode-aware regex split for scripts the Tokenizer strips
+ * (Cyrillic, Arabic, Devanagari, etc.). The fallback tokens are merged
+ * with the primary tokens so all scripts are searchable.
+ */
+export declare class BM25Index {
+    private documents;
+    private documentFrequencies;
+    private avgDocLength;
+    private totalTermCount;
+    private k1;
+    private b;
+    private sharedTokenizer;
+    private stopWords;
+    constructor(k1?: number, b?: number, tokenizerOptions?: TokenizerOptions);
+    addDocument(id: string, text: string): void;
+    removeDocument(id: string): void;
+    search(query: string, topK?: number): BM25Result[];
+    searchSubset(query: string, documentIds: string[], topK?: number): BM25Result[];
+    get size(): number;
+    has(id: string): boolean;
+    private scoreDocument;
+    private recomputeAvgDocLength;
+    /**
+     * Tokenize text using the shared Tokenizer (for English, CJK, Hangul)
+     * merged with a unicode-aware regex fallback (for Cyrillic, Arabic, etc.).
+     * This ensures all scripts are searchable while still benefiting from
+     * the Tokenizer's stemming and normalization for supported scripts.
+     */
+    private tokenize;
+}
+//# sourceMappingURL=bm25.d.ts.map