@elizaos/prompts 2.0.0-alpha.113 → 2.0.0-alpha.115

package/dist/python/prompts.py

@@ -10,6 +10,36 @@ These prompts use Handlebars-style template syntax:
 
 from __future__ import annotations
 
+ADD_CONTACT_TEMPLATE = """task: Extract contact information to add to the rolodex.
+
+context:
+{{providers}}
+
+recent_messages:
+{{recentMessages}}
+
+current_message:
+{{message}}
+
+instructions[5]:
+- identify the contact name being added
+- include entityId only if it is explicitly known from context
+- return categories as a comma-separated list
+- include notes, timezone, and language only when clearly present
+- include a short reason for why this contact should be saved
+
+output:
+TOON only. Return exactly one TOON document. No prose before or after it. No <think>.
+
+Example:
+contactName: Jane Doe
+entityId:
+categories: vip,colleague
+notes: Met at the design summit
+timezone: America/New_York
+language: English
+reason: Important collaborator to remember"""
+
 AUTONOMY_CONTINUOUS_CONTINUE_TEMPLATE = """Your job: reflect on context, decide what you want to do next, and act if appropriate.
 - Use available actions/tools when they can advance the goal.
 - Use thinking to think about and plan what you want to do.
@@ -84,36 +114,30 @@ CHOOSE_OPTION_TEMPLATE = """# Task: Choose an option from the available choices.
 Analyze the options and select the most appropriate one based on the current context.
 Provide your reasoning and the selected option ID.
 
-Respond using XML format like this:
-<response>
-    <thought>Your reasoning for the selection</thought>
-    <selected_id>The ID of the selected option</selected_id>
-</response>
+Respond using TOON like this:
+thought: Your reasoning for the selection
+selected_id: The ID of the selected option
 
-IMPORTANT: Your response must ONLY contain the <response></response> XML block above."""
+IMPORTANT: Your response must ONLY contain the TOON document above."""
 
-IMAGE_DESCRIPTION_TEMPLATE = """<task>Analyze the provided image and generate a comprehensive description with multiple levels of detail.</task>
+IMAGE_DESCRIPTION_TEMPLATE = """Task: Analyze the provided image and generate a comprehensive description with multiple levels of detail.
 
-<instructions>
+Instructions:
 Carefully examine the image and provide:
 1. A concise, descriptive title that captures the main subject or scene
 2. A brief summary description (1-2 sentences) highlighting the key elements
 3. An extensive, detailed description that covers all visible elements, composition, lighting, colors, mood, and any other relevant details
 
 Be objective and descriptive. Focus on what you can actually see in the image rather than making assumptions about context or meaning.
-</instructions>
 
-<output>
+Output:
 
-Respond using XML format like this:
-<response>
-  <title>A concise, descriptive title for the image</title>
-  <description>A brief 1-2 sentence summary of the key elements in the image</description>
-  <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>
-</response>
+Respond using TOON like this:
+title: A concise, descriptive title for the image
+description: A brief 1-2 sentence summary of the key elements in the image
+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
 
-IMPORTANT: 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>.
-</output>"""
+IMPORTANT: Your response must ONLY contain the TOON document above. Do not include any text, thinking, or reasoning before or after it."""
 
 IMAGE_GENERATION_TEMPLATE = """# Task: Generate an image prompt for {{agentName}}.
 
@@ -126,13 +150,11 @@ The prompt should be specific, descriptive, and suitable for AI image generation
 # Recent conversation:
 {{recentMessages}}
 
-Respond using XML format like this:
-<response>
-    <thought>Your reasoning for the image prompt</thought>
-    <prompt>Detailed image generation prompt</prompt>
-</response>
+Respond using TOON like this:
+thought: Your reasoning for the image prompt
+prompt: Detailed image generation prompt
 
-IMPORTANT: Your response must ONLY contain the <response></response> XML block above."""
+IMPORTANT: Your response must ONLY contain the TOON document above."""
 
 MESSAGE_HANDLER_TEMPLATE = """task: Generate dialog and actions for {{agentName}}.
 
@@ -146,8 +168,8 @@ rules[8]:
 - use IGNORE or STOP only by themselves
 - include providers only when needed
 - use provider_hints from context when present instead of restating the same rules
-- if an action needs inputs, include a <params> block with the required fields
-- if a required param is unknown, ask for clarification in <text>
+- if an action needs inputs, include them under params keyed by action name
+- if a required param is unknown, ask for clarification in text
 
 control_actions:
 - STOP means the task is done and the agent should end the run without executing more actions
