@elizaos/agent 2.0.0-alpha.396 → 2.0.0-alpha.398

package/apps/app-steward/src/services/steward-credentials.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"steward-credentials.d.ts","sourceRoot":"","sources":["../../../../../../../apps/app-steward/src/services/steward-credentials.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAMH,MAAM,WAAW,2BAA2B;IAC1C,MAAM,EAAE,MAAM,CAAC;IACf,QAAQ,EAAE,MAAM,CAAC;IACjB,OAAO,EAAE,MAAM,CAAC;IAChB,MAAM,EAAE,MAAM,CAAC;IACf,UAAU,EAAE,MAAM,CAAC;IACnB,eAAe,CAAC,EAAE;QAChB,GAAG,CAAC,EAAE,MAAM,CAAC;QACb,MAAM,CAAC,EAAE,MAAM,CAAC;KACjB,CAAC;IACF,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAQD;;;GAGG;AACH,wBAAgB,sBAAsB,IAAI,2BAA2B,GAAG,IAAI,CAe3E;AAED;;GAEG;AACH,wBAAgB,sBAAsB,CACpC,WAAW,EAAE,2BAA2B,GACvC,IAAI,CAYN;AAED;;;;;GAKG;AACH,wBAAgB,6BAA6B,CAC3C,GAAG,GAAE,MAAM,CAAC,UAAwB,GACnC,2BAA2B,GAAG,IAAI,CA6BpC"}
+{"version":3,"file":"steward-credentials.d.ts","sourceRoot":"","sources":["../../../../../../../apps/app-steward/src/services/steward-credentials.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAmBH,MAAM,WAAW,2BAA2B;IAC1C,MAAM,EAAE,MAAM,CAAC;IACf,QAAQ,EAAE,MAAM,CAAC;IACjB,OAAO,EAAE,MAAM,CAAC;IAChB,MAAM,EAAE,MAAM,CAAC;IACf,UAAU,EAAE,MAAM,CAAC;IACnB,eAAe,CAAC,EAAE;QAChB,GAAG,CAAC,EAAE,MAAM,CAAC;QACb,MAAM,CAAC,EAAE,MAAM,CAAC;KACjB,CAAC;IACF,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAQD;;;GAGG;AACH,wBAAgB,sBAAsB,IAAI,2BAA2B,GAAG,IAAI,CAe3E;AAED;;GAEG;AACH,wBAAgB,sBAAsB,CACpC,WAAW,EAAE,2BAA2B,GACvC,IAAI,CAYN;AAED;;;;;GAKG;AACH,wBAAgB,6BAA6B,CAC3C,GAAG,GAAE,MAAM,CAAC,UAAwB,GACnC,2BAA2B,GAAG,IAAI,CA6BpC"}

package/apps/app-steward/src/services/steward-credentials.js

@@ -6,8 +6,18 @@
  * Environment variables always override file values.
  */
 import fs from "node:fs";
+import { homedir } from "node:os";
 import path from "node:path";
-import { resolveStateDir } from "@elizaos/core";
+// Inlined to avoid pulling the @elizaos/core source barrel into consumers
+// that only need state-dir resolution (e.g. the Electrobun bun bundle, which
+// would otherwise transitively bundle plugin-sql, transformers, and onnxruntime).
+// Mirrors the canonical implementation in @elizaos/core's
+// src/utils/state-dir.ts: MILADY_STATE_DIR > ELIZA_STATE_DIR > ~/.milady.
+function resolveStateDir() {
+    return (process.env.MILADY_STATE_DIR?.trim() ||
+        process.env.ELIZA_STATE_DIR?.trim() ||
+        path.join(homedir(), ".milady"));
+}
 const CREDENTIALS_FILENAME = "steward-credentials.json";
 function resolveCredentialsPath() {
     return path.join(resolveStateDir(), CREDENTIALS_FILENAME);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elizaos/agent",
-  "version": "2.0.0-alpha.396",
+  "version": "2.0.0-alpha.398",
   "description": "Standalone elizaOS-based agent and backend server package.",
   "type": "module",
   "license": "MIT",
@@ -467,7 +467,7 @@
     "@elizaos/app-steward": "^0.0.0",
     "@elizaos/app-task-coordinator": "^0.0.0",
     "@elizaos/app-training": "^0.0.1",
-    "@elizaos/core": "^2.0.0-alpha.396",
+    "@elizaos/core": "^2.0.0-alpha.398",
     "@elizaos/plugin-agent-orchestrator": "^0.6.2-alpha.0",
     "@elizaos/plugin-browser-bridge": "^0.1.0",
     "@elizaos/plugin-local-embedding": "^2.0.0-alpha.12",
@@ -476,8 +476,8 @@
     "@elizaos/plugin-solana": "^2.0.0-alpha.6",
     "@elizaos/plugin-sql": "^2.0.0-alpha.19",
     "@elizaos/plugin-wechat": "^0.1.0",
-    "@elizaos/shared": "^2.0.0-alpha.396",
-    "@elizaos/skills": "^2.0.0-alpha.396",
+    "@elizaos/shared": "^2.0.0-alpha.398",
+    "@elizaos/skills": "^2.0.0-alpha.398",
     "@hapi/boom": "^10.0.1",
     "@noble/curves": "^2.0.1",
     "@solana/web3.js": "^1.98.4",

package/packages/agent/src/triggers/action.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"action.d.ts","sourceRoot":"","sources":["../../../../../src/triggers/action.ts"],"names":[],"mappings":"AACA,OAAO,EACL,KAAK,MAAM,EAWZ,MAAM,eAAe,CAAC;AA6HvB,wBAAgB,sBAAsB,CAAC,IAAI,EAAE,MAAM,GAAG,OAAO,CAO5D;AAED,eAAO,MAAM,uBAAuB,EAAE,MAiQrC,CAAC"}
+{"version":3,"file":"action.d.ts","sourceRoot":"","sources":["../../../../../src/triggers/action.ts"],"names":[],"mappings":"AACA,OAAO,EACL,KAAK,MAAM,EAWZ,MAAM,eAAe,CAAC;AAgIvB,wBAAgB,sBAAsB,CAAC,IAAI,EAAE,MAAM,GAAG,OAAO,CAW5D;AAED,eAAO,MAAM,uBAAuB,EAAE,MAyQrC,CAAC"}

package/packages/agent/src/triggers/action.js

@@ -82,15 +82,28 @@ function scheduleText(summary) {
     }
     return `on cron ${summary.cronExpression ?? "* * * * *"}`;
 }
