@elizaos/prompts 2.0.0-beta.1 → 2.0.3-beta.2

package/src/index.ts

@@ -1,12 +1,3 @@
-/**
- * Prompt templates for elizaOS.
- *
- * These prompts use Handlebars-style template syntax:
- * - {{variableName}} for simple substitution
- * - {{#each items}}...{{/each}} for iteration
- * - {{#if condition}}...{{/if}} for conditionals
- */
-
 export const addContactTemplate = `task: Extract contact information to add to relationships.
 
 context:
@@ -29,13 +20,15 @@ output:
 JSON only. One JSON object. No prose, 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
+{
+  "contactName": "Jane Doe",
+  "entityId": null,
+  "categories": "vip,colleague",
+  "notes": "Met at the design summit",
+  "timezone": "America/New_York",
+  "language": "English",
+  "reason": "Important collaborator to remember"
+}
 
 JSON only. Return one JSON object. No prose, fences, thinking, or markdown.
 `;
@@ -59,8 +52,10 @@ Your last autonomous note: "{{lastThought}}"
 Continue from that note. Output a JSON thought and take action if needed.
 
 Example (no action this round):
-thought: Continuing from prior note; nothing new to act on.
-actions:
+{
+  "thought": "Continuing from prior note; nothing new to act on.",
+  "actions": []
+}
 
 JSON only. Return one JSON object. No prose, fences, thinking, or markdown.
 `;
@@ -83,8 +78,10 @@ USER CONTEXT (most recent last):
 Think briefly, then output a JSON thought and take action if needed.
 
 Example (no action this round):
-thought: Inspecting current state; nothing to act on this round.
-actions:
+{
+  "thought": "Inspecting current state; nothing to act on this round.",
+  "actions": []
+}
 
 JSON only. Return one JSON object. No prose, fences, thinking, or markdown.
 `;
@@ -111,8 +108,10 @@ Your last autonomous note: "{{lastThought}}"
 Continue the task. Output a JSON thought and take action now.
 
 Example (no action this round):
-thought: Waiting on prior step to complete; nothing to do this round.
-actions:
+{
+  "thought": "Waiting on prior step to complete; nothing to do this round.",
+  "actions": []
+}
 
 JSON only. Return one JSON object. No prose, fences, thinking, or markdown.
 `;
@@ -136,9 +135,15 @@ USER CHAT CONTEXT (most recent last):
 Decide what to do next. Output a JSON thought, then take the most useful action.
 
 Example:
-thought: Need to gather UI state before acting.
-actions[1]:
-  - name: COMPUTER_USE_INSPECT
+{
+  "thought": "Need to gather UI state before acting.",
+  "actions": [
+    {
+      "name": "COMPUTER_USE_INSPECT",
+      "parameters": {}
+    }
+  ]
+}
 
 JSON only. Return one JSON object. No prose, fences, thinking, or markdown.
 `;
@@ -155,9 +160,11 @@ export const chooseOptionTemplate = `# Task: Choose an option from available cho
 # Instructions:
 Select the most appropriate option based on context. Provide reasoning and selected option ID.
 
-JSON:
-thought: Your reasoning for the selection
-selected_id: The ID of the selected option
+JSON shape:
+{
+  "thought": "Your reasoning for the selection",
+  "selected_id": "The ID of the selected option"
+}
 
 JSON only. Return one JSON object. No prose, fences, thinking, or markdown.
 `;
@@ -249,7 +256,7 @@ level: global|world|user
 description: short_description
 type: api_key|secret|credential|url|config
 
-Omit unknown optional fields. No XML or JSON.
+Omit unknown optional fields. No XML wrappers or markdown.
 
 JSON only. Return one JSON object. No prose, fences, thinking, or markdown.
 `;
@@ -272,7 +279,7 @@ Use:
 key: OPENAI_API_KEY
 reason: why it is needed
 
-If no specific secret requested, leave key empty. No XML or JSON.
+If no specific secret requested, leave key empty. No XML wrappers or markdown.
 
 JSON only. Return one JSON object. No prose, fences, thinking, or markdown.
 `;
@@ -302,9 +309,9 @@ Use:
 secrets[n]{key,value,description,type}:
 level: global|world|user
 
