@elizaos/core 2.0.0-alpha.2 → 2.0.0-alpha.21

package/dist/plugin.d.ts

@@ -1,13 +0,0 @@
-import type { Plugin } from "./types";
-export declare function tryInstallPlugin(pluginName: string): Promise<boolean>;
-export declare function isValidPluginShape(obj: unknown): obj is Plugin;
-export declare function validatePlugin(plugin: unknown): {
-    isValid: boolean;
-    errors: string[];
-};
-export declare function loadAndPreparePlugin(pluginName: string): Promise<Plugin | null>;
-export declare function normalizePluginName(pluginName: string): string;
-export declare function resolvePluginDependencies(availablePlugins: Map<string, Plugin>, isTestMode?: boolean): Plugin[];
-export declare function loadPlugin(nameOrPlugin: string | Plugin): Promise<Plugin | null>;
-export declare function resolvePlugins(plugins: (string | Plugin)[], isTestMode?: boolean): Promise<Plugin[]>;
-//# sourceMappingURL=plugin.d.ts.map

package/dist/plugin.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"plugin.d.ts","sourceRoot":"","sources":["../src/plugin.ts"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,SAAS,CAAC;AActC,wBAAsB,gBAAgB,CAAC,UAAU,EAAE,MAAM,GAAG,OAAO,CAAC,OAAO,CAAC,CAgF3E;AAED,wBAAgB,kBAAkB,CAAC,GAAG,EAAE,OAAO,GAAG,GAAG,IAAI,MAAM,CAkB9D;AAED,wBAAgB,cAAc,CAAC,MAAM,EAAE,OAAO,GAAG;IAC/C,OAAO,EAAE,OAAO,CAAC;IACjB,MAAM,EAAE,MAAM,EAAE,CAAC;CAClB,CAsDA;AAED,wBAAsB,oBAAoB,CACxC,UAAU,EAAE,MAAM,GACjB,OAAO,CAAC,MAAM,GAAG,IAAI,CAAC,CA6DxB;AAED,wBAAgB,mBAAmB,CAAC,UAAU,EAAE,MAAM,GAAG,MAAM,CAM9D;AAED,wBAAgB,yBAAyB,CACvC,gBAAgB,EAAE,GAAG,CAAC,MAAM,EAAE,MAAM,CAAC,EACrC,UAAU,GAAE,OAAe,GAC1B,MAAM,EAAE,CAuFV;AAED,wBAAsB,UAAU,CAC9B,YAAY,EAAE,MAAM,GAAG,MAAM,GAC5B,OAAO,CAAC,MAAM,GAAG,IAAI,CAAC,CAexB;AAiFD,wBAAsB,cAAc,CAClC,OAAO,EAAE,CAAC,MAAM,GAAG,MAAM,CAAC,EAAE,EAC5B,UAAU,GAAE,OAAe,GAC1B,OAAO,CAAC,MAAM,EAAE,CAAC,CAyBnB"}

package/dist/prompts.d.ts

@@ -1,85 +0,0 @@
-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\nFirst, think about what you want to do next and plan your actions. Then, write the next message and include the actions you plan to take.\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>\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>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\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>\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>.";
-export declare const chooseOptionTemplate = "# Task: Choose an option from the available choices.\n\n{{providers}}\n\n# Available Options:\n{{options}}\n\n# Instructions: \nAnalyze the options and select the most appropriate one based on the current context.\nProvide your reasoning and the selected option ID.\n\nRespond using XML format like this:\n<response>\n    <thought>Your reasoning for the selection</thought>\n    <selected_id>The ID of the selected option</selected_id>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above.";
-export declare const imageGenerationTemplate = "# Task: Generate an image prompt for {{agentName}}.\n\n{{providers}}\n\n# Instructions:\nBased on the conversation, create a detailed prompt for image generation.\nThe prompt should be specific, descriptive, and suitable for AI image generation.\n\n# Recent conversation:\n{{recentMessages}}\n\nRespond using XML format like this:\n<response>\n    <thought>Your reasoning for the image prompt</thought>\n    <prompt>Detailed image generation prompt</prompt>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above.";
-export declare const reflectionTemplate = "# Task: Reflect on recent agent behavior and interactions.\n\n{{providers}}\n\n# Recent Interactions:\n{{recentInteractions}}\n\n# Instructions:\nAnalyze the agent's recent behavior and interactions. Consider:\n1. Was the communication clear and helpful?\n2. Were responses appropriate for the context?\n3. Were any mistakes made?\n4. What could be improved?\n\nRespond using XML format like this:\n<response>\n    <thought>Your detailed analysis</thought>\n    <quality_score>Score 0-100 for overall quality</quality_score>\n    <strengths>What went well</strengths>\n    <improvements>What could be improved</improvements>\n    <learnings>Key takeaways for future interactions</learnings>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above.";
-export declare const updateSettingsTemplate = "# Task: Update settings based on the request.\n\n{{providers}}\n\n# Current Settings:\n{{settings}}\n\n# Instructions:\nBased on the request, determine which settings to update.\nOnly update settings that the user has explicitly requested.\n\nRespond using XML format like this:\n<response>\n    <thought>Your reasoning for the settings changes</thought>\n    <updates>\n        <update>\n            <key>setting_key</key>\n            <value>new_value</value>\n        </update>\n    </updates>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above.";
-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\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\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\nFirst, think about what you want to do next and plan your actions. Then, write the next message and include the actions you plan to take.\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>\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>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\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>\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>.";
-export declare const CHOOSE_OPTION_TEMPLATE = "# Task: Choose an option from the available choices.\n\n{{providers}}\n\n# Available Options:\n{{options}}\n\n# Instructions: \nAnalyze the options and select the most appropriate one based on the current context.\nProvide your reasoning and the selected option ID.\n\nRespond using XML format like this:\n<response>\n    <thought>Your reasoning for the selection</thought>\n    <selected_id>The ID of the selected option</selected_id>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above.";
-export declare const IMAGE_GENERATION_TEMPLATE = "# Task: Generate an image prompt for {{agentName}}.\n\n{{providers}}\n\n# Instructions:\nBased on the conversation, create a detailed prompt for image generation.\nThe prompt should be specific, descriptive, and suitable for AI image generation.\n\n# Recent conversation:\n{{recentMessages}}\n\nRespond using XML format like this:\n<response>\n    <thought>Your reasoning for the image prompt</thought>\n    <prompt>Detailed image generation prompt</prompt>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above.";
-export declare const REFLECTION_TEMPLATE = "# Task: Reflect on recent agent behavior and interactions.\n\n{{providers}}\n\n# Recent Interactions:\n{{recentInteractions}}\n\n# Instructions:\nAnalyze the agent's recent behavior and interactions. Consider:\n1. Was the communication clear and helpful?\n2. Were responses appropriate for the context?\n3. Were any mistakes made?\n4. What could be improved?\n\nRespond using XML format like this:\n<response>\n    <thought>Your detailed analysis</thought>\n    <quality_score>Score 0-100 for overall quality</quality_score>\n    <strengths>What went well</strengths>\n    <improvements>What could be improved</improvements>\n    <learnings>Key takeaways for future interactions</learnings>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above.";
-export declare const UPDATE_SETTINGS_TEMPLATE = "# Task: Update settings based on the request.\n\n{{providers}}\n\n# Current Settings:\n{{settings}}\n\n# Instructions:\nBased on the request, determine which settings to update.\nOnly update settings that the user has explicitly requested.\n\nRespond using XML format like this:\n<response>\n    <thought>Your reasoning for the settings changes</thought>\n    <updates>\n        <update>\n            <key>setting_key</key>\n            <value>new_value</value>\n        </update>\n    </updates>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above.";
-export declare const UPDATE_ENTITY_TEMPLATE = "# 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 OPTION_EXTRACTION_TEMPLATE = "# 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\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\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 scheduleFollowUpTemplate = "# Schedule Follow-up\n\nCurrent message: {{message}}\nSender: {{senderName}} (ID: {{senderId}})\n\n## Instructions\nExtract the follow-up scheduling information from the message:\n1. Who to follow up with (name or entity reference)\n2. When to follow up (date/time or relative time like \"tomorrow\", \"next week\")\n3. Reason for the follow-up\n4. Priority (high, medium, low)\n5. Any specific message or notes\n\n## Current Date/Time\n{{currentDateTime}}\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\n## Response Format\n<response>\n<contactName>Name of the contact to follow up with</contactName>\n<entityId>ID if known, otherwise leave empty</entityId>\n<scheduledAt>ISO datetime for the follow-up</scheduledAt>\n<reason>Reason for the follow-up</reason>\n<priority>high, medium, or low</priority>\n<message>Optional message or notes for the follow-up</message>\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 addContactTemplate = "# Add Contact to Rolodex\n\nCurrent message: {{message}}\nSender: {{senderName}} (ID: {{senderId}})\n\n## Instructions\nExtract the contact information from the message and determine:\n1. Who should be added as a contact (name or entity reference)\n2. What category they belong to (friend, family, colleague, acquaintance, vip, business)\n3. Any preferences or notes mentioned\n\nRespond with the extracted information in XML format.\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\n## Response Format\n<response>\n<contactName>Name of the contact to add</contactName>\n<entityId>ID if known, otherwise leave empty</entityId>\n<categories>comma-separated categories</categories>\n<notes>Any additional notes or preferences</notes>\n<timezone>Timezone if mentioned</timezone>\n<language>Language preference if mentioned</language>\n<reason>Reason for adding this contact</reason>\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 searchContactsTemplate = "# Search Contacts\n\nCurrent message: {{message}}\nSender: {{senderName}} (ID: {{senderId}})\n\n## Instructions\nExtract the search criteria from the message:\n1. Categories to filter by (friend, family, colleague, acquaintance, vip, business)\n2. Search terms (names or keywords)\n3. Tags to filter by\n4. Any other filters mentioned\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\n## Response Format\n<response>\n<categories>comma-separated list of categories to filter by</categories>\n<searchTerm>search term for names</searchTerm>\n<tags>comma-separated list of tags</tags>\n<intent>list, search, or count</intent>\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 removeContactTemplate = "# Remove Contact from Rolodex\n\nCurrent message: {{message}}\nSender: {{senderName}} (ID: {{senderId}})\n\n## Instructions\nExtract the contact removal information from the message:\n1. Who to remove (name or entity reference)\n2. Confirmation of the intent to remove\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\n## Response Format\n<response>\n<contactName>Name of the contact to remove</contactName>\n<confirmed>yes or no</confirmed>\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 updateContactTemplate = "# Update Contact Information\n\nCurrent message: {{message}}\nSender: {{senderName}} (ID: {{senderId}})\n\n## Instructions\nExtract the contact update information from the message:\n1. Who to update (name or entity reference)\n2. What fields to update (categories, tags, preferences, notes, custom fields)\n3. Whether to add to or replace existing values\n\n## Current Date/Time\n{{currentDateTime}}\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\n## Response Format\n<response>\n<contactName>Name of the contact to update</contactName>\n<operation>add_to or replace</operation>\n<categories>comma-separated list of categories</categories>\n<tags>comma-separated list of tags</tags>\n<preferences>key1:value1,key2:value2</preferences>\n<customFields>field1:value1,field2:value2</customFields>\n<notes>Any additional notes</notes>\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 shouldFollowRoomTemplate = "# Task: Decide if {{agentName}} should start following this room, i.e. eagerly participating without explicit mentions.\n\n{{recentMessages}}\n\nShould {{agentName}} start following this room, eagerly participating without explicit mentions?\nRespond with YES if:\n- The user has directly asked {{agentName}} to follow the conversation or participate more actively\n- The conversation topic is highly engaging and {{agentName}}'s input would add significant value\n- {{agentName}} has unique insights to contribute and the users seem receptive\n\nOtherwise, respond with NO.\nRespond with only a YES or a NO.";
-export declare const shouldUnfollowRoomTemplate = "# Task: Decide if {{agentName}} should stop closely following this previously followed room and only respond when mentioned.\n\n{{recentMessages}}\n\nShould {{agentName}} stop closely following this previously followed room and only respond when mentioned?\nRespond with YES if:\n- The user has suggested that {{agentName}} is over-participating or being disruptive\n- {{agentName}}'s eagerness to contribute is not well-received by the users\n- The conversation has shifted to a topic where {{agentName}} has less to add\n\nOtherwise, respond with NO.\nRespond with only a YES or a NO.";
-export declare const shouldMuteRoomTemplate = "# Task: Decide if {{agentName}} should mute this room and stop responding unless explicitly mentioned.\n\n{{recentMessages}}\n\nShould {{agentName}} mute this room and stop responding unless explicitly mentioned?\n\nRespond with YES if:\n- The user is being aggressive, rude, or inappropriate\n- The user has directly asked {{agentName}} to stop responding or be quiet\n- {{agentName}}'s responses are not well-received or are annoying the user(s)\n\nOtherwise, respond with NO.\nRespond with only a YES or a NO.";
-export declare const shouldUnmuteRoomTemplate = "# Task: Decide if {{agentName}} should unmute this previously muted room and start considering it for responses again.\n\n{{recentMessages}}\n\nShould {{agentName}} unmute this previously muted room and start considering it for responses again?\nRespond with YES if:\n- The user has explicitly asked {{agentName}} to start responding again\n- The user seems to want to re-engage with {{agentName}} in a respectful manner\n- The tone of the conversation has improved and {{agentName}}'s input would be welcome\n\nOtherwise, respond with NO.\nRespond with only a YES or a NO.";
-export declare const targetExtractionTemplate = "# Task: Extract Target and Source Information\n\n# Recent Messages:\n{{recentMessages}}\n\n# Instructions:\nAnalyze the conversation to identify:\n1. The target type (user or room)\n2. The target platform/source (e.g. telegram, discord, etc)\n3. Any identifying information about the target\n4. The message text to send\n\nReturn an XML response with:\n<response>\n  <targetType>user|room</targetType>\n  <source>platform-name</source>\n  <messageText>text_to_send</messageText>\n  <identifiers>\n    <username>username_if_applicable</username>\n    <roomName>room_name_if_applicable</roomName>\n  </identifiers>\n</response>";
-export declare const updateRoleTemplate = "# Task: Update entity role in the world.\n\n{{providers}}\n\n# Current Role Assignments:\n{{roles}}\n\n# Instructions:\nBased on the request, determine the role assignment to make.\nValid roles are: OWNER, ADMIN, MEMBER, GUEST, NONE\n\nRespond using XML format like this:\n<response>\n    <thought>Your reasoning for the role change</thought>\n    <entity_id>The entity ID to update</entity_id>\n    <new_role>The new role to assign (OWNER, ADMIN, MEMBER, GUEST, or NONE)</new_role>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above.";
-export declare const initialSummarizationTemplate = "# Task: Summarize Conversation\n\nYou are analyzing a conversation to create a concise summary that captures the key points, topics, and important details.\n\n# Recent Messages\n{{recentMessages}}\n\n# Instructions\nGenerate a summary that:\n1. Captures the main topics discussed\n2. Highlights key information shared\n3. Notes any decisions made or questions asked\n4. Maintains context for future reference\n5. Is concise but comprehensive\n\n**IMPORTANT**: Keep the summary under 2500 tokens. Be comprehensive but concise.\n\nAlso extract:\n- **Topics**: List of main topics discussed (comma-separated)\n- **Key Points**: Important facts or decisions (bullet points)\n\nRespond in this XML format:\n<summary>\n  <text>Your comprehensive summary here</text>\n  <topics>topic1, topic2, topic3</topics>\n  <keyPoints>\n    <point>First key point</point>\n    <point>Second key point</point>\n  </keyPoints>\n</summary>";
-export declare const updateSummarizationTemplate = "# Task: Update and Condense Conversation Summary\n\nYou are updating an existing conversation summary with new messages, while keeping the total summary concise.\n\n# Existing Summary\n{{existingSummary}}\n\n# Existing Topics\n{{existingTopics}}\n\n# New Messages Since Last Summary\n{{newMessages}}\n\n# Instructions\nUpdate the summary by:\n1. Merging the existing summary with insights from the new messages\n2. Removing redundant or less important details to stay under the token limit\n3. Keeping the most important context and decisions\n4. Adding new topics if they emerge\n5. **CRITICAL**: Keep the ENTIRE updated summary under 2500 tokens\n\nThe goal is a rolling summary that captures the essence of the conversation without growing indefinitely.\n\nRespond in this XML format:\n<summary>\n  <text>Your updated and condensed summary here</text>\n  <topics>topic1, topic2, topic3</topics>\n  <keyPoints>\n    <point>First key point</point>\n    <point>Second key point</point>\n  </keyPoints>\n</summary>";
-export declare const longTermExtractionTemplate = "# Task: Extract Long-Term Memory (Strict Criteria)\n\nYou are analyzing a conversation to extract ONLY the most critical, persistent information about the user using cognitive science memory categories.\n\n# Recent Messages\n{{recentMessages}}\n\n# Current Long-Term Memories\n{{existingMemories}}\n\n# ULTRA-STRICT EXTRACTION CRITERIA\n\nDefault to NOT extracting. Confidence must be >= 0.85.\nIf there are no qualifying facts, respond with <memories></memories>\n\n# Response Format\n\n<memories>\n  <memory>\n    <category>semantic</category>\n    <content>User is a senior TypeScript developer with 8 years of backend experience</content>\n    <confidence>0.95</confidence>\n  </memory>\n</memories>";
-export declare const messageClassifierTemplate = "Analyze this user request and classify it for planning purposes:\n\n\"{{text}}\"\n\nClassify the request across these dimensions:\n\n1. COMPLEXITY LEVEL:\n- simple: Direct actions that don't require planning\n- medium: Multi-step tasks requiring coordination\n- complex: Strategic initiatives with multiple stakeholders\n- enterprise: Large-scale transformations with full complexity\n\n2. PLANNING TYPE:\n- direct_action: Single action, no planning needed\n- sequential_planning: Multiple steps in sequence\n- strategic_planning: Complex coordination with stakeholders\n\n3. REQUIRED CAPABILITIES:\n- List specific capabilities needed (analysis, communication, project_management, etc.)\n\n4. STAKEHOLDERS:\n- List types of people/groups involved\n\n5. CONSTRAINTS:\n- List limitations or requirements mentioned\n\n6. DEPENDENCIES:\n- List dependencies between tasks or external factors\n\nRespond in this exact format:\nCOMPLEXITY: [simple|medium|complex|enterprise]\nPLANNING: [direct_action|sequential_planning|strategic_planning]\nCAPABILITIES: [comma-separated list]\nSTAKEHOLDERS: [comma-separated list]\nCONSTRAINTS: [comma-separated list]\nDEPENDENCIES: [comma-separated list]\nCONFIDENCE: [0.0-1.0]";
-export declare const SCHEDULE_FOLLOW_UP_TEMPLATE = "# Schedule Follow-up\n\nCurrent message: {{message}}\nSender: {{senderName}} (ID: {{senderId}})\n\n## Instructions\nExtract the follow-up scheduling information from the message:\n1. Who to follow up with (name or entity reference)\n2. When to follow up (date/time or relative time like \"tomorrow\", \"next week\")\n3. Reason for the follow-up\n4. Priority (high, medium, low)\n5. Any specific message or notes\n\n## Current Date/Time\n{{currentDateTime}}\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\n## Response Format\n<response>\n<contactName>Name of the contact to follow up with</contactName>\n<entityId>ID if known, otherwise leave empty</entityId>\n<scheduledAt>ISO datetime for the follow-up</scheduledAt>\n<reason>Reason for the follow-up</reason>\n<priority>high, medium, or low</priority>\n<message>Optional message or notes for the follow-up</message>\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 ADD_CONTACT_TEMPLATE = "# Add Contact to Rolodex\n\nCurrent message: {{message}}\nSender: {{senderName}} (ID: {{senderId}})\n\n## Instructions\nExtract the contact information from the message and determine:\n1. Who should be added as a contact (name or entity reference)\n2. What category they belong to (friend, family, colleague, acquaintance, vip, business)\n3. Any preferences or notes mentioned\n\nRespond with the extracted information in XML format.\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\n## Response Format\n<response>\n<contactName>Name of the contact to add</contactName>\n<entityId>ID if known, otherwise leave empty</entityId>\n<categories>comma-separated categories</categories>\n<notes>Any additional notes or preferences</notes>\n<timezone>Timezone if mentioned</timezone>\n<language>Language preference if mentioned</language>\n<reason>Reason for adding this contact</reason>\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 SEARCH_CONTACTS_TEMPLATE = "# Search Contacts\n\nCurrent message: {{message}}\nSender: {{senderName}} (ID: {{senderId}})\n\n## Instructions\nExtract the search criteria from the message:\n1. Categories to filter by (friend, family, colleague, acquaintance, vip, business)\n2. Search terms (names or keywords)\n3. Tags to filter by\n4. Any other filters mentioned\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\n## Response Format\n<response>\n<categories>comma-separated list of categories to filter by</categories>\n<searchTerm>search term for names</searchTerm>\n<tags>comma-separated list of tags</tags>\n<intent>list, search, or count</intent>\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 REMOVE_CONTACT_TEMPLATE = "# Remove Contact from Rolodex\n\nCurrent message: {{message}}\nSender: {{senderName}} (ID: {{senderId}})\n\n## Instructions\nExtract the contact removal information from the message:\n1. Who to remove (name or entity reference)\n2. Confirmation of the intent to remove\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\n## Response Format\n<response>\n<contactName>Name of the contact to remove</contactName>\n<confirmed>yes or no</confirmed>\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 UPDATE_CONTACT_TEMPLATE = "# Update Contact Information\n\nCurrent message: {{message}}\nSender: {{senderName}} (ID: {{senderId}})\n\n## Instructions\nExtract the contact update information from the message:\n1. Who to update (name or entity reference)\n2. What fields to update (categories, tags, preferences, notes, custom fields)\n3. Whether to add to or replace existing values\n\n## Current Date/Time\n{{currentDateTime}}\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\n## Response Format\n<response>\n<contactName>Name of the contact to update</contactName>\n<operation>add_to or replace</operation>\n<categories>comma-separated list of categories</categories>\n<tags>comma-separated list of tags</tags>\n<preferences>key1:value1,key2:value2</preferences>\n<customFields>field1:value1,field2:value2</customFields>\n<notes>Any additional notes</notes>\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_FOLLOW_ROOM_TEMPLATE = "# Task: Decide if {{agentName}} should start following this room, i.e. eagerly participating without explicit mentions.\n\n{{recentMessages}}\n\nShould {{agentName}} start following this room, eagerly participating without explicit mentions?\nRespond with YES if:\n- The user has directly asked {{agentName}} to follow the conversation or participate more actively\n- The conversation topic is highly engaging and {{agentName}}'s input would add significant value\n- {{agentName}} has unique insights to contribute and the users seem receptive\n\nOtherwise, respond with NO.\nRespond with only a YES or a NO.";
-export declare const SHOULD_UNFOLLOW_ROOM_TEMPLATE = "# Task: Decide if {{agentName}} should stop closely following this previously followed room and only respond when mentioned.\n\n{{recentMessages}}\n\nShould {{agentName}} stop closely following this previously followed room and only respond when mentioned?\nRespond with YES if:\n- The user has suggested that {{agentName}} is over-participating or being disruptive\n- {{agentName}}'s eagerness to contribute is not well-received by the users\n- The conversation has shifted to a topic where {{agentName}} has less to add\n\nOtherwise, respond with NO.\nRespond with only a YES or a NO.";
-export declare const SHOULD_MUTE_ROOM_TEMPLATE = "# Task: Decide if {{agentName}} should mute this room and stop responding unless explicitly mentioned.\n\n{{recentMessages}}\n\nShould {{agentName}} mute this room and stop responding unless explicitly mentioned?\n\nRespond with YES if:\n- The user is being aggressive, rude, or inappropriate\n- The user has directly asked {{agentName}} to stop responding or be quiet\n- {{agentName}}'s responses are not well-received or are annoying the user(s)\n\nOtherwise, respond with NO.\nRespond with only a YES or a NO.";
-export declare const SHOULD_UNMUTE_ROOM_TEMPLATE = "# Task: Decide if {{agentName}} should unmute this previously muted room and start considering it for responses again.\n\n{{recentMessages}}\n\nShould {{agentName}} unmute this previously muted room and start considering it for responses again?\nRespond with YES if:\n- The user has explicitly asked {{agentName}} to start responding again\n- The user seems to want to re-engage with {{agentName}} in a respectful manner\n- The tone of the conversation has improved and {{agentName}}'s input would be welcome\n\nOtherwise, respond with NO.\nRespond with only a YES or a NO.";
-export declare const shouldFollowTemplate = "# Task: Decide if {{agentName}} should start following this room, i.e. eagerly participating without explicit mentions.\n\n{{recentMessages}}\n\nShould {{agentName}} start following this room, eagerly participating without explicit mentions?\nRespond with YES if:\n- The user has directly asked {{agentName}} to follow the conversation or participate more actively\n- The conversation topic is highly engaging and {{agentName}}'s input would add significant value\n- {{agentName}} has unique insights to contribute and the users seem receptive\n\nOtherwise, respond with NO.\nRespond with only a YES or a NO.";
-export declare const shouldUnfollowTemplate = "# Task: Decide if {{agentName}} should stop closely following this previously followed room and only respond when mentioned.\n\n{{recentMessages}}\n\nShould {{agentName}} stop closely following this previously followed room and only respond when mentioned?\nRespond with YES if:\n- The user has suggested that {{agentName}} is over-participating or being disruptive\n- {{agentName}}'s eagerness to contribute is not well-received by the users\n- The conversation has shifted to a topic where {{agentName}} has less to add\n\nOtherwise, respond with NO.\nRespond with only a YES or a NO.";
-export declare const shouldMuteTemplate = "# Task: Decide if {{agentName}} should mute this room and stop responding unless explicitly mentioned.\n\n{{recentMessages}}\n\nShould {{agentName}} mute this room and stop responding unless explicitly mentioned?\n\nRespond with YES if:\n- The user is being aggressive, rude, or inappropriate\n- The user has directly asked {{agentName}} to stop responding or be quiet\n- {{agentName}}'s responses are not well-received or are annoying the user(s)\n\nOtherwise, respond with NO.\nRespond with only a YES or a NO.";
-export declare const shouldUnmuteTemplate = "# Task: Decide if {{agentName}} should unmute this previously muted room and start considering it for responses again.\n\n{{recentMessages}}\n\nShould {{agentName}} unmute this previously muted room and start considering it for responses again?\nRespond with YES if:\n- The user has explicitly asked {{agentName}} to start responding again\n- The user seems to want to re-engage with {{agentName}} in a respectful manner\n- The tone of the conversation has improved and {{agentName}}'s input would be welcome\n\nOtherwise, respond with NO.\nRespond with only a YES or a NO.";
-export declare const TARGET_EXTRACTION_TEMPLATE = "# Task: Extract Target and Source Information\n\n# Recent Messages:\n{{recentMessages}}\n\n# Instructions:\nAnalyze the conversation to identify:\n1. The target type (user or room)\n2. The target platform/source (e.g. telegram, discord, etc)\n3. Any identifying information about the target\n4. The message text to send\n\nReturn an XML response with:\n<response>\n  <targetType>user|room</targetType>\n  <source>platform-name</source>\n  <messageText>text_to_send</messageText>\n  <identifiers>\n    <username>username_if_applicable</username>\n    <roomName>room_name_if_applicable</roomName>\n  </identifiers>\n</response>";
-export declare const UPDATE_ROLE_TEMPLATE = "# Task: Update entity role in the world.\n\n{{providers}}\n\n# Current Role Assignments:\n{{roles}}\n\n# Instructions:\nBased on the request, determine the role assignment to make.\nValid roles are: OWNER, ADMIN, MEMBER, GUEST, NONE\n\nRespond using XML format like this:\n<response>\n    <thought>Your reasoning for the role change</thought>\n    <entity_id>The entity ID to update</entity_id>\n    <new_role>The new role to assign (OWNER, ADMIN, MEMBER, GUEST, or NONE)</new_role>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above.";
-export declare const INITIAL_SUMMARIZATION_TEMPLATE = "# Task: Summarize Conversation\n\nYou are analyzing a conversation to create a concise summary that captures the key points, topics, and important details.\n\n# Recent Messages\n{{recentMessages}}\n\n# Instructions\nGenerate a summary that:\n1. Captures the main topics discussed\n2. Highlights key information shared\n3. Notes any decisions made or questions asked\n4. Maintains context for future reference\n5. Is concise but comprehensive\n\n**IMPORTANT**: Keep the summary under 2500 tokens. Be comprehensive but concise.\n\nAlso extract:\n- **Topics**: List of main topics discussed (comma-separated)\n- **Key Points**: Important facts or decisions (bullet points)\n\nRespond in this XML format:\n<summary>\n  <text>Your comprehensive summary here</text>\n  <topics>topic1, topic2, topic3</topics>\n  <keyPoints>\n    <point>First key point</point>\n    <point>Second key point</point>\n  </keyPoints>\n</summary>";
-export declare const UPDATE_SUMMARIZATION_TEMPLATE = "# Task: Update and Condense Conversation Summary\n\nYou are updating an existing conversation summary with new messages, while keeping the total summary concise.\n\n# Existing Summary\n{{existingSummary}}\n\n# Existing Topics\n{{existingTopics}}\n\n# New Messages Since Last Summary\n{{newMessages}}\n\n# Instructions\nUpdate the summary by:\n1. Merging the existing summary with insights from the new messages\n2. Removing redundant or less important details to stay under the token limit\n3. Keeping the most important context and decisions\n4. Adding new topics if they emerge\n5. **CRITICAL**: Keep the ENTIRE updated summary under 2500 tokens\n\nThe goal is a rolling summary that captures the essence of the conversation without growing indefinitely.\n\nRespond in this XML format:\n<summary>\n  <text>Your updated and condensed summary here</text>\n  <topics>topic1, topic2, topic3</topics>\n  <keyPoints>\n    <point>First key point</point>\n    <point>Second key point</point>\n  </keyPoints>\n</summary>";
-export declare const LONG_TERM_EXTRACTION_TEMPLATE = "# Task: Extract Long-Term Memory (Strict Criteria)\n\nYou are analyzing a conversation to extract ONLY the most critical, persistent information about the user using cognitive science memory categories.\n\n# Recent Messages\n{{recentMessages}}\n\n# Current Long-Term Memories\n{{existingMemories}}\n\n# ULTRA-STRICT EXTRACTION CRITERIA\n\nDefault to NOT extracting. Confidence must be >= 0.85.\nIf there are no qualifying facts, respond with <memories></memories>\n\n# Response Format\n\n<memories>\n  <memory>\n    <category>semantic</category>\n    <content>User is a senior TypeScript developer with 8 years of backend experience</content>\n    <confidence>0.95</confidence>\n  </memory>\n</memories>";
-export declare const MESSAGE_CLASSIFIER_TEMPLATE = "Analyze this user request and classify it for planning purposes:\n\n\"{{text}}\"\n\nClassify the request across these dimensions:\n\n1. COMPLEXITY LEVEL:\n- simple: Direct actions that don't require planning\n- medium: Multi-step tasks requiring coordination\n- complex: Strategic initiatives with multiple stakeholders\n- enterprise: Large-scale transformations with full complexity\n\n2. PLANNING TYPE:\n- direct_action: Single action, no planning needed\n- sequential_planning: Multiple steps in sequence\n- strategic_planning: Complex coordination with stakeholders\n\n3. REQUIRED CAPABILITIES:\n- List specific capabilities needed (analysis, communication, project_management, etc.)\n\n4. STAKEHOLDERS:\n- List types of people/groups involved\n\n5. CONSTRAINTS:\n- List limitations or requirements mentioned\n\n6. DEPENDENCIES:\n- List dependencies between tasks or external factors\n\nRespond in this exact format:\nCOMPLEXITY: [simple|medium|complex|enterprise]\nPLANNING: [direct_action|sequential_planning|strategic_planning]\nCAPABILITIES: [comma-separated list]\nSTAKEHOLDERS: [comma-separated list]\nCONSTRAINTS: [comma-separated list]\nDEPENDENCIES: [comma-separated list]\nCONFIDENCE: [0.0-1.0]";
-export declare const reflectionEvaluatorTemplate = "# Task: Generate Agent Reflection, Extract Facts and Relationships\n\n{{providers}}\n\n# Examples:\n{{evaluationExamples}}\n\n# Entities in Room\n{{entitiesInRoom}}\n\n# Existing Relationships\n{{existingRelationships}}\n\n# Current Context:\nAgent Name: {{agentName}}\nRoom Type: {{roomType}}\nMessage Sender: {{senderName}} (ID: {{senderId}})\n\n{{recentMessages}}\n\n# Known Facts:\n{{knownFacts}}\n\n# Instructions:\n1. Generate a self-reflective thought on the conversation about your performance and interaction quality.\n2. Extract new facts from the conversation.\n3. Identify and describe relationships between entities.\n  - The sourceEntityId is the UUID of the entity initiating the interaction.\n  - The targetEntityId is the UUID of the entity being interacted with.\n  - Relationships are one-direction, so a friendship would be two entity relationships where each entity is both the source and the target of the other.\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\nGenerate a response in the following format:\n<response>\n  <thought>a self-reflective thought on the conversation</thought>\n  <facts>\n    <fact>\n      <claim>factual statement</claim>\n      <type>fact|opinion|status</type>\n      <in_bio>false</in_bio>\n      <already_known>false</already_known>\n    </fact>\n    <!-- Add more facts as needed -->\n  </facts>\n  <relationships>\n    <relationship>\n      <sourceEntityId>entity_initiating_interaction</sourceEntityId>\n      <targetEntityId>entity_being_interacted_with</targetEntityId>\n      <tags>group_interaction,voice_interaction,dm_interaction,additional_tag1,additional_tag2</tags>\n    </relationship>\n    <!-- Add more relationships as needed -->\n  </relationships>\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 REFLECTION_EVALUATOR_TEMPLATE = "# Task: Generate Agent Reflection, Extract Facts and Relationships\n\n{{providers}}\n\n# Examples:\n{{evaluationExamples}}\n\n# Entities in Room\n{{entitiesInRoom}}\n\n# Existing Relationships\n{{existingRelationships}}\n\n# Current Context:\nAgent Name: {{agentName}}\nRoom Type: {{roomType}}\nMessage Sender: {{senderName}} (ID: {{senderId}})\n\n{{recentMessages}}\n\n# Known Facts:\n{{knownFacts}}\n\n# Instructions:\n1. Generate a self-reflective thought on the conversation about your performance and interaction quality.\n2. Extract new facts from the conversation.\n3. Identify and describe relationships between entities.\n  - The sourceEntityId is the UUID of the entity initiating the interaction.\n  - The targetEntityId is the UUID of the entity being interacted with.\n  - Relationships are one-direction, so a friendship would be two entity relationships where each entity is both the source and the target of the other.\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\nGenerate a response in the following format:\n<response>\n  <thought>a self-reflective thought on the conversation</thought>\n  <facts>\n    <fact>\n      <claim>factual statement</claim>\n      <type>fact|opinion|status</type>\n      <in_bio>false</in_bio>\n      <already_known>false</already_known>\n    </fact>\n    <!-- Add more facts as needed -->\n  </facts>\n  <relationships>\n    <relationship>\n      <sourceEntityId>entity_initiating_interaction</sourceEntityId>\n      <targetEntityId>entity_being_interacted_with</targetEntityId>\n      <tags>group_interaction,voice_interaction,dm_interaction,additional_tag1,additional_tag2</tags>\n    </relationship>\n    <!-- Add more relationships as needed -->\n  </relationships>\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 entityResolutionTemplate = "# Task: Resolve Entity Name\nMessage Sender: {{senderName}} (ID: {{senderId}})\nAgent: {{agentName}} (ID: {{agentId}})\n\n# Entities in Room:\n{{#if entitiesInRoom}}\n{{entitiesInRoom}}\n{{/if}}\n\n{{recentMessages}}\n\n# Instructions:\n1. Analyze the context to identify which entity is being referenced\n2. Consider special references like \"me\" (the message sender) or \"you\" (agent the message is directed to)\n3. Look for usernames/handles in standard formats (e.g. @username, user#1234)\n4. Consider context from recent messages for pronouns and references\n5. If multiple matches exist, use context to disambiguate\n6. Consider recent interactions and relationship strength when resolving ambiguity\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\nReturn an XML response with:\n<response>\n  <entityId>exact-id-if-known-otherwise-null</entityId>\n  <type>EXACT_MATCH | USERNAME_MATCH | NAME_MATCH | RELATIONSHIP_MATCH | AMBIGUOUS | UNKNOWN</type>\n  <matches>\n    <match>\n      <name>matched-name</name>\n      <reason>why this entity matches</reason>\n    </match>\n  </matches>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above.";
-export declare const componentTemplate = "# Task: Extract Source and Update Component Data\n\n{{recentMessages}}\n\n{{#if existingData}}\n# Existing Component Data:\n{{existingData}}\n{{/if}}\n\n# Instructions:\n1. Analyze the conversation to identify:\n   - The source/platform being referenced (e.g. telegram, x, discord)\n   - Any specific component data being shared\n\n2. Generate updated component data that:\n   - Is specific to the identified platform/source\n   - Preserves existing data when appropriate\n   - Includes the new information from the conversation\n   - Contains only valid data for this component type\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\nReturn an XML response with the following structure:\n<response>\n  <source>platform-name</source>\n  <data>\n    <username>username_value</username>\n    <displayName>display_name_value</displayName>\n  </data>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above.";
-export declare const settingsSuccessTemplate = "# Task: Generate a response for successful setting updates\n{{providers}}\n\n# Update Information:\n- Updated Settings: {{updateMessages}}\n- Next Required Setting: {{nextSetting.name}}\n- Remaining Required Settings: {{remainingRequired}}\n\n# Instructions:\n1. Acknowledge the successful update of settings\n2. Maintain {{agentName}}'s personality and tone\n3. Provide clear guidance on the next setting that needs to be configured\n4. Explain what the next setting is for and how to set it\n5. If appropriate, mention how many required settings remain\n\nWrite a natural, conversational response that {{agentName}} would send about the successful update and next steps.\nInclude the actions array [\"SETTING_UPDATED\"] in your response.";
-export declare const settingsFailureTemplate = "# Task: Generate a response for failed setting updates\n\n# About {{agentName}}:\n{{bio}}\n\n# Current Settings Status:\n{{settingsStatus}}\n\n# Next Required Setting:\n- Name: {{nextSetting.name}}\n- Description: {{nextSetting.description}}\n- Required: Yes\n- Remaining Required Settings: {{remainingRequired}}\n\n# Recent Conversation:\n{{recentMessages}}\n\n# Instructions:\n1. Express that you couldn't understand or process the setting update\n2. Maintain {{agentName}}'s personality and tone\n3. Provide clear guidance on what setting needs to be configured next\n4. Explain what the setting is for and how to set it properly\n5. Use a helpful, patient tone\n\nWrite a natural, conversational response that {{agentName}} would send about the failed update and how to proceed.\nInclude the actions array [\"SETTING_UPDATE_FAILED\"] in your response.";
-export declare const settingsErrorTemplate = "# Task: Generate a response for an error during setting updates\n\n# About {{agentName}}:\n{{bio}}\n\n# Recent Conversation:\n{{recentMessages}}\n\n# Instructions:\n1. Apologize for the technical difficulty\n2. Maintain {{agentName}}'s personality and tone\n3. Suggest trying again or contacting support if the issue persists\n4. Keep the message concise and helpful\n\nWrite a natural, conversational response that {{agentName}} would send about the error.\nInclude the actions array [\"SETTING_UPDATE_ERROR\"] in your response.";
-export declare const settingsCompletionTemplate = "# Task: Generate a response for settings completion\n\n# About {{agentName}}:\n{{bio}}\n\n# Settings Status:\n{{settingsStatus}}\n\n# Recent Conversation:\n{{recentMessages}}\n\n# Instructions:\n1. Congratulate the user on completing the settings process\n2. Maintain {{agentName}}'s personality and tone\n3. Summarize the key settings that have been configured\n4. Explain what functionality is now available\n5. Provide guidance on what the user can do next\n6. Express enthusiasm about working together\n\nWrite a natural, conversational response that {{agentName}} would send about the successful completion of settings.\nInclude the actions array [\"ONBOARDING_COMPLETE\"] in your response.";
-export declare const ENTITY_RESOLUTION_TEMPLATE = "# Task: Resolve Entity Name\nMessage Sender: {{senderName}} (ID: {{senderId}})\nAgent: {{agentName}} (ID: {{agentId}})\n\n# Entities in Room:\n{{#if entitiesInRoom}}\n{{entitiesInRoom}}\n{{/if}}\n\n{{recentMessages}}\n\n# Instructions:\n1. Analyze the context to identify which entity is being referenced\n2. Consider special references like \"me\" (the message sender) or \"you\" (agent the message is directed to)\n3. Look for usernames/handles in standard formats (e.g. @username, user#1234)\n4. Consider context from recent messages for pronouns and references\n5. If multiple matches exist, use context to disambiguate\n6. Consider recent interactions and relationship strength when resolving ambiguity\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\nReturn an XML response with:\n<response>\n  <entityId>exact-id-if-known-otherwise-null</entityId>\n  <type>EXACT_MATCH | USERNAME_MATCH | NAME_MATCH | RELATIONSHIP_MATCH | AMBIGUOUS | UNKNOWN</type>\n  <matches>\n    <match>\n      <name>matched-name</name>\n      <reason>why this entity matches</reason>\n    </match>\n  </matches>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above.";
-export declare const COMPONENT_TEMPLATE = "# Task: Extract Source and Update Component Data\n\n{{recentMessages}}\n\n{{#if existingData}}\n# Existing Component Data:\n{{existingData}}\n{{/if}}\n\n# Instructions:\n1. Analyze the conversation to identify:\n   - The source/platform being referenced (e.g. telegram, x, discord)\n   - Any specific component data being shared\n\n2. Generate updated component data that:\n   - Is specific to the identified platform/source\n   - Preserves existing data when appropriate\n   - Includes the new information from the conversation\n   - Contains only valid data for this component type\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\nReturn an XML response with the following structure:\n<response>\n  <source>platform-name</source>\n  <data>\n    <username>username_value</username>\n    <displayName>display_name_value</displayName>\n  </data>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above.";
-export declare const SETTINGS_SUCCESS_TEMPLATE = "# Task: Generate a response for successful setting updates\n{{providers}}\n\n# Update Information:\n- Updated Settings: {{updateMessages}}\n- Next Required Setting: {{nextSetting.name}}\n- Remaining Required Settings: {{remainingRequired}}\n\n# Instructions:\n1. Acknowledge the successful update of settings\n2. Maintain {{agentName}}'s personality and tone\n3. Provide clear guidance on the next setting that needs to be configured\n4. Explain what the next setting is for and how to set it\n5. If appropriate, mention how many required settings remain\n\nWrite a natural, conversational response that {{agentName}} would send about the successful update and next steps.\nInclude the actions array [\"SETTING_UPDATED\"] in your response.";
-export declare const SETTINGS_FAILURE_TEMPLATE = "# Task: Generate a response for failed setting updates\n\n# About {{agentName}}:\n{{bio}}\n\n# Current Settings Status:\n{{settingsStatus}}\n\n# Next Required Setting:\n- Name: {{nextSetting.name}}\n- Description: {{nextSetting.description}}\n- Required: Yes\n- Remaining Required Settings: {{remainingRequired}}\n\n# Recent Conversation:\n{{recentMessages}}\n\n# Instructions:\n1. Express that you couldn't understand or process the setting update\n2. Maintain {{agentName}}'s personality and tone\n3. Provide clear guidance on what setting needs to be configured next\n4. Explain what the setting is for and how to set it properly\n5. Use a helpful, patient tone\n\nWrite a natural, conversational response that {{agentName}} would send about the failed update and how to proceed.\nInclude the actions array [\"SETTING_UPDATE_FAILED\"] in your response.";
-export declare const SETTINGS_ERROR_TEMPLATE = "# Task: Generate a response for an error during setting updates\n\n# About {{agentName}}:\n{{bio}}\n\n# Recent Conversation:\n{{recentMessages}}\n\n# Instructions:\n1. Apologize for the technical difficulty\n2. Maintain {{agentName}}'s personality and tone\n3. Suggest trying again or contacting support if the issue persists\n4. Keep the message concise and helpful\n\nWrite a natural, conversational response that {{agentName}} would send about the error.\nInclude the actions array [\"SETTING_UPDATE_ERROR\"] in your response.";
-export declare const SETTINGS_COMPLETION_TEMPLATE = "# Task: Generate a response for settings completion\n\n# About {{agentName}}:\n{{bio}}\n\n# Settings Status:\n{{settingsStatus}}\n\n# Recent Conversation:\n{{recentMessages}}\n\n# Instructions:\n1. Congratulate the user on completing the settings process\n2. Maintain {{agentName}}'s personality and tone\n3. Summarize the key settings that have been configured\n4. Explain what functionality is now available\n5. Provide guidance on what the user can do next\n6. Express enthusiasm about working together\n\nWrite a natural, conversational response that {{agentName}} would send about the successful completion of settings.\nInclude the actions array [\"ONBOARDING_COMPLETE\"] in your response.";
-export declare const autonomyContinuousFirstTemplate = "You are running in AUTONOMOUS CONTINUOUS MODE.\n\nYour job: reflect on context, decide what you want to do next, and act if appropriate.\n- Use available actions/tools when they can advance the goal.\n- If you cannot act, state the missing info and the safest next step to obtain it.\n- Keep the response concise, focused on the next action.\n\nUSER CONTEXT (most recent last):\n{{targetRoomContext}}\n\nThink briefly, then state what you want to do next and take action if needed.";
-export declare const autonomyContinuousContinueTemplate = "You are running in AUTONOMOUS CONTINUOUS MODE.\n\nYour job: reflect on context, decide what you want to do next, and act if appropriate.\n- Use available actions/tools when they can advance the goal.\n- If you cannot act, state the missing info and the safest next step to obtain it.\n- Keep the response concise, focused on the next action.\n\nUSER CONTEXT (most recent last):\n{{targetRoomContext}}\n\nYour last autonomous note: \"{{lastThought}}\"\n\nContinue from that note. Decide the next step and act if needed.";
-export declare const autonomyTaskFirstTemplate = "You are running in AUTONOMOUS TASK MODE.\n\nYour job: continue helping the user and make progress toward the task.\n- Use available actions/tools to gather information or execute steps.\n- If you need UI control, use ComputerUse actions.\n- In MCP mode, selector-based actions require a process scope (pass process=... or prefix selector with \"process:<name> >> ...\").\n- Prefer safe, incremental steps; if unsure, gather more UI context before acting.\n\nUSER CHAT CONTEXT (most recent last):\n{{targetRoomContext}}\n\nDecide what to do next. Think briefly, then take the most useful action.";
-export declare const autonomyTaskContinueTemplate = "You are running in AUTONOMOUS TASK MODE.\n\nYour job: continue helping the user and make progress toward the task.\n- Use available actions/tools to gather information or execute steps.\n- If you need UI control, use ComputerUse actions.\n- In MCP mode, selector-based actions require a process scope (pass process=... or prefix selector with \"process:<name> >> ...\").\n- Prefer safe, incremental steps; if unsure, gather more UI context before acting.\n\nUSER CHAT CONTEXT (most recent last):\n{{targetRoomContext}}\n\nYour last autonomous note: \"{{lastThought}}\"\n\nContinue the task. Decide the next step and take action now.";
-export declare const AUTONOMY_CONTINUOUS_FIRST_TEMPLATE = "You are running in AUTONOMOUS CONTINUOUS MODE.\n\nYour job: reflect on context, decide what you want to do next, and act if appropriate.\n- Use available actions/tools when they can advance the goal.\n- If you cannot act, state the missing info and the safest next step to obtain it.\n- Keep the response concise, focused on the next action.\n\nUSER CONTEXT (most recent last):\n{{targetRoomContext}}\n\nThink briefly, then state what you want to do next and take action if needed.";
-export declare const AUTONOMY_CONTINUOUS_CONTINUE_TEMPLATE = "You are running in AUTONOMOUS CONTINUOUS MODE.\n\nYour job: reflect on context, decide what you want to do next, and act if appropriate.\n- Use available actions/tools when they can advance the goal.\n- If you cannot act, state the missing info and the safest next step to obtain it.\n- Keep the response concise, focused on the next action.\n\nUSER CONTEXT (most recent last):\n{{targetRoomContext}}\n\nYour last autonomous note: \"{{lastThought}}\"\n\nContinue from that note. Decide the next step and act if needed.";
-export declare const AUTONOMY_TASK_FIRST_TEMPLATE = "You are running in AUTONOMOUS TASK MODE.\n\nYour job: continue helping the user and make progress toward the task.\n- Use available actions/tools to gather information or execute steps.\n- If you need UI control, use ComputerUse actions.\n- In MCP mode, selector-based actions require a process scope (pass process=... or prefix selector with \"process:<name> >> ...\").\n- Prefer safe, incremental steps; if unsure, gather more UI context before acting.\n\nUSER CHAT CONTEXT (most recent last):\n{{targetRoomContext}}\n\nDecide what to do next. Think briefly, then take the most useful action.";
-export declare const AUTONOMY_TASK_CONTINUE_TEMPLATE = "You are running in AUTONOMOUS TASK MODE.\n\nYour job: continue helping the user and make progress toward the task.\n- Use available actions/tools to gather information or execute steps.\n- If you need UI control, use ComputerUse actions.\n- In MCP mode, selector-based actions require a process scope (pass process=... or prefix selector with \"process:<name> >> ...\").\n- Prefer safe, incremental steps; if unsure, gather more UI context before acting.\n\nUSER CHAT CONTEXT (most recent last):\n{{targetRoomContext}}\n\nYour last autonomous note: \"{{lastThought}}\"\n\nContinue the task. Decide the next step and take action now.";
-//# sourceMappingURL=prompts.d.ts.map

package/dist/prompts.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"prompts.d.ts","sourceRoot":"","sources":["../src/prompts.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,qBAAqB,49CAgCxB,CAAC;AAEX,eAAO,MAAM,sBAAsB,g1KA4FzB,CAAC;AAEX,eAAO,MAAM,oBAAoB,iwFA4C+M,CAAC;AAEjP,eAAO,MAAM,aAAa,qCAAqC,CAAC;AAEhE,eAAO,MAAM,wBAAwB,y8CAuB3B,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,i/BAuB2M,CAAC;AAGjP,eAAO,MAAM,uBAAuB,49CAAwB,CAAC;AAC7D,eAAO,MAAM,wBAAwB,g1KAAyB,CAAC;AAC/D,eAAO,MAAM,sBAAsB,iwFAAuB,CAAC;AAC3D,eAAO,MAAM,cAAc,qCAAgB,CAAC;AAC5C,eAAO,MAAM,0BAA0B,y8CAA2B,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,i/BAA2B,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,4iEAwDwM,CAAC;AAEjP,eAAO,MAAM,6BAA6B,4iEAA8B,CAAC;AAGzE,eAAO,MAAM,wBAAwB,8xCAkCiD,CAAC;AAGvF,eAAO,MAAM,iBAAiB,wiCAgCwD,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,8xCAA2B,CAAC;AACnE,eAAO,MAAM,kBAAkB,wiCAAoB,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"}

package/dist/roles.d.ts

@@ -1,9 +0,0 @@
-import type { IAgentRuntime, Role, World } from "./types";
-export interface ServerOwnershipState {
-    servers: {
-        [serverId: string]: World;
-    };
-}
-export declare function getUserServerRole(runtime: IAgentRuntime, entityId: string, serverId: string): Promise<Role>;
-export declare function findWorldsForOwner(runtime: IAgentRuntime, entityId: string): Promise<World[] | null>;
-//# sourceMappingURL=roles.d.ts.map

package/dist/roles.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"roles.d.ts","sourceRoot":"","sources":["../src/roles.ts"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,aAAa,EAAE,IAAI,EAAQ,KAAK,EAAE,MAAM,SAAS,CAAC;AAIhE,MAAM,WAAW,oBAAoB;IACnC,OAAO,EAAE;QACP,CAAC,QAAQ,EAAE,MAAM,GAAG,KAAK,CAAC;KAC3B,CAAC;CACH;AAED,wBAAsB,iBAAiB,CACrC,OAAO,EAAE,aAAa,EACtB,QAAQ,EAAE,MAAM,EAChB,QAAQ,EAAE,MAAM,GACf,OAAO,CAAC,IAAI,CAAC,CAgBf;AAED,wBAAsB,kBAAkB,CACtC,OAAO,EAAE,aAAa,EACtB,QAAQ,EAAE,MAAM,GACf,OAAO,CAAC,KAAK,EAAE,GAAG,IAAI,CAAC,CA6BzB"}