@@ -155,35 +177,27 @@ control_actions:
 
 fields[5]{name,meaning}:
 - thought | short plan
-- actions | ordered XML <action> elements
-- providers | comma-separated provider names, or empty
+- actions | ordered array of action names
+- providers | array of provider names, or empty
 - text | next message for {{agentName}}
 - simple | true or false
+- params | optional object keyed by action name containing required inputs
 
 formatting:
 - wrap multi-line code in fenced code blocks
 - use inline backticks for short code identifiers
 
-<output>
-XML only. Return exactly one <response> block. No prose before or after it. No <think>.
+output:
+TOON only. Return exactly one TOON document. No prose before or after it. No <think>.
 
 Example:
-<response>
-  <thought>Reply briefly. No extra providers needed.</thought>
-  <actions>
-    <action>
-      <name>REPLY</name>
-    </action>
-  </actions>
-  <providers></providers>
-  <text>Your message here</text>
-  <simple>true</simple>
-</response>
-</output>"""
-
-MULTI_STEP_DECISION_TEMPLATE = """<task>
-Determine the next step the assistant should take in this conversation to help the user reach their goal.
-</task>
+thought: Reply briefly. No extra providers needed.
+actions[1]: REPLY
+providers[0]:
+text: Your message here
+simple: true"""
+
+MULTI_STEP_DECISION_TEMPLATE = """Determine the next step the assistant should take in this conversation to help the user reach their goal.
 
 {{recentMessages}}
 
@@ -209,27 +223,21 @@ These are the actions or data provider calls that have already been used in this
 
 {{actionResults}}
 
-<keys>
+keys:
 "thought" Clearly explain your reasoning for the selected providers and/or action, and how this step contributes to resolving the user's request.
 "action"  Name of the action to execute after providers return (can be empty if no action is needed).
 "providers" List of provider names to call in this step (can be empty if none are needed).
 "isFinish" Set to true only if the task is fully complete.
-</keys>
 
 ⚠️ 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.
 
-<output>
-<response>
-  <thought>Your thought here</thought>
-  <action>ACTION</action>
-  <providers>PROVIDER1,PROVIDER2</providers>
-  <isFinish>true | false</isFinish>
-</response>
-</output>"""
+output:
+thought: Your thought here
+action: ACTION
+providers[2]: PROVIDER1,PROVIDER2
+isFinish: false"""
 
-MULTI_STEP_SUMMARY_TEMPLATE = """<task>
-Summarize what the assistant has done so far and provide a final response to the user based on the completed steps.
-</task>
+MULTI_STEP_SUMMARY_TEMPLATE = """Summarize what the assistant has done so far and provide a final response to the user based on the completed steps.
 
 # Context Information
 {{bio}}
@@ -257,13 +265,10 @@ Here are the actions taken by the assistant to fulfill the request:
 
  - Review the execution trace and last reasoning step carefully
 
- - Your final output MUST be in this XML format:
-<output>
-<response>
-  <thought>Your thought here</thought>
-  <text>Your final message to the user</text>
-</response>
-</output>"""
+ - Your final output MUST be TOON in this format:
+output:
+thought: Your thought here
+text: Your final message to the user"""
 
 OPTION_EXTRACTION_TEMPLATE = """# Task: Extract selected task and option from user message
 
@@ -280,17 +285,13 @@ OPTION_EXTRACTION_TEMPLATE = """# Task: Extract selected task and option from us
 4. If no clear selection is made, return null for both fields
 
 
-Return in XML format:
-<response>
-  <taskId>string_or_null</taskId>
-  <selectedOption>OPTION_NAME_or_null</selectedOption>
-</response>
+Return in TOON format:
+taskId: string_or_null
+selectedOption: OPTION_NAME_or_null
 
-IMPORTANT: 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>."""
+IMPORTANT: Your response must ONLY contain the TOON document above. Do not include any text, thinking, or reasoning before or after it."""
 
-POST_ACTION_DECISION_TEMPLATE = """<task>
-Continue helping the user after reviewing the latest action results.
-</task>
+POST_ACTION_DECISION_TEMPLATE = """Continue helping the user after reviewing the latest action results.
 
 context:
 {{providers}}
@@ -308,50 +309,37 @@ rules[9]:
 - use IGNORE or STOP only by themselves
 - include providers only when needed
 - use provider_hints from context when present instead of restating the same rules
