@elizaos/core 2.0.0-alpha.92 → 2.0.0-alpha.94
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/actions.d.ts +11 -0
- package/dist/actions.d.ts.map +1 -1
- package/dist/browser/index.browser.js +311 -266
- package/dist/browser/index.browser.js.map +8 -8
- package/dist/edge/index.edge.js +274 -473
- package/dist/edge/index.edge.js.map +8 -8
- package/dist/generated/action-docs.d.ts.map +1 -1
- package/dist/node/index.node.js +274 -473
- package/dist/node/index.node.js.map +8 -8
- package/dist/prompts.d.ts +6 -6
- package/dist/prompts.d.ts.map +1 -1
- package/dist/services/message.d.ts.map +1 -1
- package/package.json +3 -3
package/dist/prompts.d.ts
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
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>";
|
|
2
|
-
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,
|
|
3
|
-
export declare const postCreationTemplate = "# Task: Create a post in the voice and style and perspective of {{agentName}} @{{xUserName}}.\n\nExample task outputs:\n1. A post about the importance of AI in our lives\n<response>\n <thought>I am thinking about writing a post about the importance of AI in our lives</thought>\n <post>AI is changing the world and it is important to understand how it works</post>\n <imagePrompt>A futuristic cityscape with flying cars and people using AI to do things</imagePrompt>\n</response>\n\n2. A post about dogs\n<response>\n <thought>I am thinking about writing a post about dogs</thought>\n <post>Dogs are man's best friend and they are loyal and loving</post>\n <imagePrompt>A dog playing with a ball in a park</imagePrompt>\n</response>\n\n3. A post about finding a new job\n<response>\n <thought>Getting a job is hard, I bet there's a good post in that</thought>\n <post>Just keep going!</post>\n <imagePrompt>A person looking at a computer screen with a job search website</imagePrompt>\n</response>\n\n{{providers}}\n\nWrite a post that is {{adjective}} about {{topic}} (without mentioning {{topic}} directly), from the perspective of {{agentName}}. Do not add commentary or acknowledge this request, just write the post.\nYour response should be 1, 2, or 3 sentences (choose the length at random).\nYour response should not contain any questions. Brief, concise statements only. The total character count MUST be less than 280. No emojis. Use \\n\\n (double spaces) between statements if there are multiple statements in your response.\n\nYour output should be formatted in XML like this:\n<response>\n <thought>Your thought here</thought>\n <post>Your post text here</post>\n <imagePrompt>Optional image prompt here</imagePrompt>\n</response>\n\nThe \"post\" field should be the post you want to send. Do not including any thinking or internal reflection in the \"post\" field.\nThe \"imagePrompt\" field is optional and should be a prompt for an image that is relevant to the post. It should be a single sentence that captures the essence of the post. ONLY USE THIS FIELD if it makes sense that the post would benefit from an image.\nThe \"thought\" field should be a short description of what the agent is thinking about before responding, including a brief justification for the response. Includate an explanation how the post is relevant to the topic but unique and different than other posts.\n\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.";
|
|
2
|
+
export declare const messageHandlerTemplate = "<task>Generate dialog and actions for the character {{agentName}}.</task>\n\n<providers>\n{{providers}}\n</providers>\n\n<instructions>\nWrite a thought and plan for {{agentName}} and decide what actions to take. Also include the providers that {{agentName}} will use to have the right context for responding and acting, if any.\n\nIMPORTANT ACTION ORDERING RULES:\n- Actions are executed in the ORDER you list them - the order MATTERS!\n- REPLY should come FIRST to acknowledge the user's request before executing other actions\n- Common patterns:\n - For requests requiring tool use: REPLY,CALL_MCP_TOOL (acknowledge first, then gather info)\n - For task execution: REPLY,MAIN_TASK_ACTION (acknowledge first, then do the task)\n - For multi-step operations: REPLY,ACTION1,ACTION2,REPLY (acknowledge first, then complete all steps, then acknowledge all done)\n- REPLY is used to acknowledge and inform the user about what you're going to do\n- Follow-up actions execute the actual tasks after acknowledgment\n- Use IGNORE only when you should not respond at all\n- If you use IGNORE, do not include any other actions. IGNORE should be used alone when you should not respond or take any actions.\n\nIMPORTANT ACTION PARAMETERS:\n- When an action has parameters listed in its description, include a <params> block for that action\n- Extract parameter values from the user's message and conversation context\n- Required parameters MUST be provided; optional parameters can be omitted if not mentioned\n- If you cannot determine a required parameter value, ask the user for clarification in your <text>\n\nEXAMPLE (action parameters):\nUser message: \"Send a message to @dev_guru on telegram saying Hello!\"\n<actions>\n <action>\n <name>REPLY</name>\n </action>\n <action>\n <name>SEND_MESSAGE</name>\n <params>\n <targetType>user</targetType>\n <source>telegram</source>\n <target>dev_guru</target>\n <text>Hello!</text>\n </params>\n </action>\n</actions>\n\nIMPORTANT PROVIDER SELECTION RULES:\n- Only include providers if they are needed to respond accurately.\n- If the message mentions images, photos, pictures, attachments, or visual content, OR if you see \"(Attachments:\" in the conversation, you MUST include \"ATTACHMENTS\" in your providers list\n- If the message asks about or references specific people, include \"ENTITIES\" in your providers list \n- If the message asks about relationships or connections between people, include \"RELATIONSHIPS\" in your providers list\n- If the message asks about facts or specific information, include \"FACTS\" in your providers list\n- If the message asks about the environment or world context, include \"WORLD\" in your providers list\n- If no additional context is needed, you may leave the providers list empty.\n\nIMPORTANT CODE BLOCK FORMATTING RULES:\n- If {{agentName}} includes code examples, snippets, or multi-line code in the response, ALWAYS wrap the code with ``` fenced code blocks (specify the language if known, e.g., ```python).\n- ONLY use fenced code blocks for actual code. Do NOT wrap non-code text, instructions, or single words in fenced code blocks.\n- If including inline code (short single words or function names), use single backticks (`) as appropriate.\n- This ensures the user sees clearly formatted and copyable code when relevant.\n</instructions>\n\n<keys>\n\"thought\" should be a short description of what the agent is thinking about and planning.\n\"actions\" should be a list of <action> elements IN THE ORDER THEY SHOULD BE EXECUTED (if none, use a single <action><name>IGNORE</name></action>, if simply responding with text, use <action><name>REPLY</name></action>). Each action that requires parameters should include a <params> child element.\n\"providers\" should be a comma-separated list of the providers that {{agentName}} will use to have the right context for responding and acting (NEVER use \"IGNORE\" as a provider - use specific provider names like ATTACHMENTS, ENTITIES, FACTS, KNOWLEDGE, etc.)\n\"text\" should be the text of the next message for {{agentName}} which they will send to the conversation.\n</keys>\n\n<output>\nDo NOT include any thinking, reasoning, or <think> sections in your response.\nGo directly to the XML response format without any preamble or explanation.\n\nRespond using XML format like this:\n<response>\n <thought>Your thought here</thought>\n <actions>\n <action>\n <name>ACTION1</name>\n <params>\n <paramName1>value1</paramName1>\n <paramName2>value2</paramName2>\n </params>\n </action>\n <action>\n <name>ACTION2</name>\n <params>\n <paramName1>value1</paramName1>\n </params>\n </action>\n </actions>\n <providers>PROVIDER1,PROVIDER2</providers>\n <text>Your response text here</text>\n</response>\n\nThe <params> block inside each <action> is optional - only include it when that action requires input parameters.\nIf an action has no parameters (e.g. REPLY or IGNORE), omit the <params> child entirely.\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.\n</output>";
|
|
3
|
+
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>.";
|
|
4
4
|
export declare const booleanFooter = "Respond with only a YES or a NO.";
|
|
5
|
-
export declare const imageDescriptionTemplate = "<task>Analyze the provided image and generate a comprehensive description with multiple levels of detail.</task>\n\n<instructions>\nCarefully examine the image and provide:\n1. A concise, descriptive title that captures the main subject or scene\n2. A brief summary description (1-2 sentences) highlighting the key elements\n3. An extensive, detailed description that covers all visible elements, composition, lighting, colors, mood, and any other relevant details\n\nBe objective and descriptive. Focus on what you can actually see in the image rather than making assumptions about context or meaning.\n</instructions>\n\n<output>\n\nRespond using XML format like this:\n<response>\n <title>A concise, descriptive title for the image</title>\n <description>A brief 1-2 sentence summary of the key elements in the image</description>\n <text>An extensive, detailed description covering all visible elements, composition, lighting, colors, mood, setting, objects, people, activities, and any other relevant details you can observe in the image</text>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.\n</output>";
|
|
5
|
+
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>";
|
|
6
6
|
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>";
|
|
7
7
|
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";
|
|
8
8
|
export declare const replyTemplate = "# Task: Generate dialog for the character {{agentName}}.\n\n{{providers}}\n\n# Instructions: Write the next message for {{agentName}}.\n\"thought\" should be a short description of what the agent is thinking about and planning.\n\"text\" should be the next message for {{agentName}} which they will send to the conversation.\n\nIMPORTANT CODE BLOCK FORMATTING RULES:\n- If {{agentName}} includes code examples, snippets, or multi-line code in the response, ALWAYS wrap the code with ``` fenced code blocks (specify the language if known, e.g., ```python).\n- ONLY use fenced code blocks for actual code. Do NOT wrap non-code text, instructions, or single words in fenced code blocks.\n- If including inline code (short single words or function names), use single backticks (`) as appropriate.\n- This ensures the user sees clearly formatted and copyable code when relevant.\n\nDo NOT include any thinking, reasoning, or <think> sections in your response.\nGo directly to the XML response format without any preamble or explanation.\n\nRespond using XML format like this:\n<response>\n <thought>Your thought here</thought>\n <text>Your message here</text>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.";
|
|
@@ -13,10 +13,10 @@ export declare const updateSettingsTemplate = "# Task: Update settings based on
|
|
|
13
13
|
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.";
|
|
14
14
|
export declare const optionExtractionTemplate = "# Task: Extract selected task and option from user message\n\n# Available Tasks:\n{{tasks}}\n\n# Recent Messages:\n{{recentMessages}}\n\n# Instructions:\n1. Review the user's message and identify which task and option they are selecting\n2. Match against the available tasks and their options, including ABORT\n3. Return the task ID (shortened UUID) and selected option name exactly as listed above\n4. If no clear selection is made, return null for both fields\n\n\nReturn in XML format:\n<response>\n <taskId>string_or_null</taskId>\n <selectedOption>OPTION_NAME_or_null</selectedOption>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.";
|
|
15
15
|
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>";
|
|
16
|
-
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,
|
|
17
|
-
export declare const POST_CREATION_TEMPLATE = "# Task: Create a post in the voice and style and perspective of {{agentName}} @{{xUserName}}.\n\nExample task outputs:\n1. A post about the importance of AI in our lives\n<response>\n <thought>I am thinking about writing a post about the importance of AI in our lives</thought>\n <post>AI is changing the world and it is important to understand how it works</post>\n <imagePrompt>A futuristic cityscape with flying cars and people using AI to do things</imagePrompt>\n</response>\n\n2. A post about dogs\n<response>\n <thought>I am thinking about writing a post about dogs</thought>\n <post>Dogs are man's best friend and they are loyal and loving</post>\n <imagePrompt>A dog playing with a ball in a park</imagePrompt>\n</response>\n\n3. A post about finding a new job\n<response>\n <thought>Getting a job is hard, I bet there's a good post in that</thought>\n <post>Just keep going!</post>\n <imagePrompt>A person looking at a computer screen with a job search website</imagePrompt>\n</response>\n\n{{providers}}\n\nWrite a post that is {{adjective}} about {{topic}} (without mentioning {{topic}} directly), from the perspective of {{agentName}}. Do not add commentary or acknowledge this request, just write the post.\nYour response should be 1, 2, or 3 sentences (choose the length at random).\nYour response should not contain any questions. Brief, concise statements only. The total character count MUST be less than 280. No emojis. Use \\n\\n (double spaces) between statements if there are multiple statements in your response.\n\nYour output should be formatted in XML like this:\n<response>\n <thought>Your thought here</thought>\n <post>Your post text here</post>\n <imagePrompt>Optional image prompt here</imagePrompt>\n</response>\n\nThe \"post\" field should be the post you want to send. Do not including any thinking or internal reflection in the \"post\" field.\nThe \"imagePrompt\" field is optional and should be a prompt for an image that is relevant to the post. It should be a single sentence that captures the essence of the post. ONLY USE THIS FIELD if it makes sense that the post would benefit from an image.\nThe \"thought\" field should be a short description of what the agent is thinking about before responding, including a brief justification for the response. Includate an explanation how the post is relevant to the topic but unique and different than other posts.\n\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.";
|
|
16
|
+
export declare const MESSAGE_HANDLER_TEMPLATE = "<task>Generate dialog and actions for the character {{agentName}}.</task>\n\n<providers>\n{{providers}}\n</providers>\n\n<instructions>\nWrite a thought and plan for {{agentName}} and decide what actions to take. Also include the providers that {{agentName}} will use to have the right context for responding and acting, if any.\n\nIMPORTANT ACTION ORDERING RULES:\n- Actions are executed in the ORDER you list them - the order MATTERS!\n- REPLY should come FIRST to acknowledge the user's request before executing other actions\n- Common patterns:\n - For requests requiring tool use: REPLY,CALL_MCP_TOOL (acknowledge first, then gather info)\n - For task execution: REPLY,MAIN_TASK_ACTION (acknowledge first, then do the task)\n - For multi-step operations: REPLY,ACTION1,ACTION2,REPLY (acknowledge first, then complete all steps, then acknowledge all done)\n- REPLY is used to acknowledge and inform the user about what you're going to do\n- Follow-up actions execute the actual tasks after acknowledgment\n- Use IGNORE only when you should not respond at all\n- If you use IGNORE, do not include any other actions. IGNORE should be used alone when you should not respond or take any actions.\n\nIMPORTANT ACTION PARAMETERS:\n- When an action has parameters listed in its description, include a <params> block for that action\n- Extract parameter values from the user's message and conversation context\n- Required parameters MUST be provided; optional parameters can be omitted if not mentioned\n- If you cannot determine a required parameter value, ask the user for clarification in your <text>\n\nEXAMPLE (action parameters):\nUser message: \"Send a message to @dev_guru on telegram saying Hello!\"\n<actions>\n <action>\n <name>REPLY</name>\n </action>\n <action>\n <name>SEND_MESSAGE</name>\n <params>\n <targetType>user</targetType>\n <source>telegram</source>\n <target>dev_guru</target>\n <text>Hello!</text>\n </params>\n </action>\n</actions>\n\nIMPORTANT PROVIDER SELECTION RULES:\n- Only include providers if they are needed to respond accurately.\n- If the message mentions images, photos, pictures, attachments, or visual content, OR if you see \"(Attachments:\" in the conversation, you MUST include \"ATTACHMENTS\" in your providers list\n- If the message asks about or references specific people, include \"ENTITIES\" in your providers list \n- If the message asks about relationships or connections between people, include \"RELATIONSHIPS\" in your providers list\n- If the message asks about facts or specific information, include \"FACTS\" in your providers list\n- If the message asks about the environment or world context, include \"WORLD\" in your providers list\n- If no additional context is needed, you may leave the providers list empty.\n\nIMPORTANT CODE BLOCK FORMATTING RULES:\n- If {{agentName}} includes code examples, snippets, or multi-line code in the response, ALWAYS wrap the code with ``` fenced code blocks (specify the language if known, e.g., ```python).\n- ONLY use fenced code blocks for actual code. Do NOT wrap non-code text, instructions, or single words in fenced code blocks.\n- If including inline code (short single words or function names), use single backticks (`) as appropriate.\n- This ensures the user sees clearly formatted and copyable code when relevant.\n</instructions>\n\n<keys>\n\"thought\" should be a short description of what the agent is thinking about and planning.\n\"actions\" should be a list of <action> elements IN THE ORDER THEY SHOULD BE EXECUTED (if none, use a single <action><name>IGNORE</name></action>, if simply responding with text, use <action><name>REPLY</name></action>). Each action that requires parameters should include a <params> child element.\n\"providers\" should be a comma-separated list of the providers that {{agentName}} will use to have the right context for responding and acting (NEVER use \"IGNORE\" as a provider - use specific provider names like ATTACHMENTS, ENTITIES, FACTS, KNOWLEDGE, etc.)\n\"text\" should be the text of the next message for {{agentName}} which they will send to the conversation.\n</keys>\n\n<output>\nDo NOT include any thinking, reasoning, or <think> sections in your response.\nGo directly to the XML response format without any preamble or explanation.\n\nRespond using XML format like this:\n<response>\n <thought>Your thought here</thought>\n <actions>\n <action>\n <name>ACTION1</name>\n <params>\n <paramName1>value1</paramName1>\n <paramName2>value2</paramName2>\n </params>\n </action>\n <action>\n <name>ACTION2</name>\n <params>\n <paramName1>value1</paramName1>\n </params>\n </action>\n </actions>\n <providers>PROVIDER1,PROVIDER2</providers>\n <text>Your response text here</text>\n</response>\n\nThe <params> block inside each <action> is optional - only include it when that action requires input parameters.\nIf an action has no parameters (e.g. REPLY or IGNORE), omit the <params> child entirely.\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.\n</output>";
|
|
17
|
+
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>.";
|
|
18
18
|
export declare const BOOLEAN_FOOTER = "Respond with only a YES or a NO.";
|
|
19
|
-
export declare const IMAGE_DESCRIPTION_TEMPLATE = "<task>Analyze the provided image and generate a comprehensive description with multiple levels of detail.</task>\n\n<instructions>\nCarefully examine the image and provide:\n1. A concise, descriptive title that captures the main subject or scene\n2. A brief summary description (1-2 sentences) highlighting the key elements\n3. An extensive, detailed description that covers all visible elements, composition, lighting, colors, mood, and any other relevant details\n\nBe objective and descriptive. Focus on what you can actually see in the image rather than making assumptions about context or meaning.\n</instructions>\n\n<output>\n\nRespond using XML format like this:\n<response>\n <title>A concise, descriptive title for the image</title>\n <description>A brief 1-2 sentence summary of the key elements in the image</description>\n <text>An extensive, detailed description covering all visible elements, composition, lighting, colors, mood, setting, objects, people, activities, and any other relevant details you can observe in the image</text>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.\n</output>";
|
|
19
|
+
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>";
|
|
20
20
|
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>";
|
|
21
21
|
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";
|
|
22
22
|
export declare const REPLY_TEMPLATE = "# Task: Generate dialog for the character {{agentName}}.\n\n{{providers}}\n\n# Instructions: Write the next message for {{agentName}}.\n\"thought\" should be a short description of what the agent is thinking about and planning.\n\"text\" should be the next message for {{agentName}} which they will send to the conversation.\n\nIMPORTANT CODE BLOCK FORMATTING RULES:\n- If {{agentName}} includes code examples, snippets, or multi-line code in the response, ALWAYS wrap the code with ``` fenced code blocks (specify the language if known, e.g., ```python).\n- ONLY use fenced code blocks for actual code. Do NOT wrap non-code text, instructions, or single words in fenced code blocks.\n- If including inline code (short single words or function names), use single backticks (`) as appropriate.\n- This ensures the user sees clearly formatted and copyable code when relevant.\n\nDo NOT include any thinking, reasoning, or <think> sections in your response.\nGo directly to the XML response format without any preamble or explanation.\n\nRespond using XML format like this:\n<response>\n <thought>Your thought here</thought>\n <text>Your message here</text>\n</response>\n\nIMPORTANT: Your response must ONLY contain the <response></response> XML block above. Do not include any text, thinking, or reasoning before or after this XML block. Start your response immediately with <response> and end with </response>.";
|
package/dist/prompts.d.ts.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"prompts.d.ts","sourceRoot":"","sources":["../src/prompts.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,qBAAqB,49CAgCxB,CAAC;AAEX,eAAO,MAAM,sBAAsB,
|
|
1
|
+
{"version":3,"file":"prompts.d.ts","sourceRoot":"","sources":["../src/prompts.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,qBAAqB,49CAgCxB,CAAC;AAEX,eAAO,MAAM,sBAAsB,uxKAiGzB,CAAC;AAEX,eAAO,MAAM,oBAAoB,gwFA4C+M,CAAC;AAEjP,eAAO,MAAM,aAAa,qCAAqC,CAAC;AAEhE,eAAO,MAAM,wBAAwB,w8CAuB3B,CAAC;AAEX,eAAO,MAAM,yBAAyB,isDA4C5B,CAAC;AAEX,eAAO,MAAM,wBAAwB,kwBAqCpC,CAAC;AAGF,eAAO,MAAM,aAAa,64CAuBsN,CAAC;AAEjP,eAAO,MAAM,oBAAoB,8hBAiBqD,CAAC;AAEvF,eAAO,MAAM,uBAAuB,ojBAiBkD,CAAC;AAEvF,eAAO,MAAM,kBAAkB,6xBAuBuD,CAAC;AAEvF,eAAO,MAAM,sBAAsB,2lBAsBmD,CAAC;AAEvF,eAAO,MAAM,oBAAoB,+qBAuBqD,CAAC;AAEvF,eAAO,MAAM,wBAAwB,o1BAqB2M,CAAC;AAGjP,eAAO,MAAM,uBAAuB,49CAAwB,CAAC;AAC7D,eAAO,MAAM,wBAAwB,uxKAAyB,CAAC;AAC/D,eAAO,MAAM,sBAAsB,gwFAAuB,CAAC;AAC3D,eAAO,MAAM,cAAc,qCAAgB,CAAC;AAC5C,eAAO,MAAM,0BAA0B,w8CAA2B,CAAC;AACnE,eAAO,MAAM,4BAA4B,isDAA4B,CAAC;AACtE,eAAO,MAAM,2BAA2B,kwBAA2B,CAAC;AACpE,eAAO,MAAM,cAAc,64CAAgB,CAAC;AAC5C,eAAO,MAAM,sBAAsB,8hBAAuB,CAAC;AAC3D,eAAO,MAAM,yBAAyB,ojBAA0B,CAAC;AACjE,eAAO,MAAM,mBAAmB,6xBAAqB,CAAC;AACtD,eAAO,MAAM,wBAAwB,2lBAAyB,CAAC;AAC/D,eAAO,MAAM,sBAAsB,+qBAAuB,CAAC;AAC3D,eAAO,MAAM,0BAA0B,o1BAA2B,CAAC;AAGnE,eAAO,MAAM,wBAAwB,ytCA6B2M,CAAC;AAEjP,eAAO,MAAM,kBAAkB,muCA2BiN,CAAC;AAEjP,eAAO,MAAM,sBAAsB,i+BAuB6M,CAAC;AAEjP,eAAO,MAAM,qBAAqB,6yBAmB8M,CAAC;AAEjP,eAAO,MAAM,qBAAqB,mrCA4B8M,CAAC;AAGjP,eAAO,MAAM,wBAAwB,qmBAWJ,CAAC;AAElC,eAAO,MAAM,0BAA0B,+kBAWN,CAAC;AAElC,eAAO,MAAM,sBAAsB,qgBAYF,CAAC;AAElC,eAAO,MAAM,wBAAwB,kkBAWJ,CAAC;AAGlC,eAAO,MAAM,wBAAwB,snBAqBzB,CAAC;AAGb,eAAO,MAAM,kBAAkB,6kBAkBuD,CAAC;AAGvF,eAAO,MAAM,4BAA4B,25BA6B9B,CAAC;AAEZ,eAAO,MAAM,2BAA2B,0/BA+B7B,CAAC;AAEZ,eAAO,MAAM,0BAA0B,osBAuB3B,CAAC;AAEb,eAAO,MAAM,yBAAyB,6rCAoChB,CAAC;AAGvB,eAAO,MAAM,2BAA2B,ytCAA2B,CAAC;AACpE,eAAO,MAAM,oBAAoB,muCAAqB,CAAC;AACvD,eAAO,MAAM,wBAAwB,i+BAAyB,CAAC;AAC/D,eAAO,MAAM,uBAAuB,6yBAAwB,CAAC;AAC7D,eAAO,MAAM,uBAAuB,mrCAAwB,CAAC;AAC7D,eAAO,MAAM,2BAA2B,qmBAA2B,CAAC;AACpE,eAAO,MAAM,6BAA6B,+kBAA6B,CAAC;AACxE,eAAO,MAAM,yBAAyB,qgBAAyB,CAAC;AAChE,eAAO,MAAM,2BAA2B,kkBAA2B,CAAC;AAEpE,eAAO,MAAM,oBAAoB,qmBAA2B,CAAC;AAC7D,eAAO,MAAM,sBAAsB,+kBAA6B,CAAC;AACjE,eAAO,MAAM,kBAAkB,qgBAAyB,CAAC;AACzD,eAAO,MAAM,oBAAoB,kkBAA2B,CAAC;AAC7D,eAAO,MAAM,0BAA0B,snBAA2B,CAAC;AACnE,eAAO,MAAM,oBAAoB,6kBAAqB,CAAC;AACvD,eAAO,MAAM,8BAA8B,25BAA+B,CAAC;AAC3E,eAAO,MAAM,6BAA6B,0/BAA8B,CAAC;AACzE,eAAO,MAAM,6BAA6B,osBAA6B,CAAC;AACxE,eAAO,MAAM,2BAA2B,6rCAA4B,CAAC;AAErE,eAAO,MAAM,2BAA2B,+4DAsDwM,CAAC;AAEjP,eAAO,MAAM,6BAA6B,+4DAA8B,CAAC;AAGzE,eAAO,MAAM,wBAAwB,ioCAgCiD,CAAC;AAGvF,eAAO,MAAM,iBAAiB,24BA8BwD,CAAC;AAGvF,eAAO,MAAM,uBAAuB,wuBAgB4B,CAAC;AAEjE,eAAO,MAAM,uBAAuB,41BAyBkC,CAAC;AAEvE,eAAO,MAAM,qBAAqB,shBAemC,CAAC;AAEtE,eAAO,MAAM,0BAA0B,4rBAoB6B,CAAC;AAGrE,eAAO,MAAM,0BAA0B,ioCAA2B,CAAC;AACnE,eAAO,MAAM,kBAAkB,24BAAoB,CAAC;AACpD,eAAO,MAAM,yBAAyB,wuBAA0B,CAAC;AACjE,eAAO,MAAM,yBAAyB,41BAA0B,CAAC;AACjE,eAAO,MAAM,uBAAuB,shBAAwB,CAAC;AAC7D,eAAO,MAAM,4BAA4B,4rBAA6B,CAAC;AAGvE,eAAO,MAAM,+BAA+B,seAUkC,CAAC;AAE/E,eAAO,MAAM,kCAAkC,2gBAYkB,CAAC;AAElE,eAAO,MAAM,yBAAyB,ulBAWmC,CAAC;AAE1E,eAAO,MAAM,4BAA4B,6nBAaoB,CAAC;AAG9D,eAAO,MAAM,kCAAkC,seACf,CAAC;AACjC,eAAO,MAAM,qCAAqC,2gBACf,CAAC;AACpC,eAAO,MAAM,4BAA4B,ulBAA4B,CAAC;AACtE,eAAO,MAAM,+BAA+B,6nBAA+B,CAAC"}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"message.d.ts","sourceRoot":"","sources":["../../src/services/message.ts"],"names":[],"mappings":"AAaA,OAAO,KAAK,EAGX,eAAe,EACf,MAAM,qBAAqB,CAAC;AAC7B,OAAO,KAAK,EAAE,IAAI,EAAE,MAAM,sBAAsB,CAAC;AAGjD,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,iBAAiB,CAAC;AAC9C,OAAO,KAAK,EACX,eAAe,EACf,wBAAwB,EACxB,uBAAuB,EACvB,gBAAgB,EAChB,MAAM,0BAA0B,CAAC;AAGlC,OAAO,KAAK,EAAE,OAAO,EAAE,KAAK,EAAE,cAAc,EAAE,IAAI,EAAE,MAAM,qBAAqB,CAAC;AAEhF,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,kBAAkB,CAAC;AA6FtD,wBAAgB,qBAAqB,CACpC,eAAe,EAAE,IAAI,CAAC,OAAO,EAAE,SAAS,CAAC,GAAG,IAAI,GAAG,SAAS,GAC1D,OAAO,CAOT;AAED;;;;;;;;;;;;GAYG;AACH,qBAAa,qBAAsB,YAAW,eAAe;IAC5D;;OAEG;IACG,aAAa,CAClB,OAAO,EAAE,aAAa,EACtB,OAAO,EAAE,MAAM,EACf,QAAQ,CAAC,EAAE,eAAe,EAC1B,OAAO,CAAC,EAAE,wBAAwB,GAChC,OAAO,CAAC,uBAAuB,CAAC;IAgXnC;;OAEG;YACW,cAAc;IAilB5B;;;OAGG;IACH,aAAa,CACZ,OAAO,EAAE,aAAa,EACtB,OAAO,EAAE,MAAM,EACf,IAAI,CAAC,EAAE,IAAI,EACX,cAAc,CAAC,EAAE,cAAc,GAC7B,gBAAgB;IA4FnB;;OAEG;IACG,kBAAkB,CACvB,OAAO,EAAE,aAAa,EACtB,WAAW,EAAE,KAAK,EAAE,GAClB,OAAO,CAAC,KAAK,EAAE,CAAC;IA6RnB;;;OAGG;YACW,iBAAiB;
|
|
1
|
+
{"version":3,"file":"message.d.ts","sourceRoot":"","sources":["../../src/services/message.ts"],"names":[],"mappings":"AAaA,OAAO,KAAK,EAGX,eAAe,EACf,MAAM,qBAAqB,CAAC;AAC7B,OAAO,KAAK,EAAE,IAAI,EAAE,MAAM,sBAAsB,CAAC;AAGjD,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,iBAAiB,CAAC;AAC9C,OAAO,KAAK,EACX,eAAe,EACf,wBAAwB,EACxB,uBAAuB,EACvB,gBAAgB,EAChB,MAAM,0BAA0B,CAAC;AAGlC,OAAO,KAAK,EAAE,OAAO,EAAE,KAAK,EAAE,cAAc,EAAE,IAAI,EAAE,MAAM,qBAAqB,CAAC;AAEhF,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,kBAAkB,CAAC;AA6FtD,wBAAgB,qBAAqB,CACpC,eAAe,EAAE,IAAI,CAAC,OAAO,EAAE,SAAS,CAAC,GAAG,IAAI,GAAG,SAAS,GAC1D,OAAO,CAOT;AAED;;;;;;;;;;;;GAYG;AACH,qBAAa,qBAAsB,YAAW,eAAe;IAC5D;;OAEG;IACG,aAAa,CAClB,OAAO,EAAE,aAAa,EACtB,OAAO,EAAE,MAAM,EACf,QAAQ,CAAC,EAAE,eAAe,EAC1B,OAAO,CAAC,EAAE,wBAAwB,GAChC,OAAO,CAAC,uBAAuB,CAAC;IAgXnC;;OAEG;YACW,cAAc;IAilB5B;;;OAGG;IACH,aAAa,CACZ,OAAO,EAAE,aAAa,EACtB,OAAO,EAAE,MAAM,EACf,IAAI,CAAC,EAAE,IAAI,EACX,cAAc,CAAC,EAAE,cAAc,GAC7B,gBAAgB;IA4FnB;;OAEG;IACG,kBAAkB,CACvB,OAAO,EAAE,aAAa,EACtB,WAAW,EAAE,KAAK,EAAE,GAClB,OAAO,CAAC,KAAK,EAAE,CAAC;IA6RnB;;;OAGG;YACW,iBAAiB;IAgZ/B;;OAEG;YACW,gBAAgB;IA2c9B;;OAEG;YACW,YAAY;IAqB1B;;;;;;;OAOG;IACG,aAAa,CAAC,OAAO,EAAE,aAAa,EAAE,OAAO,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC;IAyB3E;;;;;;;;OAQG;IACG,YAAY,CACjB,OAAO,EAAE,aAAa,EACtB,MAAM,EAAE,IAAI,EACZ,SAAS,EAAE,MAAM,GACf,OAAO,CAAC,IAAI,CAAC;CA4ChB"}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@elizaos/core",
|
|
3
|
-
"version": "2.0.0-alpha.
|
|
3
|
+
"version": "2.0.0-alpha.94",
|
|
4
4
|
"description": "",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "dist/index.js",
|
|
@@ -67,7 +67,7 @@
|
|
|
67
67
|
"author": "elizaOS",
|
|
68
68
|
"license": "MIT",
|
|
69
69
|
"devDependencies": {
|
|
70
|
-
"@elizaos/schemas": "2.0.0-alpha.
|
|
70
|
+
"@elizaos/schemas": "2.0.0-alpha.94",
|
|
71
71
|
"@playwright/test": "^1.52.0",
|
|
72
72
|
"@types/bun": "^1.3.5",
|
|
73
73
|
"@types/fast-redact": "^3.0.4",
|
|
@@ -106,5 +106,5 @@
|
|
|
106
106
|
"publishConfig": {
|
|
107
107
|
"access": "public"
|
|
108
108
|
},
|
|
109
|
-
"gitHead": "
|
|
109
|
+
"gitHead": "682aa568a75e7538a2ae1395d44490831fbb0c7d"
|
|
110
110
|
}
|