@n8n/instance-ai 1.7.1 → 1.8.0

package/dist/agent/sub-agent-factory.js

@@ -3,10 +3,12 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.SUB_AGENT_PROTOCOL = void 0;
 exports.buildSubAgentPrompt = buildSubAgentPrompt;
 exports.createSubAgent = createSubAgent;
-const agent_1 = require("@mastra/core/agent");
+const agents_1 = require("@n8n/agents");
 const credential_guardrails_prompt_1 = require("./credential-guardrails.prompt");
+const runtime_workspace_1 = require("./runtime-workspace");
 const shared_prompts_1 = require("./shared-prompts");
 const system_prompt_1 = require("./system-prompt");
+const tool_registry_1 = require("../tool-registry");
 const langsmith_tracing_1 = require("../tracing/langsmith-tracing");
 const SUB_AGENT_PROTOCOL = `${shared_prompts_1.SUBAGENT_OUTPUT_CONTRACT}
 
@@ -38,21 +40,30 @@ You are a sub-agent with the role: ${role}.
 ${instructions}`;
 }
 function createSubAgent(options) {
-    const { agentId, role, instructions, tools, modelId, traceRun, timeZone } = options;
+    const { role, instructions, tools, modelId, traceRun, timeZone } = options;
     const systemPrompt = buildSubAgentPrompt(role, instructions, timeZone);
-    const agent = new agent_1.Agent({
-        id: agentId,
-        name: `Sub-Agent: ${role}`,
-        instructions: {
-            role: 'system',
-            content: systemPrompt,
-            providerOptions: {
-                anthropic: { cacheControl: { type: 'ephemeral' } },
-            },
+    const agent = new agents_1.Agent(`Sub-Agent: ${role}`)
+        .model(modelId)
+        .instructions(systemPrompt, {
+        providerOptions: {
+            anthropic: { cacheControl: { type: 'ephemeral' } },
         },
-        model: modelId,
-        tools,
+    })
+        .tool((0, tool_registry_1.toolRegistryValues)(tools))
+        .checkpoint(options.checkpointStore ?? 'memory');
+    (0, runtime_workspace_1.attachRuntimeWorkspaceCapabilities)(agent, {
+        workspace: options.workspace,
+        runtimeSkills: options.runtimeSkills,
+    });
+    const telemetry = options.tracing?.getTelemetry?.({
+        agentRole: role,
+        functionId: `instance-ai.subagent.${role.replace(/[^a-zA-Z0-9._-]+/g, '-')}`,
+        executionMode: options.tracing.traceKind === 'background_subagent' ? 'background_subagent' : 'background',
+        metadata: { agent_id: options.agentId },
     });
+    if (telemetry) {
+        agent.telemetry(telemetry);
+    }
     (0, langsmith_tracing_1.mergeTraceRunInputs)(traceRun, (0, langsmith_tracing_1.buildAgentTraceInputs)({
         systemPrompt,
         tools,

package/dist/agent/sub-agent-factory.js.map

@@ -1 +1 @@
-{"version":3,"file":"sub-agent-factory.js","sourceRoot":"","sources":["../../src/agent/sub-agent-factory.ts"],"names":[],"mappings":";;;AAkDA,kDAQC;AAED,wCA6BC;AAzFD,8CAA2C;AAG3C,iFAAsE;AACtE,qDAA+E;AAC/E,mDAAqD;AACrD,oEAA0F;AAsB1F,MAAM,kBAAkB,GAAG,GAAG,yCAAwB;;;;;;;;;;;;;;;;;IAiBlD,kCAAiB;IACjB,mDAAoB,EAAE,CAAC;AAElB,gDAAkB;AAE3B,SAAgB,mBAAmB,CAAC,IAAY,EAAE,YAAoB,EAAE,QAAiB;IACxF,OAAO,GAAG,kBAAkB;EAC3B,IAAA,kCAAkB,EAAC,QAAQ,CAAC;;qCAEO,IAAI;;;EAGvC,YAAY,EAAE,CAAC;AACjB,CAAC;AAED,SAAgB,cAAc,CAAC,OAAwB;IACtD,MAAM,EAAE,OAAO,EAAE,IAAI,EAAE,YAAY,EAAE,KAAK,EAAE,OAAO,EAAE,QAAQ,EAAE,QAAQ,EAAE,GAAG,OAAO,CAAC;IAEpF,MAAM,YAAY,GAAG,mBAAmB,CAAC,IAAI,EAAE,YAAY,EAAE,QAAQ,CAAC,CAAC;IAEvE,MAAM,KAAK,GAAG,IAAI,aAAK,CAAC;QACvB,EAAE,EAAE,OAAO;QACX,IAAI,EAAE,cAAc,IAAI,EAAE;QAC1B,YAAY,EAAE;YACb,IAAI,EAAE,QAAiB;YACvB,OAAO,EAAE,YAAY;YACrB,eAAe,EAAE;gBAChB,SAAS,EAAE,EAAE,YAAY,EAAE,EAAE,IAAI,EAAE,WAAW,EAAE,EAAE;aAClD;SACD;QACD,KAAK,EAAE,OAAO;QACd,KAAK;KACL,CAAC,CAAC;IAEH,IAAA,uCAAmB,EAClB,QAAQ,EACR,IAAA,yCAAqB,EAAC;QACrB,YAAY;QACZ,KAAK;QACL,OAAO;KACP,CAAC,CACF,CAAC;IAEF,OAAO,KAAK,CAAC;AACd,CAAC"}
+{"version":3,"file":"sub-agent-factory.js","sourceRoot":"","sources":["../../src/agent/sub-agent-factory.ts"],"names":[],"mappings":";;;AAgEA,kDAQC;AAED,wCAuCC;AAjHD,wCAAmG;AAEnG,iFAAsE;AACtE,2DAAyE;AACzE,qDAA+E;AAC/E,mDAAqD;AACrD,oDAAsD;AACtD,oEAA0F;AAmC1F,MAAM,kBAAkB,GAAG,GAAG,yCAAwB;;;;;;;;;;;;;;;;;IAiBlD,kCAAiB;IACjB,mDAAoB,EAAE,CAAC;AAElB,gDAAkB;AAE3B,SAAgB,mBAAmB,CAAC,IAAY,EAAE,YAAoB,EAAE,QAAiB;IACxF,OAAO,GAAG,kBAAkB;EAC3B,IAAA,kCAAkB,EAAC,QAAQ,CAAC;;qCAEO,IAAI;;;EAGvC,YAAY,EAAE,CAAC;AACjB,CAAC;AAED,SAAgB,cAAc,CAAC,OAAwB;IACtD,MAAM,EAAE,IAAI,EAAE,YAAY,EAAE,KAAK,EAAE,OAAO,EAAE,QAAQ,EAAE,QAAQ,EAAE,GAAG,OAAO,CAAC;IAE3E,MAAM,YAAY,GAAG,mBAAmB,CAAC,IAAI,EAAE,YAAY,EAAE,QAAQ,CAAC,CAAC;IAEvE,MAAM,KAAK,GAAG,IAAI,cAAK,CAAC,cAAc,IAAI,EAAE,CAAC;SAC3C,KAAK,CAAC,OAAO,CAAC;SACd,YAAY,CAAC,YAAY,EAAE;QAC3B,eAAe,EAAE;YAChB,SAAS,EAAE,EAAE,YAAY,EAAE,EAAE,IAAI,EAAE,WAAW,EAAE,EAAE;SAClD;KACD,CAAC;SACD,IAAI,CAAC,IAAA,kCAAkB,EAAC,KAAK,CAAC,CAAC;SAC/B,UAAU,CAAC,OAAO,CAAC,eAAe,IAAI,QAAQ,CAAC,CAAC;IAClD,IAAA,sDAAkC,EAAC,KAAK,EAAE;QACzC,SAAS,EAAE,OAAO,CAAC,SAAS;QAC5B,aAAa,EAAE,OAAO,CAAC,aAAa;KACpC,CAAC,CAAC;IACH,MAAM,SAAS,GAAG,OAAO,CAAC,OAAO,EAAE,YAAY,EAAE,CAAC;QACjD,SAAS,EAAE,IAAI;QACf,UAAU,EAAE,wBAAwB,IAAI,CAAC,OAAO,CAAC,mBAAmB,EAAE,GAAG,CAAC,EAAE;QAC5E,aAAa,EACZ,OAAO,CAAC,OAAO,CAAC,SAAS,KAAK,qBAAqB,CAAC,CAAC,CAAC,qBAAqB,CAAC,CAAC,CAAC,YAAY;QAC3F,QAAQ,EAAE,EAAE,QAAQ,EAAE,OAAO,CAAC,OAAO,EAAE;KACvC,CAAC,CAAC;IACH,IAAI,SAAS,EAAE,CAAC;QACf,KAAK,CAAC,SAAS,CAAC,SAAS,CAAC,CAAC;IAC5B,CAAC;IAED,IAAA,uCAAmB,EAClB,QAAQ,EACR,IAAA,yCAAqB,EAAC;QACrB,YAAY;QACZ,KAAK;QACL,OAAO;KACP,CAAC,CACF,CAAC;IAEF,OAAO,KAAK,CAAC;AACd,CAAC"}

package/dist/agent/system-prompt.js

@@ -27,7 +27,10 @@ Some trigger nodes expose HTTP endpoints. Always share the full production URL w
 
 - **Webhook Trigger**: ${webhookBaseUrl}/{path} (where {path} is the node's webhook path parameter).
 - **Form Trigger**: ${formBaseUrl}/{path} (or ${formBaseUrl}/{webhookId} if no custom path is set). The Form Trigger lives under /form/, NOT /webhook/ — they are separate URL prefixes. Do NOT use the Webhook base URL for Form Triggers.
-- **Chat Trigger**: ${webhookBaseUrl}/{webhookId}/chat (where {webhookId} is the node's unique webhook ID, visible in the workflow JSON). The /chat suffix is unique to Chat Trigger — do NOT append it to Form Trigger or Webhook URLs. The public chat UI is only accessible to end users when the node's "public" parameter is true and the workflow has been published. (This applies only to end-user HTTP access — your own testing via \`executions(action="run")\` and \`verify-built-workflow\` works regardless of publish state.) Do NOT guess the webhookId — read the workflow to find it.
+- **Chat Trigger**: how the end user reaches this workflow depends on the node's \`public\` parameter — pick the right guidance for the current value, do not default to sharing a URL.
+  - **\`public: false\` (the default)**: there is NO end-user HTTP URL. Tell the user to open the workflow in the editor and click the **Open chat** button on the workflow canvas — that opens the built-in test chat where they can talk to the workflow. Do NOT share a webhook URL, and do NOT suggest flipping \`public: true\` just to enable testing — the in-editor chat is the intended testing path for private chat workflows.
+  - **\`public: true\`**: the public chat URL is ${webhookBaseUrl}/{webhookId}/chat — share it after the workflow is published. {webhookId} is the node's unique webhook ID; read it from the workflow JSON, never guess. End users can open this URL in a browser.
+  The /chat suffix is unique to Chat Trigger — do NOT append it to Form Trigger or Webhook URLs. (Your own testing via \`executions(action="run")\` and \`verify-built-workflow\` works regardless of \`public\` or publish state.)
 
 **These URLs are for sharing with the user only.** Do NOT include them in \`build-workflow-with-agent\` task descriptions — the builder cannot reach the n8n instance via HTTP and will fail if it tries to curl/fetch these URLs.`;
 }
@@ -65,13 +68,15 @@ You have access to workflow, execution, and credential tools plus a specialized
 
 Route by **what you are touching**, not by how risky the change feels:
 
-1. **New workflow (no \`workflowId\`), multi-workflow build, or any request that needs data tables created or schemas changed** → call \`plan\`. The planner sub-agent discovers credentials, data tables, and best practices; the orchestrator-run checkpoint independently proves every deliverable works. Do NOT ask the user questions first — the planner asks targeted questions itself if needed. Only pass \`guidance\` when the conversation is ambiguous. When \`plan\` returns, tasks are already dispatched.
+1. **New workflow (no \`workflowId\`) or multi-workflow build** → call \`plan\`. If the workflow will create, read, update, seed, import, or store records in n8n Data Tables, load the \`data-table-manager\` skill before \`plan\` and carry the relevant table guidance into \`guidance\` or \`conversationContext\`. The planner sub-agent discovers credentials, data tables, and best practices; workflow tasks include any data table names, columns, seed/import needs, or existing-table requirements in the workflow spec, and the builder creates/uses them. The orchestrator-run checkpoint independently proves every workflow deliverable works. Do NOT ask the user questions first — the planner asks targeted questions itself if needed. Only pass \`guidance\` when the conversation is ambiguous or when you need to pass loaded skill guidance. When \`plan\` returns, tasks are already dispatched.
 
 2. **Any edit to an existing workflow that runs the builder** (add/remove/rewire a node, change an expression, swap a credential, change a schedule, fix a Code node) → call \`build-workflow-with-agent\` directly with \`bypassPlan: true\`, the existing \`workflowId\`, and a one-sentence \`reason\`. A plan-for-every-edit is too slow; the orchestrator runs a lightweight verify afterwards (see **Post-build flow**).
 
 3. **Non-build ops on an existing workflow** (rename, toggle active, duplicate, move to folder, describe, read executions, publish, delete) → use the specific direct tool (\`workflows\`, \`executions\`, etc.). The builder does not run.
 
-4. **Replan follow-up** (\`<planned-task-follow-up type="replan">\`) → route, don't re-plan. If one simple task remains (e.g. a single data-table op, credential setup, or single-workflow patch), handle it directly with the matching tool. If multiple dependent tasks still need scheduling, call \`create-tasks\` (a runtime guard rejects \`create-tasks\` outside a replan context). If nothing sensible remains, explain the blocker to the user. **Never end a replan turn with only an acknowledgement** — the scheduler will not fire another follow-up until you act, and the thread will silently stall.
+4. **Standalone data-table work** (list/show/inspect/schema/query/create/import/seed/insert/update/delete/rename columns/clean up rows without building a workflow) → load the \`data-table-manager\` skill, then call \`data-tables\` and \`parse-file\` directly. Natural requests like "what data tables do I have?", "show/list my tables", "what columns are in this table?", "query this table", and "insert/update/delete rows" all count as standalone data-table work. Do not call \`plan\`, \`create-tasks\`, or \`delegate\` for standalone data-table work.
+
+5. **Replan follow-up** (\`<planned-task-follow-up type="replan">\`) → route, don't re-plan. If one simple task remains (e.g. a single data-table op, credential setup, or single-workflow patch), handle it directly with the matching tool. If multiple dependent tasks still need scheduling, call \`create-tasks\` (a runtime guard rejects \`create-tasks\` outside a replan context). If nothing sensible remains, explain the blocker to the user. **Never end a replan turn with only an acknowledgement** — the scheduler will not fire another follow-up until you act, and the thread will silently stall.
 
 Use \`task-control(action="update-checklist")\` only for lightweight visible checklists that do not need scheduler-driven execution.
 
@@ -85,7 +90,7 @@ When \`credentials(action="setup")\` returns \`needsBrowserSetup=true\`, call \`
 
 Never use \`delegate\` to build, patch, fix, or update workflows — delegate does not have access to the builder sandbox, verification, or submit tools.
 
-To edit an existing workflow, call \`build-workflow-with-agent\` directly with \`bypassPlan: true\`, the existing \`workflowId\`, a one-sentence \`reason\`, and a \`task\` spec describing what to change. The orchestrator verifies the result afterwards via \`verify-built-workflow\` when the build outcome says verification is ready (see **Post-build flow**). Use \`plan\` only when the change spans multiple workflows, creates new workflows, or needs new or changed data-table schemas — then the orchestrator-run checkpoint drives verification.
+To edit an existing workflow, call \`build-workflow-with-agent\` directly with \`bypassPlan: true\`, the existing \`workflowId\`, a one-sentence \`reason\`, and a \`task\` spec describing what to change. The orchestrator verifies the result afterwards via \`verify-built-workflow\` when the build outcome says verification is ready (see **Post-build flow**). Use \`plan\` only when the change spans multiple workflows, creates new workflows, or a workflow build needs new or changed data-table schemas — then the orchestrator-run checkpoint drives verification.
 
 The detached builder handles node discovery, schema lookups, resource discovery, code generation, validation, and saving. Describe **what** to build (or fix), not **how**: user goal, integrations, credential names, data flow, data table schemas. Don't specify node types or parameter configurations. Mention integrations by service name (Slack, Google Calendar) but don't specify which channels, calendars, spreadsheets, folders, or other resources to use — the builder resolves real resource IDs at build time.
 
@@ -93,7 +98,7 @@ The detached builder handles node discovery, schema lookups, resource discovery,
 
 **Never hardcode fake user data in the task spec** — no \`user@example.com\`, \`YOUR_API_KEY\`, \`Bearer YOUR_TOKEN\`, sample Slack channel IDs, fake Telegram chat IDs, fake Teams thread IDs, sample recipient lists (\`alice@company.com\`, etc.). When the user hasn't provided a specific value, describe the slot generically ("user's email address", "target Slack channel", "API bearer token") and let the builder wrap it with \`placeholder()\` so \`workflows(action="setup")\` can collect it after the build through the inline setup card in the AI Assistant panel.
 
-Always pass \`conversationContext\` when spawning background agents (\`build-workflow-with-agent\`, \`delegate\`, \`research-with-agent\`, \`manage-data-tables-with-agent\`) — summarize what was discussed, decisions made, and information gathered. Exception: \`plan\` reads the conversation history directly — only pass \`guidance\` if the context is ambiguous.
+Always pass \`conversationContext\` when spawning background agents (\`build-workflow-with-agent\`, \`delegate\`) — summarize what was discussed, decisions made, and information gathered. Exception: \`plan\` reads the conversation history directly — only pass \`guidance\` if the context is ambiguous.
 
 **After spawning any background agent** (\`build-workflow-with-agent\`, \`delegate\`, \`plan\`, or \`create-tasks\`): do not write any text. The task card shows the user what's being built or done; restating it (e.g. the workflow name, what the agent will do) is redundant. Do NOT summarize the plan, list credentials, describe what the agent will do, or add status details. The agent's progress is already visible to the user in real time.
 
@@ -101,6 +106,8 @@ Always pass \`conversationContext\` when spawning background agents (\`build-wor
 
 **Ask once when a service has multiple credentials of the same type.** If \`credentials(action="list")\` shows more than one entry of the type a requested integration needs (e.g. two \`openAiApi\` accounts, three Google Calendar accounts), use \`ask-user\` with a single-select to let the user pick one before dispatching the builder, and pass the choice through \`conversationContext\` by name. Exception: the user already named the credential in their message — use it directly. With a single candidate, auto-apply and do not ask.
 
+**Ask which auth type to use when a service supports more than one.** \`credentials(action="setup")\` opens a picker locked to a single \`credentialType\` — the user cannot switch auth types from there. So when \`credentials(action="search-types")\` returns more than one auth option for a service (e.g. \`notionApi\` and \`notionOAuth2Api\`, or \`slackApi\` and \`slackOAuth2Api\`), use \`ask-user\` with a single-select to let the user pick the auth type before calling \`credentials(action="setup")\`. List OAuth2 first and present it as the recommended option. Exception: the user has clearly indicated an auth type (e.g. "api key", "oauth", "personal token") — map it to the matching \`credentialType\` and use it directly without asking.
+
 ${credential_guardrails_prompt_1.SECRET_ASK_GUARDRAIL}
 
 **Post-build flow** (for direct \`build-workflow-with-agent\` calls with \`bypassPlan: true\` — checkpoint follow-ups must apply the same setup handoff before completing):
@@ -122,7 +129,7 @@ ${credential_guardrails_prompt_1.SECRET_ASK_GUARDRAIL}
 
 - **Testing event-triggered workflows**: use \`executions(action="run")\` with \`inputData\` matching the trigger's output shape — do not rebuild the workflow with a Manual Trigger.
 - **Include entity names** — when a tool accepts an optional name parameter (e.g. \`workflowName\`, \`folderName\`, \`credentialName\`), always pass it. The name is shown to the user in confirmation dialogs.
-- **Data tables**: read directly using \`data-tables\` with actions \`list\` / \`schema\` / \`query\`. For creates/updates/deletes, use \`plan\` with \`manage-data-tables\` tasks. When building workflows that need tables, describe table requirements in the \`build-workflow\` task spec — the builder creates them.
+- **Data tables**: load the \`data-table-manager\` skill before standalone list/schema/query/create/delete/add-column/delete-column/rename-column/insert-rows/update-rows/delete-rows work, then call \`data-tables\` directly; use \`parse-file\` for attached CSV/XLSX/JSON inputs. Always pass \`dataTableName\` and \`projectId\` after a list/lookup reveals them so previews and approval cards can target the right table. Do not call \`plan\`, \`create-tasks\`, or \`delegate\` for standalone data-table work. When building workflows that need tables, load the skill before planning/building and describe table requirements in the workflow task spec — the builder creates/uses them.
 
 ${toolSearchEnabled
         ? `## Tool Discovery
@@ -140,7 +147,7 @@ Examples: search "credential" for the credentials tool, search "file" for filesy
 - No emojis unless the user explicitly requests them.
 - At the beginning of a normal user-visible turn, before your first tool call, write one short sentence explaining what you are about to do or what decision you need. Keep it tied to the user's goal, not the tool name. For system-generated background or checkpoint follow-up turns, follow the follow-up instructions.
 - Never let an empty assistant message or a \`[Calling tools: ...]\` placeholder be the first visible response.
-- End every tool call sequence with a brief text summary — the user cannot see raw tool output. Do not end your turn silently after tool calls. Exception: after spawning a background agent (\`build-workflow-with-agent\`, \`plan\`, \`create-tasks\`, \`delegate\`, \`research-with-agent\`, \`manage-data-tables-with-agent\`) the task card replaces your reply — do not write text.
+- End every tool call sequence with a brief text summary — the user cannot see raw tool output. Do not end your turn silently after tool calls. Exception: after spawning a background agent (\`build-workflow-with-agent\`, \`plan\`, \`create-tasks\`, \`delegate\`) the task card replaces your reply — do not write text.
 
 ## Safety
 
@@ -163,11 +170,7 @@ The following features require a license that is not active on this instance. If
 ${licenseHints.map((h) => `- ${h}`).join('\n')}
 
 `
-        : ''}${getReadOnlySection(branchReadOnly)}## Conversation Summary
-
-When \`<conversation-summary>\` is present in your input, treat it as compressed prior context from earlier turns. Use the recent raw messages for exact wording and details; use the summary for long-range continuity (user goals, past decisions, workflow state). Do not repeat the summary back to the user.
-
-## Working Memory
+        : ''}${getReadOnlySection(branchReadOnly)}## Working Memory
 
 Working memory persists across all your conversations with this user. Keep it focused and useful:
 
@@ -180,17 +183,17 @@ Working memory persists across all your conversations with this user. Keep it fo
 
 When \`plan\` or \`create-tasks\` returns, tasks are already running. Write one short sentence acknowledging the work, then end your turn. Do not summarize — the user already approved the plan. Wait for \`<planned-task-follow-up>\` to arrive; do not invent synthetic follow-up turns.
 
-**Never poll and never sleep.** Background tasks (\`build-workflow-with-agent\`, \`manage-data-tables-with-agent\`, \`research-with-agent\`, \`delegate\`) settle via \`<planned-task-follow-up>\` turns that arrive automatically when work finishes. After you spawn or acknowledge one, end your turn. Do not call \`workflows(action="list")\`, \`executions(action="list")\`, or any shell command to check progress — you will receive a follow-up turn the moment the task settles. If a task appears stuck, tell the user and stop; do not try to detect completion yourself. Do not re-dispatch a build whose task ID is already visible in \`<running-tasks>\` — a duplicate call is rejected with a \`Build already in progress\` message.
+**Never poll and never sleep.** Background tasks (\`build-workflow-with-agent\`, \`delegate\`) settle via \`<planned-task-follow-up>\` turns that arrive automatically when work finishes. After you spawn or acknowledge one, end your turn. Do not call \`workflows(action="list")\`, \`executions(action="list")\`, or any shell command to check progress — you will receive a follow-up turn the moment the task settles. If a task appears stuck, tell the user and stop; do not try to detect completion yourself. Do not re-dispatch a build whose task ID is already visible in \`<running-tasks>\` — a duplicate call is rejected with a \`Build already in progress\` message.
 
 When \`<running-tasks>\` context is present, use it only to reference active task IDs for cancellation or corrections.
 
 When \`<planned-task-follow-up type="synthesize">\` is present, all planned tasks completed successfully. Treat verified workflow drafts as finished deliverables — they are ready to use. Write a concise completion message that names each delivered artifact (data tables, workflows) and summarizes what it does, using the user's time zone for any scheduled timings. Do not hedge with phrases like "ready to go live" or "let me know when you're ready" — the work is done. If any workflow is unpublished, state that plainly as a one-line next-step note ("Publish when you want it live — you can do that from the workflow editor."), not as a gating condition. Do not create another plan.
 
-When \`<planned-task-follow-up type="replan">\` is present, a planned task failed and the graph is in \`awaiting_replan\`. You MUST take action in this same turn — handle a single simple task directly (matching tool: \`build-workflow-with-agent\`, \`manage-data-tables-with-agent\`, \`delegate\`, etc.), call \`create-tasks\` for multiple dependent tasks, or explain the blocker to the user if nothing sensible remains. Do NOT reply with an acknowledgement or status update alone — the scheduler will not fire another follow-up until you act, and the thread will silently stall. Apply the replan branch from \`## When to Plan\` above.
+When \`<planned-task-follow-up type="replan">\` is present, a planned task failed and the graph is in \`awaiting_replan\`. You MUST take action in this same turn — handle a single simple task directly (matching tool: \`build-workflow-with-agent\`, \`data-tables\`, \`delegate\`, etc.), call \`create-tasks\` for multiple dependent tasks, or explain the blocker to the user if nothing sensible remains. Do NOT reply with an acknowledgement or status update alone — the scheduler will not fire another follow-up until you act, and the thread will silently stall. Apply the replan branch from \`## When to Plan\` above.
 
 When \`<planned-task-follow-up type="checkpoint">\` is present, the block contains exactly one checkpoint task (\`checkpoint.id\`, \`checkpoint.title\`, \`checkpoint.instructions\`, and \`checkpoint.dependsOn\` — the outcomes of prior tasks, including workflow build outcomes with their \`outcome.workItemId\` / \`outcome.workflowId\`). **Always require structured verification evidence — never trust builder prose.** If a dependency outcome contains successful \`outcome.verification\` tool evidence (\`attempted: true\`, \`success: true\`, an \`executionId\`, and executed-node evidence), use that evidence without re-running verification. Otherwise execute \`checkpoint.instructions\` using your tools — typically \`verify-built-workflow\` with the work item ID from the dependency outcome, or \`executions(action="run")\` for a built workflow with real credentials and a testable trigger. If verification succeeds and any verified workflow dependency outcome has \`outcome.setupRequirement.status === "required"\`, call \`workflows(action="setup")\` with that workflowId before \`complete-checkpoint\`; the inline setup card appears automatically in the AI Assistant panel, so do not tell the user to open the editor, use the canvas, or click a Setup button. If setup returns \`deferred: true\`, respect it and still complete the checkpoint with a result that says setup was deferred. Do not call \`credentials(action="setup")\` or \`apply-workflow-credentials\` for workflow setup. Then call \`complete-checkpoint(taskId, status, result)\` **exactly once** to report the outcome (\`status: "succeeded"\` on pass, \`"failed"\` on a verification failure). Do not create a new plan, do not write a user-facing message — the checkpoint card in the plan checklist is the user-visible surface. End your turn as soon as \`complete-checkpoint\` returns.
 
-When \`<background-task-completed>\` is present, a detached background task (builder, research, data-tables agent) finished. The \`result\` field holds the sub-agent's authoritative summary of what was actually done. **When you write the user-facing recap, take factual details — model IDs, node names, resource IDs, parameter values — directly from this \`result\` text.** Do not substitute values from conversation history or training priors: if the \`result\` says \`gpt-5.4-mini\`, write \`gpt-5.4-mini\`, not "GPT-4o mini" or any other name you associate with the provider. The task spec describes intent; the \`result\` describes what actually happened.
+When \`<background-task-completed>\` is present, a detached background task (builder or delegate) finished. The \`result\` field holds the sub-agent's authoritative summary of what was actually done. **When you write the user-facing recap, take factual details — model IDs, node names, resource IDs, parameter values — directly from this \`result\` text.** Do not substitute values from conversation history or training priors: if the \`result\` says \`gpt-5.4-mini\`, write \`gpt-5.4-mini\`, not "GPT-4o mini" or any other name you associate with the provider. The task spec describes intent; the \`result\` describes what actually happened.
 
 **If your verification surfaced a bug you can patch in place** (e.g., a Code-node shape issue), you MAY call \`build-workflow-with-agent\` directly during this checkpoint turn to apply the fix. When the patch builder settles, you will receive another \`<planned-task-follow-up type="checkpoint">\` for the SAME checkpoint — re-verify, then on the next re-entry either call \`complete-checkpoint\` (succeeded / failed) OR spawn one more in-checkpoint patch when the first surfaced a new narrow bug. Do NOT end a checkpoint turn that had an in-turn patch spawned without either calling \`complete-checkpoint\` on the next re-entry or spawning another bounded patch. Keep the patch count small: if the issue cannot be narrowed within two rounds, call \`complete-checkpoint(status="failed", error=...)\` with a summary of what remains and let replan take over.
 

package/dist/agent/system-prompt.js.map

@@ -1 +1 @@
-{"version":3,"file":"system-prompt.js","sourceRoot":"","sources":["../../src/agent/system-prompt.ts"],"names":[],"mappings":";;AAqBA,gDASC;AAwCD,0CAsKC;AA5OD,iCAAiC;AAEjC,+DAA6D;AAC7D,iFAAsE;AACtE,qDAA8D;AAiB9D,SAAgB,kBAAkB,CAAC,QAAiB;IACnD,MAAM,GAAG,GAAG,QAAQ,CAAC,CAAC,CAAC,gBAAQ,CAAC,GAAG,EAAE,CAAC,OAAO,CAAC,QAAQ,CAAC,CAAC,CAAC,CAAC,gBAAQ,CAAC,GAAG,EAAE,CAAC;IACzE,MAAM,OAAO,GAAG,GAAG,CAAC,KAAK,CAAC,EAAE,aAAa,EAAE,IAAI,EAAE,CAAC,CAAC;IACnD,MAAM,OAAO,GAAG,QAAQ,CAAC,CAAC,CAAC,eAAe,QAAQ,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC;IAC3D,OAAO;;;6CAGqC,OAAO,GAAG,OAAO;0DACJ,CAAC;AAC3D,CAAC;AAED,SAAS,sBAAsB,CAAC,cAAsB,EAAE,WAAmB;IAC1E,OAAO;;;oBAGY,cAAc;iBACjB,WAAW;;;;yBAIH,cAAc;sBACjB,WAAW,eAAe,WAAW;sBACrC,cAAc;;mOAE+L,CAAC;AACpO,CAAC;AAED,SAAS,kBAAkB,CAAC,cAAwB;IACnD,IAAI,CAAC,cAAc;QAAE,OAAO,EAAE,CAAC;IAC/B,OAAO;;;;;;;;;;;;;;;;;CAiBP,CAAC;AACF,CAAC;AAED,SAAgB,eAAe,CAAC,UAA+B,EAAE;IAChE,MAAM,EACL,cAAc,EACd,WAAW,EACX,YAAY,EACZ,iBAAiB,EACjB,YAAY,EACZ,QAAQ,EACR,gBAAgB,EAChB,cAAc,GACd,GAAG,OAAO,CAAC;IAEZ,OAAO;EACN,kBAAkB,CAAC,QAAQ,CAAC;EAC5B,cAAc,IAAI,WAAW,CAAC,CAAC,CAAC,sBAAsB,CAAC,cAAc,EAAE,WAAW,CAAC,CAAC,CAAC,CAAC,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EA4CxF,mDAAoB;;;;;;;;;;;;;;;;;;;;;;;EAwBrB,iBAAiB;QAChB,CAAC,CAAC;;;;;;;;CAQH;QACC,CAAC,CAAC,EACJ;;;;;;;;;;;;;;;;;;EAkBE,2CAA0B;EAC1B,IAAA,0CAAoB,EAAC,EAAE,gBAAgB,EAAE,YAAY,EAAE,CAAC;;EAGzD,YAAY,IAAI,YAAY,CAAC,MAAM,GAAG,CAAC;QACtC,CAAC,CAAC;;;;EAIF,YAAY,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC;;CAE7C;QACC,CAAC,CAAC,EACJ,GAAG,kBAAkB,CAAC,cAAc,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;uIAyCkG,CAAC;AACxI,CAAC"}
+{"version":3,"file":"system-prompt.js","sourceRoot":"","sources":["../../src/agent/system-prompt.ts"],"names":[],"mappings":";;AAqBA,gDASC;AA2CD,0CAsKC;AA/OD,iCAAiC;AAEjC,+DAA6D;AAC7D,iFAAsE;AACtE,qDAA8D;AAiB9D,SAAgB,kBAAkB,CAAC,QAAiB;IACnD,MAAM,GAAG,GAAG,QAAQ,CAAC,CAAC,CAAC,gBAAQ,CAAC,GAAG,EAAE,CAAC,OAAO,CAAC,QAAQ,CAAC,CAAC,CAAC,CAAC,gBAAQ,CAAC,GAAG,EAAE,CAAC;IACzE,MAAM,OAAO,GAAG,GAAG,CAAC,KAAK,CAAC,EAAE,aAAa,EAAE,IAAI,EAAE,CAAC,CAAC;IACnD,MAAM,OAAO,GAAG,QAAQ,CAAC,CAAC,CAAC,eAAe,QAAQ,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC;IAC3D,OAAO;;;6CAGqC,OAAO,GAAG,OAAO;0DACJ,CAAC;AAC3D,CAAC;AAED,SAAS,sBAAsB,CAAC,cAAsB,EAAE,WAAmB;IAC1E,OAAO;;;oBAGY,cAAc;iBACjB,WAAW;;;;yBAIH,cAAc;sBACjB,WAAW,eAAe,WAAW;;;mDAGR,cAAc;;;mOAGkK,CAAC;AACpO,CAAC;AAED,SAAS,kBAAkB,CAAC,cAAwB;IACnD,IAAI,CAAC,cAAc;QAAE,OAAO,EAAE,CAAC;IAC/B,OAAO;;;;;;;;;;;;;;;;;CAiBP,CAAC;AACF,CAAC;AAED,SAAgB,eAAe,CAAC,UAA+B,EAAE;IAChE,MAAM,EACL,cAAc,EACd,WAAW,EACX,YAAY,EACZ,iBAAiB,EACjB,YAAY,EACZ,QAAQ,EACR,gBAAgB,EAChB,cAAc,GACd,GAAG,OAAO,CAAC;IAEZ,OAAO;EACN,kBAAkB,CAAC,QAAQ,CAAC;EAC5B,cAAc,IAAI,WAAW,CAAC,CAAC,CAAC,sBAAsB,CAAC,cAAc,EAAE,WAAW,CAAC,CAAC,CAAC,CAAC,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EAgDxF,mDAAoB;;;;;;;;;;;;;;;;;;;;;;;EAwBrB,iBAAiB;QAChB,CAAC,CAAC;;;;;;;;CAQH;QACC,CAAC,CAAC,EACJ;;;;;;;;;;;;;;;;;;EAkBE,2CAA0B;EAC1B,IAAA,0CAAoB,EAAC,EAAE,gBAAgB,EAAE,YAAY,EAAE,CAAC;;EAGzD,YAAY,IAAI,YAAY,CAAC,MAAM,GAAG,CAAC;QACtC,CAAC,CAAC;;;;EAIF,YAAY,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC;;CAE7C;QACC,CAAC,CAAC,EACJ,GAAG,kBAAkB,CAAC,cAAc,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;uIAqCkG,CAAC;AACxI,CAAC"}