-- if an action needs inputs, include a <params> block with the required fields
-- if a required param is unknown, ask for clarification in <text>
+- if an action needs inputs, include them under params keyed by action name
+- if a required param is unknown, ask for clarification in text
 - if the task is complete, either reply to the user or use STOP to end the run
 - STOP is a terminal control action even if it is not listed in available actions
 
-<output>
-XML only. Return exactly one <response> block. No prose before or after it. No <think>.
-
-<response>
-  <thought>Your thought here</thought>
-  <actions>
-    <action>
-      <name>ACTION</name>
-    </action>
-  </actions>
-  <providers></providers>
-  <text>Your message here</text>
-  <simple>true</simple>
-</response>
-</output>"""
+output:
+TOON only. Return exactly one TOON document. No prose before or after it. No <think>.
+
+thought: Your thought here
+actions[1]: ACTION
+providers[0]:
+text: Your message here
+simple: true"""
 
 POST_CREATION_TEMPLATE = """# Task: Create a post in the voice and style and perspective of {{agentName}} @{{xUserName}}.
 
 Example task outputs:
 1. A post about the importance of AI in our lives
-<response>
-  <thought>I am thinking about writing a post about the importance of AI in our lives</thought>
-  <post>AI is changing the world and it is important to understand how it works</post>
-  <imagePrompt>A futuristic cityscape with flying cars and people using AI to do things</imagePrompt>
-</response>
+thought: I am thinking about writing a post about the importance of AI in our lives
+post: AI is changing the world and it is important to understand how it works
+imagePrompt: A futuristic cityscape with flying cars and people using AI to do things
 
 2. A post about dogs
-<response>
-  <thought>I am thinking about writing a post about dogs</thought>
-  <post>Dogs are man's best friend and they are loyal and loving</post>
-  <imagePrompt>A dog playing with a ball in a park</imagePrompt>
-</response>
+thought: I am thinking about writing a post about dogs
+post: Dogs are man's best friend and they are loyal and loving
+imagePrompt: A dog playing with a ball in a park
 
 3. A post about finding a new job
-<response>
-  <thought>Getting a job is hard, I bet there's a good post in that</thought>
-  <post>Just keep going!</post>
-  <imagePrompt>A person looking at a computer screen with a job search website</imagePrompt>
-</response>
+thought: Getting a job is hard, I bet there's a good post in that
+post: Just keep going!
+imagePrompt: A person looking at a computer screen with a job search website
 
 {{providers}}
 
@@ -359,19 +347,17 @@ Write a post that is {{adjective}} about {{topic}} (without mentioning {{topic}}
 Your response should be 1, 2, or 3 sentences (choose the length at random).
 Your 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.
 
-Your output should be formatted in XML like this:
-<response>
-  <thought>Your thought here</thought>
-  <post>Your post text here</post>
-  <imagePrompt>Optional image prompt here</imagePrompt>
-</response>
+Your output should be formatted as TOON like this:
+thought: Your thought here
+post: Your post text here
+imagePrompt: Optional image prompt here
 
 The "post" field should be the post you want to send. Do not including any thinking or internal reflection in the "post" field.
 The "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.
 The "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.
 
 
-IMPORTANT: 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>."""
+IMPORTANT: Your response must ONLY contain the TOON document above. Do not include any text, thinking, or reasoning before or after it."""
 
 REFLECTION_EVALUATOR_TEMPLATE = """# Task: Generate Agent Reflection, Extract Facts and Relationships
 
@@ -405,29 +391,14 @@ Message Sender: {{senderName}} (ID: {{senderId}})
   - 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.
 
 