+const EVERY_N_UNIT_PATTERN = /\bevery\s+\d+\s*(second|minute|hour|day|week|month)s?\b/i;
 export function looksLikeTriggerIntent(text) {
     const trimmed = text.trim();
     if (!trimmed) {
         return false;
     }
-    return findKeywordTermMatch(trimmed, TRIGGER_INTENT_TERMS) !== undefined;
+    if (findKeywordTermMatch(trimmed, TRIGGER_INTENT_TERMS) !== undefined) {
+        return true;
+    }
+    return EVERY_N_UNIT_PATTERN.test(trimmed);
 }
 export const createTriggerTaskAction = {
     name: CREATE_TRIGGER_TASK_ACTION,
+    // SET_REMINDER is deliberately absent: it collides with LIFE's same simile
+    // (life.ts:2499) and LIFE owns the user-facing reminder/alarm concept.
+    // CREATE_TRIGGER_TASK is for programmatic scheduled jobs (cron, interval,
+    // agent-owned heartbeats), not LifeOps reminders. When both actions share
+    // a simile, runtime.processActions (runtime.ts:2400-2440) resolves it via
+    // first-match iteration order, so the collision was dispatching user
+    // reminder intents to whichever action registered first — a race the
+    // planner's validate-time gating cannot override (processActions does not
+    // re-validate at dispatch, per runtime.ts:2473).
     similes: [
         "CREATE_TRIGGER",
         "SCHEDULE_TRIGGER",
@@ -99,7 +112,6 @@ export const createTriggerTaskAction = {
         "SCHEDULE_HEARTBEAT",
         "CREATE_AUTOMATION",
         "SCHEDULE_AUTOMATION",
-        "SET_REMINDER",
         "CREATE_CRON",
         "CREATE_RECURRING",
     ],

package/packages/app-core/src/api/client-n8n.js

@@ -32,10 +32,16 @@ ElizaClient.prototype.updateN8nWorkflow = async function (id, request) {
     });
 };
 ElizaClient.prototype.generateN8nWorkflow = async function (request) {
+    // LLM-driven workflow generation runs keyword extraction, node search,
+    // generation, multiple correction passes, and feasibility assessment
+    // sequentially — easily 30-90s on a cold cache. The 10s default fetch
+    // timeout is far too aggressive and surfaces as
+    // "Request timed out after 10000ms" in the Automations UI even when
+    // the backend would have succeeded a few seconds later.
     return this.fetch("/api/n8n/workflows/generate", {
         method: "POST",
         body: JSON.stringify(request),
-    });
+    }, { timeoutMs: 120_000 });
 };
 ElizaClient.prototype.activateN8nWorkflow = async function (id) {
     return this.fetch(`/api/n8n/workflows/${encodeURIComponent(id)}/activate`, {

package/packages/app-core/src/components/pages/AutomationsView.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"AutomationsView.d.ts","sourceRoot":"","sources":["../../../../../../../app-core/src/components/pages/AutomationsView.tsx"],"names":[],"mappings":"AAAA;;GAEG;AAsrKH,wBAAgB,eAAe,4CAO9B;AAED,wBAAgB,uBAAuB,4CAmBtC"}
+{"version":3,"file":"AutomationsView.d.ts","sourceRoot":"","sources":["../../../../../../../app-core/src/components/pages/AutomationsView.tsx"],"names":[],"mappings":"AAAA;;GAEG;AA+wKH,wBAAgB,eAAe,4CAO9B;AAED,wBAAgB,uBAAuB,4CAoDtC"}

package/packages/app-core/src/components/pages/AutomationsView.js

@@ -534,6 +534,15 @@ function useAutomationsViewController() {
     useEffect(() => {
         if (!selectedItemId)
             return;
+        // Exempt in-flight workflow drafts — they're not in allItems until
+        // generateWorkflowFromPrompt finishes and refreshAutomations
+        // surfaces the real workflow. Without this exemption the draft
+        // selection gets cleared mid-generation, the auto-select effect
+        // below picks lastSelectedIdRef (typically a task like Heartbeat),
+        // and the user lands somewhere unexpected — defeating the
+        // WorkflowGenerationProgress UI we just added on the draft pane.
+        if (selectedItemId.startsWith("workflow-draft:"))
+            return;
         if (!allItems.some((item) => item.id === selectedItemId)) {
             setSelectedItemId(null);
             setSelectedItemKind(null);
@@ -774,7 +783,42 @@ function useAutomationsViewController() {
         if (editorOpen || editingId || editingTaskId)
             return null;
         if (selectedItemId) {
-            return allItems.find((item) => item.id === selectedItemId) ?? null;
+            const found = allItems.find((item) => item.id === selectedItemId);
+            if (found)
+                return found;
+            // In-flight workflow draft (createWorkflowDraft set selectedItemId
+            // BEFORE refreshAutomations surfaced the real workflow). Synthesize
+            // a minimal draft item so AutomationDraftPane renders with the
+            // WorkflowGenerationProgress card during the LLM call.
+            //
+            // The `room` field is left null here. `activeWorkflowConversation`
+            // — the live conversation tied to this draft — lives in
+            // AutomationsLayout (a different scope from this controller hook),
+            // so we cannot read it from here without a larger refactor.
+            // Instead, handleDeleteDraft reads activeWorkflowConversation
+            // directly and falls back to it when item.room is missing on a
+            // synthesized draft (see the handler below).
+            if (selectedItemId.startsWith("workflow-draft:")) {
+                const draftId = selectedItemId.slice("workflow-draft:".length);
+                const synthesized = {
+                    id: selectedItemId,
+                    type: "automation_draft",
+                    source: "workflow_draft",
+                    title: "New workflow",
+                    description: "",
+                    status: "draft",
+                    enabled: false,
+                    system: false,
+                    isDraft: true,
+                    hasBackingWorkflow: false,
+                    updatedAt: null,
+                    draftId,
+                    schedules: [],
+                    room: null,
+                };
+                return synthesized;
+            }
+            return null;
         }
         return allItems[0] ?? null;
     }, [allItems, editingId, editingTaskId, editorOpen, selectedItemId]);
@@ -2216,6 +2260,33 @@ function AutomationsLayout() {
         try {
             await client.deleteN8nWorkflow(item.workflowId);
             await Promise.all(item.schedules.map((schedule) => client.deleteTrigger(schedule.id)));
+            // Also delete the chat conversation/room that backed this workflow.
+            // Without this, the `/api/automations` aggregator keeps surfacing the
+            // workflow row as a ghost entry because rooms with workflowId
+            // metadata are listed even when the underlying n8n workflow is gone.
+            const conversationId = item.room?.conversationId;
+            if (conversationId) {
+                try {
+                    await client.deleteConversation(conversationId);
+                }
+                catch (roomErr) {
+                    // Non-fatal: the workflow itself is deleted; surface the room
+                    // failure to the user but don't roll back.
+                    setPageNotice(`Workflow deleted, but its chat room could not be removed: ${roomErr instanceof Error ? roomErr.message : String(roomErr)}`);
+                }
+            }
+            if (selectedItemId === item.id) {
+                setSelectedItemId(null);
+                setSelectedItemKind(null);
+            }
+            // Mirror handleDeleteDraft: also clear the active workflow
+            // conversation if it's the one tied to the deleted workflow.
+            // Without this, refreshAutomationsWithDraftBinding keeps receiving
+            // a stale conversation reference on subsequent refreshes.
+            if (conversationId &&
+                activeWorkflowConversation?.id === conversationId) {
+                setActiveWorkflowConversation(null);
+            }
             await ctx.refreshAutomations();
         }
         catch (error) {
@@ -2228,7 +2299,15 @@ function AutomationsLayout() {
         finally {
             setWorkflowBusyId(null);
         }
-    }, [ctx, t]);
+    }, [
+        activeWorkflowConversation?.id,
+        ctx,
+        selectedItemId,
+        setActiveWorkflowConversation,
+        setSelectedItemId,
+        setSelectedItemKind,
+        t,
+    ]);
     const handleDuplicateWorkflow = useCallback(async (item) => {
         if (!item.workflowId) {
             return;
@@ -2247,7 +2326,13 @@ function AutomationsLayout() {
         }
     }, [ctx, selectWorkflowById]);
     const handleDeleteDraft = useCallback(async (item) => {
-        const conversationId = item.room?.conversationId;
+        // Synthesized in-flight drafts (workflow-draft:* ids surfaced
+        // before refreshAutomations completes) have no `room` because the
+        // controller's resolvedSelectedItem useMemo can't reach
+        // activeWorkflowConversation from its scope. Fall back to the
+        // live activeWorkflowConversation when item.room is missing —
+        // that's the same conversation the synthesized item represents.
+        const conversationId = item.room?.conversationId ?? activeWorkflowConversation?.id ?? null;
         if (!conversationId) {
             setPageNotice("This draft is missing its automation room.");
             return;
@@ -2377,5 +2462,33 @@ export function AutomationsView() {
 }
 export function AutomationsDesktopShell() {
     const controller = useAutomationsViewController();
-    return (_jsx(AutomationsViewContext.Provider, { value: controller, children: _jsx(AppWorkspaceChrome, { testId: "automations-workspace", chat: _jsx(AutomationsSidebarChat, { activeItem: controller.resolvedSelectedItem }), main: _jsx("div", { className: "flex flex-col flex-1 min-h-0 min-w-0 overflow-hidden", children: _jsx(AutomationsLayout, {}) }) }) }));
+    // Collapse the right-rail chat dock when no workflow / draft is
+    // selected. The Automations Overview page already has a centered hero
+    // compose ("Describe a task or workflow…") that's the canonical create
+    // surface; the bottom-right dock + hero showed two inputs at once and
+    // confused users. When a workflow or draft IS selected, the rail (and
+    // its PageScopedChatPane) opens so the user can edit/refine.
+    //
+    // Stay in CONTROLLED mode at all times. An earlier revision flipped
+    // between controlled (when nothing selected) and uncontrolled (when
+    // something selected); that left AppWorkspaceChrome's internal
+    // `internalCollapsed` stuck at `true` after the controlled phase, so
+    // the rail never opened on the first selection. Always-controlled
+    // avoids that transition entirely.
+    const hasScopedItem = controller.resolvedSelectedItem != null;
+    const [userCollapsedWhenSelected, setUserCollapsedWhenSelected] = useState(false);
+    // When the user clears the selection, also reset the toggle so the next
+    // selection starts with the rail open by default.
+    useEffect(() => {
+        if (!hasScopedItem)
+            setUserCollapsedWhenSelected(false);
+    }, [hasScopedItem]);
+    const chatCollapsed = hasScopedItem ? userCollapsedWhenSelected : true;
+    const handleToggleChat = useCallback((next) => {
+        // No-op when nothing is selected — the rail is force-closed in that
+        // state and the toggle button is hidden, so this should never fire.
+        if (hasScopedItem)
+            setUserCollapsedWhenSelected(next);
+    }, [hasScopedItem]);
+    return (_jsx(AutomationsViewContext.Provider, { value: controller, children: _jsx(AppWorkspaceChrome, { testId: "automations-workspace", chat: _jsx(AutomationsSidebarChat, { activeItem: controller.resolvedSelectedItem }), chatCollapsed: chatCollapsed, onToggleChat: handleToggleChat, hideCollapseButton: !hasScopedItem, main: _jsx("div", { className: "flex flex-col flex-1 min-h-0 min-w-0 overflow-hidden", children: _jsx(AutomationsLayout, {}) }) }) }));
 }

package/packages/app-core/src/components/pages/WorkflowGraphViewer.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"WorkflowGraphViewer.d.ts","sourceRoot":"","sources":["../../../../../../../app-core/src/components/pages/WorkflowGraphViewer.tsx"],"names":[],"mappings":"AA0BA,OAAO,KAAK,EAEV,iBAAiB,EACjB,WAAW,EAEZ,MAAM,6BAA6B,CAAC;AA6hBrC,UAAU,wBAAwB;IAChC,QAAQ,EAAE,WAAW,GAAG,IAAI,CAAC;IAC7B,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,YAAY,CAAC,EAAE,OAAO,CAAC;IACvB,qBAAqB,CAAC,EAAE,MAAM,CAAC;IAC/B,kBAAkB,CAAC,EAAE,MAAM,CAAC;IAC5B,WAAW,CAAC,EAAE,CAAC,QAAQ,EAAE,MAAM,KAAK,IAAI,CAAC;IACzC,kBAAkB,CAAC,EAAE,MAAM,IAAI,CAAC;IAChC,6EAA6E;IAC7E,MAAM,CAAC,EAAE,iBAAiB,GAAG,IAAI,CAAC;CACnC;AAED,wBAAgB,mBAAmB,CAAC,EAClC,QAAQ,EACR,OAAe,EACf,YAAoB,EACpB,qBAAgD,EAChD,kBAAqE,EACrE,WAAW,EACX,kBAAkB,EAClB,MAAM,GACP,EAAE,wBAAwB,2CAwQ1B"}
+{"version":3,"file":"WorkflowGraphViewer.d.ts","sourceRoot":"","sources":["../../../../../../../app-core/src/components/pages/WorkflowGraphViewer.tsx"],"names":[],"mappings":"AA0BA,OAAO,KAAK,EAEV,iBAAiB,EACjB,WAAW,EAEZ,MAAM,6BAA6B,CAAC;AAwrBrC,UAAU,wBAAwB;IAChC,QAAQ,EAAE,WAAW,GAAG,IAAI,CAAC;IAC7B,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,YAAY,CAAC,EAAE,OAAO,CAAC;IACvB,qBAAqB,CAAC,EAAE,MAAM,CAAC;IAC/B,kBAAkB,CAAC,EAAE,MAAM,CAAC;IAC5B,WAAW,CAAC,EAAE,CAAC,QAAQ,EAAE,MAAM,KAAK,IAAI,CAAC;IACzC,kBAAkB,CAAC,EAAE,MAAM,IAAI,CAAC;IAChC,6EAA6E;IAC7E,MAAM,CAAC,EAAE,iBAAiB,GAAG,IAAI,CAAC;CACnC;AAED,wBAAgB,mBAAmB,CAAC,EAClC,QAAQ,EACR,OAAe,EACf,YAAoB,EACpB,qBAAgD,EAChD,kBAAqE,EACrE,WAAW,EACX,kBAAkB,EAClB,MAAM,GACP,EAAE,wBAAwB,2CA+P1B"}

package/packages/app-core/src/components/pages/WorkflowGraphViewer.js

@@ -1,4 +1,4 @@
-import { jsxs as _jsxs, jsx as _jsx, Fragment as _Fragment } from "react/jsx-runtime";
+import { jsx as _jsx, jsxs as _jsxs, Fragment as _Fragment } from "react/jsx-runtime";
 import { Button, Dialog, DialogContent, DialogHeader, DialogTitle, Spinner, StatusBadge, } from "@elizaos/ui";
 import { Background, Controls, MiniMap, ReactFlow, } from "@xyflow/react";
 import { ExternalLink, Maximize2, X } from "lucide-react";
@@ -170,6 +170,77 @@ function graphChrome(uiTheme) {
         overlayChipText: "#60a5fa",
     };
 }
+// ── Generation progress overlay ───────────────────────────────────────────────
+/**
+ * Stage messages for `WorkflowGenerationProgress`. The plugin's workflow
+ * generation today is a single request/response, so the client cannot yet
+ * observe the actual stage in real time. We cycle through plausible labels
+ * on a fixed timer based on observed median latencies of each phase:
+ *   1. extractKeywords (fast — runtime-context provider + keyword LLM call)
+ *   2. searchNodes + credential filter + fetchRuntimeContext
+ *   3. generateWorkflow (LLM, slowest)
+ *   4. validateAndRepair + injectMissingCredentialBlocks
+ *   5. deployWorkflow + resolveCredentials + activate
+ *
+ * When the plugin grows a server-sent-events streaming endpoint, the timer
+ * can be replaced with real per-stage progress events.
+ */
+const WORKFLOW_GENERATION_STAGES = [
+    {
+        label: "Understanding your prompt",
+        hint: "Extracting keywords + matching providers",
+        startsAt: 0,
+    },
+    {
+        label: "Finding the right nodes",
+        hint: "Searching catalog + checking credentials",
+        startsAt: 3,
+    },
+    {
+        label: "Generating workflow",
+        hint: "Asking the LLM with runtime facts",
+        startsAt: 6,
+    },
+    {
+        label: "Validating + repairing",
+        hint: "Clamping versions + auto-fixing references",
+        startsAt: 18,
+    },
+    {
+        label: "Deploying to n8n",
+        hint: "Minting credentials + activating",
+        startsAt: 24,
+    },
+    {
+        label: "Almost done",
+        hint: "Wrapping up — this is taking a bit longer than usual",
+        startsAt: 35,
+    },
+];
+function WorkflowGenerationProgress({ chrome, }) {
+    const [elapsed, setElapsed] = useState(0);
+    useEffect(() => {
+        const start = Date.now();
+        const id = setInterval(() => {
+            setElapsed(Math.floor((Date.now() - start) / 1000));
+        }, 500);
+        return () => clearInterval(id);
+    }, []);
+    const currentIndex = WORKFLOW_GENERATION_STAGES.reduce((acc, stage, idx) => (elapsed >= stage.startsAt ? idx : acc), 0);
+    return (_jsx("div", { className: "w-full max-w-md rounded-xl border px-5 py-4 text-sm shadow-lg", style: {
+            background: chrome.overlayChipBg,
+            color: chrome.overlayChipText,
+            borderColor: chrome.overlayChipText,
+        }, children: _jsxs("div", { className: "flex items-start gap-3", children: [_jsx(Spinner, { className: "mt-0.5 h-4 w-4 shrink-0" }), _jsxs("div", { className: "min-w-0 flex-1 space-y-3", children: [_jsxs("div", { children: [_jsx("div", { className: "font-semibold", children: "Building your workflow\u2026" }), _jsx("div", { className: "text-xs opacity-70", children: "Generations usually take 10\u201330 seconds." })] }), _jsx("ol", { className: "space-y-1.5", children: WORKFLOW_GENERATION_STAGES.map((stage, idx) => {
+                                const isDone = idx < currentIndex;
+                                const isActive = idx === currentIndex;
+                                return (_jsxs("li", { className: `flex items-start gap-2 text-xs transition-opacity ${isDone || isActive ? "opacity-100" : "opacity-40"}`, children: [_jsx("span", { className: `mt-0.5 inline-flex h-3.5 w-3.5 shrink-0 items-center justify-center rounded-full border ${isDone
+                                                ? "border-current bg-current/15"
+                                                : isActive
+                                                    ? "border-current bg-current/15"
+                                                    : "border-current/40"}`, "aria-hidden": true, children: isDone ? (_jsx("svg", { viewBox: "0 0 12 12", className: "h-2.5 w-2.5", fill: "none", stroke: "currentColor", strokeWidth: "2", role: "img", "aria-label": "completed", children: _jsx("path", { d: "M2.5 6.5l2.5 2.5 4.5-5", strokeLinecap: "round", strokeLinejoin: "round" }) })) : isActive ? (_jsx("span", { className: "h-1.5 w-1.5 animate-pulse rounded-full bg-current", "aria-hidden": true })) : null }), _jsxs("span", { className: "min-w-0 flex-1", children: [_jsx("span", { className: `font-medium ${isActive ? "" : "opacity-70"}`, children: stage.label }), (isDone || isActive) && (_jsxs("span", { className: "ml-1.5 opacity-60", children: ["\u2014 ", stage.hint] }))] })] }, stage.label));
+                            }) })] })] }) }));
+}
 // ── Node detail drawer ────────────────────────────────────────────────────────
 const PARAM_TRUNCATE_LENGTH = 200;
 function ParamValue({ value }) {
@@ -317,10 +388,7 @@ export function WorkflowGraphViewer({ workflow, loading = false, isGenerating =
         ? "animate-pulse ring-2 ring-blue-500/50"
         : "ring-1 ring-border/30";
     const chrome = graphChrome(uiTheme);
-    return (_jsxs(_Fragment, { children: [_jsxs("div", { ref: containerRef, role: "img", "aria-label": ariaLabel, className: `relative overflow-hidden rounded-lg ${borderClass}`, style: { height: 420, background: chrome.canvasBg }, children: [loading && !hasNodes && (_jsx("div", { className: "absolute inset-0 flex items-center justify-center", children: _jsx(Spinner, { className: "h-6 w-6 text-muted" }) })), !loading && !hasNodes && !isGenerating && (_jsxs("div", { className: "absolute inset-0 flex flex-col items-center justify-center gap-3 px-6 text-center", children: [_jsx("p", { className: `text-sm font-medium ${chrome.emptyTitleClass}`, children: "Blank workflow" }), _jsx("p", { className: `max-w-sm text-xs ${chrome.emptyHelpClass}`, children: emptyStateHelpText }), onEmptyStateAction && (_jsx("button", { type: "button", className: "mt-1 rounded-md border border-border/40 bg-bg/40 px-3 py-1.5 text-xs text-txt hover:bg-bg/70 transition-colors", onClick: onEmptyStateAction, children: emptyStateActionLabel }))] })), isGenerating && (_jsx("div", { className: "absolute inset-0 z-10 flex items-center justify-center backdrop-blur-[1px]", style: { background: chrome.overlayBg }, children: _jsxs("div", { className: "flex items-center gap-2 rounded-full border border-blue-500/30 px-4 py-2 text-sm", style: {
-                                background: chrome.overlayChipBg,
-                                color: chrome.overlayChipText,
-                            }, children: [_jsx(Spinner, { className: "h-4 w-4" }), "Building workflow..."] }) })), !loading && (_jsx("div", { role: "presentation", className: "h-full w-full", onClick: (e) => e.stopPropagation(), onKeyDown: (e) => e.stopPropagation(), children: _jsxs(ReactFlow, { nodes: nodes, edges: isGenerating ? generatingEdges(edges) : edges, nodesDraggable: !isGenerating, nodesConnectable: false, edgesReconnectable: false, onNodeClick: handleNodeClick, fitView: true, fitViewOptions: { padding: 0.2, maxZoom: 1.2 }, proOptions: { hideAttribution: true }, "aria-label": ariaLabel, children: [_jsx(Background, { color: chrome.dots, gap: 20, size: 1 }), _jsx(Controls, { showInteractive: false }), hasNodes && (_jsx(MiniMap, { nodeColor: (n) => {
+    return (_jsxs(_Fragment, { children: [_jsxs("div", { ref: containerRef, role: "img", "aria-label": ariaLabel, className: `relative overflow-hidden rounded-lg ${borderClass}`, style: { height: 420, background: chrome.canvasBg }, children: [loading && !hasNodes && (_jsx("div", { className: "absolute inset-0 flex items-center justify-center", children: _jsx(Spinner, { className: "h-6 w-6 text-muted" }) })), !loading && !hasNodes && !isGenerating && (_jsxs("div", { className: "absolute inset-0 flex flex-col items-center justify-center gap-3 px-6 text-center", children: [_jsx("p", { className: `text-sm font-medium ${chrome.emptyTitleClass}`, children: "Blank workflow" }), _jsx("p", { className: `max-w-sm text-xs ${chrome.emptyHelpClass}`, children: emptyStateHelpText }), onEmptyStateAction && (_jsx("button", { type: "button", className: "mt-1 rounded-md border border-border/40 bg-bg/40 px-3 py-1.5 text-xs text-txt hover:bg-bg/70 transition-colors", onClick: onEmptyStateAction, children: emptyStateActionLabel }))] })), isGenerating && (_jsx("div", { className: "absolute inset-0 z-10 flex items-center justify-center backdrop-blur-[1px]", style: { background: chrome.overlayBg }, children: _jsx(WorkflowGenerationProgress, { chrome: chrome }) })), !loading && (_jsx("div", { role: "presentation", className: "h-full w-full", onClick: (e) => e.stopPropagation(), onKeyDown: (e) => e.stopPropagation(), children: _jsxs(ReactFlow, { nodes: nodes, edges: isGenerating ? generatingEdges(edges) : edges, nodesDraggable: !isGenerating, nodesConnectable: false, edgesReconnectable: false, onNodeClick: handleNodeClick, fitView: true, fitViewOptions: { padding: 0.2, maxZoom: 1.2 }, proOptions: { hideAttribution: true }, "aria-label": ariaLabel, children: [_jsx(Background, { color: chrome.dots, gap: 20, size: 1 }), _jsx(Controls, { showInteractive: false }), hasNodes && (_jsx(MiniMap, { nodeColor: (n) => {
                                         const colors = n.data
                                             ?.colors;
                                         return colors?.border ?? "#475569";

package/packages/app-core/src/components/pages/page-scoped-conversations.js

@@ -32,7 +32,7 @@ export const PAGE_SCOPE_COPY = {
     "page-automations": {
         title: "Automations",
         body: "Use me to create or inspect a task or n8n workflow. Tell me the trigger, timing, and result.",
-        systemAddendum: "You are answering inside the Automations view. The user can create tasks and n8n workflows, attach either one to a schedule or event, configure wake mode, max runs, and enabled state, browse templates, inspect existing automations, and troubleshoot failed runs. Treat tasks as simple prompt-driven automations and workflows as multi-step n8n pipelines. Recommend the smaller task shape unless the user clearly needs a multi-step pipeline. Use createTriggerTaskAction and manageTasksAction when the request is concrete. Reference live tasks and workflows in context by display name. Never fabricate automation names.",
+        systemAddendum: "You are answering inside the Automations view. The user can create tasks and n8n workflows, attach either one to a schedule or event, configure wake mode, max runs, and enabled state, browse templates, inspect existing automations, and troubleshoot failed runs. Treat tasks as simple prompt-driven automations and workflows as multi-step n8n pipelines. Recommend the smaller task shape unless the user clearly needs a multi-step pipeline. When the user describes a concrete automation, dispatch it via the planner's <actions> field using <action><name>CREATE_TRIGGER_TASK</name></action> for scheduled or event tasks, or <action><name>MANAGE_TASKS</name></action> for task list operations. Reference live tasks and workflows in context by display name. Never fabricate automation names.",
     },
     "page-apps": {
         title: "Apps chat",

package/packages/app-core/src/components/workspace/AppWorkspaceChrome.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"AppWorkspaceChrome.d.ts","sourceRoot":"","sources":["../../../../../../../app-core/src/components/workspace/AppWorkspaceChrome.tsx"],"names":[],"mappings":"AAYA,OAAO,EAEL,KAAK,GAAG,EACR,KAAK,SAAS,EAOf,MAAM,OAAO,CAAC;AAGf,OAAO,EAEL,KAAK,uBAAuB,EAC7B,MAAM,gCAAgC,CAAC;AACxC,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,uCAAuC,CAAC;AAEvE,eAAO,MAAM,qCAAqC,wCACX,CAAC;AACxC,eAAO,MAAM,2CAA2C,oCACrB,CAAC;AAOpC,UAAU,kCAAkC;IAC1C,YAAY,EAAE,MAAM,IAAI,CAAC;IACzB,QAAQ,EAAE,MAAM,IAAI,CAAC;IACrB,UAAU,EAAE,OAAO,CAAC;CACrB;AAKD,wBAAgB,yBAAyB,IAAI,kCAAkC,GAAG,IAAI,CAErF;AAED,UAAU,mCAAmC;IAC3C,MAAM,CAAC,EAAE,MAAM,CAAC;CACjB;AAED,wBAAgB,8BAA8B,CAAC,EAC7C,MAAsC,GACvC,EAAE,mCAAmC,GAAG,GAAG,CAAC,OAAO,GAAG,IAAI,CAgB1D;AA0HD,MAAM,WAAW,uBAAuB;IACtC,wDAAwD;IACxD,GAAG,CAAC,EAAE,SAAS,CAAC;IAChB,kCAAkC;IAClC,IAAI,EAAE,SAAS,CAAC;IAChB;;;OAGG;IACH,IAAI,CAAC,EAAE,SAAS,CAAC;IACjB;;;OAGG;IACH,SAAS,CAAC,EAAE,SAAS,CAAC;IACtB;;;OAGG;IACH,uBAAuB,CAAC,EAAE,IAAI,CAC5B,uBAAuB,EACvB,OAAO,GAAG,eAAe,CAC1B,CAAC;IACF;;;OAGG;IACH,aAAa,CAAC,EAAE,OAAO,CAAC;IACxB;;;OAGG;IACH,YAAY,CAAC,EAAE,CAAC,IAAI,EAAE,OAAO,KAAK,IAAI,CAAC;IACvC;;;;OAIG;IACH,oBAAoB,CAAC,EAAE,OAAO,CAAC;IAC/B,gFAAgF;IAChF,kBAAkB,CAAC,EAAE,OAAO,CAAC;IAC7B,gFAAgF;IAChF,YAAY,CAAC,EAAE,OAAO,CAAC;IACvB,+CAA+C;IAC/C,MAAM,CAAC,EAAE,MAAM,CAAC;CACjB;AAyBD,2EAA2E;AAC3E,wBAAgB,kBAAkB,CAAC,EACjC,GAAG,EACH,IAAI,EACJ,IAAI,EACJ,SAAS,EACT,uBAAuB,EACvB,aAAa,EAAE,iBAAiB,EAChC,YAAY,EACZ,oBAA4B,EAC5B,kBAA0B,EAC1B,YAAoB,EACpB,MAA+B,GAChC,EAAE,uBAAuB,GAAG,GAAG,CAAC,OAAO,CAgRvC"}
+{"version":3,"file":"AppWorkspaceChrome.d.ts","sourceRoot":"","sources":["../../../../../../../app-core/src/components/workspace/AppWorkspaceChrome.tsx"],"names":[],"mappings":"AAYA,OAAO,EAEL,KAAK,GAAG,EACR,KAAK,SAAS,EAOf,MAAM,OAAO,CAAC;AAGf,OAAO,EAEL,KAAK,uBAAuB,EAC7B,MAAM,gCAAgC,CAAC;AACxC,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,uCAAuC,CAAC;AAEvE,eAAO,MAAM,qCAAqC,wCACX,CAAC;AACxC,eAAO,MAAM,2CAA2C,oCACrB,CAAC;AAOpC,UAAU,kCAAkC;IAC1C,YAAY,EAAE,MAAM,IAAI,CAAC;IACzB,QAAQ,EAAE,MAAM,IAAI,CAAC;IACrB,UAAU,EAAE,OAAO,CAAC;CACrB;AAKD,wBAAgB,yBAAyB,IAAI,kCAAkC,GAAG,IAAI,CAErF;AAED,UAAU,mCAAmC;IAC3C,MAAM,CAAC,EAAE,MAAM,CAAC;CACjB;AAED,wBAAgB,8BAA8B,CAAC,EAC7C,MAAsC,GACvC,EAAE,mCAAmC,GAAG,GAAG,CAAC,OAAO,GAAG,IAAI,CAgB1D;AA0HD,MAAM,WAAW,uBAAuB;IACtC,wDAAwD;IACxD,GAAG,CAAC,EAAE,SAAS,CAAC;IAChB,kCAAkC;IAClC,IAAI,EAAE,SAAS,CAAC;IAChB;;;OAGG;IACH,IAAI,CAAC,EAAE,SAAS,CAAC;IACjB;;;OAGG;IACH,SAAS,CAAC,EAAE,SAAS,CAAC;IACtB;;;OAGG;IACH,uBAAuB,CAAC,EAAE,IAAI,CAC5B,uBAAuB,EACvB,OAAO,GAAG,eAAe,CAC1B,CAAC;IACF;;;OAGG;IACH,aAAa,CAAC,EAAE,OAAO,CAAC;IACxB;;;OAGG;IACH,YAAY,CAAC,EAAE,CAAC,IAAI,EAAE,OAAO,KAAK,IAAI,CAAC;IACvC;;;;OAIG;IACH,oBAAoB,CAAC,EAAE,OAAO,CAAC;IAC/B,gFAAgF;IAChF,kBAAkB,CAAC,EAAE,OAAO,CAAC;IAC7B,gFAAgF;IAChF,YAAY,CAAC,EAAE,OAAO,CAAC;IACvB,+CAA+C;IAC/C,MAAM,CAAC,EAAE,MAAM,CAAC;CACjB;AAyBD,2EAA2E;AAC3E,wBAAgB,kBAAkB,CAAC,EACjC,GAAG,EACH,IAAI,EACJ,IAAI,EACJ,SAAS,EACT,uBAAuB,EACvB,aAAa,EAAE,iBAAiB,EAChC,YAAY,EACZ,oBAA4B,EAC5B,kBAA0B,EAC1B,YAAoB,EACpB,MAA+B,GAChC,EAAE,uBAAuB,GAAG,GAAG,CAAC,OAAO,CA6RvC"}

package/packages/app-core/src/components/workspace/AppWorkspaceChrome.js

@@ -79,14 +79,27 @@ export function AppWorkspaceChrome({ nav, main, chat, chatScope, pageScopedChatP
     const collapsed = isControlled
         ? (chatCollapsedProp ?? false)
         : internalCollapsed;
+    // Controlled mode is the source of truth on every viewport — including
+    // mobile. When the page passes chatCollapsed=true (e.g. forcing a
+    // single canonical compose surface in an empty state), the mobile
+    // pane-switcher must respect that and not flip back to open via local
+    // mobileChatOpen state.
     const effectiveCollapsed = chatDisabled
         ? true
-        : isMobileViewport
-            ? !mobileChatOpen
-            : collapsed;
+        : isControlled
+            ? collapsed
+            : isMobileViewport
+                ? !mobileChatOpen
+                : collapsed;
     const handleToggle = useCallback((next) => {
         if (isMobileViewport) {
             mobileSidebarControl?.setOpen(false);
+            if (isControlled) {
+                // Page is the source of truth on mobile too — defer to it
+                // instead of touching local mobileChatOpen state.
+                onToggleChat?.(next);
+                return;
+            }
             setMobileChatOpen(chatDisabled ? false : !next);
             return;
         }
@@ -200,7 +213,7 @@ export function AppWorkspaceChrome({ nav, main, chat, chatScope, pageScopedChatP
     const chatContent = chat ??
         (chatScope ? (_jsx(PageScopedChatPane, { ...pageScopedChatPaneProps, scope: chatScope })) : (_jsx(ChatView, { variant: "default" })));
     return (_jsx(WorkspaceMobileSidebarControlsContext.Provider, { value: mobileSidebarControlsValue, children: _jsx(AppWorkspaceChatChromeContext.Provider, { value: chatChromeContextValue, children: _jsxs("div", { className: `flex min-h-0 min-w-0 w-full flex-1 bg-bg pb-[var(--eliza-mobile-nav-offset,0px)] ${isMobileViewport ? "flex-col" : ""}`, "data-testid": testId, children: [isMobileViewport &&
-                        (!chatDisabled || mobileSidebarControl !== null) ? (_jsx(MobileWorkspacePaneSwitcher, { chatAvailable: !chatDisabled, chatOpen: !effectiveCollapsed, sidebar: mobileSidebarControl, onChat: () => handleToggle(false), onMain: handleOpenMobileMain, onSidebar: handleOpenMobileSidebar })) : null, _jsxs("div", { className: `relative min-h-0 min-w-0 flex-1 flex-col overflow-hidden ${isMobileViewport && !effectiveCollapsed ? "hidden" : "flex"}`, children: [nav, _jsx("div", { className: "relative flex min-h-0 flex-1 flex-col overflow-hidden", children: main })] }), chatDisabled ? null : effectiveCollapsed ? (_jsx("aside", { className: "w-0 min-w-0 shrink-0", "data-testid": `${testId}-chat-sidebar`, "data-collapsed": true, children: isMobileViewport ? null : (_jsx(AppWorkspaceChatDockToggleButton, { collapsed: true, testId: `${testId}-chat-expand` })) })) : (_jsxs(_Fragment, { children: [isMobileViewport ? (_jsx("aside", { className: "flex min-h-0 min-w-0 w-full flex-1 flex-col overflow-hidden bg-bg", "data-testid": `${testId}-chat-sidebar`, children: _jsx("div", { className: "flex min-h-0 flex-1 flex-col overflow-hidden", children: chatContent }) })) : null, !isMobileViewport ? (_jsxs("aside", { className: "relative flex shrink-0 flex-col overflow-hidden bg-bg", style: {
+                        (!chatDisabled || mobileSidebarControl !== null) ? (_jsx(MobileWorkspacePaneSwitcher, { chatAvailable: !chatDisabled, chatOpen: !effectiveCollapsed, sidebar: mobileSidebarControl, onChat: () => handleToggle(false), onMain: handleOpenMobileMain, onSidebar: handleOpenMobileSidebar })) : null, _jsxs("div", { className: `relative min-h-0 min-w-0 flex-1 flex-col overflow-hidden ${isMobileViewport && !effectiveCollapsed ? "hidden" : "flex"}`, children: [nav, _jsx("div", { className: "relative flex min-h-0 flex-1 flex-col overflow-hidden", children: main })] }), chatDisabled ? null : effectiveCollapsed ? (_jsx("aside", { className: "w-0 min-w-0 shrink-0", "data-testid": `${testId}-chat-sidebar`, "data-collapsed": true, children: !isMobileViewport && !hideCollapseButton ? (_jsx(AppWorkspaceChatDockToggleButton, { collapsed: true, testId: `${testId}-chat-expand` })) : null })) : (_jsxs(_Fragment, { children: [isMobileViewport ? (_jsx("aside", { className: "flex min-h-0 min-w-0 w-full flex-1 flex-col overflow-hidden bg-bg", "data-testid": `${testId}-chat-sidebar`, children: _jsx("div", { className: "flex min-h-0 flex-1 flex-col overflow-hidden", children: chatContent }) })) : null, !isMobileViewport ? (_jsxs("aside", { className: "relative flex shrink-0 flex-col overflow-hidden bg-bg", style: {
                                     width: `${chatWidth}px`,
                                     minWidth: `${chatWidth}px`,
                                 }, "data-testid": `${testId}-chat-sidebar`, children: [_jsx("hr", { "aria-label": "Resize chat", "aria-orientation": "vertical", "aria-valuemin": 0, "aria-valuemax": 100, "aria-valuenow": 50, tabIndex: 0, "data-testid": `${testId}-chat-resize-handle`, onPointerDown: handleResizePointerDown, className: "absolute inset-y-0 left-0 z-20 m-0 h-full w-3 -translate-x-1/2 cursor-col-resize touch-none select-none border-0 bg-transparent transition-colors hover:bg-accent/20" }), _jsx("div", { className: "flex min-h-0 flex-1 flex-col overflow-hidden", children: chatContent })] })) : null, !isMobileViewport && !hideCollapseButton ? (_jsx(AppWorkspaceChatDockToggleButton, { collapsed: false, testId: `${testId}-chat-collapse` })) : null] }))] }) }) }));

package/packages/app-core/src/i18n/locales/en.json

@@ -135,6 +135,8 @@
     "automations.n8n.deleteConfirmMessage": "Permanently delete this workflow. This cannot be undone.",
     "automations.n8n.deleteConfirmWorkflow": "Delete \"{{name}}\"? This cannot be undone.",
     "automations.n8n.deleteFailed": "Failed to delete workflow.",
+    "automations.n8n.detailEmptyBody": "Select a workflow from the sidebar to view its details, or switch to the dashboard to create a new one.",
+    "automations.n8n.detailEmptyHeading": "No workflow selected",
     "automations.n8n.deleteWorkflow": "Delete workflow",
     "automations.n8n.errorDeleteWorkflow": "Failed to delete workflow: {{message}}",
     "automations.n8n.errorLoadStatus": "Failed to load n8n status: {{message}}",

package/packages/shared/src/index.d.ts

@@ -11,8 +11,6 @@ export * from "./connectors";
 export * from "./contracts";
 export * from "./dev-settings-banner-style";
 export * from "./dev-settings-table";
-export type { ConnectorAdminWhitelist, RoleCheckResult, RoleGrantSource, RoleName, RolesConfig as ElizaCoreRolesConfig, RolesWorldMetadata, ServerOwnershipState, } from "./eliza-core-roles";
-export { canModifyRole, checkSenderPrivateAccess, checkSenderRole, findWorldsForOwner, getConfiguredOwnerEntityIds, getConnectorAdminWhitelist, getEntityRole, getLiveEntityMetadataFromMessage, getUserServerRole, hasConfiguredCanonicalOwner, matchEntityToConnectorAdminWhitelist, normalizeRole, ROLE_RANK, resolveCanonicalOwnerId, resolveCanonicalOwnerIdForMessage, resolveEntityRole, resolveWorldForMessage, setConnectorAdminWhitelist, setEntityRole, } from "./eliza-core-roles";
 export * from "./env-utils";
 export * from "./onboarding-presets";
 export * from "./onboarding-presets.characters";

package/packages/shared/src/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../../../shared/src/index.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAGH,cAAc,gBAAgB,CAAC;AAE/B,cAAc,aAAa,CAAC;AAI5B,YAAY,EACV,YAAY,EACZ,qBAAqB,EACrB,gCAAgC,EAChC,mBAAmB,EACnB,WAAW,EACX,yBAAyB,EACzB,mBAAmB,EACnB,gBAAgB,EAChB,qBAAqB,EACrB,oBAAoB,EACpB,YAAY,EACZ,eAAe,EACf,WAAW,EACX,UAAU,EACV,iBAAiB,EACjB,sBAAsB,EACtB,eAAe,EACf,iBAAiB,EACjB,aAAa,EACb,oBAAoB,EACpB,uBAAuB,EACvB,gBAAgB,EAChB,iBAAiB,EACjB,iBAAiB,EACjB,WAAW,EACX,sBAAsB,EACtB,kBAAkB,EAClB,mBAAmB,EACnB,cAAc,EACd,kBAAkB,EAClB,qBAAqB,EACrB,eAAe,EACf,mBAAmB,EACnB,UAAU,EACV,SAAS,EACT,cAAc,EACd,2BAA2B,EAC3B,iBAAiB,EACjB,qBAAqB,EACrB,eAAe,EACf,WAAW,EACX,eAAe,EACf,gBAAgB,EAChB,4BAA4B,EAC5B,0BAA0B,EAC1B,yBAAyB,EACzB,cAAc,EACd,iBAAiB,EACjB,eAAe,EACf,eAAe,EACf,aAAa,EACb,sBAAsB,EACtB,gCAAgC,EAChC,iBAAiB,EACjB,0BAA0B,EAC1B,0BAA0B,EAC1B,+BAA+B,EAC/B,gCAAgC,EAChC,6BAA6B,EAC7B,kBAAkB,EAClB,mBAAmB,EACnB,iBAAiB,EACjB,mBAAmB,EACnB,sBAAsB,EACtB,oBAAoB,EACpB,gBAAgB,EAChB,UAAU,EACV,iBAAiB,EACjB,iBAAiB,EACjB,gBAAgB,EAChB,oBAAoB,EACpB,WAAW,EACX,gBAAgB,EAChB,uBAAuB,EACvB,yBAAyB,EACzB,qBAAqB,EAErB,oBAAoB,IAAI,iCAAiC,EACzD,gBAAgB,IAAI,6BAA6B,EACjD,yBAAyB,EACzB,mBAAmB,EACnB,eAAe,EACf,eAAe,EACf,eAAe,EACf,aAAa,EACb,mBAAmB,EACnB,iBAAiB,EACjB,gBAAgB,EAChB,mCAAmC,EACnC,4BAA4B,EAC5B,wBAAwB,EACxB,6BAA6B,EAC7B,6BAA6B,EAC7B,4BAA4B,EAC5B,2BAA2B,EAC3B,aAAa,EACb,mBAAmB,EACnB,YAAY,EACZ,eAAe,EACf,kBAAkB,EAClB,qBAAqB,EACrB,sBAAsB,EACtB,qBAAqB,EACrB,kBAAkB,EAClB,cAAc,EACd,QAAQ,EACR,iBAAiB,EACjB,qBAAqB,EACrB,qBAAqB,EACrB,mBAAmB,EACnB,YAAY,EACZ,SAAS,EACT,0BAA0B,EAC1B,cAAc,EACd,iBAAiB,EACjB,mBAAmB,EACnB,YAAY,EACZ,iBAAiB,EACjB,mBAAmB,EACnB,iBAAiB,EACjB,aAAa,EACb,iBAAiB,EACjB,mBAAmB,EACnB,WAAW,EACX,eAAe,EACf,SAAS,EACT,mBAAmB,EACnB,gBAAgB,EAChB,WAAW,EACX,sBAAsB,EACtB,qBAAqB,EACrB,oBAAoB,EACpB,WAAW,EACX,YAAY,EACZ,mBAAmB,EACnB,gBAAgB,EAChB,WAAW,EACX,WAAW,EACX,SAAS,EACT,OAAO,EACP,sBAAsB,EACtB,WAAW,EACX,YAAY,EACZ,SAAS,EACT,kBAAkB,EAClB,UAAU,GACX,MAAM,gBAAgB,CAAC;AACxB,cAAc,cAAc,CAAC;AAK7B,cAAc,aAAa,CAAC;AAC5B,cAAc,6BAA6B,CAAC;AAC5C,cAAc,sBAAsB,CAAC;AACrC,YAAY,EACV,uBAAuB,EACvB,eAAe,EACf,eAAe,EACf,QAAQ,EACR,WAAW,IAAI,oBAAoB,EACnC,kBAAkB,EAClB,oBAAoB,GACrB,MAAM,oBAAoB,CAAC;AAK5B,OAAO,EACL,aAAa,EACb,wBAAwB,EACxB,eAAe,EACf,kBAAkB,EAClB,2BAA2B,EAC3B,0BAA0B,EAC1B,aAAa,EACb,gCAAgC,EAChC,iBAAiB,EACjB,2BAA2B,EAC3B,oCAAoC,EACpC,aAAa,EACb,SAAS,EACT,uBAAuB,EACvB,iCAAiC,EACjC,iBAAiB,EACjB,sBAAsB,EACtB,0BAA0B,EAC1B,aAAa,GACd,MAAM,oBAAoB,CAAC;AAC5B,cAAc,aAAa,CAAC;AAC5B,cAAc,sBAAsB,CAAC;AACrC,cAAc,iCAAiC,CAAC;AAChD,cAAc,yBAAyB,CAAC;AACxC,cAAc,WAAW,CAAC;AAC1B,cAAc,eAAe,CAAC;AAE9B,OAAO,EACL,2BAA2B,EAC3B,wBAAwB,EACxB,yBAAyB,GAC1B,MAAM,kBAAkB,CAAC;AAC1B,cAAc,eAAe,CAAC;AAC9B,cAAc,UAAU,CAAC;AACzB,cAAc,eAAe,CAAC;AAC9B,cAAc,uBAAuB,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../../../shared/src/index.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAGH,cAAc,gBAAgB,CAAC;AAE/B,cAAc,aAAa,CAAC;AAI5B,YAAY,EACV,YAAY,EACZ,qBAAqB,EACrB,gCAAgC,EAChC,mBAAmB,EACnB,WAAW,EACX,yBAAyB,EACzB,mBAAmB,EACnB,gBAAgB,EAChB,qBAAqB,EACrB,oBAAoB,EACpB,YAAY,EACZ,eAAe,EACf,WAAW,EACX,UAAU,EACV,iBAAiB,EACjB,sBAAsB,EACtB,eAAe,EACf,iBAAiB,EACjB,aAAa,EACb,oBAAoB,EACpB,uBAAuB,EACvB,gBAAgB,EAChB,iBAAiB,EACjB,iBAAiB,EACjB,WAAW,EACX,sBAAsB,EACtB,kBAAkB,EAClB,mBAAmB,EACnB,cAAc,EACd,kBAAkB,EAClB,qBAAqB,EACrB,eAAe,EACf,mBAAmB,EACnB,UAAU,EACV,SAAS,EACT,cAAc,EACd,2BAA2B,EAC3B,iBAAiB,EACjB,qBAAqB,EACrB,eAAe,EACf,WAAW,EACX,eAAe,EACf,gBAAgB,EAChB,4BAA4B,EAC5B,0BAA0B,EAC1B,yBAAyB,EACzB,cAAc,EACd,iBAAiB,EACjB,eAAe,EACf,eAAe,EACf,aAAa,EACb,sBAAsB,EACtB,gCAAgC,EAChC,iBAAiB,EACjB,0BAA0B,EAC1B,0BAA0B,EAC1B,+BAA+B,EAC/B,gCAAgC,EAChC,6BAA6B,EAC7B,kBAAkB,EAClB,mBAAmB,EACnB,iBAAiB,EACjB,mBAAmB,EACnB,sBAAsB,EACtB,oBAAoB,EACpB,gBAAgB,EAChB,UAAU,EACV,iBAAiB,EACjB,iBAAiB,EACjB,gBAAgB,EAChB,oBAAoB,EACpB,WAAW,EACX,gBAAgB,EAChB,uBAAuB,EACvB,yBAAyB,EACzB,qBAAqB,EAErB,oBAAoB,IAAI,iCAAiC,EACzD,gBAAgB,IAAI,6BAA6B,EACjD,yBAAyB,EACzB,mBAAmB,EACnB,eAAe,EACf,eAAe,EACf,eAAe,EACf,aAAa,EACb,mBAAmB,EACnB,iBAAiB,EACjB,gBAAgB,EAChB,mCAAmC,EACnC,4BAA4B,EAC5B,wBAAwB,EACxB,6BAA6B,EAC7B,6BAA6B,EAC7B,4BAA4B,EAC5B,2BAA2B,EAC3B,aAAa,EACb,mBAAmB,EACnB,YAAY,EACZ,eAAe,EACf,kBAAkB,EAClB,qBAAqB,EACrB,sBAAsB,EACtB,qBAAqB,EACrB,kBAAkB,EAClB,cAAc,EACd,QAAQ,EACR,iBAAiB,EACjB,qBAAqB,EACrB,qBAAqB,EACrB,mBAAmB,EACnB,YAAY,EACZ,SAAS,EACT,0BAA0B,EAC1B,cAAc,EACd,iBAAiB,EACjB,mBAAmB,EACnB,YAAY,EACZ,iBAAiB,EACjB,mBAAmB,EACnB,iBAAiB,EACjB,aAAa,EACb,iBAAiB,EACjB,mBAAmB,EACnB,WAAW,EACX,eAAe,EACf,SAAS,EACT,mBAAmB,EACnB,gBAAgB,EAChB,WAAW,EACX,sBAAsB,EACtB,qBAAqB,EACrB,oBAAoB,EACpB,WAAW,EACX,YAAY,EACZ,mBAAmB,EACnB,gBAAgB,EAChB,WAAW,EACX,WAAW,EACX,SAAS,EACT,OAAO,EACP,sBAAsB,EACtB,WAAW,EACX,YAAY,EACZ,SAAS,EACT,kBAAkB,EAClB,UAAU,GACX,MAAM,gBAAgB,CAAC;AACxB,cAAc,cAAc,CAAC;AAK7B,cAAc,aAAa,CAAC;AAC5B,cAAc,6BAA6B,CAAC;AAC5C,cAAc,sBAAsB,CAAC;AAOrC,cAAc,aAAa,CAAC;AAC5B,cAAc,sBAAsB,CAAC;AACrC,cAAc,iCAAiC,CAAC;AAChD,cAAc,yBAAyB,CAAC;AACxC,cAAc,WAAW,CAAC;AAC1B,cAAc,eAAe,CAAC;AAE9B,OAAO,EACL,2BAA2B,EAC3B,wBAAwB,EACxB,yBAAyB,GAC1B,MAAM,kBAAkB,CAAC;AAC1B,cAAc,eAAe,CAAC;AAC9B,cAAc,UAAU,CAAC;AACzB,cAAc,eAAe,CAAC;AAC9B,cAAc,uBAAuB,CAAC"}

package/packages/shared/src/index.js

@@ -16,11 +16,12 @@ export * from "./connectors";
 export * from "./contracts";
 export * from "./dev-settings-banner-style";
 export * from "./dev-settings-table";
-// `eliza-core-roles` defines its own `RolesConfig` that overlaps with the
-// `RolesConfig` re-exported from `@elizaos/core` via `./config`. Skip the
-// duplicate name here — callers needing the vendored role helpers should use
-// the named exports below.
-export { canModifyRole, checkSenderPrivateAccess, checkSenderRole, findWorldsForOwner, getConfiguredOwnerEntityIds, getConnectorAdminWhitelist, getEntityRole, getLiveEntityMetadataFromMessage, getUserServerRole, hasConfiguredCanonicalOwner, matchEntityToConnectorAdminWhitelist, normalizeRole, ROLE_RANK, resolveCanonicalOwnerId, resolveCanonicalOwnerIdForMessage, resolveEntityRole, resolveWorldForMessage, setConnectorAdminWhitelist, setEntityRole, } from "./eliza-core-roles";
+// `eliza-core-roles` is intentionally NOT re-exported from this barrel.
+// It pulls runtime imports (`logger`, `createUniqueUuid`) from `@elizaos/core`,
+// which would drag the entire `@elizaos/core` source graph (plugin-sql,
+// transformers, onnxruntime) into every consumer of `@elizaos/shared`.
+// Callers that need the vendored role helpers must import them through the
+// dedicated subpath: `import { ROLE_RANK } from "@elizaos/shared/eliza-core-roles"`.
 export * from "./env-utils";
 export * from "./onboarding-presets";
 export * from "./onboarding-presets.characters";

package/packages/typescript/src/prompts.d.ts

@@ -35,8 +35,8 @@ export declare const longTermExtractionTemplate = "# Task: Extract Long-Term Mem
 export declare const LONG_TERM_EXTRACTION_TEMPLATE = "# Task: Extract Long-Term Memory (Strict Criteria)\n\nYou are analyzing a conversation to extract ONLY the most critical, persistent information about the user using cognitive science memory categories.\n\n# Recent Messages\n{{recentMessages}}\n\n# Current Long-Term Memories\n{{existingMemories}}\n\n# Memory Categories (Based on Cognitive Science)\n\n## 1. EPISODIC Memory\nPersonal experiences and specific events with temporal/spatial context.\n**Examples:**\n- \"User completed migration project from MongoDB to PostgreSQL in Q2 2024\"\n- \"User encountered authentication bug in production on March 15th\"\n- \"User had a negative experience with Docker networking in previous job\"\n\n**Requirements:**\n- Must include WHO did WHAT, WHEN/WHERE\n- Must be a specific, concrete event (not a pattern)\n- Must have significant impact or relevance to future work\n\n## 2. SEMANTIC Memory\nGeneral facts, concepts, knowledge, and established truths about the user.\n**Examples:**\n- \"User is a senior backend engineer with 8 years experience\"\n- \"User specializes in distributed systems and microservices architecture\"\n- \"User's primary programming language is TypeScript\"\n- \"User works at Acme Corp as technical lead\"\n\n**Requirements:**\n- Must be factual, timeless information\n- Must be explicitly stated or demonstrated conclusively\n- No speculation or inference from single instances\n- Core identity, expertise, or knowledge only\n\n## 3. PROCEDURAL Memory\nSkills, workflows, methodologies, and how-to knowledge.\n**Examples:**\n- \"User follows strict TDD workflow: write tests first, then implementation\"\n- \"User prefers git rebase over merge to maintain linear history\"\n- \"User's debugging process: check logs \u2192 reproduce locally \u2192 binary search\"\n- \"User always writes JSDoc comments before implementing functions\"\n\n**Requirements:**\n- Must describe HOW user does something\n- Must be a repeated, consistent pattern (seen 3+ times or explicitly stated as standard practice)\n- Must be a workflow, methodology, or skill application\n- Not one-off preferences\n\n# ULTRA-STRICT EXTRACTION CRITERIA\n\n## DO EXTRACT (Only These):\n\n**EPISODIC:**\n- Significant completed projects or milestones\n- Important bugs, incidents, or problems encountered\n- Major decisions made with lasting impact\n- Formative experiences that shape future work\n\n**SEMANTIC:**\n- Professional identity (role, title, company)\n- Core expertise and specializations (stated explicitly or demonstrated conclusively)\n- Primary languages, frameworks, or tools (not exploratory use)\n- Established facts about their work context\n\n**PROCEDURAL:**\n- Consistent workflows demonstrated 3+ times or explicitly stated\n- Standard practices user always follows\n- Methodology preferences with clear rationale\n- Debugging, testing, or development processes\n\n## NEVER EXTRACT:\n\n- **One-time requests or tasks** (e.g., \"can you generate an image\", \"help me debug this\")\n- **Casual conversations** without lasting significance\n- **Exploratory questions** (e.g., \"how does X work?\")\n- **Temporary context** (current bug, today's task)\n- **Preferences from single occurrence** (e.g., user asked for code once)\n- **Social pleasantries** (thank you, greetings)\n- **Testing or experimentation** (trying out a feature)\n- **Common patterns everyone has** (likes clear explanations)\n- **Situational information** (working on feature X today)\n- **Opinions without persistence** (single complaint, isolated praise)\n- **General knowledge** (not specific to user)\n\n# Quality Gates (ALL Must Pass)\n\n1. **Significance Test**: Will this matter in 3+ months?\n2. **Specificity Test**: Is this concrete and actionable?\n3. **Evidence Test**: Is there strong evidence (3+ instances OR explicit self-identification)?\n4. **Uniqueness Test**: Is this specific to THIS user (not generic)?\n5. **Confidence Test**: Confidence must be >= 0.85 (be VERY conservative)\n6. **Non-Redundancy Test**: Does this add NEW information not in existing memories?\n\n# Confidence Scoring (Be Conservative)\n\n- **0.95-1.0**: User explicitly stated as core identity/practice AND demonstrated multiple times\n- **0.85-0.94**: User explicitly stated OR consistently demonstrated 5+ times\n- **0.75-0.84**: Strong pattern (3-4 instances) with supporting context\n- **Below 0.75**: DO NOT EXTRACT (insufficient evidence)\n\n# Critical Instructions\n\n1. **Default to NOT extracting** - When in doubt, skip it\n2. **Require overwhelming evidence** - One or two mentions is NOT enough\n3. **Focus on what's PERSISTENT** - Not what's temporary or situational\n4. **Verify against existing memories** - Don't duplicate or contradict\n5. **Maximum 2-3 extractions per run** - Quality over quantity\n\n**If there are no qualifying facts (which is common), return no memories entries.**\n\n# Response Format\n\nmemories[0]:\n  category: semantic\n  content: User is a senior TypeScript developer with 8 years of backend experience\n  confidence: 0.95\nmemories[1]:\n  category: procedural\n  content: User follows TDD workflow: writes tests before implementation, runs tests after each change\n  confidence: 0.88\nmemories[2]:\n  category: episodic\n  content: User led database migration from MongoDB to PostgreSQL for payment system in Q2 2024\n  confidence: 0.92";
 export declare const messageClassifierTemplate = "Analyze this user request and classify it for planning purposes:\n\n\"{{text}}\"\n\nClassify the request across these dimensions:\n\n1. COMPLEXITY LEVEL:\n- simple: Direct actions that don't require planning\n- medium: Multi-step tasks requiring coordination\n- complex: Strategic initiatives with multiple stakeholders\n- enterprise: Large-scale transformations with full complexity\n\n2. PLANNING TYPE:\n- direct_action: Single action, no planning needed\n- sequential_planning: Multiple steps in sequence\n- strategic_planning: Complex coordination with stakeholders\n\n3. REQUIRED CAPABILITIES:\n- List specific capabilities needed (analysis, communication, project_management, etc.)\n\n4. STAKEHOLDERS:\n- List types of people/groups involved\n\n5. CONSTRAINTS:\n- List limitations or requirements mentioned\n\n6. DEPENDENCIES:\n- List dependencies between tasks or external factors\n\nRespond in this exact format:\nCOMPLEXITY: [simple|medium|complex|enterprise]\nPLANNING: [direct_action|sequential_planning|strategic_planning]\nCAPABILITIES: [comma-separated list]\nSTAKEHOLDERS: [comma-separated list]\nCONSTRAINTS: [comma-separated list]\nDEPENDENCIES: [comma-separated list]\nCONFIDENCE: [0.0-1.0]";
 export declare const MESSAGE_CLASSIFIER_TEMPLATE = "Analyze this user request and classify it for planning purposes:\n\n\"{{text}}\"\n\nClassify the request across these dimensions:\n\n1. COMPLEXITY LEVEL:\n- simple: Direct actions that don't require planning\n- medium: Multi-step tasks requiring coordination\n- complex: Strategic initiatives with multiple stakeholders\n- enterprise: Large-scale transformations with full complexity\n\n2. PLANNING TYPE:\n- direct_action: Single action, no planning needed\n- sequential_planning: Multiple steps in sequence\n- strategic_planning: Complex coordination with stakeholders\n\n3. REQUIRED CAPABILITIES:\n- List specific capabilities needed (analysis, communication, project_management, etc.)\n\n4. STAKEHOLDERS:\n- List types of people/groups involved\n\n5. CONSTRAINTS:\n- List limitations or requirements mentioned\n\n6. DEPENDENCIES:\n- List dependencies between tasks or external factors\n\nRespond in this exact format:\nCOMPLEXITY: [simple|medium|complex|enterprise]\nPLANNING: [direct_action|sequential_planning|strategic_planning]\nCAPABILITIES: [comma-separated list]\nSTAKEHOLDERS: [comma-separated list]\nCONSTRAINTS: [comma-separated list]\nDEPENDENCIES: [comma-separated list]\nCONFIDENCE: [0.0-1.0]";
-export declare const messageHandlerTemplate = "task: Generate dialog and actions for {{agentName}}.\n\ncontext:\n{{providers}}\n\nrules[21]:\n- think briefly, then respond\n- always include a <thought> field, even for direct replies\n- actions execute in listed order\n- if replying without another grounded state/action query, REPLY goes first\n- REPLY means a direct chat reply in the current conversation only; it is not an email reply, inbox workflow, or external-channel send\n- set simple=true only when the planner's text should be sent directly as the final reply without running REPLY again\n- if actions are REPLY-only and you want the REPLY action to generate the final user-facing message, set simple=false\n- use IGNORE or STOP only by themselves\n- include providers only when needed\n- use only action and provider names that appear in the listed runtime surface; never invent new action names, provider names, benchmark ids, or paraphrased tool labels\n- when the user asks about uploaded files, documents, prior uploads, or knowledge-base contents, call the relevant providers before replying instead of asking the user to resend the material\n- when the user refers to \"the uploaded file\", \"the document I uploaded\", or a prior upload without naming it, treat that as a provider lookup request first; only ask which file after grounded document/knowledge lookup still leaves multiple plausible answers\n- use provider_hints from context when present instead of restating the same rules\n- if an action needs inputs, include them inside that action's <params> block\n- if a required param is unknown, ask for clarification in text\n- for live status questions or remaining-work queries, do not answer from recent conversation alone; call the relevant action/provider to refresh state, and do not pair it with a speculative REPLY that guesses the result\n- when an action will fetch the state and produce the final grounded answer, do not add REPLY just to say \"checking\", \"let me look\", or similar filler; use the action alone and leave text empty\n- when the user asks you to create, store, remember, schedule, remind, upload, follow up, route, escalate, or set a standing policy, choose the matching action instead of handling it in prose only\n- for standing or future-condition requests like \"if/when X, do Y\", still choose the action that records, queues, or routes that behavior on the first turn\n- if a matching action can own the task and ask the missing follow-up itself, still select that action and put the clarification in text; do not reply in prose alone\n- when the user defines a durable preference, recurring block, escalation policy, upload policy, approval-gated workflow, or multi-device reminder rule, select the owning action even if some implementation details are still missing\n\t- do not wait for portal names, deck attachments, updated-id uploads, exact flight times, reservation ids, fee-risk item names, priority labels, event IDs, exact travel preferences, or the definition of \"important\" before selecting the owning action; let the action gather those details\n\t- future portal uploads, updated-id interventions, and cancellation-fee warning policies are operational workflows, not prose acknowledgements; choose LIFEOPS_COMPUTER_USE or PUBLISH_DEVICE_INTENT first and let those actions ask the missing follow-up\n\t- for LifeOps create requests with a clear defaultable habit or natural window, such as drinking water, stretch breaks during the day, weekday-after-lunch Invisalign checks, or brushing when waking up and before bed, call LIFE instead of asking for exact clock times unless the user explicitly asks for precise scheduling\n- only choose actions that directly satisfy the user's request or an explicit live-state question; do not opportunistically triage inboxes, summarize calendars, propose meetings, or call adjacent tools just because provider context makes them available\n- when the user is venting, reflecting, stating an opinion, or asking for generic advice about a domain, stay in REPLY or NONE unless they explicitly ask you to inspect state, change state, send something, schedule something, or perform a real operation\n\ncontrol_actions:\n- STOP means the task is done and the agent should end the run without executing more actions\n- STOP is a terminal control action even if it is not listed in available actions\n\nfields[5]{name,meaning}:\n- thought | short plan\n- actions | ordered <action> entries inside <actions>\n- providers | array of provider names, or empty\n- text | next message for {{agentName}}\n- simple | true only when text itself should be sent directly as the final reply; false when actions should run, including REPLY-driven finalization\n\nformatting:\n- wrap multi-line code in fenced code blocks\n- use inline backticks for short code identifiers\n\noutput:\nXML only. Return exactly one <response>...</response> document. No prose before or after it. No <think>.\n\nExample:\n<response>\n  <thought>Reply briefly. No extra providers needed.</thought>\n  <actions>\n    <action>\n      <name>REPLY</name>\n    </action>\n  </actions>\n  <providers></providers>\n  <text>Your message here</text>\n  <simple>true</simple>\n</response>";
-export declare const MESSAGE_HANDLER_TEMPLATE = "task: Generate dialog and actions for {{agentName}}.\n\ncontext:\n{{providers}}\n\nrules[21]:\n- think briefly, then respond\n- always include a <thought> field, even for direct replies\n- actions execute in listed order\n- if replying without another grounded state/action query, REPLY goes first\n- REPLY means a direct chat reply in the current conversation only; it is not an email reply, inbox workflow, or external-channel send\n- set simple=true only when the planner's text should be sent directly as the final reply without running REPLY again\n- if actions are REPLY-only and you want the REPLY action to generate the final user-facing message, set simple=false\n- use IGNORE or STOP only by themselves\n- include providers only when needed\n- use only action and provider names that appear in the listed runtime surface; never invent new action names, provider names, benchmark ids, or paraphrased tool labels\n- when the user asks about uploaded files, documents, prior uploads, or knowledge-base contents, call the relevant providers before replying instead of asking the user to resend the material\n- when the user refers to \"the uploaded file\", \"the document I uploaded\", or a prior upload without naming it, treat that as a provider lookup request first; only ask which file after grounded document/knowledge lookup still leaves multiple plausible answers\n- use provider_hints from context when present instead of restating the same rules\n- if an action needs inputs, include them inside that action's <params> block\n- if a required param is unknown, ask for clarification in text\n- for live status questions or remaining-work queries, do not answer from recent conversation alone; call the relevant action/provider to refresh state, and do not pair it with a speculative REPLY that guesses the result\n- when an action will fetch the state and produce the final grounded answer, do not add REPLY just to say \"checking\", \"let me look\", or similar filler; use the action alone and leave text empty\n- when the user asks you to create, store, remember, schedule, remind, upload, follow up, route, escalate, or set a standing policy, choose the matching action instead of handling it in prose only\n- for standing or future-condition requests like \"if/when X, do Y\", still choose the action that records, queues, or routes that behavior on the first turn\n- if a matching action can own the task and ask the missing follow-up itself, still select that action and put the clarification in text; do not reply in prose alone\n- when the user defines a durable preference, recurring block, escalation policy, upload policy, approval-gated workflow, or multi-device reminder rule, select the owning action even if some implementation details are still missing\n\t- do not wait for portal names, deck attachments, updated-id uploads, exact flight times, reservation ids, fee-risk item names, priority labels, event IDs, exact travel preferences, or the definition of \"important\" before selecting the owning action; let the action gather those details\n\t- future portal uploads, updated-id interventions, and cancellation-fee warning policies are operational workflows, not prose acknowledgements; choose LIFEOPS_COMPUTER_USE or PUBLISH_DEVICE_INTENT first and let those actions ask the missing follow-up\n\t- for LifeOps create requests with a clear defaultable habit or natural window, such as drinking water, stretch breaks during the day, weekday-after-lunch Invisalign checks, or brushing when waking up and before bed, call LIFE instead of asking for exact clock times unless the user explicitly asks for precise scheduling\n- only choose actions that directly satisfy the user's request or an explicit live-state question; do not opportunistically triage inboxes, summarize calendars, propose meetings, or call adjacent tools just because provider context makes them available\n- when the user is venting, reflecting, stating an opinion, or asking for generic advice about a domain, stay in REPLY or NONE unless they explicitly ask you to inspect state, change state, send something, schedule something, or perform a real operation\n\ncontrol_actions:\n- STOP means the task is done and the agent should end the run without executing more actions\n- STOP is a terminal control action even if it is not listed in available actions\n\nfields[5]{name,meaning}:\n- thought | short plan\n- actions | ordered <action> entries inside <actions>\n- providers | array of provider names, or empty\n- text | next message for {{agentName}}\n- simple | true only when text itself should be sent directly as the final reply; false when actions should run, including REPLY-driven finalization\n\nformatting:\n- wrap multi-line code in fenced code blocks\n- use inline backticks for short code identifiers\n\noutput:\nXML only. Return exactly one <response>...</response> document. No prose before or after it. No <think>.\n\nExample:\n<response>\n  <thought>Reply briefly. No extra providers needed.</thought>\n  <actions>\n    <action>\n      <name>REPLY</name>\n    </action>\n  </actions>\n  <providers></providers>\n  <text>Your message here</text>\n  <simple>true</simple>\n</response>";
+export declare const messageHandlerTemplate = "task: Generate dialog and actions for {{agentName}}.\n\ncontext:\n{{providers}}\n\nrules[21]:\n- think briefly, then respond\n- always include a <thought> field, even for direct replies\n- actions execute in listed order\n- if replying without another grounded state/action query, REPLY goes first\n- REPLY means a direct chat reply in the current conversation only; it is not an email reply, inbox workflow, or external-channel send\n- set simple=true only when the planner's text should be sent directly as the final reply without running REPLY again\n- if actions are REPLY-only and you want the REPLY action to generate the final user-facing message, set simple=false\n- use IGNORE or STOP only by themselves\n- include providers only when needed\n- use only action and provider names that appear in the listed runtime surface; never invent new action names, provider names, benchmark ids, or paraphrased tool labels\n- when the user asks about uploaded files, documents, prior uploads, or knowledge-base contents, call the relevant providers before replying instead of asking the user to resend the material\n- when the user refers to \"the uploaded file\", \"the document I uploaded\", or a prior upload without naming it, treat that as a provider lookup request first; only ask which file after grounded document/knowledge lookup still leaves multiple plausible answers\n- use provider_hints from context when present instead of restating the same rules\n- if an action needs inputs, include them inside that action's <params> block\n- if a required param is unknown, ask for clarification in text\n- for live status questions or remaining-work queries, do not answer from recent conversation alone; call the relevant action/provider to refresh state, and do not pair it with a speculative REPLY that guesses the result\n- when an action will fetch the state and produce the final grounded answer, do not add REPLY just to say \"checking\", \"let me look\", or similar filler; use the action alone and leave text empty\n- when the user asks you to create, store, remember, schedule, remind, upload, follow up, route, escalate, or set a standing policy, choose the matching action instead of handling it in prose only\n- when the request names an external integration (Gmail, Discord, Slack, Telegram, GitHub, Google Sheets, Google Calendar, Google Drive, Notion, etc.) AND describes data movement between services or scheduled invocation of an external API, prefer CREATE_N8N_WORKFLOW; reserve CREATE_TRIGGER_TASK for self-driven scheduled prompts to the agent itself with no external API calls\n- for standing or future-condition requests like \"if/when X, do Y\", still choose the action that records, queues, or routes that behavior on the first turn\n- if a matching action can own the task and ask the missing follow-up itself, still select that action and put the clarification in text; do not reply in prose alone\n- when the user defines a durable preference, recurring block, escalation policy, upload policy, approval-gated workflow, or multi-device reminder rule, select the owning action even if some implementation details are still missing\n\t- do not wait for portal names, deck attachments, updated-id uploads, exact flight times, reservation ids, fee-risk item names, priority labels, event IDs, exact travel preferences, or the definition of \"important\" before selecting the owning action; let the action gather those details\n\t- future portal uploads, updated-id interventions, and cancellation-fee warning policies are operational workflows, not prose acknowledgements; choose LIFEOPS_COMPUTER_USE or PUBLISH_DEVICE_INTENT first and let those actions ask the missing follow-up\n\t- for LifeOps create requests with a clear defaultable habit or natural window, such as drinking water, stretch breaks during the day, weekday-after-lunch Invisalign checks, or brushing when waking up and before bed, call LIFE instead of asking for exact clock times unless the user explicitly asks for precise scheduling\n- only choose actions that directly satisfy the user's request or an explicit live-state question; do not opportunistically triage inboxes, summarize calendars, propose meetings, or call adjacent tools just because provider context makes them available\n- when the user is venting, reflecting, stating an opinion, or asking for generic advice about a domain, stay in REPLY or NONE unless they explicitly ask you to inspect state, change state, send something, schedule something, or perform a real operation\n\ncontrol_actions:\n- STOP means the task is done and the agent should end the run without executing more actions\n- STOP is a terminal control action even if it is not listed in available actions\n\nfields[5]{name,meaning}:\n- thought | short plan\n- actions | ordered <action> entries inside <actions>\n- providers | array of provider names, or empty\n- text | next message for {{agentName}}\n- simple | true only when text itself should be sent directly as the final reply; false when actions should run, including REPLY-driven finalization\n\nformatting:\n- wrap multi-line code in fenced code blocks\n- use inline backticks for short code identifiers\n\noutput:\nXML only. Return exactly one <response>...</response> document. No prose before or after it. No <think>.\n\nExample:\n<response>\n  <thought>Reply briefly. No extra providers needed.</thought>\n  <actions>\n    <action>\n      <name>REPLY</name>\n    </action>\n  </actions>\n  <providers></providers>\n  <text>Your message here</text>\n  <simple>true</simple>\n</response>";
+export declare const MESSAGE_HANDLER_TEMPLATE = "task: Generate dialog and actions for {{agentName}}.\n\ncontext:\n{{providers}}\n\nrules[21]:\n- think briefly, then respond\n- always include a <thought> field, even for direct replies\n- actions execute in listed order\n- if replying without another grounded state/action query, REPLY goes first\n- REPLY means a direct chat reply in the current conversation only; it is not an email reply, inbox workflow, or external-channel send\n- set simple=true only when the planner's text should be sent directly as the final reply without running REPLY again\n- if actions are REPLY-only and you want the REPLY action to generate the final user-facing message, set simple=false\n- use IGNORE or STOP only by themselves\n- include providers only when needed\n- use only action and provider names that appear in the listed runtime surface; never invent new action names, provider names, benchmark ids, or paraphrased tool labels\n- when the user asks about uploaded files, documents, prior uploads, or knowledge-base contents, call the relevant providers before replying instead of asking the user to resend the material\n- when the user refers to \"the uploaded file\", \"the document I uploaded\", or a prior upload without naming it, treat that as a provider lookup request first; only ask which file after grounded document/knowledge lookup still leaves multiple plausible answers\n- use provider_hints from context when present instead of restating the same rules\n- if an action needs inputs, include them inside that action's <params> block\n- if a required param is unknown, ask for clarification in text\n- for live status questions or remaining-work queries, do not answer from recent conversation alone; call the relevant action/provider to refresh state, and do not pair it with a speculative REPLY that guesses the result\n- when an action will fetch the state and produce the final grounded answer, do not add REPLY just to say \"checking\", \"let me look\", or similar filler; use the action alone and leave text empty\n- when the user asks you to create, store, remember, schedule, remind, upload, follow up, route, escalate, or set a standing policy, choose the matching action instead of handling it in prose only\n- when the request names an external integration (Gmail, Discord, Slack, Telegram, GitHub, Google Sheets, Google Calendar, Google Drive, Notion, etc.) AND describes data movement between services or scheduled invocation of an external API, prefer CREATE_N8N_WORKFLOW; reserve CREATE_TRIGGER_TASK for self-driven scheduled prompts to the agent itself with no external API calls\n- for standing or future-condition requests like \"if/when X, do Y\", still choose the action that records, queues, or routes that behavior on the first turn\n- if a matching action can own the task and ask the missing follow-up itself, still select that action and put the clarification in text; do not reply in prose alone\n- when the user defines a durable preference, recurring block, escalation policy, upload policy, approval-gated workflow, or multi-device reminder rule, select the owning action even if some implementation details are still missing\n\t- do not wait for portal names, deck attachments, updated-id uploads, exact flight times, reservation ids, fee-risk item names, priority labels, event IDs, exact travel preferences, or the definition of \"important\" before selecting the owning action; let the action gather those details\n\t- future portal uploads, updated-id interventions, and cancellation-fee warning policies are operational workflows, not prose acknowledgements; choose LIFEOPS_COMPUTER_USE or PUBLISH_DEVICE_INTENT first and let those actions ask the missing follow-up\n\t- for LifeOps create requests with a clear defaultable habit or natural window, such as drinking water, stretch breaks during the day, weekday-after-lunch Invisalign checks, or brushing when waking up and before bed, call LIFE instead of asking for exact clock times unless the user explicitly asks for precise scheduling\n- only choose actions that directly satisfy the user's request or an explicit live-state question; do not opportunistically triage inboxes, summarize calendars, propose meetings, or call adjacent tools just because provider context makes them available\n- when the user is venting, reflecting, stating an opinion, or asking for generic advice about a domain, stay in REPLY or NONE unless they explicitly ask you to inspect state, change state, send something, schedule something, or perform a real operation\n\ncontrol_actions:\n- STOP means the task is done and the agent should end the run without executing more actions\n- STOP is a terminal control action even if it is not listed in available actions\n\nfields[5]{name,meaning}:\n- thought | short plan\n- actions | ordered <action> entries inside <actions>\n- providers | array of provider names, or empty\n- text | next message for {{agentName}}\n- simple | true only when text itself should be sent directly as the final reply; false when actions should run, including REPLY-driven finalization\n\nformatting:\n- wrap multi-line code in fenced code blocks\n- use inline backticks for short code identifiers\n\noutput:\nXML only. Return exactly one <response>...</response> document. No prose before or after it. No <think>.\n\nExample:\n<response>\n  <thought>Reply briefly. No extra providers needed.</thought>\n  <actions>\n    <action>\n      <name>REPLY</name>\n    </action>\n  </actions>\n  <providers></providers>\n  <text>Your message here</text>\n  <simple>true</simple>\n</response>";
 export declare const multiStepDecisionTemplate = "Determine the next step the assistant should take in this conversation to help the user reach their goal.\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\nUse only action and provider names that appear in the listed runtime surface. Never invent new action names, provider names, benchmark ids, or paraphrased tool labels.\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\nkeys:\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\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\noutput:\nthought: Your thought here\naction: ACTION\nproviders[2]: PROVIDER1,PROVIDER2\nisFinish: false";
 export declare const MULTI_STEP_DECISION_TEMPLATE = "Determine the next step the assistant should take in this conversation to help the user reach their goal.\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\nUse only action and provider names that appear in the listed runtime surface. Never invent new action names, provider names, benchmark ids, or paraphrased tool labels.\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\nkeys:\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\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\noutput:\nthought: Your thought here\naction: ACTION\nproviders[2]: PROVIDER1,PROVIDER2\nisFinish: false";
 export declare const multiStepSummaryTemplate = "Summarize what the assistant has done so far and provide a final response to the user based on the completed steps.\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 TOON in this format:\noutput:\nthought: Your thought here\ntext: Your final message to the user";