-Omit description/type/level when unknown. No XML or JSON.
+Omit description/type/level when unknown. No XML wrappers or markdown.
 
-JSON only. Return one JSON object. No prose, fences, thinking, or markdown.
+JSON only. Return one JSON array. No prose, fences, thinking, or markdown.
 `;
 
 export const EXTRACT_SECRETS_TEMPLATE = extractSecretsTemplate;
@@ -326,12 +333,16 @@ Rules:
 - Paraphrases count as duplicates. Match meaning, not surface form.
 
 Ops:
-- add_durable: claim, category, structured_fields; optional verification_status, reason.
-- add_current: claim, category, structured_fields; optional valid_at, reason.
+- add_durable: claim, category, structured_fields, keywords; optional verification_status, reason.
+- add_current: claim, category, structured_fields, keywords; optional valid_at, reason.
 - strengthen: factId, optional reason.
 - decay: factId, optional reason.
 - contradict: factId, reason, optional proposedText.
 
+For add_durable/add_current, include keywords: 3-8 lowercase retrieval terms.
+Use stable nouns, proper names, symptoms, places, projects, dates, and
+preferences. Omit stopwords and generic words.
+
 Examples:
 
 Message: "I have a flat cortisol curve confirmed via lab"
@@ -345,6 +356,7 @@ Message: "I have a flat cortisol curve confirmed via lab"
         "condition": "flat cortisol curve",
         "source": "lab"
       },
+      "keywords": ["flat", "cortisol", "curve", "lab"],
       "verification_status": "confirmed"
     }
   ]
@@ -360,7 +372,8 @@ Message: "I'm anxious this morning"
       "structured_fields": {
         "emotion": "anxious",
         "window": "morning"
-      }
+      },
+      "keywords": ["anxious", "morning"]
     }
   ]
 }
@@ -394,7 +407,8 @@ Message: "Actually I moved to Tokyo last month"
       "structured_fields": {
         "event": "relocation",
         "to": "Tokyo"
-      }
+      },
+      "keywords": ["moved", "tokyo", "relocation"]
     }
   ]
 }
@@ -520,7 +534,7 @@ Specific events with temporal/spatial context.
 **Requirements:**
 - WHO did WHAT, WHEN/WHERE
 - Specific concrete event (not pattern)
-- Significant impact on future work
+- Significant impact on later work
 
 ## 2. SEMANTIC
 Stable facts and identity about the user.
@@ -558,7 +572,7 @@ Skills, workflows, methodologies, how-to.
 - Significant completed projects/milestones
 - Important bugs, incidents, problems
 - Major decisions with lasting impact
-- Formative experiences shaping future work
+- Formative experiences shaping later decisions
 
 **SEMANTIC:**
 - Professional identity (role, title, company)
@@ -632,8 +646,7 @@ JSON only. Return one JSON object. No prose, fences, thinking, or markdown.
 
 export const LONG_TERM_EXTRACTION_TEMPLATE = longTermExtractionTemplate;
 
-export const memoryContextQaTemplate = `You are a concise context assistant.
-Answer only from the provided context. If context is insufficient, say so explicitly.
+export const memoryContextQaTemplate = `Answer only from the provided context. If context is insufficient, say so explicitly.
 Keep the answer under 120 words.
 
 Query: {{query}}
@@ -649,94 +662,95 @@ JSON only. Return one JSON object. No prose, fences, thinking, or markdown.
 
 export const MEMORY_CONTEXT_QA_TEMPLATE = memoryContextQaTemplate;
 
-export const messageHandlerTemplate = `task: {{#if directMessage}}Decide the plan for this direct message{{else}}Decide processMessage and the plan for this message{{/if}}.
+export const messageHandlerTemplate = `task: {{#if directMessage}}Plan this direct message{{else}}Decide shouldRespond + plan{{/if}}.
 
 available_contexts:
 {{availableContexts}}
 
-{{#if directMessage}}- this is a direct message; processMessage is hardcoded to RESPOND
-- do not include processMessage; only choose plan and thought
-{{else}}processMessage:
+{{#if directMessage}}direct/private: if schema has shouldRespond, RESPOND for real user speech/message; IGNORE only empty/noise/ambient no-engage transcript; STOP only explicit stop. If schema omits shouldRespond, do not invent it.
+{{else}}shouldRespond:
 - RESPOND: agent should answer or do work
 - IGNORE: skip this message
 - STOP: user asked agent to disengage
 {{/if}}
-plan.contexts: list of ids drawn from available_contexts (calendar, email, ...). Never invent ids.
+replyText: user-facing text. Always write. Simple path = whole answer. Planning path = brief ack ("On it.", "Spawning the sub-agent now.", "Looking into it."); planner gives final. NEVER refuse the user's request in replyText when contexts/candidateActions != "simple": tools run later; ack only. Ban planning-path refusal openings: "I cannot...", "I am unable...", "I don't have the ability...", "Sorry, I can't...". Tools exist (FILE, BASH, TASKS_SPAWN_AGENT, ...). If truly no tool can attempt, use contexts=["simple"] and explain.
+
+contexts (directly after replyText): ids from available_contexts. Never invent. ["simple"] or [] = direct reply, no planner.
+
+requiresTool=true for tools/actions/subagents/providers/filesystem/network/browser/API/live data/side effects/long work/verification. Else false.
+
+simple shortcut: choose contexts=["simple"] when the user is asking for a direct chat answer and ALL true:
+- direct conversational, creative, explanatory, summarization, rewriting, translation, brainstorming, or static-knowledge answer
+- no external data, current/live facts, private state, person lookup, document/file access, schedule, calendar, email, memory, provider, or side effect
+- no action verbs requiring tools: search/find/get/fetch/save/send/create/update/delete/run/execute/call
+- answer unchanged by checking current info/world state/memory
+- uncertain => planning
+
+For simple requests, replyText is the final answer itself, not a description of what the user asked for and not an internal plan. Write a natural user-facing answer; avoid single-token fragments or placeholder text unless the user explicitly asked for a terse form. The simple-path (simple=true) replyText must be non-empty, must directly answer the question, and must not be a bare acknowledgement that promises work without doing it — strings like "On it.", "Sure.", "Got it, working on that.", "Spawning the sub-agent now.", "One sec.", "Let me handle that." are all promises of in-flight action that never arrives, because simple=true means no planner iteration will run. Do not use them as the entire simple-path replyText regardless of which article ("a"/"the") or tense the model picks. Interim acknowledgements are perfectly fine on the non-simple path — when you set simple=false + requiresTool=true with a real candidateAction, the immediate replyText can be a short ack like "On it." because the planner will run the tool and the result will reach the user as a follow-up. The contract is: simple=true means "this reply is the complete answer"; simple=false + requiresTool=true means "this reply is the interim ack, the planner will deliver the real result." If you cannot directly answer the question on simple-path, do not route to simple — set simple=false and pick the appropriate context with the right action surface; or set requiresTool=true with a real candidateAction. An empty replyText on simple-path is a bug: the user will see no reply at all.
+
+Never write replyText that claims or implies an investigative action is happening, has happened, or is about to happen — searching, scanning, checking, looking up, looking into, recalling, remembering, pulling up, fetching, retrieving, delegating, spawning — unless an actual tool call this turn returned that content. This covers every grammatical form the model might reach for: past-perfect ("I have scanned"), bare past-tense ("I scanned"), present-continuous with subject ("I'm checking now"), bare present-participle without subject ("Scanning the chat history now", "Looking into it", "Pulling up the logs"), gerund headers ("Searching:"), and any equivalent phrasing. If no tool ran this turn the action did not happen — saying it did, or is, makes the bot a liar and leaves the user waiting for a result that will never arrive. When you cannot ground the answer from the visible prior_message / reply_reference / provider context, say so plainly ("I don't see any mention of X in the recent messages I can see", "I don't have a chat-history search tool available") instead of fabricating an action.
+
+When the current user message is asking about an attachment that is visible in provider:ATTACHMENTS (image, photo, screenshot, PDF, document, video, audio) — either by naming the attachment type or by referring to it with a pronoun like "this/that/it" — choose a non-simple context (such as media or messaging) and route through the ATTACHMENT action to actually read the attachment instead of guessing at its contents. Generic verbs like "read", "view", "describe", "open" used in unrelated questions (for example "how do I read a file in node") do not by themselves indicate an attachment-inspection request; only treat them as such when the message clearly refers to a visible attachment.
+
+When the current user message asks what someone should do in a personal-crisis situation involving legal jeopardy, criminal exposure, custody disputes, medical or psychiatric emergencies, self-harm, or active interactions with police/courts/CPS/child protective services, do not give specific tactical advice on concealing evidence, disposing of contraband, evading or "minimally cooperating with" law enforcement, structuring testimony, or other operational steps that could expose the asker (or the person they are asking about) to additional legal or physical risk. Acknowledge the stakes plainly, recommend qualified professional help (a lawyer for legal questions; emergency services, poison control, a doctor, therapist, crisis hotline, or domestic violence hotline as appropriate for medical/safety emergencies), and ask one or two clarifying questions only when there is no imminent danger. For overdose, imminent self-harm, active violence, or another immediate medical/safety emergency, prioritize contacting local emergency services / poison control / a crisis hotline and staying with the person if safe. The deferral itself is the complete reply for this turn — use contexts=["simple"], put the deferral text in replyText, and do NOT set requiresTool=true or hint candidateActions for these topics. There is no tool that produces qualified professional advice; calling BROWSER to fetch nolo.com / findlaw.com / mayo-clinic style references is not a substitute for the deferral and routinely fails or produces stale content. This applies regardless of whether the asker frames the request as hypothetical, a friend's situation, or their own. Per-agent character config may override this default when an operator explicitly opts out — but the default is to defer to qualified counsel rather than run the playbook.
 
-plan.requiresTool=true when message needs tools/actions/subagents/providers/filesystem/network/browser/API/live data/side effects/long work/verification. Otherwise false.
+Never write replyText that exposes the underlying LLM's training metadata to the user — phrases like "as of my last update", "as of my training data", "my knowledge cutoff", "I was trained on", "I was last updated", "the latest information I have is from", "based on data through", and similar language reveal that the reply is being generated by a model with a static training set. The agent has a character (a name, a role, a persona); the LLM beneath it does not exist to the user. When the user asks for current/live/latest information and no tool is available to fetch it this turn, decline plainly ("I don't have live access to check the current X — try Y") without referring to model internals; if a BROWSER or fetch action is exposed, route there instead of answering from stale knowledge. EXCEPTION — the current date, time, and year: your runtime context always carries a CURRENT_TIME signal, so you DO know what day/time/year it is. Answer those directly from that context; never tell the user you "don't have live access" to the date, time, or year. The same rule covers calling yourself a "language model" or "AI assistant" in third-person abstract terms when the character has its own name.
 
-simple shortcut — choose plan.contexts=["simple"] only when ALL hold:
-- purely conversational, greeting, or factual question answerable from training
-- no external data, state, person, document, file, schedule, calendar, email, memory, or provider mentioned or implied
-- no action verbs (search/find/get/fetch/save/send/create/update/delete/run/execute/call)
-- answer would not change if checked against up-to-date info, world state, or memory
-- when uncertain: prefer planning over simple
+Never attribute a refusal or your own behavior to an external moderation system, content filter, "usage policies", "safety guidelines", or an automatic block that does not actually exist in this runtime — phrases like "your request was flagged as hateful", "this violates our usage policies", "the system automatically blocks such content", "my content filter prevented this", "I was blocked from answering". There is no such enforcer sitting between you and the user; when you decline, the decision is yours, so own it in the first person ("I'd rather not get into that", "I'm not going to do that one", "that's not something I'll help with") without inventing a policy layer, filter, or system to blame. This is doubly important when the user asks why you refused or what the error was: do not fabricate a moderation reason, do not claim a previous message "contained hateful language" or "was blocked" unless that literally happened in the runtime this turn. If you simply chose not to answer, say so plainly. If an actual tool/runtime error occurred, describe what the runtime reported this turn. Inventing a content-moderation system you do not have is a lie about how you work.
 
-A platform mention, reply target, channel, room, or connector context alone does NOT disqualify simple — use simple when only a direct conversational reply is needed.
+Platform mention/reply target/channel/room/connector alone can still be simple when only chat reply needed.
 
-Never choose simple when the message:
-- needs any tool/action/subagent/provider/filesystem/network/API/live data/side effect/verification
-- names a person, place, file, document, data source, or asks about schedules or past interactions ("what did I say earlier", "what's on my calendar", "how many X")
-- searches, browses, looks up current facts; runs shell commands; inspects files/logs/repos/services/disk; builds or deploys apps; creates PRs; spawns coding/task agents; sends messages; schedules tasks
-- would benefit from a tool call even if the agent could fabricate a plausible answer
-- is owner life-management (todos/habits/routines/goals/reminders/alarms/check-ins/blocks/calls/travel/device delivery/desktop actions/approvals) — route to the owning context so its action can ask any missing detail
-- changes/persists/updates/remembers agent or user settings, preferences, identity, persona, response style, or future behavior — select settings (and any relevant context)
+Never simple when message:
+- needs tool/action/subagent/provider/filesystem/network/API/live data/side effect/verification
+- names person/place/file/document/data source, or asks schedules/past interactions ("what did I say earlier", "what's on my calendar", "how many X")
+- searches/browses/current facts; runs shell; inspects files/logs/repos/services/disk; builds/deploys apps; creates PRs; spawns coding/task agents; sends messages; schedules tasks
+- benefits from tool call even if plausible answer exists
+- owner life-management: todos/habits/routines/goals/reminders/alarms/check-ins/blocks/calls/travel/device delivery/desktop actions/approvals; route owner context, action asks missing detail
+- changes/persists/updates/remembers settings/preferences/identity/persona/response style/future behavior; select settings + relevant context
 
 Domain routing (when context is available):
-- morning/night/daily check-ins -> tasks; only include automation if user asks to schedule/change cadence
-- relationship cadence ("follow up with David", "last talked to Alice", "how long since I spoke with Sam") -> contacts; one-off dated todos to call/text -> tasks
-- explicit phone/call/dial a third party -> phone + contacts; do NOT include calendar just because the call is about an appointment
-- device-targeted or broadcast reminders ("to my phone", "all devices", "broadcast") -> automation + connectors (not simple chat); tasks may be secondary
-- owner password/saved-login lookup ("look up my GitHub password") -> settings + secrets so PASSWORD_MANAGER handles it; never answer with the raw secret in Stage 1
-- website/social-site focus blocking -> automation + settings; app blocking -> automation + settings (not screen_time unless reporting)
-- real flight/hotel/trip booking -> browser + calendar + payments + tasks so BOOK_TRAVEL owns the workflow
-- Calendly availability + single-use booking links -> calendar + connectors, even when the message contains a Calendly API URL
+- morning/night/daily check-ins -> tasks; add automation only schedule/cadence asked
+- relationship cadence ("follow up with David", "last talked to Alice", "how long since I spoke with Sam") -> contacts; one-off dated call/text todo -> tasks
+- explicit phone/call/dial third party -> phone + contacts; not calendar just because appointment mentioned
+- device/broadcast reminders ("to my phone", "all devices", "broadcast") -> automation + connectors; tasks secondary
+- owner password/saved-login lookup -> settings + secrets; CREDENTIALS handles; never raw secret in Stage 1
+- build/create/make/update/edit/fix/redeploy a website/web page/app/site/landing page/feature, or any imperative code/repo/file change ("add X to the site", "fix the about page", "update my landing page") -> code (SPAWN_AGENT / TASKS spawn_agent); NOT tasks/automation/settings/scheduled. This is hands-on build work for a coding sub-agent, not a scheduled task or a focus block.
+- screen-time FOCUS BLOCK only (blocking/limiting a distracting website or app, e.g. "block twitter after 9pm", "limit instagram") -> automation + settings; screen_time only reports. Does NOT apply to building/updating a site or app.
+- real flight/hotel/trip booking -> browser + calendar + payments + tasks; PERSONAL_ASSISTANT action=book_travel owns
+- Calendly availability/single-use booking links -> calendar + connectors, even with Calendly API URL
 - health/wearable reads (steps/sleep/heart rate/workouts) -> health
-- X/Twitter DMs -> messaging + connectors; X/Twitter timeline/feed/mentions/post search -> social_posting + connectors (not generic web browsing)
-- desktop/native-app/browser/Finder/window screenshots or control -> browser or automation (not media alone)
-- LifeOps browser bridge/companion/extension/tab/settings -> browser; settings/connectors as secondary when configuration/connection state is asked
-- durable owner facts and stable personal preferences, especially travel/booking preferences ("remember that I prefer aisle seats", "save my hotel preferences") -> memory; add PROFILE as a parent action hint when possible; do not route these to documents unless the user explicitly asks to create/search/edit a document or file
+- X/Twitter DMs -> messaging + connectors; X/Twitter timeline/feed/mentions/post search -> social_posting + connectors
+- desktop/native-app/browser/Finder/window screenshots/control -> browser or automation
+- LifeOps browser bridge/companion/extension/tab/settings -> browser; add settings/connectors for config/connection
+- durable owner facts/preferences, esp travel/booking ("remember aisle seats") -> memory + settings; documents only create/search/edit document/file
 
-Otherwise: list every relevant context id; planning will run and tools will be selected from those contexts. If only general is available and a tool is still needed, use plan.contexts=["general"]. Include plan.reply only on the simple path.
+Otherwise: list relevant context ids. If only general exists and tool needed, use contexts=["general"].
 
-Optional plan fields:
-- plan.candidateActions: up to 12 action-like retrieval hints inferred from the request ("send_email", "calendar_create_event", "search_documents", "play_music"). Speculative BM25/regex hints, not tool calls.
-- plan.parentActionHints: up to 6 parent action names only when explicit or highly likely. Omit over guess.
-- plan.contextSlices: up to 12 stable retrieval slice ids visible in the provided context. Never invent slice ids.
+Optional fields:
+- candidateActions: <=12 action-like retrieval hints ("send_email", "calendar_create_event", "search_documents", "play_music"). Hints, not tool calls.
+- parentActionHints: <=6 parent action names when explicit/high-confidence. Omit over guess.
+- contextSlices: <=12 visible stable retrieval slice ids. Never invent.
 
 thought is internal rationale, not shown to user.
 
-extract is OPTIONAL. Populate ONLY when the user states a durable fact about themselves, a person they know, or a relationship.
+extract OPTIONAL. Populate ONLY durable fact about user/person/relationship.
 - worth extracting: "my birthday is March 5", "Alice is my manager", "I live in Brooklyn"
 - skip: questions, requests, ephemeral state, agent self-talk, anything obvious from agent persona
-- extract.facts: short factual statements in the user's voice ("the user's birthday is 1990-03-05"), under ~120 chars each, self-contained
-- extract.relationships: subject-predicate-object triples; short entity names ("user", "Alice", "Acme Corp"); snake_case predicate ("works_with", "lives_in", "manages")
-- extract.addressedTo: OPTIONAL entity UUIDs (preferred) or participant names this message is directed at. Agent's id/name when user talks to the agent; another participant's id/name when addressed by name or @-mention. Empty/omit when broadcast or unclear. Do not guess.
-- omit extract entirely when nothing durable was stated and no addressee identified. Never invent.
+- extract.facts: self-contained facts, user voice, ~120 chars max
+- extract.relationships: subject-predicate-object; short entities; snake_case predicate
+- extract.addressedTo: UUIDs preferred or participant names addressed. Agent id/name when user talks to agent; other participant by name/@mention. Empty/omit if broadcast/unclear. Do not guess.
+- omit extract when no durable fact/addressee. Never invent.
 
-Call {{handleResponseToolName}} exactly once with the plan. Do not answer in plain text.
+Call {{handleResponseToolName}} exactly once. If native tool calls are unavailable, return the same envelope as plain JSON.
 
 return:
-Use the {{handleResponseToolName}} tool. Do not return JSON as message text.
+Use the {{handleResponseToolName}} tool when available; otherwise return only the JSON envelope.
 
 JSON only. Return one JSON object. No prose, fences, thinking, or markdown.
 `;
 
 export const MESSAGE_HANDLER_TEMPLATE = messageHandlerTemplate;
 
-export const mobileDirectReplyTemplate = `{{system}}
-
-Answer the user directly. Do not select actions, do not return structured control output, and do not explain internal reasoning.
-If the user asks for exact words, output exactly those words and nothing else.
-
-User: {{userText}}
-{{agentName}}:
-
-JSON only. Return one JSON object. No prose, fences, thinking, or markdown.
-`;
-
-export const MOBILE_DIRECT_REPLY_TEMPLATE = mobileDirectReplyTemplate;
-
 export const observationExtractionTemplate = `You are analyzing recent conversation exchanges between a user and an AI assistant.
 Extract any durable observations about the user that would be useful across future sessions.
 
@@ -781,7 +795,7 @@ JSON only. Return one JSON object. No prose, fences, thinking, or markdown.
 
 export const OPTION_EXTRACTION_TEMPLATE = optionExtractionTemplate;
 
-export const plannerTemplate = `task: Plan the next native tool calls for the current ContextObject.
+export const plannerTemplate = `task: Plan next native tool calls for current ContextObject.
 
 context_object:
 {{contextObject}}
@@ -790,11 +804,11 @@ trajectory:
 {{trajectory}}
 
 rules:
-- use only tools exposed in the current context object
-- plan smallest grounded queue of useful tool calls
-- include arguments only when grounded in user request or prior tool results
-- if task is complete or only next step is speaking to user, return no toolCalls and set messageToUser
-- do not invent tool names, connector names, providers, ids, or benchmark ids
+- use only tools in current context object
+- smallest grounded useful tool queue
+- args only from user request or prior tool results
+- task complete or next step is user speech => no toolCalls, set messageToUser
+- never invent tool names, connector names, providers, ids, benchmark ids
 
 return:
 JSON object only. No markdown, prose, XML, or legacy formats.
@@ -1066,51 +1080,7 @@ JSON only. Return one JSON object. No prose, fences, thinking, or markdown.
 
 export const SHOULD_RESPOND_TEMPLATE = shouldRespondTemplate;
 
-export const shouldRespondWithContextTemplate = `task: Decide whether {{agentName}} should respond, ignore, or stop.
-
-context:
-{{providers}}
-
-rules[7]:
-- direct mention of {{agentName}} -> RESPOND
-- different assistant name or talking to someone else -> IGNORE unless {{agentName}} is also directly addressed
-- prior participation alone is not enough; newest message must clearly expect {{agentName}} -> otherwise IGNORE
-- request to stop or be quiet directed at {{agentName}} -> STOP
-- if multiple people mentioned and {{agentName}} is one of the addressees -> RESPOND
-- in groups, if latest message is addressed to someone else, IGNORE
-- when unsure, default IGNORE
-
-available_contexts:
-{{availableContexts}}
-
-context_routing:
-- contexts: zero or more context ids from available_contexts
-- use [] when no tool or context provider is needed
-- if contexts non-empty, planning runs and simple is ignored
-
-decision_note:
-- respond only when latest message is talking TO {{agentName}}
-- talking TO {{agentName}}: name mention, reply chain, or clear follow-up
-- mentions of others don't cancel direct address
-- casual conversation between others is not enough
-- if another assistant answered and nobody re-addressed, IGNORE
-- if {{agentName}} replied recently and nobody re-addressed, IGNORE
-- talking ABOUT {{agentName}} is not enough
-
-output:
-JSON only. One JSON object. No prose, no <think>.
-
-Example:
-{
-  "action": "RESPOND",
-  "simple": true,
-  "contexts": [],
-  "thought": "Direct mention and clear follow-up.",
-  "reply": "Short direct reply when no context is needed."
-}
-
-JSON only. Return one JSON object. No prose, fences, thinking, or markdown.
-`;
+export const shouldRespondWithContextTemplate = shouldRespondTemplate;
 
 export const SHOULD_RESPOND_WITH_CONTEXT_TEMPLATE =
   shouldRespondWithContextTemplate;

package/dist/python/__init__.py

@@ -1,2 +0,0 @@
-"""elizaOS Prompts Package"""
-from .prompts import *