-Generate a response in the following format:
-<response>
-  <thought>a self-reflective thought on the conversation</thought>
-  <facts>
-    <fact>
-      <claim>factual statement</claim>
-      <type>fact|opinion|status</type>
-      <in_bio>false</in_bio>
-      <already_known>false</already_known>
-    </fact>
-    <!-- Add more facts as needed -->
-  </facts>
-  <relationships>
-    <relationship>
-      <sourceEntityId>entity_initiating_interaction</sourceEntityId>
-      <targetEntityId>entity_being_interacted_with</targetEntityId>
-      <tags>group_interaction,voice_interaction,dm_interaction,additional_tag1,additional_tag2</tags>
-    </relationship>
-    <!-- Add more relationships as needed -->
-  </relationships>
-</response>
-
-IMPORTANT: 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>."""
+Generate a response in the following TOON format:
+thought: a self-reflective thought on the conversation
+facts[1]{claim,type,in_bio,already_known}:
+  "factual statement",fact,false,false
+relationships[1]{sourceEntityId,targetEntityId,tags}:
+  entity_initiating_interaction,entity_being_interacted_with,"group_interaction,voice_interaction,dm_interaction,additional_tag1,additional_tag2"
+
+IMPORTANT: Your response must ONLY contain the TOON document above. Do not include any text, thinking, or reasoning before or after it."""
 
 REFLECTION_TEMPLATE = """# Task: Reflect on recent agent behavior and interactions.
 
@@ -443,16 +414,35 @@ Analyze the agent's recent behavior and interactions. Consider:
 3. Were any mistakes made?
 4. What could be improved?
 
-Respond using XML format like this:
-<response>
-    <thought>Your detailed analysis</thought>
-    <quality_score>Score 0-100 for overall quality</quality_score>
-    <strengths>What went well</strengths>
-    <improvements>What could be improved</improvements>
-    <learnings>Key takeaways for future interactions</learnings>
-</response>
+Respond using TOON like this:
+thought: Your detailed analysis
+quality_score: Score 0-100 for overall quality
+strengths: What went well
+improvements: What could be improved
+learnings: Key takeaways for future interactions
 
-IMPORTANT: Your response must ONLY contain the <response></response> XML block above."""
+IMPORTANT: Your response must ONLY contain the TOON document above."""
+
+REMOVE_CONTACT_TEMPLATE = """task: Extract the contact removal request.
+
+context:
+{{providers}}
+
+current_message:
+{{message}}
+
+instructions[4]:
+- identify the contact name to remove
+- set confirmed to yes only when the user explicitly confirms removal
+- set confirmed to no when confirmation is absent or ambiguous
+- return only the requested contact
+
+output:
+TOON only. Return exactly one TOON document. No prose before or after it. No <think>.
+
+Example:
+contactName: Jane Doe
+confirmed: yes"""
 
 REPLY_TEMPLATE = """# Task: Generate dialog for the character {{agentName}}.
 
@@ -469,15 +459,104 @@ IMPORTANT CODE BLOCK FORMATTING RULES:
 - This ensures the user sees clearly formatted and copyable code when relevant.
 
 Do NOT include any thinking, reasoning, or <think> sections in your response.
-Go directly to the XML response format without any preamble or explanation.
+Go directly to the TOON response format without any preamble or explanation.
+
+Respond using TOON like this:
+thought: Your thought here
+text: Your message here
+
+IMPORTANT: Your response must ONLY contain the TOON document above. Do not include any text, thinking, or reasoning before or after it."""
+
+SCHEDULE_FOLLOW_UP_TEMPLATE = """task: Extract follow-up scheduling information from the request.
+
+context:
+{{providers}}
+
+current_message:
+{{message}}
+
+current_datetime:
+{{currentDateTime}}
+
+instructions[5]:
+- identify who to follow up with
+- include entityId only when it is explicitly known
+- convert requested timing into an ISO datetime in scheduledAt
+- normalize priority to high, medium, or low
+- include message only when the user asked for a specific note or reminder text
+
+output:
+TOON only. Return exactly one TOON document. No prose before or after it. No <think>.
+
+Example:
+contactName: Jane Doe
+entityId:
+scheduledAt: 2026-04-06T14:00:00.000Z
+reason: Check in on the proposal
+priority: medium
+message: Send the latest deck before the call"""
+
+SEARCH_CONTACTS_TEMPLATE = """task: Extract contact search criteria from the request.
+
+context:
+{{providers}}
+
+current_message:
+{{message}}
+
+instructions[5]:
+- return categories as a comma-separated list when the user filters by category
+- return tags as a comma-separated list when the user filters by tags
+- return searchTerm for any name or free-text lookup
+- set intent to count when the user only wants a count, otherwise list
+- omit fields that are not clearly requested
+
+output:
+TOON only. Return exactly one TOON document. No prose before or after it. No <think>.
+
+Example:
+categories: vip,colleague
+searchTerm: Jane
+tags: ai,design
+intent: list"""
+
+SHOULD_FOLLOW_ROOM_TEMPLATE = """task: Decide whether {{agentName}} should follow this room.
+
+context:
+{{providers}}
+
+current_message:
+{{message}}
+
+instructions[3]:
+- return true only when the user is clearly asking {{agentName}} to follow, join, listen to, or stay engaged in this room
+- return false when the request is ambiguous or unrelated
+- prefer false when uncertain
+
+output:
+TOON only. Return exactly one TOON document. No prose before or after it. No <think>.
+
+Example:
+decision: true"""
+
+SHOULD_MUTE_ROOM_TEMPLATE = """task: Decide whether {{agentName}} should mute this room.
+
+context:
+{{providers}}
 
-Respond using XML format like this:
-<response>
-    <thought>Your thought here</thought>
-    <text>Your message here</text>
-</response>
+current_message:
+{{message}}
 
-IMPORTANT: 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>."""
+instructions[3]:
+- return true only when the user is clearly asking {{agentName}} to mute, silence, or ignore this room
+- return false when the request is ambiguous or unrelated
+- prefer false when uncertain
+
+output:
+TOON only. Return exactly one TOON document. No prose before or after it. No <think>.
+
+Example:
+decision: true"""
 
 SHOULD_RESPOND_TEMPLATE = """task: Decide whether {{agentName}} should respond, ignore, or stop.
 
@@ -492,20 +571,131 @@ rules[6]:
 - talking to someone else -> IGNORE
 - if unsure, prefer IGNORE over hallucinating relevance
 
+available_contexts:
+{{availableContexts}}
+
+context_routing:
+- primaryContext: choose one context from available_contexts, or "general" if none apply
+- secondaryContexts: optional comma-separated list of additional relevant contexts
+- evidenceTurnIds: optional comma-separated list of message IDs supporting the decision
+
+decision_note:
+- talking TO {{agentName}} means name mention, reply chain, or direct continuation
+- talking ABOUT {{agentName}} is not enough
+
+output:
+TOON only. Return exactly one TOON document. No prose before or after it. No <think>.
+
+Example:
+name: {{agentName}}
+reasoning: Direct mention and clear follow-up.
+action: RESPOND
+primaryContext: general
+secondaryContexts:
+evidenceTurnIds:"""
+
+SHOULD_RESPOND_WITH_CONTEXT_TEMPLATE = """task: Decide whether {{agentName}} should respond and which domain context applies.
+
+context:
+{{providers}}
+
+available_contexts:
+{{availableContexts}}
+
+rules[6]:
+- direct mention of {{agentName}} -> RESPOND
+- different assistant name -> IGNORE
+- continuing an active thread with {{agentName}} -> RESPOND
+- request to stop or be quiet -> STOP
+- talking to someone else -> IGNORE
+- if unsure, prefer IGNORE over hallucinating relevance
+
+context_routing:
+- primaryContext: the single best-matching domain from available_contexts
+- secondaryContexts: zero or more additional domains that are relevant
+- action intent does not only come from the last message; consider the full recent conversation
+- if no specific domain applies, use "general"
+
 decision_note:
 - talking TO {{agentName}} means name mention, reply chain, or direct continuation
 - talking ABOUT {{agentName}} is not enough
+- context routing always applies, even for IGNORE/STOP decisions
+
+output:
+TOON only. Return exactly one TOON document. No prose before or after it. No <think>.
+
+Example:
+name: {{agentName}}
+reasoning: Direct mention asking about token balance.
+action: RESPOND
+primaryContext: wallet
+secondaryContexts: []"""
+
+SHOULD_UNFOLLOW_ROOM_TEMPLATE = """task: Decide whether {{agentName}} should unfollow this room.
+
+context:
+{{providers}}
+
+current_message:
+{{message}}
+
+instructions[3]:
+- return true only when the user is clearly asking {{agentName}} to stop following or leave this room
+- return false when the request is ambiguous or unrelated
+- prefer false when uncertain
+
+output:
+TOON only. Return exactly one TOON document. No prose before or after it. No <think>.
+
+Example:
+decision: true"""
+
+SHOULD_UNMUTE_ROOM_TEMPLATE = """task: Decide whether {{agentName}} should unmute this room.
+
+context:
+{{providers}}
+
+current_message:
+{{message}}
+
+instructions[3]:
+- return true only when the user is clearly asking {{agentName}} to unmute or resume listening to this room
+- return false when the request is ambiguous or unrelated
+- prefer false when uncertain
+
+output:
+TOON only. Return exactly one TOON document. No prose before or after it. No <think>.
+
+Example:
+decision: true"""
+
+UPDATE_CONTACT_TEMPLATE = """task: Extract contact updates from the request.
+
+context:
+{{providers}}
+
+current_message:
+{{message}}
+
+instructions[6]:
+- identify the contact name to update
+- set operation to replace unless the user clearly says to add_to or remove_from
+- return categories and tags as comma-separated lists
+- return preferences and customFields as comma-separated key:value pairs
+- include notes only when explicitly requested
+- omit fields that are not being changed
 
-<output>
-XML only. Return exactly one <response> block. No prose before or after it. No <think>.
+output:
+TOON only. Return exactly one TOON document. No prose before or after it. No <think>.
 
 Example:
-<response>
-  <name>{{agentName}}</name>
-  <reasoning>Direct mention and clear follow-up.</reasoning>
-  <action>RESPOND | IGNORE | STOP</action>
-</response>
-</output>"""
+contactName: Jane Doe
+operation: add_to
+categories: vip
+tags: ai,friend
+preferences: timezone:America/New_York,language:English
+customFields: company:Acme,title:Designer
+notes: Prefers async communication"""
 
 UPDATE_ENTITY_TEMPLATE = """# Task: Update entity information.
 
@@ -518,19 +708,13 @@ UPDATE_ENTITY_TEMPLATE = """# Task: Update entity information.
 Based on the request, determine what information about the entity should be updated.
 Only update fields that the user has explicitly requested to change.
 
-Respond using XML format like this:
-<response>
-    <thought>Your reasoning for the entity update</thought>
-    <entity_id>The entity ID to update</entity_id>
-    <updates>
-        <field>
-            <name>field_name</name>
-            <value>new_value</value>
-        </field>
-    </updates>
-</response>
+Respond using TOON like this:
+thought: Your reasoning for the entity update
+entity_id: The entity ID to update
+updates[1]{name,value}:
+  field_name,new_value
 
-IMPORTANT: Your response must ONLY contain the <response></response> XML block above."""
+IMPORTANT: Your response must ONLY contain the TOON document above."""
 
 UPDATE_SETTINGS_TEMPLATE = """# Task: Update settings based on the request.
 
@@ -543,22 +727,17 @@ UPDATE_SETTINGS_TEMPLATE = """# Task: Update settings based on the request.
 Based on the request, determine which settings to update.
 Only update settings that the user has explicitly requested.
 
-Respond using XML format like this:
-<response>
-    <thought>Your reasoning for the settings changes</thought>
-    <updates>
-        <update>
-            <key>setting_key</key>
-            <value>new_value</value>
-        </update>
-    </updates>
-</response>
+Respond using TOON like this:
+thought: Your reasoning for the settings changes
+updates[1]{key,value}:
+  setting_key,new_value
 
-IMPORTANT: Your response must ONLY contain the <response></response> XML block above."""
+IMPORTANT: Your response must ONLY contain the TOON document above."""
 
 BOOLEAN_FOOTER = "Respond with only a YES or a NO."
 
 __all__ = [
+    "ADD_CONTACT_TEMPLATE",
     "AUTONOMY_CONTINUOUS_CONTINUE_TEMPLATE",
     "AUTONOMY_CONTINUOUS_FIRST_TEMPLATE",
     "AUTONOMY_TASK_CONTINUE_TEMPLATE",
@@ -574,8 +753,17 @@ __all__ = [
     "POST_CREATION_TEMPLATE",
     "REFLECTION_EVALUATOR_TEMPLATE",
     "REFLECTION_TEMPLATE",
+    "REMOVE_CONTACT_TEMPLATE",
     "REPLY_TEMPLATE",
+    "SCHEDULE_FOLLOW_UP_TEMPLATE",
+    "SEARCH_CONTACTS_TEMPLATE",
+    "SHOULD_FOLLOW_ROOM_TEMPLATE",
+    "SHOULD_MUTE_ROOM_TEMPLATE",
     "SHOULD_RESPOND_TEMPLATE",
+    "SHOULD_RESPOND_WITH_CONTEXT_TEMPLATE",
+    "SHOULD_UNFOLLOW_ROOM_TEMPLATE",
+    "SHOULD_UNMUTE_ROOM_TEMPLATE",
+    "UPDATE_CONTACT_TEMPLATE",
     "UPDATE_ENTITY_TEMPLATE",
     "UPDATE_SETTINGS_TEMPLATE",
     "BOOLEAN_FOOTER",