@agent-native/core 0.101.12 → 0.101.13

package/dist/server/agent-chat/framework-prompts.js.map

@@ -1 +1 @@
-{"version":3,"file":"framework-prompts.js","sourceRoot":"","sources":["../../../src/server/agent-chat/framework-prompts.ts"],"names":[],"mappings":"AAAA,OAAO,QAAQ,MAAM,WAAW,CAAC;AAIjC,OAAO,EACL,kBAAkB,EAClB,yBAAyB,GAE1B,MAAM,qBAAqB,CAAC;AAC7B,OAAO,EAAE,eAAe,EAAE,MAAM,uBAAuB,CAAC;AACxD,OAAO,EAAE,qBAAqB,EAAE,MAAM,qBAAqB,CAAC;AAC5D,OAAO,EAAE,uBAAuB,EAAE,MAAM,yBAAyB,CAAC;AAClE,OAAO,EACL,6BAA6B,EAC7B,0BAA0B,GAC3B,MAAM,oBAAoB,CAAC;AAC5B,OAAO,EAAE,MAAM,EAAE,MAAM,cAAc,CAAC;AACtC,OAAO,EAAE,iBAAiB,EAAE,MAAM,uBAAuB,CAAC;AAE1D,8EAA8E;AAC9E,yEAAyE;AACzE,2EAA2E;AAC3E,yEAAyE;AACzE,8EAA8E;AAE9E,MAAM,oCAAoC,GAAG,GAAG,CAAC;AAEjD;;;;;;;;GAQG;AACH,MAAM,UAAU,qBAAqB,CACnC,QAAyB,EACzB,OAA2E;IAS3E,4EAA4E;IAC5E,gFAAgF;IAChF,0EAA0E;IAC1E,MAAM,cAAc,GAAG,kBAAkB,CAAC,QAAQ,EAAE,OAAO,CAAC,CAAC;IAC7D,MAAM,sBAAsB,GAAG,yBAAyB,CAAC,QAAQ,EAAE,OAAO,CAAC,CAAC;IAC5E,MAAM,qBAAqB,GAAG,OAAO,EAAE,cAAc,KAAK,KAAK,CAAC;IAChE,MAAM,oBAAoB,GAAG,qBAAqB;QAChD,CAAC,CAAC,uJAAuJ;QACzJ,CAAC,CAAC,8FAA8F,CAAC;IACnG,MAAM,oBAAoB,GAAG,qBAAqB;QAChD,CAAC,CAAC,wKAAwK;QAC1K,CAAC,CAAC,qGAAqG,CAAC;IAC1G,MAAM,4BAA4B,GAAG,qBAAqB;QACxD,CAAC,CAAC,gcAAgc;QAClc,CAAC,CAAC,gLAAgL,CAAC;IACrL,MAAM,yBAAyB,GAAG,qBAAqB;QACrD,CAAC,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;qbA0C+a;QACjb,CAAC,CAAC;;qZAE+Y,CAAC;IACpZ,MAAM,4BAA4B,GAAG,qBAAqB;QACxD,CAAC,CAAC;;;;;;;;;;;;;;;;0yBAgBoyB;QACtyB,CAAC,CAAC;;kNAE4M,CAAC;IAEjN,MAAM,qBAAqB,GAAG;;;;;;;;;;0FAU0D,oBAAoB,kHAAkH,oBAAoB;;EAElP,yBAAyB;;;;EAIzB,4BAA4B;;;;;;;;;;;;;EAa5B,cAAc,EAAE,CAAC;IAEjB,MAAM,oBAAoB,GAAG;;;;;;;;;;;;;;;;;;;;;EAqB7B,cAAc,EAAE,CAAC;IAEjB,MAAM,6BAA6B,GAAG;;;;;;;;;;6EAUqC,oBAAoB,8CAA8C,oBAAoB;;EAEjK,4BAA4B;;;;;EAK5B,sBAAsB,EAAE,CAAC;IAEzB,MAAM,4BAA4B,GAAG;;;;;;;;;;;;;;;EAerC,sBAAsB,EAAE,CAAC;IAEzB,OAAO;QACL,cAAc;QACd,sBAAsB;QACtB,qBAAqB;QACrB,oBAAoB;QACpB,6BAA6B;QAC7B,4BAA4B;KAC7B,CAAC;AACJ,CAAC;AAED,MAAM,CAAC,MAAM,gCAAgC,GAAG,CAAC,GAAG,EAAE;IACpD,yEAAyE;IACzE,MAAM,EACJ,cAAc,EAAE,aAAa,EAC7B,sBAAsB,EAAE,oBAAoB,GAC7C,GAAG,qBAAqB,EAAE,CAAC;IAC5B,OAAO;QACL,aAAa;QACb,oBAAoB;QACpB,wBAAwB,EAAE,0BAA0B;QACpD,qBAAqB;QACrB,qBAAqB;QACrB,uBAAuB;QACvB,6BAA6B;KAC9B,CAAC;AACJ,CAAC,CAAC,EAAE,CAAC;AAEL;;;;GAIG;AACH,MAAM,CAAC,KAAK,UAAU,gBAAgB,CACpC,KAAa,EACb,aAAa,GAAwB,MAAM;IAE3C,IAAI,CAAC;QACH,OAAO,MAAM,qBAAqB,CAAC;YACjC,KAAK;YACL,KAAK,EAAE,eAAe,EAAE,IAAI,IAAI;YAChC,aAAa;SACd,CAAC,CAAC;IACL,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,EAAE,CAAC;IACZ,CAAC;AACH,CAAC;AAED;;;;;;;;;;;GAWG;AACH,MAAM,UAAU,qBAAqB,CACnC,QAAqC,EACrC,IAAI,GAAmB,MAAM,EAC7B,gBAA2B;IAE3B,IAAI,CAAC,QAAQ,IAAI,MAAM,CAAC,IAAI,CAAC,QAAQ,CAAC,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,EAAE,CAAC;IAE/D,MAAM,gBAAgB,GAAG,MAAM,CAAC,OAAO,CAAC,QAAQ,CAAC,CAAC;IAClD,MAAM,YAAY,GAAG,gBAAgB,CAAC,CAAC,CAAC,IAAI,GAAG,CAAC,gBAAgB,CAAC,CAAC,CAAC,CAAC,SAAS,CAAC;IAC9E,MAAM,aAAa,GAAG,YAAY;QAChC,CAAC,CAAC,gBAAgB,CAAC,MAAM,CAAC,CAAC,CAAC,IAAI,CAAC,EAAE,EAAE,CAAC,YAAY,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC;QAC7D,CAAC,CAAC,gBAAgB,CAAC;IACrB,MAAM,kBAAkB,GAAG,gBAAgB,CAAC,MAAM,GAAG,aAAa,CAAC,MAAM,CAAC;IAC1E,MAAM,gBAAgB,GAAG,CAAC,KAAkB,EAAE,EAAE,CAC9C,KAAK,CAAC,MAAM,IAAI,OAAO,KAAK,CAAC,MAAM,CAAC,QAAQ,KAAK,QAAQ;QACvD,CAAC,CAAC,0BAA0B,KAAK,CAAC,MAAM,CAAC,QAAQ,KAAK;QACtD,CAAC,CAAC,EAAE,CAAC;IAET,IAAI,IAAI,KAAK,MAAM,EAAE,CAAC;QACpB,MAAM,YAAY,GAAG,aAAa,CAAC,GAAG,CAAC,CAAC,CAAC,IAAI,EAAE,KAAK,CAAC,EAAE,EAAE;YACvD,MAAM,IAAI,GAAG,iBAAiB,CAC5B,KAAK,CAAC,IAAI,CAAC,WAAW,EACtB,oCAAoC,CACrC,CAAC;YACF,OAAO,OAAO,IAAI,QAAQ,IAAI,GAAG,gBAAgB,CAAC,KAAK,CAAC,EAAE,CAAC;QAC7D,CAAC,CAAC,CAAC;QAEH,OAAO;;;;EAIT,YAAY,CAAC,IAAI,CAAC,IAAI,CAAC,GACnB,kBAAkB,GAAG,CAAC;YACpB,CAAC,CAAC,OAAO,kBAAkB,0BAA0B,kBAAkB,KAAK,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,OAAO,sHAAsH;YACrN,CAAC,CAAC,EACN,EAAE,CAAC;IACL,CAAC;IAED,MAAM,KAAK,GAAG,aAAa,CAAC,GAAG,CAAC,CAAC,CAAC,IAAI,EAAE,KAAK,CAAC,EAAE,EAAE;QAChD,MAAM,IAAI,GAAG,KAAK,CAAC,IAAI,CAAC,WAAW,CAAC;QACpC,MAAM,MAAM,GAAG,KAAK,CAAC,IAAI,CAAC,UAAU,EAAE,UAAU,CAAC;QACjD,MAAM,cAAc,GAAG,IAAI,GAAG,CAAC,KAAK,CAAC,IAAI,CAAC,UAAU,EAAE,QAAQ,IAAI,EAAE,CAAC,CAAC;QAEtE,4EAA4E;QAC5E,IAAI,CAAC,MAAM,IAAI,MAAM,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;YAChD,OAAO,mBAAmB,IAAI,QAAQ,IAAI,GAAG,gBAAgB,CAAC,KAAK,CAAC,EAAE,CAAC;QACzE,CAAC;QACD,MAAM,OAAO,GAAG,MAAM,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC;QACvC,8DAA8D;QAC9D,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,EAAE;YACxB,MAAM,EAAE,GAAG,cAAc,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;YACzC,MAAM,EAAE,GAAG,cAAc,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;YACzC,IAAI,EAAE,KAAK,EAAE;gBAAE,OAAO,EAAE,GAAG,EAAE,CAAC;YAC9B,OAAO,CAAC,CAAC,aAAa,CAAC,CAAC,CAAC,CAAC;QAC5B,CAAC,CAAC,CAAC;QACH,MAAM,QAAQ,GAAa,EAAE,CAAC;QAC9B,MAAM,QAAQ,GAAa,EAAE,CAAC;QAC9B,MAAM,aAAa,GAAa,EAAE,CAAC;QACnC,KAAK,MAAM,CAAC,CAAC,EAAE,CAAC,CAAC,IAAI,OAAO,EAAE,CAAC;YAC7B,MAAM,IAAI,GAAI,CAAuB,CAAC,IAAI,IAAI,KAAK,CAAC;YACpD,MAAM,IAAI,GAAG,KAAK,CAAC,KAAK,IAAI,GAAG,CAAC;YAChC,IAAI,cAAc,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC;gBAC1B,QAAQ,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;gBACpB,aAAa,CAAC,IAAI,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC;YAC/B,CAAC;iBAAM,CAAC;gBACN,QAAQ,CAAC,IAAI,CAAC,IAAI,IAAI,GAAG,CAAC,CAAC;YAC7B,CAAC;QACH,CAAC;QACD,MAAM,GAAG,GAAG,CAAC,cAAc,GAAG,IAAI,EAAE,GAAG,QAAQ,EAAE,GAAG,QAAQ,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;QACxE,MAAM,YAAY,GAChB,aAAa,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,cAAc,aAAa,CAAC,IAAI,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC;QAC5E,OAAO,OAAO,GAAG,QAAQ,IAAI,IAAI,YAAY,GAAG,gBAAgB,CAAC,KAAK,CAAC,EAAE,CAAC;IAC5E,CAAC,CAAC,CAAC;IAEH,OAAO;;;;;;EAMP,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC;AACrB,CAAC;AAED;;;;;;;;GAQG;AACH,MAAM,iBAAiB,GAAG;IACxB,sBAAsB;IACtB,mBAAmB;IACnB,sBAAsB;IACtB,qBAAqB;IACrB,sBAAsB;IACtB,UAAU;CACF,CAAC;AAEX,MAAM,UAAU,6BAA6B,CAC3C,QAAqC;IAErC,OAAO,iBAAiB,CAAC,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,IAAI,QAAQ,CAAC,CAAC;AAC9D,CAAC;AAED,MAAM,UAAU,yBAAyB,CACvC,QAAqC;IAErC,MAAM,cAAc,GAAG,sBAAsB,IAAI,QAAQ,CAAC;IAC1D,MAAM,oBAAoB,GAAG,qBAAqB,IAAI,QAAQ,CAAC;IAC/D,MAAM,sBAAsB,GAAG;QAC7B,sBAAsB,IAAI,QAAQ,CAAC,CAAC,CAAC,wBAAwB,CAAC,CAAC,CAAC,IAAI;QACpE,mBAAmB,IAAI,QAAQ,CAAC,CAAC,CAAC,qBAAqB,CAAC,CAAC,CAAC,IAAI;KAC/D,CAAC,MAAM,CAAC,OAAO,CAAC,CAAC;IAClB,MAAM,UAAU,GAAG,UAAU,IAAI,QAAQ,CAAC;IAC1C,MAAM,gBAAgB,GAAG,sBAAsB,IAAI,QAAQ,CAAC;IAC5D,IACE,CAAC,cAAc;QACf,CAAC,oBAAoB;QACrB,CAAC,UAAU;QACX,CAAC,gBAAgB;QAEjB,OAAO,EAAE,CAAC;IAEZ,MAAM,SAAS,GAAG;QAChB,GAAG,sBAAsB;QACzB,cAAc,CAAC,CAAC,CAAC,wBAAwB,CAAC,CAAC,CAAC,IAAI;QAChD,oBAAoB,CAAC,CAAC,CAAC,uBAAuB,CAAC,CAAC,CAAC,IAAI;QACrD,gBAAgB,CAAC,CAAC,CAAC,wBAAwB,CAAC,CAAC,CAAC,IAAI;QAClD,UAAU,CAAC,CAAC,CAAC,YAAY,CAAC,CAAC,CAAC,IAAI;KACjC,CAAC,MAAM,CAAC,OAAO,CAAC,CAAC;IAElB,OAAO;;kCAEyB,SAAS,CAAC,IAAI,CAAC,IAAI,CAAC;;;;6wBAIutB,CAAC;AAC9wB,CAAC;AAED;;;GAGG;AACH,MAAM,CAAC,KAAK,UAAU,YAAY,CAChC,GAAW,EACX,MAAc,EACd,KAAa,EACb,OAAuE;IAEvE,IAAI,KAAK,GAAG,CAAC,IAAI,OAAO,CAAC,MAAM,IAAI,GAAG;QAAE,OAAO;IAC/C,MAAM,IAAI,GAAG,IAAI,GAAG,CAAC;QACnB,cAAc;QACd,MAAM;QACN,OAAO;QACP,SAAS;QACT,MAAM;QACN,QAAQ;QACR,QAAQ;QACR,MAAM;KACP,CAAC,CAAC;IACH,IAAI,OAA8B,CAAC;IACnC,IAAI,CAAC;QACH,MAAM,EAAE,GAAG,MAAM,MAAM,EAAE,CAAC;QAC1B,OAAO,GAAG,EAAE,CAAC,WAAW,CAAC,GAAG,EAAE,EAAE,aAAa,EAAE,IAAI,EAAE,CAAC,CAAC;IACzD,CAAC;IAAC,MAAM,CAAC;QACP,OAAO;IACT,CAAC;IACD,KAAK,MAAM,KAAK,IAAI,OAAO,EAAE,CAAC;QAC5B,IAAI,OAAO,CAAC,MAAM,IAAI,GAAG;YAAE,OAAO;QAClC,IAAI,IAAI,CAAC,GAAG,CAAC,KAAK,CAAC,IAAI,CAAC,IAAI,KAAK,CAAC,IAAI,CAAC,UAAU,CAAC,GAAG,CAAC;YAAE,SAAS;QACjE,MAAM,OAAO,GAAG,MAAM,CAAC,CAAC,CAAC,GAAG,MAAM,IAAI,KAAK,CAAC,IAAI,EAAE,CAAC,CAAC,CAAC,KAAK,CAAC,IAAI,CAAC;QAChE,MAAM,KAAK,GAAG,KAAK,CAAC,WAAW,EAAE,CAAC;QAClC,OAAO,CAAC,IAAI,CAAC;YACX,IAAI,EAAE,OAAO;YACb,IAAI,EAAE,KAAK,CAAC,IAAI;YAChB,IAAI,EAAE,KAAK,CAAC,CAAC,CAAC,QAAQ,CAAC,CAAC,CAAC,MAAM;SAChC,CAAC,CAAC;QACH,IAAI,KAAK;YACP,MAAM,YAAY,CAChB,QAAQ,CAAC,IAAI,CAAC,GAAG,EAAE,KAAK,CAAC,IAAI,CAAC,EAC9B,OAAO,EACP,KAAK,GAAG,CAAC,EACT,OAAO,CACR,CAAC;IACN,CAAC;AACH,CAAC","sourcesContent":["import nodePath from \"node:path\";\n\nimport type { ActionEntry } from \"../../agent/production-agent.js\";\nimport type { DatabaseToolsOption } from \"../../scripts/db/tool-mode.js\";\nimport {\n  buildFrameworkCore,\n  buildFrameworkCoreCompact,\n  type PromptExamples,\n} from \"../prompts/index.js\";\nimport { getRequestOrgId } from \"../request-context.js\";\nimport { loadSchemaPromptBlock } from \"../schema-prompt.js\";\nimport { resolveInitialToolNames } from \"./action-filters-a2a.js\";\nimport {\n  createDataWidgetActionEntries,\n  FRAMEWORK_CONTEXT_SECTIONS,\n} from \"./context-tools.js\";\nimport { lazyFs } from \"./lazy-fs.js\";\nimport { compactPromptLine } from \"./prompt-resources.js\";\n\n// ---------------------------------------------------------------------------\n// Framework-level system prompt assembly (production/dev, full/compact),\n// the \"Available Actions\" and corpus-tools prompt sections, the SQL schema\n// block, and the codebase file-tree walker used by a few dev-mode tools.\n// ---------------------------------------------------------------------------\n\nconst MAX_ACTION_SUMMARY_DESCRIPTION_CHARS = 140;\n\n/**\n * Framework-level instructions injected into every agent's system prompt.\n * Prompt text lives in packages/core/src/server/prompts/ so this file stays\n * focused on routing and assembly logic.\n *\n * buildFrameworkPrompts() is called once per plugin instantiation (not per\n * request) with the template's promptExamples, producing the four assembled\n * prompt strings used at request time.\n */\nexport function buildFrameworkPrompts(\n  examples?: PromptExamples,\n  options?: { databaseTools?: DatabaseToolsOption; extensionTools?: boolean },\n): {\n  FRAMEWORK_CORE: string;\n  FRAMEWORK_CORE_COMPACT: string;\n  PROD_FRAMEWORK_PROMPT: string;\n  DEV_FRAMEWORK_PROMPT: string;\n  PROD_FRAMEWORK_PROMPT_COMPACT: string;\n  DEV_FRAMEWORK_PROMPT_COMPACT: string;\n} {\n  // Note: FIRST_SESSION_PERSONALIZATION is NOT appended here — it is injected\n  // at per-request prompt-assembly time only for new threads (no prior messages).\n  // This prevents the ~1.5KB block from appearing on every request forever.\n  const FRAMEWORK_CORE = buildFrameworkCore(examples, options);\n  const FRAMEWORK_CORE_COMPACT = buildFrameworkCoreCompact(examples, options);\n  const extensionToolsEnabled = options?.extensionTools !== false;\n  const planModeArtifactList = extensionToolsEnabled\n    ? \"source-code handoffs and app-created artifacts such as extensions, widgets, dashboards, calculators, mini-apps, documents, designs, slides, or videos\"\n    : \"source-code handoffs and app-created artifacts such as documents, designs, slides, or videos\";\n  const planModeBlockedTools = extensionToolsEnabled\n    ? \"`render-inline-extension`, `create-extension`, `update-extension`, `connect-builder`, or any action that creates, updates, deletes, sends, publishes, or persists data\"\n    : \"`connect-builder`, or any action that creates, updates, deletes, sends, publishes, or persists data\";\n  const extensionConnectBuilderGuard = extensionToolsEnabled\n    ? \"If the complete request can be satisfied by a self-contained extension or an existing named slot, use `render-inline-extension`, `create-extension`, `show-extension-inline`, or `update-extension` instead. If the exact placement or behavior requires changing the host UI or no suitable slot exists, continue with the normal `connect-builder` source-change flow even if the user called it an extension; never stop at saying extensions cannot do it.\"\n    : \"Because extension tools are disabled, do NOT invent an extension workflow. Only use `connect-builder` when the request genuinely requires changing the host app's source code.\";\n  const extensionInstructionsFull = extensionToolsEnabled\n    ? `### Generative UI and Extensions (Mini-Apps)\n\nIn Act mode, if the user asks for generated interactive UI in chat, choose the smallest extension action that matches the lifetime:\n\n- For a **one-time inline UI** that answers the current chat turn (knobs, controls, pickers, calculators, temporary dashboards, visualizers), call \\`render-inline-extension\\` immediately with a self-contained Alpine.js HTML body. It renders inside the transcript and is not saved.\n- For a **reusable or saved UI** (an extension/widget/dashboard/calculator/mini-app the user can reopen from Extensions), call \\`create-extension\\` with a self-contained Alpine.js HTML body. It saves to the Extensions view and also renders inline in chat.\n- To **reuse an existing saved extension inline**, call \\`show-extension-inline\\` with its id, or a search string when the id is unknown.\n\nThese are **NOT** source-code changes and do **NOT** go through \\`connect-builder\\`. Extensions are sandboxed mini-apps — no source files are touched, no PR is opened, no build is required. Saved extensions can be edited later via \\`update-extension\\`.\n\nIf the app exposes native actions or instructions for dashboards, reports, analyses, charts, documents, decks, or other domain artifacts, use those app-native actions first. Choose an extension only when the user explicitly asks for an extension/custom mini-app, or when the app's native artifact format cannot faithfully express the requested interaction.\n\nKeep \\`create-extension\\` payloads compact enough to finish quickly. For complex extensions, create a useful working v1 first, then call \\`update-extension\\` with focused edits for refinements instead of trying to assemble one enormous initial tool input.\n\nGenerated UI content can use appAction(), appFetch(), dbQuery(), extensionFetch(), extensionData, agentNative.ui.output(value, opts?), and agentNative.chat.send(...)/sendToAgentChat(...). Use appAction() for app data writes, and dbQuery() only for read-only inspection of known app SQL tables. It can receive chat inputs through slotContext/window.onSlotContext. Use agentNative.ui.output for passive current values from knobs, sliders, selections, and controls; it writes application state at \\`inline-ui:<extensionId>:output\\` scoped to the inline extension id returned by \\`render-inline-extension\\` or \\`show-extension-inline\\`. When the user later says \"use that value\", \"apply the current setting\", or similar, read it with \\`readAppState(\"inline-ui:<id>:output\")\\` instead of asking them to send it again. Use agentNative.chat.send for visible submit/apply actions that should put a message into chat. Transient extensionData is browser-local and not agent-readable, synced, promoted, or garbage-collected; use application_state/appFetch, appAction, ui.output, or chat.send for anything the agent or app must observe. Use semantic Tailwind classes like bg-background, text-foreground, bg-primary, border-border, and text-muted-foreground so the UI inherits the parent app theme.\n\nIf the user asks to change, edit, fix, style, rename, or add behavior to an existing extension/widget/dashboard/calculator/mini-app, use the current extension id from \\`<current-screen>\\` or \\`<current-url>\\` when present. Call \\`get-extension\\` only if you need to inspect its content, then \\`update-extension\\` with that id. After one content read, keep the body in working memory and move to focused \\`update-extension\\` \\`edits\\`/\\`patches\\`; do not loop on repeated \\`get-extension\\` + \\`run-code\\` string scans before writing. Use \\`list-extensions\\` only when no current id/name is available. Existing extension edits are SQL data updates, not source-code changes, even when the request says \"change the UI\" or \"fix this\". Do **NOT** call \\`connect-builder\\` for existing extension edits.\n\nIn Act mode, when in doubt — if the request asks for a new small interactive utility and does not need reuse, choose \\`render-inline-extension\\`; if it mentions saving/reuse or asks for an extension/widget/dashboard/calculator/mini-app, choose \\`create-extension\\`. If it references an existing one or the current extension page, choose \\`update-extension\\`. Do **not** preface the call with planning text like \"let me build the dashboard…\" — just call the right extension action directly.\n\nNote: \"extension\" is the user-facing primitive (the sandboxed Alpine.js mini-app). Don't confuse it with the LLM concept of \"tools\" (function calls) — those are how you invoke ANY action, including \\`create-extension\\` itself.\n\nFor existing extensions, use \\`get-extension\\` or \\`update-extension\\` directly when \\`<current-screen>\\` or \\`<current-url>\\` provides an \\`extensionId\\`. Use \\`list-extensions\\` only to browse or resolve an unknown name. If the user wants a shared extension removed only from their view, use \\`hide-extension\\` — do not query or mutate the legacy \\`tools\\` table directly.\n\n### Extensions vs. Code Changes — Pick the Right Path\n\nRoute by the exact outcome, not by whether the user calls it an extension. Extensions render in their own sandboxed iframe, either on their own page or inside an existing named slot. They CANNOT change the host app's nav, restyle or inject elements into existing native components, replace built-in views, or render at an arbitrary location that has no slot.\n\n<routing>\n| The request is for…                                              | Path                          |\n| ---------------------------------------------------------------- | ------------------------------ |\n| A one-off interactive answer inside chat (controls, picker, calculator, temporary visualizer) | \\`render-inline-extension\\` — inline only |\n| A new self-contained surface (widget, dashboard, calculator, viewer, list, tracker) | \\`create-extension\\` — ships instantly, no PR |\n| Loading a saved extension inside chat | \\`show-extension-inline\\` |\n| Editing an existing extension (fix, restyle, rename, add behavior) | \\`update-extension\\`           |\n| The host app's own chrome (nav bar, sidebar, layout, routes, shipped components, existing styles, business logic) | \\`connect-builder\\` — a real source-code change |\n| UI inside or beside a native component where no named slot exists | \\`connect-builder\\` — add the native UI or a suitable slot in source |\n| Ambiguous, satisfiable either way (e.g. \"give me an unread view\") | \\`render-inline-extension\\` for chat-only, \\`create-extension\\` for reusable |\n</routing>\n\nIf an extension could only approximate the request in a different location, do not silently downgrade the requirement and do not end with \"extensions cannot do that.\" Briefly explain the boundary, then follow the normal source-code handoff so the app can still be customized fully.\n\nWorked examples: \"a widget showing unread emails grouped by sender\", \"a tracker for my newsletter subscriptions\", \"a custom kanban board with drag-and-drop rules the app does not have\" → \\`create-extension\\`. \"Add an Unread tab to the left navigation\", \"show local time beside every native Calendar attendee row\", \"make the subject lines wrap\", \"change the inbox grouping logic\", \"add a field to the compose form\" → \\`connect-builder\\`.`\n    : `### Extensions Disabled\n\nExtension creation and management tools are disabled for this app. Do not claim you can create, edit, hide, or delete Agent-Native extensions unless the template exposes its own typed action for that workflow. For requests that would otherwise be handled as an extension/widget/dashboard/calculator mini-app, explain that this app has disabled extension tools and use the app's available actions instead.`;\n  const extensionInstructionsCompact = extensionToolsEnabled\n    ? `### Generative UI and Extensions (Mini-Apps)\n\nIn Act mode, if the user asks for generated interactive UI in chat, call \\`render-inline-extension\\` for one-time inline controls/knobs/calculators/visualizers that do not need saving. If the user asks for an **extension**, **widget**, **dashboard**, **calculator**, or **mini-app** that should be reusable or saved, call \\`create-extension\\` with a self-contained Alpine.js HTML body. To load a saved extension inline, call \\`show-extension-inline\\`. These are NOT code changes — extensions are sandboxed mini-apps. Do not preface with \"let me build…\" — just call the right extension action.\n\nUse app-native artifact actions first when they exist for dashboards, reports, analyses, charts, documents, decks, or similar domain artifacts. Pick \\`create-extension\\` only for explicit extension/custom mini-app requests or for behavior the native artifact format cannot support.\n\nKeep the first \\`create-extension\\` call compact and working. If the request is complex, create the v1 first and then refine with focused \\`update-extension\\` edits.\n\nGenerated UI can read chat inputs from slotContext/window.onSlotContext, see/update app state through appFetch/appAction, use extensionData, record passive current values through agentNative.ui.output(value, opts?), and send visible results through agentNative.chat.send(...) or sendToAgentChat(...). ui.output writes \\`inline-ui:<extensionId>:output\\` in application state; when the user asks to use the current slider/selection/value, read \\`readAppState(\"inline-ui:<id>:output\")\\`. Transient extensionData is browser-local only, so do not rely on it for values the agent or app must observe. Use semantic Tailwind theme classes.\n\nIf the user asks to change, edit, fix, style, rename, or add behavior to an existing extension/widget/dashboard/calculator/mini-app, use the current extension id from \\`<current-screen>\\` or \\`<current-url>\\` when present. Call \\`get-extension\\` only if you need to inspect its content, then \\`update-extension\\` with that id. After one content read, use focused \\`update-extension\\` \\`edits\\`/\\`patches\\`; do not repeatedly re-read and scan the same HTML with \\`run-code\\` before writing. Use \\`list-extensions\\` only when no current id/name is available. Existing extension edits are SQL data updates, not source-code changes. Do NOT call \\`connect-builder\\` for them.\n\nFor existing extensions, use \\`get-extension\\` or \\`update-extension\\` directly when \\`<current-screen>\\` or \\`<current-url>\\` provides an \\`extensionId\\`. Use \\`list-extensions\\` only to browse or resolve an unknown name. Use \\`hide-extension\\` when the user wants a shared extension removed only from their own view. Do not query the legacy \\`tools\\` table directly.\n\n### Extensions vs. Code Changes — Pick the Right Path\n\nIf the user wants a **one-off interactive answer in chat**, use \\`render-inline-extension\\`. If they want a **new reusable self-contained surface** (custom widget, dashboard, list, viewer, calculator), use \\`create-extension\\` — extensions ship instantly without a PR. Extensions can render only on their own page or in an existing named slot; they cannot inject UI into arbitrary native components. If the exact request changes host chrome, native components, layout, styles, routes, business logic, or needs placement where no slot exists, treat it as a source-code change and use the normal \\`connect-builder\\` flow even if the user called it an extension. Never stop at \"extensions cannot do that\" or silently offer a different placement; explain the boundary briefly and continue the code-change handoff.`\n    : `### Extensions Disabled\n\nExtension creation and management tools are disabled for this app. Do not claim you can create, edit, hide, or delete Agent-Native extensions unless the template exposes its own typed action for that workflow.`;\n\n  const PROD_FRAMEWORK_PROMPT = `## Agent-Native Framework — Production Mode\n\nYou are an AI agent in an agent-native application, running in **production mode**.\n\nThe agent and the UI are equal partners — everything the UI can do, you can do via your tools, and vice versa. They share the same SQL database and stay in sync automatically.\n\n**In production mode, you operate through registered actions exposed as tools.** These are your capabilities — use them to read data, take actions, and help the user. You cannot edit source code or access the filesystem directly. Your tools are the app's API.\n\n### Plan Mode\n\nIf the current turn is in Plan mode, plan before anything gets written. This applies to ${planModeArtifactList}. Use only read-only tools, clarify the goal when needed, and return a concrete plan for approval. Do not call ${planModeBlockedTools} until the user switches back to Act mode.\n\n${extensionInstructionsFull}\n\n### Code Changes Not Available — Call \\`connect-builder\\` Immediately\n\n${extensionConnectBuilderGuard}\n\nIn Act mode, when the user asks you to change the UI, modify code, add a feature, fix a bug in the app itself, change styles, add a hook, create a component, add a route, add an integration, or anything else that requires editing source files — you MUST take exactly these steps, in order:\n\n1. Briefly acknowledge the user's specific request in their own terms — one short clause naming what they asked for (e.g. \"Got it — wider subject lines in the email list.\"). Do NOT restate the request verbatim, do NOT add a generic preamble, and do NOT promise outcomes. Skip this step entirely if the user already knows you're handing off (e.g. they said \"send this to Builder\").\n2. Call the \\`connect-builder\\` tool, passing the user's full request verbatim as the \\`prompt\\` argument. This renders an inline card. The returned \\`builderEnabled\\` flag is authoritative: \\`true\\` means Builder Cloud Agents can take the code-change handoff; \\`false\\` means this still requires a code change, but no Builder Cloud Agent can run from this workspace. If Builder is connected and \\`builderEnabled\\` is true, the card hands the prompt off to Builder's cloud agent on one click and returns a branch URL. If Builder is not connected and \\`builderEnabled\\` is true, it shows the Connect Builder flow. If \\`builderEnabled\\` is false, it still shows the card, but as a code-change fallback instead of a runnable cloud handoff.\n3. After the card renders, inspect the tool result and write one sentence that frames the next click around what the user just asked — not as a Builder pitch. If \\`builderEnabled\\` is true and the card can send, say something like \"Click Send to Builder and it'll wire that up for you.\" If the user needs to connect first, say something like \"Connect Builder once and it'll handle this and future changes.\" If \\`builderEnabled\\` is false, say: \"This requires a code change. Edit locally or use Builder.io to edit this code in the cloud and continue customizing the app any way you like.\" Do NOT say \"click Send to Builder\", mention a branch URL, say the card is pre-loaded, or imply a Builder Cloud Agent can run when \\`builderEnabled\\` is false.\n\nWhen \\`builderEnabled\\` is false, Builder Cloud Agents are not self-serve from Builder org settings. Do NOT tell the user to go to Builder org settings, beta features, \"Cloud Agents\", or \"AI Agents\" to enable them. The only allowed guidance is the card's code-change fallback: edit locally, use Agent Native Desktop, or use Builder.io to edit this code in the cloud and continue customizing the app any way you like.\n\n**Act-mode handoff — do exactly this:** The moment a code change is requested, call \\`connect-builder\\` with the user's verbatim request, then write one sentence framing the next click. That is the whole job: Builder plans and edits in its own sandbox, so the planning, file-mapping, and code all happen there, not here. Keep your turn to the call plus that one sentence — skip code exploration, implementation plans, \\`resources\\` writes of specs, and sub-agents (they have no code-editing tools either). You don't need filesystem access to recommend Builder, so don't reach for it or list tools you lack.\n\nBuilder Cloud Agents are the recommended path when \\`builderEnabled\\` is true because they are one-click and run in the cloud. Local dev, Agent Native Desktop, and Builder.io cloud editing are the fallback when \\`builderEnabled\\` is false.\n${FRAMEWORK_CORE}`;\n\n  const DEV_FRAMEWORK_PROMPT = `## Agent-Native Framework — Development Mode\n\nYou are an AI agent in an agent-native application, running in **development mode**.\n\nThe agent and the UI are equal partners — everything the UI can do, you can do via tools/scripts, and vice versa. They share the same SQL database and stay in sync automatically.\n\n**In development mode, you have full local access — use it with senior-engineer judgment** (read before you edit, keep changes scoped, verify before you claim done):\n- Run any shell command via the \\`bash\\` tool (node, curl, pnpm, rg, git, etc.), including arbitrary code: \\`bash({ command: 'node -e \"console.log(1+1)\"' })\\`\n- Read and write any file on the filesystem; edit source, install packages, modify the app\n- Query and modify the database\n- Call external APIs (via bash with curl, or via scripts)\n\nWhen no dedicated tool/action exists for what you need, reach for \\`bash\\` — e.g. \\`bash({ command: 'curl -s https://api.example.com/data' })\\`.\n\n**Template-specific actions are invoked via bash, NOT as direct tools.** In dev mode, the only tools registered as native tool calls are framework-level utilities (bash, read, edit, write, database, resources, chat, teams, jobs). Anything from the template's \\`actions/\\` directory must be run through bash: \\`bash({ command: 'pnpm action <name> --arg value' })\\`. The \"Available Actions\" section below shows the exact CLI syntax for each one — copy that command verbatim and pass it to \\`bash\\`. Do not try to call template actions by name as if they were tools; they will not appear in your tool list.\n\nWhen editing code, follow the agent-native architecture:\n- Every feature needs all four areas: UI + scripts + skills/instructions + application-state sync\n- All SQL must be dialect-agnostic (works on SQLite and Postgres)\n- No Node.js-specific APIs in server routes (must work on Cloudflare Workers, etc.)\n- Use shadcn/ui components and Tabler Icons for all UI work\n${FRAMEWORK_CORE}`;\n\n  const PROD_FRAMEWORK_PROMPT_COMPACT = `## Agent-Native Framework — Production Mode\n\nYou are an AI agent in an agent-native application, running in **production mode**.\n\nThe agent and the UI are equal partners — everything the UI can do, you can do via your tools, and vice versa. They share the same SQL database and stay in sync automatically.\n\n**In production mode, you operate through registered actions exposed as tools.** These are your capabilities — use them to read data, take actions, and help the user. You cannot edit source code or access the filesystem directly. Your tools are the app's API.\n\n### Plan Mode\n\nIf the turn is in Plan mode, plan before anything gets written — including ${planModeArtifactList}. Use read-only tools only and do not call ${planModeBlockedTools} until the user switches back to Act mode.\n\n${extensionInstructionsCompact}\n\n### Code Changes — Call \\`connect-builder\\`\n\nIn Act mode, when a request genuinely needs a source-code edit (per the rules above), do this in order: (1) briefly acknowledge the user's specific ask in their own terms — one short clause, no preamble — then (2) call \\`connect-builder\\` with the user's request as the \\`prompt\\`, then (3) inspect \\`builderEnabled\\` in the result and write one sentence framing the next click around what they asked for, not a Builder pitch. When \\`builderEnabled\\` is true, Builder Cloud Agents can take the handoff; when \\`builderEnabled\\` is false, say this requires a code change and they can edit locally or use Builder.io to edit this code in the cloud and continue customizing the app any way they like. Do NOT write code, list files, make plans, or spawn sub-agents. Mention \\`npx agent-native create <app-name>\\`, Agent Native Desktop, or the code-change fallback when Builder Cloud Agents aren't available. Never tell users to enable Builder Cloud Agents from Builder org settings, beta features, \"Cloud Agents\", or \"AI Agents\"; they are not self-serve there.\n${FRAMEWORK_CORE_COMPACT}`;\n\n  const DEV_FRAMEWORK_PROMPT_COMPACT = `## Agent-Native Framework — Development Mode\n\nYou are an AI agent in an agent-native application, running in **development mode**.\n\nThe agent and the UI are equal partners — everything the UI can do, you can do via tools/scripts, and vice versa. They share the same SQL database and stay in sync automatically.\n\n**In development mode, you have full local access** — shell, filesystem, database, external APIs, source edits, and package installs. Use it with senior-engineer judgment: read before you edit, keep changes scoped, verify before you claim done.\n\n**Template-specific actions are invoked via bash, NOT as direct tools.** Run them with: \\`bash({ command: 'pnpm action <name> --arg value' })\\`. See the \"Available Actions\" section below for CLI syntax.\n\nWhen editing code, follow the agent-native architecture:\n- Every feature needs all four areas: UI + scripts + skills/instructions + application-state sync\n- All SQL must be dialect-agnostic (works on SQLite and Postgres)\n- No Node.js-specific APIs in server routes (must work on Cloudflare Workers, etc.)\n- Use shadcn/ui components and Tabler Icons for all UI work\n${FRAMEWORK_CORE_COMPACT}`;\n\n  return {\n    FRAMEWORK_CORE,\n    FRAMEWORK_CORE_COMPACT,\n    PROD_FRAMEWORK_PROMPT,\n    DEV_FRAMEWORK_PROMPT,\n    PROD_FRAMEWORK_PROMPT_COMPACT,\n    DEV_FRAMEWORK_PROMPT_COMPACT,\n  };\n}\n\nexport const _agentChatPromptSectionsForTests = (() => {\n  // Built with default (no template-specific) examples for test stability.\n  const {\n    FRAMEWORK_CORE: frameworkCore,\n    FRAMEWORK_CORE_COMPACT: frameworkCoreCompact,\n  } = buildFrameworkPrompts();\n  return {\n    frameworkCore,\n    frameworkCoreCompact,\n    frameworkContextSections: FRAMEWORK_CONTEXT_SECTIONS,\n    buildFrameworkPrompts,\n    generateActionsPrompt,\n    resolveInitialToolNames,\n    createDataWidgetActionEntries,\n  };\n})();\n\n/**\n * Build the per-request SQL-schema context block. Reads AGENT_ORG_ID live\n * from the environment so scheduler/A2A/HTTP call sites all see whatever\n * org was just resolved for this request.\n */\nexport async function buildSchemaBlock(\n  owner: string,\n  databaseTools: DatabaseToolsOption = \"read\",\n): Promise<string> {\n  try {\n    return await loadSchemaPromptBlock({\n      owner,\n      orgId: getRequestOrgId() ?? null,\n      databaseTools,\n    });\n  } catch {\n    return \"\";\n  }\n}\n\n/**\n * Generates a system prompt section describing registered template actions.\n * This helps the agent prefer template-specific actions over raw db-query/db-exec.\n *\n * Two output modes:\n *\n *   - `\"tool\"` — used in production, where template actions are registered\n *     as native Anthropic tools. Output reads `name(arg*: type; ...) — desc`.\n *   - `\"cli\"` — used in dev, where template actions are NOT registered as\n *     native tools and must be invoked via `bash(command=\"pnpm action ...\")`.\n *     Output reads `pnpm action name --arg <type> [--opt <type>] — desc`.\n */\nexport function generateActionsPrompt(\n  registry: Record<string, ActionEntry>,\n  mode: \"cli\" | \"tool\" = \"tool\",\n  initialToolNames?: string[],\n): string {\n  if (!registry || Object.keys(registry).length === 0) return \"\";\n\n  const allActionEntries = Object.entries(registry);\n  const initialNames = initialToolNames ? new Set(initialToolNames) : undefined;\n  const actionEntries = initialNames\n    ? allActionEntries.filter(([name]) => initialNames.has(name))\n    : allActionEntries;\n  const omittedActionCount = allActionEntries.length - actionEntries.length;\n  const nativeWidgetNote = (entry: ActionEntry) =>\n    entry.chatUI && typeof entry.chatUI.renderer === \"string\"\n      ? ` Native chat widget: \\`${entry.chatUI.renderer}\\`.`\n      : \"\";\n\n  if (mode === \"tool\") {\n    const summaryLines = actionEntries.map(([name, entry]) => {\n      const desc = compactPromptLine(\n        entry.tool.description,\n        MAX_ACTION_SUMMARY_DESCRIPTION_CHARS,\n      );\n      return `- \\`${name}\\` — ${desc}${nativeWidgetNote(entry)}`;\n    });\n\n    return `\\n\\n## Available Actions\n\n**Use these actions directly as tool calls.** They handle database access, validation, and business logic internally. The native tool schemas contain the full parameter details.\n\n${summaryLines.join(\"\\n\")}${\n      omittedActionCount > 0\n        ? `\\n\\n${omittedActionCount} less-common app action${omittedActionCount === 1 ? \" is\" : \"s are\"} available on demand. Use \\`tool-search\\` with a specific capability query to load the matching schemas when needed.`\n        : \"\"\n    }`;\n  }\n\n  const lines = actionEntries.map(([name, entry]) => {\n    const desc = entry.tool.description;\n    const params = entry.tool.parameters?.properties;\n    const requiredFields = new Set(entry.tool.parameters?.required ?? []);\n\n    // CLI mode: emit `pnpm action <name> --required <type> [--optional <type>]`\n    if (!params || Object.keys(params).length === 0) {\n      return `- \\`pnpm action ${name}\\` — ${desc}${nativeWidgetNote(entry)}`;\n    }\n    const entries = Object.entries(params);\n    // Required first (alphabetical), then optional (alphabetical)\n    entries.sort(([a], [b]) => {\n      const ar = requiredFields.has(a) ? 0 : 1;\n      const br = requiredFields.has(b) ? 0 : 1;\n      if (ar !== br) return ar - br;\n      return a.localeCompare(b);\n    });\n    const required: string[] = [];\n    const optional: string[] = [];\n    const requiredNames: string[] = [];\n    for (const [k, v] of entries) {\n      const type = (v as { type?: string }).type ?? \"any\";\n      const flag = `--${k} <${type}>`;\n      if (requiredFields.has(k)) {\n        required.push(flag);\n        requiredNames.push(`--${k}`);\n      } else {\n        optional.push(`[${flag}]`);\n      }\n    }\n    const cmd = [\"pnpm action \" + name, ...required, ...optional].join(\" \");\n    const requiredNote =\n      requiredNames.length > 0 ? ` Required: ${requiredNames.join(\", \")}.` : \"\";\n    return `- \\`${cmd}\\` — ${desc}.${requiredNote}${nativeWidgetNote(entry)}`;\n  });\n\n  return `\\n\\n## Available Actions\n\n**These template actions are NOT exposed as direct tools in dev mode. To run any of them, use the \\`bash\\` tool with the exact command shown below.** Example: \\`bash(command=\"pnpm action add-slide --deckId abc --content 'Hello'\")\\`.\n\nDo NOT try to call these by name as if they were tools — they will not exist in your tool list. Always go through \\`bash\\`.\n\n${lines.join(\"\\n\")}`;\n}\n\n/**\n * Tool names `generateCorpusToolsPrompt` teaches BY NAME, in the same order\n * it lists them. Exported so callers that build a request's initial\n * engine-tool set can fold in exactly the subset present in a given\n * registry — keeping \"what the prompt just told the model exists\" and\n * \"what tools are actually callable on the first request\" in sync. See the\n * corpus-prompt/initial-tools note at this function's call site in\n * agent-chat-plugin.ts.\n */\nconst CORPUS_TOOL_NAMES = [\n  \"provider-api-catalog\",\n  \"provider-api-docs\",\n  \"provider-api-request\",\n  \"provider-corpus-job\",\n  \"query-staged-dataset\",\n  \"run-code\",\n] as const;\n\nexport function corpusToolNamesTaughtByPrompt(\n  registry: Record<string, ActionEntry>,\n): string[] {\n  return CORPUS_TOOL_NAMES.filter((name) => name in registry);\n}\n\nexport function generateCorpusToolsPrompt(\n  registry: Record<string, ActionEntry>,\n): string {\n  const hasProviderApi = \"provider-api-request\" in registry;\n  const hasProviderCorpusJob = \"provider-corpus-job\" in registry;\n  const providerDiscoveryTools = [\n    \"provider-api-catalog\" in registry ? \"`provider-api-catalog`\" : null,\n    \"provider-api-docs\" in registry ? \"`provider-api-docs`\" : null,\n  ].filter(Boolean);\n  const hasRunCode = \"run-code\" in registry;\n  const hasStagedDataset = \"query-staged-dataset\" in registry;\n  if (\n    !hasProviderApi &&\n    !hasProviderCorpusJob &&\n    !hasRunCode &&\n    !hasStagedDataset\n  )\n    return \"\";\n\n  const available = [\n    ...providerDiscoveryTools,\n    hasProviderApi ? \"`provider-api-request`\" : null,\n    hasProviderCorpusJob ? \"`provider-corpus-job`\" : null,\n    hasStagedDataset ? \"`query-staged-dataset`\" : null,\n    hasRunCode ? \"`run-code`\" : null,\n  ].filter(Boolean);\n\n  return `\\n\\n## Broad Provider And Corpus Workflows\n\nAvailable corpus-capable tools: ${available.join(\", \")}.\n\nFor broad provider searches, raw API access, multi-page cohorts, cross-source joins, classification/counting over records, or absence-sensitive answers, do not stop at a bounded shortcut action. Use the provider's broad API/search/list surface, fetch every relevant page or an explicit bounded cohort, stage/save large responses when needed, and reduce the corpus with durable corpus jobs, staged-dataset queries, or code execution.\n\nWhen \\`provider-corpus-job\\` is available, prefer it for transcript/message/ticket/issue/document scans that may exceed one turn, need provider-side backoff, or need a defensible \"not found\" conclusion. Use operation=\"start\" with mode=\"paginated-search\" for any paginated provider endpoint, or mode=\"batch-search\" when a prior cohort of ids/records must feed a second provider endpoint. Continue paused jobs with operation=\"continue\" until status is completed or quota_wait, then read operation=\"results\". In run-code, prefer providerFetchAll() for short cursor/page/offset pagination and providerRequest() when response status, headers, or truncation metadata matters. Report source, filters, row counts, pagination/truncation, failed pages, quota_wait times, and remaining gaps.`;\n}\n\n/**\n * Walks the local filesystem (dev mode only) to build a bounded file/folder\n * tree, used by a couple of dev-mode workspace-inspection tools.\n */\nexport async function collectFiles(\n  dir: string,\n  prefix: string,\n  depth: number,\n  results: Array<{ path: string; name: string; type: \"file\" | \"folder\" }>,\n): Promise<void> {\n  if (depth > 4 || results.length >= 500) return;\n  const skip = new Set([\n    \"node_modules\",\n    \".git\",\n    \".next\",\n    \".output\",\n    \"dist\",\n    \".cache\",\n    \".turbo\",\n    \"data\",\n  ]);\n  let entries: import(\"fs\").Dirent[];\n  try {\n    const fs = await lazyFs();\n    entries = fs.readdirSync(dir, { withFileTypes: true });\n  } catch {\n    return;\n  }\n  for (const entry of entries) {\n    if (results.length >= 500) return;\n    if (skip.has(entry.name) || entry.name.startsWith(\".\")) continue;\n    const relPath = prefix ? `${prefix}/${entry.name}` : entry.name;\n    const isDir = entry.isDirectory();\n    results.push({\n      path: relPath,\n      name: entry.name,\n      type: isDir ? \"folder\" : \"file\",\n    });\n    if (isDir)\n      await collectFiles(\n        nodePath.join(dir, entry.name),\n        relPath,\n        depth + 1,\n        results,\n      );\n  }\n}\n"]}
+{"version":3,"file":"framework-prompts.js","sourceRoot":"","sources":["../../../src/server/agent-chat/framework-prompts.ts"],"names":[],"mappings":"AAAA,OAAO,QAAQ,MAAM,WAAW,CAAC;AAIjC,OAAO,EACL,kBAAkB,EAClB,yBAAyB,GAE1B,MAAM,qBAAqB,CAAC;AAC7B,OAAO,EAAE,eAAe,EAAE,MAAM,uBAAuB,CAAC;AACxD,OAAO,EAAE,qBAAqB,EAAE,MAAM,qBAAqB,CAAC;AAC5D,OAAO,EAAE,uBAAuB,EAAE,MAAM,yBAAyB,CAAC;AAClE,OAAO,EACL,6BAA6B,EAC7B,0BAA0B,GAC3B,MAAM,oBAAoB,CAAC;AAC5B,OAAO,EAAE,MAAM,EAAE,MAAM,cAAc,CAAC;AACtC,OAAO,EAAE,iBAAiB,EAAE,MAAM,uBAAuB,CAAC;AAE1D,8EAA8E;AAC9E,yEAAyE;AACzE,2EAA2E;AAC3E,yEAAyE;AACzE,8EAA8E;AAE9E,MAAM,oCAAoC,GAAG,GAAG,CAAC;AAEjD;;;;;;;;GAQG;AACH,MAAM,UAAU,qBAAqB,CACnC,QAAyB,EACzB,OAA2E;IAS3E,MAAM,cAAc,GAAG,kBAAkB,CAAC,QAAQ,EAAE,OAAO,CAAC,CAAC;IAC7D,MAAM,sBAAsB,GAAG,yBAAyB,CAAC,QAAQ,EAAE,OAAO,CAAC,CAAC;IAC5E,MAAM,qBAAqB,GAAG,OAAO,EAAE,cAAc,KAAK,KAAK,CAAC;IAChE,MAAM,oBAAoB,GAAG,qBAAqB;QAChD,CAAC,CAAC,uJAAuJ;QACzJ,CAAC,CAAC,8FAA8F,CAAC;IACnG,MAAM,oBAAoB,GAAG,qBAAqB;QAChD,CAAC,CAAC,wKAAwK;QAC1K,CAAC,CAAC,qGAAqG,CAAC;IAC1G,MAAM,4BAA4B,GAAG,qBAAqB;QACxD,CAAC,CAAC,gcAAgc;QAClc,CAAC,CAAC,gLAAgL,CAAC;IACrL,MAAM,yBAAyB,GAAG,qBAAqB;QACrD,CAAC,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;qbA0C+a;QACjb,CAAC,CAAC;;qZAE+Y,CAAC;IACpZ,MAAM,4BAA4B,GAAG,qBAAqB;QACxD,CAAC,CAAC;;;;;;;;;;;;;;;;0yBAgBoyB;QACtyB,CAAC,CAAC;;kNAE4M,CAAC;IAEjN,MAAM,qBAAqB,GAAG;;;;;;;;;;0FAU0D,oBAAoB,kHAAkH,oBAAoB;;EAElP,yBAAyB;;;;EAIzB,4BAA4B;;;;;;;;;;;;;EAa5B,cAAc,EAAE,CAAC;IAEjB,MAAM,oBAAoB,GAAG;;;;;;;;;;;;;;;;;;;;;EAqB7B,cAAc,EAAE,CAAC;IAEjB,MAAM,6BAA6B,GAAG;;;;;;;;;;6EAUqC,oBAAoB,8CAA8C,oBAAoB;;EAEjK,4BAA4B;;;;;EAK5B,sBAAsB,EAAE,CAAC;IAEzB,MAAM,4BAA4B,GAAG;;;;;;;;;;;;;;;EAerC,sBAAsB,EAAE,CAAC;IAEzB,OAAO;QACL,cAAc;QACd,sBAAsB;QACtB,qBAAqB;QACrB,oBAAoB;QACpB,6BAA6B;QAC7B,4BAA4B;KAC7B,CAAC;AACJ,CAAC;AAED,MAAM,CAAC,MAAM,gCAAgC,GAAG,CAAC,GAAG,EAAE;IACpD,yEAAyE;IACzE,MAAM,EACJ,cAAc,EAAE,aAAa,EAC7B,sBAAsB,EAAE,oBAAoB,GAC7C,GAAG,qBAAqB,EAAE,CAAC;IAC5B,OAAO;QACL,aAAa;QACb,oBAAoB;QACpB,wBAAwB,EAAE,0BAA0B;QACpD,qBAAqB;QACrB,qBAAqB;QACrB,uBAAuB;QACvB,6BAA6B;KAC9B,CAAC;AACJ,CAAC,CAAC,EAAE,CAAC;AAEL;;;;GAIG;AACH,MAAM,CAAC,KAAK,UAAU,gBAAgB,CACpC,KAAa,EACb,aAAa,GAAwB,MAAM;IAE3C,IAAI,CAAC;QACH,OAAO,MAAM,qBAAqB,CAAC;YACjC,KAAK;YACL,KAAK,EAAE,eAAe,EAAE,IAAI,IAAI;YAChC,aAAa;SACd,CAAC,CAAC;IACL,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,EAAE,CAAC;IACZ,CAAC;AACH,CAAC;AAED;;;;;;;;;;;GAWG;AACH,MAAM,UAAU,qBAAqB,CACnC,QAAqC,EACrC,IAAI,GAAmB,MAAM,EAC7B,gBAA2B;IAE3B,IAAI,CAAC,QAAQ,IAAI,MAAM,CAAC,IAAI,CAAC,QAAQ,CAAC,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,EAAE,CAAC;IAE/D,MAAM,gBAAgB,GAAG,MAAM,CAAC,OAAO,CAAC,QAAQ,CAAC,CAAC;IAClD,MAAM,YAAY,GAAG,gBAAgB,CAAC,CAAC,CAAC,IAAI,GAAG,CAAC,gBAAgB,CAAC,CAAC,CAAC,CAAC,SAAS,CAAC;IAC9E,MAAM,aAAa,GAAG,YAAY;QAChC,CAAC,CAAC,gBAAgB,CAAC,MAAM,CAAC,CAAC,CAAC,IAAI,CAAC,EAAE,EAAE,CAAC,YAAY,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC;QAC7D,CAAC,CAAC,gBAAgB,CAAC;IACrB,MAAM,kBAAkB,GAAG,gBAAgB,CAAC,MAAM,GAAG,aAAa,CAAC,MAAM,CAAC;IAC1E,MAAM,gBAAgB,GAAG,CAAC,KAAkB,EAAE,EAAE,CAC9C,KAAK,CAAC,MAAM,IAAI,OAAO,KAAK,CAAC,MAAM,CAAC,QAAQ,KAAK,QAAQ;QACvD,CAAC,CAAC,0BAA0B,KAAK,CAAC,MAAM,CAAC,QAAQ,KAAK;QACtD,CAAC,CAAC,EAAE,CAAC;IAET,IAAI,IAAI,KAAK,MAAM,EAAE,CAAC;QACpB,MAAM,YAAY,GAAG,aAAa,CAAC,GAAG,CAAC,CAAC,CAAC,IAAI,EAAE,KAAK,CAAC,EAAE,EAAE;YACvD,MAAM,IAAI,GAAG,iBAAiB,CAC5B,KAAK,CAAC,IAAI,CAAC,WAAW,EACtB,oCAAoC,CACrC,CAAC;YACF,OAAO,OAAO,IAAI,QAAQ,IAAI,GAAG,gBAAgB,CAAC,KAAK,CAAC,EAAE,CAAC;QAC7D,CAAC,CAAC,CAAC;QAEH,OAAO;;;;EAIT,YAAY,CAAC,IAAI,CAAC,IAAI,CAAC,GACnB,kBAAkB,GAAG,CAAC;YACpB,CAAC,CAAC,OAAO,kBAAkB,0BAA0B,kBAAkB,KAAK,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,OAAO,sHAAsH;YACrN,CAAC,CAAC,EACN,EAAE,CAAC;IACL,CAAC;IAED,MAAM,KAAK,GAAG,aAAa,CAAC,GAAG,CAAC,CAAC,CAAC,IAAI,EAAE,KAAK,CAAC,EAAE,EAAE;QAChD,MAAM,IAAI,GAAG,KAAK,CAAC,IAAI,CAAC,WAAW,CAAC;QACpC,MAAM,MAAM,GAAG,KAAK,CAAC,IAAI,CAAC,UAAU,EAAE,UAAU,CAAC;QACjD,MAAM,cAAc,GAAG,IAAI,GAAG,CAAC,KAAK,CAAC,IAAI,CAAC,UAAU,EAAE,QAAQ,IAAI,EAAE,CAAC,CAAC;QAEtE,4EAA4E;QAC5E,IAAI,CAAC,MAAM,IAAI,MAAM,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;YAChD,OAAO,mBAAmB,IAAI,QAAQ,IAAI,GAAG,gBAAgB,CAAC,KAAK,CAAC,EAAE,CAAC;QACzE,CAAC;QACD,MAAM,OAAO,GAAG,MAAM,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC;QACvC,8DAA8D;QAC9D,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,EAAE;YACxB,MAAM,EAAE,GAAG,cAAc,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;YACzC,MAAM,EAAE,GAAG,cAAc,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;YACzC,IAAI,EAAE,KAAK,EAAE;gBAAE,OAAO,EAAE,GAAG,EAAE,CAAC;YAC9B,OAAO,CAAC,CAAC,aAAa,CAAC,CAAC,CAAC,CAAC;QAC5B,CAAC,CAAC,CAAC;QACH,MAAM,QAAQ,GAAa,EAAE,CAAC;QAC9B,MAAM,QAAQ,GAAa,EAAE,CAAC;QAC9B,MAAM,aAAa,GAAa,EAAE,CAAC;QACnC,KAAK,MAAM,CAAC,CAAC,EAAE,CAAC,CAAC,IAAI,OAAO,EAAE,CAAC;YAC7B,MAAM,IAAI,GAAI,CAAuB,CAAC,IAAI,IAAI,KAAK,CAAC;YACpD,MAAM,IAAI,GAAG,KAAK,CAAC,KAAK,IAAI,GAAG,CAAC;YAChC,IAAI,cAAc,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC;gBAC1B,QAAQ,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;gBACpB,aAAa,CAAC,IAAI,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC;YAC/B,CAAC;iBAAM,CAAC;gBACN,QAAQ,CAAC,IAAI,CAAC,IAAI,IAAI,GAAG,CAAC,CAAC;YAC7B,CAAC;QACH,CAAC;QACD,MAAM,GAAG,GAAG,CAAC,cAAc,GAAG,IAAI,EAAE,GAAG,QAAQ,EAAE,GAAG,QAAQ,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;QACxE,MAAM,YAAY,GAChB,aAAa,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,cAAc,aAAa,CAAC,IAAI,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC;QAC5E,OAAO,OAAO,GAAG,QAAQ,IAAI,IAAI,YAAY,GAAG,gBAAgB,CAAC,KAAK,CAAC,EAAE,CAAC;IAC5E,CAAC,CAAC,CAAC;IAEH,OAAO;;;;;;EAMP,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC;AACrB,CAAC;AAED;;;;;;;;GAQG;AACH,MAAM,iBAAiB,GAAG;IACxB,sBAAsB;IACtB,mBAAmB;IACnB,sBAAsB;IACtB,qBAAqB;IACrB,sBAAsB;IACtB,UAAU;CACF,CAAC;AAEX,MAAM,UAAU,6BAA6B,CAC3C,QAAqC;IAErC,OAAO,iBAAiB,CAAC,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,IAAI,QAAQ,CAAC,CAAC;AAC9D,CAAC;AAED,MAAM,UAAU,yBAAyB,CACvC,QAAqC;IAErC,MAAM,cAAc,GAAG,sBAAsB,IAAI,QAAQ,CAAC;IAC1D,MAAM,oBAAoB,GAAG,qBAAqB,IAAI,QAAQ,CAAC;IAC/D,MAAM,sBAAsB,GAAG;QAC7B,sBAAsB,IAAI,QAAQ,CAAC,CAAC,CAAC,wBAAwB,CAAC,CAAC,CAAC,IAAI;QACpE,mBAAmB,IAAI,QAAQ,CAAC,CAAC,CAAC,qBAAqB,CAAC,CAAC,CAAC,IAAI;KAC/D,CAAC,MAAM,CAAC,OAAO,CAAC,CAAC;IAClB,MAAM,UAAU,GAAG,UAAU,IAAI,QAAQ,CAAC;IAC1C,MAAM,gBAAgB,GAAG,sBAAsB,IAAI,QAAQ,CAAC;IAC5D,IACE,CAAC,cAAc;QACf,CAAC,oBAAoB;QACrB,CAAC,UAAU;QACX,CAAC,gBAAgB;QAEjB,OAAO,EAAE,CAAC;IAEZ,MAAM,SAAS,GAAG;QAChB,GAAG,sBAAsB;QACzB,cAAc,CAAC,CAAC,CAAC,wBAAwB,CAAC,CAAC,CAAC,IAAI;QAChD,oBAAoB,CAAC,CAAC,CAAC,uBAAuB,CAAC,CAAC,CAAC,IAAI;QACrD,gBAAgB,CAAC,CAAC,CAAC,wBAAwB,CAAC,CAAC,CAAC,IAAI;QAClD,UAAU,CAAC,CAAC,CAAC,YAAY,CAAC,CAAC,CAAC,IAAI;KACjC,CAAC,MAAM,CAAC,OAAO,CAAC,CAAC;IAElB,OAAO;;kCAEyB,SAAS,CAAC,IAAI,CAAC,IAAI,CAAC;;;;6wBAIutB,CAAC;AAC9wB,CAAC;AAED;;;GAGG;AACH,MAAM,CAAC,KAAK,UAAU,YAAY,CAChC,GAAW,EACX,MAAc,EACd,KAAa,EACb,OAAuE;IAEvE,IAAI,KAAK,GAAG,CAAC,IAAI,OAAO,CAAC,MAAM,IAAI,GAAG;QAAE,OAAO;IAC/C,MAAM,IAAI,GAAG,IAAI,GAAG,CAAC;QACnB,cAAc;QACd,MAAM;QACN,OAAO;QACP,SAAS;QACT,MAAM;QACN,QAAQ;QACR,QAAQ;QACR,MAAM;KACP,CAAC,CAAC;IACH,IAAI,OAA8B,CAAC;IACnC,IAAI,CAAC;QACH,MAAM,EAAE,GAAG,MAAM,MAAM,EAAE,CAAC;QAC1B,OAAO,GAAG,EAAE,CAAC,WAAW,CAAC,GAAG,EAAE,EAAE,aAAa,EAAE,IAAI,EAAE,CAAC,CAAC;IACzD,CAAC;IAAC,MAAM,CAAC;QACP,OAAO;IACT,CAAC;IACD,KAAK,MAAM,KAAK,IAAI,OAAO,EAAE,CAAC;QAC5B,IAAI,OAAO,CAAC,MAAM,IAAI,GAAG;YAAE,OAAO;QAClC,IAAI,IAAI,CAAC,GAAG,CAAC,KAAK,CAAC,IAAI,CAAC,IAAI,KAAK,CAAC,IAAI,CAAC,UAAU,CAAC,GAAG,CAAC;YAAE,SAAS;QACjE,MAAM,OAAO,GAAG,MAAM,CAAC,CAAC,CAAC,GAAG,MAAM,IAAI,KAAK,CAAC,IAAI,EAAE,CAAC,CAAC,CAAC,KAAK,CAAC,IAAI,CAAC;QAChE,MAAM,KAAK,GAAG,KAAK,CAAC,WAAW,EAAE,CAAC;QAClC,OAAO,CAAC,IAAI,CAAC;YACX,IAAI,EAAE,OAAO;YACb,IAAI,EAAE,KAAK,CAAC,IAAI;YAChB,IAAI,EAAE,KAAK,CAAC,CAAC,CAAC,QAAQ,CAAC,CAAC,CAAC,MAAM;SAChC,CAAC,CAAC;QACH,IAAI,KAAK;YACP,MAAM,YAAY,CAChB,QAAQ,CAAC,IAAI,CAAC,GAAG,EAAE,KAAK,CAAC,IAAI,CAAC,EAC9B,OAAO,EACP,KAAK,GAAG,CAAC,EACT,OAAO,CACR,CAAC;IACN,CAAC;AACH,CAAC","sourcesContent":["import nodePath from \"node:path\";\n\nimport type { ActionEntry } from \"../../agent/production-agent.js\";\nimport type { DatabaseToolsOption } from \"../../scripts/db/tool-mode.js\";\nimport {\n  buildFrameworkCore,\n  buildFrameworkCoreCompact,\n  type PromptExamples,\n} from \"../prompts/index.js\";\nimport { getRequestOrgId } from \"../request-context.js\";\nimport { loadSchemaPromptBlock } from \"../schema-prompt.js\";\nimport { resolveInitialToolNames } from \"./action-filters-a2a.js\";\nimport {\n  createDataWidgetActionEntries,\n  FRAMEWORK_CONTEXT_SECTIONS,\n} from \"./context-tools.js\";\nimport { lazyFs } from \"./lazy-fs.js\";\nimport { compactPromptLine } from \"./prompt-resources.js\";\n\n// ---------------------------------------------------------------------------\n// Framework-level system prompt assembly (production/dev, full/compact),\n// the \"Available Actions\" and corpus-tools prompt sections, the SQL schema\n// block, and the codebase file-tree walker used by a few dev-mode tools.\n// ---------------------------------------------------------------------------\n\nconst MAX_ACTION_SUMMARY_DESCRIPTION_CHARS = 140;\n\n/**\n * Framework-level instructions injected into every agent's system prompt.\n * Prompt text lives in packages/core/src/server/prompts/ so this file stays\n * focused on routing and assembly logic.\n *\n * buildFrameworkPrompts() is called once per plugin instantiation (not per\n * request) with the template's promptExamples, producing the four assembled\n * prompt strings used at request time.\n */\nexport function buildFrameworkPrompts(\n  examples?: PromptExamples,\n  options?: { databaseTools?: DatabaseToolsOption; extensionTools?: boolean },\n): {\n  FRAMEWORK_CORE: string;\n  FRAMEWORK_CORE_COMPACT: string;\n  PROD_FRAMEWORK_PROMPT: string;\n  DEV_FRAMEWORK_PROMPT: string;\n  PROD_FRAMEWORK_PROMPT_COMPACT: string;\n  DEV_FRAMEWORK_PROMPT_COMPACT: string;\n} {\n  const FRAMEWORK_CORE = buildFrameworkCore(examples, options);\n  const FRAMEWORK_CORE_COMPACT = buildFrameworkCoreCompact(examples, options);\n  const extensionToolsEnabled = options?.extensionTools !== false;\n  const planModeArtifactList = extensionToolsEnabled\n    ? \"source-code handoffs and app-created artifacts such as extensions, widgets, dashboards, calculators, mini-apps, documents, designs, slides, or videos\"\n    : \"source-code handoffs and app-created artifacts such as documents, designs, slides, or videos\";\n  const planModeBlockedTools = extensionToolsEnabled\n    ? \"`render-inline-extension`, `create-extension`, `update-extension`, `connect-builder`, or any action that creates, updates, deletes, sends, publishes, or persists data\"\n    : \"`connect-builder`, or any action that creates, updates, deletes, sends, publishes, or persists data\";\n  const extensionConnectBuilderGuard = extensionToolsEnabled\n    ? \"If the complete request can be satisfied by a self-contained extension or an existing named slot, use `render-inline-extension`, `create-extension`, `show-extension-inline`, or `update-extension` instead. If the exact placement or behavior requires changing the host UI or no suitable slot exists, continue with the normal `connect-builder` source-change flow even if the user called it an extension; never stop at saying extensions cannot do it.\"\n    : \"Because extension tools are disabled, do NOT invent an extension workflow. Only use `connect-builder` when the request genuinely requires changing the host app's source code.\";\n  const extensionInstructionsFull = extensionToolsEnabled\n    ? `### Generative UI and Extensions (Mini-Apps)\n\nIn Act mode, if the user asks for generated interactive UI in chat, choose the smallest extension action that matches the lifetime:\n\n- For a **one-time inline UI** that answers the current chat turn (knobs, controls, pickers, calculators, temporary dashboards, visualizers), call \\`render-inline-extension\\` immediately with a self-contained Alpine.js HTML body. It renders inside the transcript and is not saved.\n- For a **reusable or saved UI** (an extension/widget/dashboard/calculator/mini-app the user can reopen from Extensions), call \\`create-extension\\` with a self-contained Alpine.js HTML body. It saves to the Extensions view and also renders inline in chat.\n- To **reuse an existing saved extension inline**, call \\`show-extension-inline\\` with its id, or a search string when the id is unknown.\n\nThese are **NOT** source-code changes and do **NOT** go through \\`connect-builder\\`. Extensions are sandboxed mini-apps — no source files are touched, no PR is opened, no build is required. Saved extensions can be edited later via \\`update-extension\\`.\n\nIf the app exposes native actions or instructions for dashboards, reports, analyses, charts, documents, decks, or other domain artifacts, use those app-native actions first. Choose an extension only when the user explicitly asks for an extension/custom mini-app, or when the app's native artifact format cannot faithfully express the requested interaction.\n\nKeep \\`create-extension\\` payloads compact enough to finish quickly. For complex extensions, create a useful working v1 first, then call \\`update-extension\\` with focused edits for refinements instead of trying to assemble one enormous initial tool input.\n\nGenerated UI content can use appAction(), appFetch(), dbQuery(), extensionFetch(), extensionData, agentNative.ui.output(value, opts?), and agentNative.chat.send(...)/sendToAgentChat(...). Use appAction() for app data writes, and dbQuery() only for read-only inspection of known app SQL tables. It can receive chat inputs through slotContext/window.onSlotContext. Use agentNative.ui.output for passive current values from knobs, sliders, selections, and controls; it writes application state at \\`inline-ui:<extensionId>:output\\` scoped to the inline extension id returned by \\`render-inline-extension\\` or \\`show-extension-inline\\`. When the user later says \"use that value\", \"apply the current setting\", or similar, read it with \\`readAppState(\"inline-ui:<id>:output\")\\` instead of asking them to send it again. Use agentNative.chat.send for visible submit/apply actions that should put a message into chat. Transient extensionData is browser-local and not agent-readable, synced, promoted, or garbage-collected; use application_state/appFetch, appAction, ui.output, or chat.send for anything the agent or app must observe. Use semantic Tailwind classes like bg-background, text-foreground, bg-primary, border-border, and text-muted-foreground so the UI inherits the parent app theme.\n\nIf the user asks to change, edit, fix, style, rename, or add behavior to an existing extension/widget/dashboard/calculator/mini-app, use the current extension id from \\`<current-screen>\\` or \\`<current-url>\\` when present. Call \\`get-extension\\` only if you need to inspect its content, then \\`update-extension\\` with that id. After one content read, keep the body in working memory and move to focused \\`update-extension\\` \\`edits\\`/\\`patches\\`; do not loop on repeated \\`get-extension\\` + \\`run-code\\` string scans before writing. Use \\`list-extensions\\` only when no current id/name is available. Existing extension edits are SQL data updates, not source-code changes, even when the request says \"change the UI\" or \"fix this\". Do **NOT** call \\`connect-builder\\` for existing extension edits.\n\nIn Act mode, when in doubt — if the request asks for a new small interactive utility and does not need reuse, choose \\`render-inline-extension\\`; if it mentions saving/reuse or asks for an extension/widget/dashboard/calculator/mini-app, choose \\`create-extension\\`. If it references an existing one or the current extension page, choose \\`update-extension\\`. Do **not** preface the call with planning text like \"let me build the dashboard…\" — just call the right extension action directly.\n\nNote: \"extension\" is the user-facing primitive (the sandboxed Alpine.js mini-app). Don't confuse it with the LLM concept of \"tools\" (function calls) — those are how you invoke ANY action, including \\`create-extension\\` itself.\n\nFor existing extensions, use \\`get-extension\\` or \\`update-extension\\` directly when \\`<current-screen>\\` or \\`<current-url>\\` provides an \\`extensionId\\`. Use \\`list-extensions\\` only to browse or resolve an unknown name. If the user wants a shared extension removed only from their view, use \\`hide-extension\\` — do not query or mutate the legacy \\`tools\\` table directly.\n\n### Extensions vs. Code Changes — Pick the Right Path\n\nRoute by the exact outcome, not by whether the user calls it an extension. Extensions render in their own sandboxed iframe, either on their own page or inside an existing named slot. They CANNOT change the host app's nav, restyle or inject elements into existing native components, replace built-in views, or render at an arbitrary location that has no slot.\n\n<routing>\n| The request is for…                                              | Path                          |\n| ---------------------------------------------------------------- | ------------------------------ |\n| A one-off interactive answer inside chat (controls, picker, calculator, temporary visualizer) | \\`render-inline-extension\\` — inline only |\n| A new self-contained surface (widget, dashboard, calculator, viewer, list, tracker) | \\`create-extension\\` — ships instantly, no PR |\n| Loading a saved extension inside chat | \\`show-extension-inline\\` |\n| Editing an existing extension (fix, restyle, rename, add behavior) | \\`update-extension\\`           |\n| The host app's own chrome (nav bar, sidebar, layout, routes, shipped components, existing styles, business logic) | \\`connect-builder\\` — a real source-code change |\n| UI inside or beside a native component where no named slot exists | \\`connect-builder\\` — add the native UI or a suitable slot in source |\n| Ambiguous, satisfiable either way (e.g. \"give me an unread view\") | \\`render-inline-extension\\` for chat-only, \\`create-extension\\` for reusable |\n</routing>\n\nIf an extension could only approximate the request in a different location, do not silently downgrade the requirement and do not end with \"extensions cannot do that.\" Briefly explain the boundary, then follow the normal source-code handoff so the app can still be customized fully.\n\nWorked examples: \"a widget showing unread emails grouped by sender\", \"a tracker for my newsletter subscriptions\", \"a custom kanban board with drag-and-drop rules the app does not have\" → \\`create-extension\\`. \"Add an Unread tab to the left navigation\", \"show local time beside every native Calendar attendee row\", \"make the subject lines wrap\", \"change the inbox grouping logic\", \"add a field to the compose form\" → \\`connect-builder\\`.`\n    : `### Extensions Disabled\n\nExtension creation and management tools are disabled for this app. Do not claim you can create, edit, hide, or delete Agent-Native extensions unless the template exposes its own typed action for that workflow. For requests that would otherwise be handled as an extension/widget/dashboard/calculator mini-app, explain that this app has disabled extension tools and use the app's available actions instead.`;\n  const extensionInstructionsCompact = extensionToolsEnabled\n    ? `### Generative UI and Extensions (Mini-Apps)\n\nIn Act mode, if the user asks for generated interactive UI in chat, call \\`render-inline-extension\\` for one-time inline controls/knobs/calculators/visualizers that do not need saving. If the user asks for an **extension**, **widget**, **dashboard**, **calculator**, or **mini-app** that should be reusable or saved, call \\`create-extension\\` with a self-contained Alpine.js HTML body. To load a saved extension inline, call \\`show-extension-inline\\`. These are NOT code changes — extensions are sandboxed mini-apps. Do not preface with \"let me build…\" — just call the right extension action.\n\nUse app-native artifact actions first when they exist for dashboards, reports, analyses, charts, documents, decks, or similar domain artifacts. Pick \\`create-extension\\` only for explicit extension/custom mini-app requests or for behavior the native artifact format cannot support.\n\nKeep the first \\`create-extension\\` call compact and working. If the request is complex, create the v1 first and then refine with focused \\`update-extension\\` edits.\n\nGenerated UI can read chat inputs from slotContext/window.onSlotContext, see/update app state through appFetch/appAction, use extensionData, record passive current values through agentNative.ui.output(value, opts?), and send visible results through agentNative.chat.send(...) or sendToAgentChat(...). ui.output writes \\`inline-ui:<extensionId>:output\\` in application state; when the user asks to use the current slider/selection/value, read \\`readAppState(\"inline-ui:<id>:output\")\\`. Transient extensionData is browser-local only, so do not rely on it for values the agent or app must observe. Use semantic Tailwind theme classes.\n\nIf the user asks to change, edit, fix, style, rename, or add behavior to an existing extension/widget/dashboard/calculator/mini-app, use the current extension id from \\`<current-screen>\\` or \\`<current-url>\\` when present. Call \\`get-extension\\` only if you need to inspect its content, then \\`update-extension\\` with that id. After one content read, use focused \\`update-extension\\` \\`edits\\`/\\`patches\\`; do not repeatedly re-read and scan the same HTML with \\`run-code\\` before writing. Use \\`list-extensions\\` only when no current id/name is available. Existing extension edits are SQL data updates, not source-code changes. Do NOT call \\`connect-builder\\` for them.\n\nFor existing extensions, use \\`get-extension\\` or \\`update-extension\\` directly when \\`<current-screen>\\` or \\`<current-url>\\` provides an \\`extensionId\\`. Use \\`list-extensions\\` only to browse or resolve an unknown name. Use \\`hide-extension\\` when the user wants a shared extension removed only from their own view. Do not query the legacy \\`tools\\` table directly.\n\n### Extensions vs. Code Changes — Pick the Right Path\n\nIf the user wants a **one-off interactive answer in chat**, use \\`render-inline-extension\\`. If they want a **new reusable self-contained surface** (custom widget, dashboard, list, viewer, calculator), use \\`create-extension\\` — extensions ship instantly without a PR. Extensions can render only on their own page or in an existing named slot; they cannot inject UI into arbitrary native components. If the exact request changes host chrome, native components, layout, styles, routes, business logic, or needs placement where no slot exists, treat it as a source-code change and use the normal \\`connect-builder\\` flow even if the user called it an extension. Never stop at \"extensions cannot do that\" or silently offer a different placement; explain the boundary briefly and continue the code-change handoff.`\n    : `### Extensions Disabled\n\nExtension creation and management tools are disabled for this app. Do not claim you can create, edit, hide, or delete Agent-Native extensions unless the template exposes its own typed action for that workflow.`;\n\n  const PROD_FRAMEWORK_PROMPT = `## Agent-Native Framework — Production Mode\n\nYou are an AI agent in an agent-native application, running in **production mode**.\n\nThe agent and the UI are equal partners — everything the UI can do, you can do via your tools, and vice versa. They share the same SQL database and stay in sync automatically.\n\n**In production mode, you operate through registered actions exposed as tools.** These are your capabilities — use them to read data, take actions, and help the user. You cannot edit source code or access the filesystem directly. Your tools are the app's API.\n\n### Plan Mode\n\nIf the current turn is in Plan mode, plan before anything gets written. This applies to ${planModeArtifactList}. Use only read-only tools, clarify the goal when needed, and return a concrete plan for approval. Do not call ${planModeBlockedTools} until the user switches back to Act mode.\n\n${extensionInstructionsFull}\n\n### Code Changes Not Available — Call \\`connect-builder\\` Immediately\n\n${extensionConnectBuilderGuard}\n\nIn Act mode, when the user asks you to change the UI, modify code, add a feature, fix a bug in the app itself, change styles, add a hook, create a component, add a route, add an integration, or anything else that requires editing source files — you MUST take exactly these steps, in order:\n\n1. Briefly acknowledge the user's specific request in their own terms — one short clause naming what they asked for (e.g. \"Got it — wider subject lines in the email list.\"). Do NOT restate the request verbatim, do NOT add a generic preamble, and do NOT promise outcomes. Skip this step entirely if the user already knows you're handing off (e.g. they said \"send this to Builder\").\n2. Call the \\`connect-builder\\` tool, passing the user's full request verbatim as the \\`prompt\\` argument. This renders an inline card. The returned \\`builderEnabled\\` flag is authoritative: \\`true\\` means Builder Cloud Agents can take the code-change handoff; \\`false\\` means this still requires a code change, but no Builder Cloud Agent can run from this workspace. If Builder is connected and \\`builderEnabled\\` is true, the card hands the prompt off to Builder's cloud agent on one click and returns a branch URL. If Builder is not connected and \\`builderEnabled\\` is true, it shows the Connect Builder flow. If \\`builderEnabled\\` is false, it still shows the card, but as a code-change fallback instead of a runnable cloud handoff.\n3. After the card renders, inspect the tool result and write one sentence that frames the next click around what the user just asked — not as a Builder pitch. If \\`builderEnabled\\` is true and the card can send, say something like \"Click Send to Builder and it'll wire that up for you.\" If the user needs to connect first, say something like \"Connect Builder once and it'll handle this and future changes.\" If \\`builderEnabled\\` is false, say: \"This requires a code change. Edit locally or use Builder.io to edit this code in the cloud and continue customizing the app any way you like.\" Do NOT say \"click Send to Builder\", mention a branch URL, say the card is pre-loaded, or imply a Builder Cloud Agent can run when \\`builderEnabled\\` is false.\n\nWhen \\`builderEnabled\\` is false, Builder Cloud Agents are not self-serve from Builder org settings. Do NOT tell the user to go to Builder org settings, beta features, \"Cloud Agents\", or \"AI Agents\" to enable them. The only allowed guidance is the card's code-change fallback: edit locally, use Agent Native Desktop, or use Builder.io to edit this code in the cloud and continue customizing the app any way you like.\n\n**Act-mode handoff — do exactly this:** The moment a code change is requested, call \\`connect-builder\\` with the user's verbatim request, then write one sentence framing the next click. That is the whole job: Builder plans and edits in its own sandbox, so the planning, file-mapping, and code all happen there, not here. Keep your turn to the call plus that one sentence — skip code exploration, implementation plans, \\`resources\\` writes of specs, and sub-agents (they have no code-editing tools either). You don't need filesystem access to recommend Builder, so don't reach for it or list tools you lack.\n\nBuilder Cloud Agents are the recommended path when \\`builderEnabled\\` is true because they are one-click and run in the cloud. Local dev, Agent Native Desktop, and Builder.io cloud editing are the fallback when \\`builderEnabled\\` is false.\n${FRAMEWORK_CORE}`;\n\n  const DEV_FRAMEWORK_PROMPT = `## Agent-Native Framework — Development Mode\n\nYou are an AI agent in an agent-native application, running in **development mode**.\n\nThe agent and the UI are equal partners — everything the UI can do, you can do via tools/scripts, and vice versa. They share the same SQL database and stay in sync automatically.\n\n**In development mode, you have full local access — use it with senior-engineer judgment** (read before you edit, keep changes scoped, verify before you claim done):\n- Run any shell command via the \\`bash\\` tool (node, curl, pnpm, rg, git, etc.), including arbitrary code: \\`bash({ command: 'node -e \"console.log(1+1)\"' })\\`\n- Read and write any file on the filesystem; edit source, install packages, modify the app\n- Query and modify the database\n- Call external APIs (via bash with curl, or via scripts)\n\nWhen no dedicated tool/action exists for what you need, reach for \\`bash\\` — e.g. \\`bash({ command: 'curl -s https://api.example.com/data' })\\`.\n\n**Template-specific actions are invoked via bash, NOT as direct tools.** In dev mode, the only tools registered as native tool calls are framework-level utilities (bash, read, edit, write, database, resources, chat, teams, jobs). Anything from the template's \\`actions/\\` directory must be run through bash: \\`bash({ command: 'pnpm action <name> --arg value' })\\`. The \"Available Actions\" section below shows the exact CLI syntax for each one — copy that command verbatim and pass it to \\`bash\\`. Do not try to call template actions by name as if they were tools; they will not appear in your tool list.\n\nWhen editing code, follow the agent-native architecture:\n- Every feature needs all four areas: UI + scripts + skills/instructions + application-state sync\n- All SQL must be dialect-agnostic (works on SQLite and Postgres)\n- No Node.js-specific APIs in server routes (must work on Cloudflare Workers, etc.)\n- Use shadcn/ui components and Tabler Icons for all UI work\n${FRAMEWORK_CORE}`;\n\n  const PROD_FRAMEWORK_PROMPT_COMPACT = `## Agent-Native Framework — Production Mode\n\nYou are an AI agent in an agent-native application, running in **production mode**.\n\nThe agent and the UI are equal partners — everything the UI can do, you can do via your tools, and vice versa. They share the same SQL database and stay in sync automatically.\n\n**In production mode, you operate through registered actions exposed as tools.** These are your capabilities — use them to read data, take actions, and help the user. You cannot edit source code or access the filesystem directly. Your tools are the app's API.\n\n### Plan Mode\n\nIf the turn is in Plan mode, plan before anything gets written — including ${planModeArtifactList}. Use read-only tools only and do not call ${planModeBlockedTools} until the user switches back to Act mode.\n\n${extensionInstructionsCompact}\n\n### Code Changes — Call \\`connect-builder\\`\n\nIn Act mode, when a request genuinely needs a source-code edit (per the rules above), do this in order: (1) briefly acknowledge the user's specific ask in their own terms — one short clause, no preamble — then (2) call \\`connect-builder\\` with the user's request as the \\`prompt\\`, then (3) inspect \\`builderEnabled\\` in the result and write one sentence framing the next click around what they asked for, not a Builder pitch. When \\`builderEnabled\\` is true, Builder Cloud Agents can take the handoff; when \\`builderEnabled\\` is false, say this requires a code change and they can edit locally or use Builder.io to edit this code in the cloud and continue customizing the app any way they like. Do NOT write code, list files, make plans, or spawn sub-agents. Mention \\`npx agent-native create <app-name>\\`, Agent Native Desktop, or the code-change fallback when Builder Cloud Agents aren't available. Never tell users to enable Builder Cloud Agents from Builder org settings, beta features, \"Cloud Agents\", or \"AI Agents\"; they are not self-serve there.\n${FRAMEWORK_CORE_COMPACT}`;\n\n  const DEV_FRAMEWORK_PROMPT_COMPACT = `## Agent-Native Framework — Development Mode\n\nYou are an AI agent in an agent-native application, running in **development mode**.\n\nThe agent and the UI are equal partners — everything the UI can do, you can do via tools/scripts, and vice versa. They share the same SQL database and stay in sync automatically.\n\n**In development mode, you have full local access** — shell, filesystem, database, external APIs, source edits, and package installs. Use it with senior-engineer judgment: read before you edit, keep changes scoped, verify before you claim done.\n\n**Template-specific actions are invoked via bash, NOT as direct tools.** Run them with: \\`bash({ command: 'pnpm action <name> --arg value' })\\`. See the \"Available Actions\" section below for CLI syntax.\n\nWhen editing code, follow the agent-native architecture:\n- Every feature needs all four areas: UI + scripts + skills/instructions + application-state sync\n- All SQL must be dialect-agnostic (works on SQLite and Postgres)\n- No Node.js-specific APIs in server routes (must work on Cloudflare Workers, etc.)\n- Use shadcn/ui components and Tabler Icons for all UI work\n${FRAMEWORK_CORE_COMPACT}`;\n\n  return {\n    FRAMEWORK_CORE,\n    FRAMEWORK_CORE_COMPACT,\n    PROD_FRAMEWORK_PROMPT,\n    DEV_FRAMEWORK_PROMPT,\n    PROD_FRAMEWORK_PROMPT_COMPACT,\n    DEV_FRAMEWORK_PROMPT_COMPACT,\n  };\n}\n\nexport const _agentChatPromptSectionsForTests = (() => {\n  // Built with default (no template-specific) examples for test stability.\n  const {\n    FRAMEWORK_CORE: frameworkCore,\n    FRAMEWORK_CORE_COMPACT: frameworkCoreCompact,\n  } = buildFrameworkPrompts();\n  return {\n    frameworkCore,\n    frameworkCoreCompact,\n    frameworkContextSections: FRAMEWORK_CONTEXT_SECTIONS,\n    buildFrameworkPrompts,\n    generateActionsPrompt,\n    resolveInitialToolNames,\n    createDataWidgetActionEntries,\n  };\n})();\n\n/**\n * Build the per-request SQL-schema context block. Reads AGENT_ORG_ID live\n * from the environment so scheduler/A2A/HTTP call sites all see whatever\n * org was just resolved for this request.\n */\nexport async function buildSchemaBlock(\n  owner: string,\n  databaseTools: DatabaseToolsOption = \"read\",\n): Promise<string> {\n  try {\n    return await loadSchemaPromptBlock({\n      owner,\n      orgId: getRequestOrgId() ?? null,\n      databaseTools,\n    });\n  } catch {\n    return \"\";\n  }\n}\n\n/**\n * Generates a system prompt section describing registered template actions.\n * This helps the agent prefer template-specific actions over raw db-query/db-exec.\n *\n * Two output modes:\n *\n *   - `\"tool\"` — used in production, where template actions are registered\n *     as native Anthropic tools. Output reads `name(arg*: type; ...) — desc`.\n *   - `\"cli\"` — used in dev, where template actions are NOT registered as\n *     native tools and must be invoked via `bash(command=\"pnpm action ...\")`.\n *     Output reads `pnpm action name --arg <type> [--opt <type>] — desc`.\n */\nexport function generateActionsPrompt(\n  registry: Record<string, ActionEntry>,\n  mode: \"cli\" | \"tool\" = \"tool\",\n  initialToolNames?: string[],\n): string {\n  if (!registry || Object.keys(registry).length === 0) return \"\";\n\n  const allActionEntries = Object.entries(registry);\n  const initialNames = initialToolNames ? new Set(initialToolNames) : undefined;\n  const actionEntries = initialNames\n    ? allActionEntries.filter(([name]) => initialNames.has(name))\n    : allActionEntries;\n  const omittedActionCount = allActionEntries.length - actionEntries.length;\n  const nativeWidgetNote = (entry: ActionEntry) =>\n    entry.chatUI && typeof entry.chatUI.renderer === \"string\"\n      ? ` Native chat widget: \\`${entry.chatUI.renderer}\\`.`\n      : \"\";\n\n  if (mode === \"tool\") {\n    const summaryLines = actionEntries.map(([name, entry]) => {\n      const desc = compactPromptLine(\n        entry.tool.description,\n        MAX_ACTION_SUMMARY_DESCRIPTION_CHARS,\n      );\n      return `- \\`${name}\\` — ${desc}${nativeWidgetNote(entry)}`;\n    });\n\n    return `\\n\\n## Available Actions\n\n**Use these actions directly as tool calls.** They handle database access, validation, and business logic internally. The native tool schemas contain the full parameter details.\n\n${summaryLines.join(\"\\n\")}${\n      omittedActionCount > 0\n        ? `\\n\\n${omittedActionCount} less-common app action${omittedActionCount === 1 ? \" is\" : \"s are\"} available on demand. Use \\`tool-search\\` with a specific capability query to load the matching schemas when needed.`\n        : \"\"\n    }`;\n  }\n\n  const lines = actionEntries.map(([name, entry]) => {\n    const desc = entry.tool.description;\n    const params = entry.tool.parameters?.properties;\n    const requiredFields = new Set(entry.tool.parameters?.required ?? []);\n\n    // CLI mode: emit `pnpm action <name> --required <type> [--optional <type>]`\n    if (!params || Object.keys(params).length === 0) {\n      return `- \\`pnpm action ${name}\\` — ${desc}${nativeWidgetNote(entry)}`;\n    }\n    const entries = Object.entries(params);\n    // Required first (alphabetical), then optional (alphabetical)\n    entries.sort(([a], [b]) => {\n      const ar = requiredFields.has(a) ? 0 : 1;\n      const br = requiredFields.has(b) ? 0 : 1;\n      if (ar !== br) return ar - br;\n      return a.localeCompare(b);\n    });\n    const required: string[] = [];\n    const optional: string[] = [];\n    const requiredNames: string[] = [];\n    for (const [k, v] of entries) {\n      const type = (v as { type?: string }).type ?? \"any\";\n      const flag = `--${k} <${type}>`;\n      if (requiredFields.has(k)) {\n        required.push(flag);\n        requiredNames.push(`--${k}`);\n      } else {\n        optional.push(`[${flag}]`);\n      }\n    }\n    const cmd = [\"pnpm action \" + name, ...required, ...optional].join(\" \");\n    const requiredNote =\n      requiredNames.length > 0 ? ` Required: ${requiredNames.join(\", \")}.` : \"\";\n    return `- \\`${cmd}\\` — ${desc}.${requiredNote}${nativeWidgetNote(entry)}`;\n  });\n\n  return `\\n\\n## Available Actions\n\n**These template actions are NOT exposed as direct tools in dev mode. To run any of them, use the \\`bash\\` tool with the exact command shown below.** Example: \\`bash(command=\"pnpm action add-slide --deckId abc --content 'Hello'\")\\`.\n\nDo NOT try to call these by name as if they were tools — they will not exist in your tool list. Always go through \\`bash\\`.\n\n${lines.join(\"\\n\")}`;\n}\n\n/**\n * Tool names `generateCorpusToolsPrompt` teaches BY NAME, in the same order\n * it lists them. Exported so callers that build a request's initial\n * engine-tool set can fold in exactly the subset present in a given\n * registry — keeping \"what the prompt just told the model exists\" and\n * \"what tools are actually callable on the first request\" in sync. See the\n * corpus-prompt/initial-tools note at this function's call site in\n * agent-chat-plugin.ts.\n */\nconst CORPUS_TOOL_NAMES = [\n  \"provider-api-catalog\",\n  \"provider-api-docs\",\n  \"provider-api-request\",\n  \"provider-corpus-job\",\n  \"query-staged-dataset\",\n  \"run-code\",\n] as const;\n\nexport function corpusToolNamesTaughtByPrompt(\n  registry: Record<string, ActionEntry>,\n): string[] {\n  return CORPUS_TOOL_NAMES.filter((name) => name in registry);\n}\n\nexport function generateCorpusToolsPrompt(\n  registry: Record<string, ActionEntry>,\n): string {\n  const hasProviderApi = \"provider-api-request\" in registry;\n  const hasProviderCorpusJob = \"provider-corpus-job\" in registry;\n  const providerDiscoveryTools = [\n    \"provider-api-catalog\" in registry ? \"`provider-api-catalog`\" : null,\n    \"provider-api-docs\" in registry ? \"`provider-api-docs`\" : null,\n  ].filter(Boolean);\n  const hasRunCode = \"run-code\" in registry;\n  const hasStagedDataset = \"query-staged-dataset\" in registry;\n  if (\n    !hasProviderApi &&\n    !hasProviderCorpusJob &&\n    !hasRunCode &&\n    !hasStagedDataset\n  )\n    return \"\";\n\n  const available = [\n    ...providerDiscoveryTools,\n    hasProviderApi ? \"`provider-api-request`\" : null,\n    hasProviderCorpusJob ? \"`provider-corpus-job`\" : null,\n    hasStagedDataset ? \"`query-staged-dataset`\" : null,\n    hasRunCode ? \"`run-code`\" : null,\n  ].filter(Boolean);\n\n  return `\\n\\n## Broad Provider And Corpus Workflows\n\nAvailable corpus-capable tools: ${available.join(\", \")}.\n\nFor broad provider searches, raw API access, multi-page cohorts, cross-source joins, classification/counting over records, or absence-sensitive answers, do not stop at a bounded shortcut action. Use the provider's broad API/search/list surface, fetch every relevant page or an explicit bounded cohort, stage/save large responses when needed, and reduce the corpus with durable corpus jobs, staged-dataset queries, or code execution.\n\nWhen \\`provider-corpus-job\\` is available, prefer it for transcript/message/ticket/issue/document scans that may exceed one turn, need provider-side backoff, or need a defensible \"not found\" conclusion. Use operation=\"start\" with mode=\"paginated-search\" for any paginated provider endpoint, or mode=\"batch-search\" when a prior cohort of ids/records must feed a second provider endpoint. Continue paused jobs with operation=\"continue\" until status is completed or quota_wait, then read operation=\"results\". In run-code, prefer providerFetchAll() for short cursor/page/offset pagination and providerRequest() when response status, headers, or truncation metadata matters. Report source, filters, row counts, pagination/truncation, failed pages, quota_wait times, and remaining gaps.`;\n}\n\n/**\n * Walks the local filesystem (dev mode only) to build a bounded file/folder\n * tree, used by a couple of dev-mode workspace-inspection tools.\n */\nexport async function collectFiles(\n  dir: string,\n  prefix: string,\n  depth: number,\n  results: Array<{ path: string; name: string; type: \"file\" | \"folder\" }>,\n): Promise<void> {\n  if (depth > 4 || results.length >= 500) return;\n  const skip = new Set([\n    \"node_modules\",\n    \".git\",\n    \".next\",\n    \".output\",\n    \"dist\",\n    \".cache\",\n    \".turbo\",\n    \"data\",\n  ]);\n  let entries: import(\"fs\").Dirent[];\n  try {\n    const fs = await lazyFs();\n    entries = fs.readdirSync(dir, { withFileTypes: true });\n  } catch {\n    return;\n  }\n  for (const entry of entries) {\n    if (results.length >= 500) return;\n    if (skip.has(entry.name) || entry.name.startsWith(\".\")) continue;\n    const relPath = prefix ? `${prefix}/${entry.name}` : entry.name;\n    const isDir = entry.isDirectory();\n    results.push({\n      path: relPath,\n      name: entry.name,\n      type: isDir ? \"folder\" : \"file\",\n    });\n    if (isDir)\n      await collectFiles(\n        nodePath.join(dir, entry.name),\n        relPath,\n        depth + 1,\n        results,\n      );\n  }\n}\n"]}

package/dist/server/agent-chat-plugin.d.ts

@@ -23,28 +23,6 @@ export { loadRunCodeToolEntries };
 export { shouldDisableRecurringJobsRuntime };
 export { finalizeClaimedAgentChatProcessRunFailure };
 export declare function buildLeanRunPolicyPrompt(codeEditingSurfaceRestriction: string, prodCodeExecPromptNote: string): string;
-/**
- * Returns whether `owner` has already finished (or explicitly skipped) the
- * First-Session Personalization flow, via the owner-scoped
- * `application_state` "personalization" flag the agent itself writes
- * (`writeAppState("personalization", { done: true })` — see
- * FIRST_SESSION_PERSONALIZATION in prompts/framework-core.ts).
- *
- * This used to be gated on "does this thread have prior messages", which
- * flips false the instant a second request comes in for the SAME thread —
- * making turn 2's system prompt diverge from turn 1's and invalidating the
- * prompt-cache prefix on every thread's second request. The flow itself
- * spans two turns (turn 1 asks the personalization questions and waits;
- * turn 2 answers them and only then writes the "done" flag), so this flag
- * is still false when BOTH turns' system prompts are assembled — turn 1
- * and turn 2 come out byte-identical. It only flips once the flow
- * completes, and it never flips back, so every later turn (and every
- * later thread the same owner creates) stays consistent from then on. As
- * a bonus, it also fixes a latent waste: the old gate re-included the
- * ~1.5KB block on turn 1 of every new thread a user ever created, even
- * long after they'd completed personalization once.
- */
-export declare function hasCompletedFirstSessionPersonalization(owner: string): Promise<boolean>;
 /**
  * Pick the URL allowlist to enforce for a `${keys.NAME}` reference used by
  * the agent fetch tool.

package/dist/server/agent-chat-plugin.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"agent-chat-plugin.d.ts","sourceRoot":"","sources":["../../src/server/agent-chat-plugin.ts"],"names":[],"mappings":"AA6IA,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,4BAA4B,CAAC;AAEvE,OAAO,EACL,yBAAyB,EACzB,KAAK,6BAA6B,EACnC,MAAM,+BAA+B,CAAC;AAqCvC,OAAO,EAAE,yBAAyB,EAAE,CAAC;AACrC,YAAY,EAAE,6BAA6B,EAAE,CAAC;AAuB9C,OAAO,EACL,0BAA0B,EAK1B,eAAe,EACf,eAAe,EACf,wBAAwB,EACxB,yBAAyB,EAE1B,MAAM,oCAAoC,CAAC;AAW5C,OAAO,EACL,gCAAgC,EAOjC,MAAM,mCAAmC,CAAC;AAC3C,OAAO,EACL,KAAK,sBAAsB,EAC3B,KAAK,cAAc,EACpB,MAAM,gCAAgC,CAAC;AACxC,OAAO,EAAE,yCAAyC,EAAE,MAAM,qCAAqC,CAAC;AAChG,OAAO,EACL,sBAAsB,EAGvB,MAAM,kCAAkC,CAAC;AAC1C,OAAO,EAAE,iCAAiC,EAAE,MAAM,wCAAwC,CAAC;AAC3F,OAAO,EAEL,sCAAsC,EACvC,MAAM,iCAAiC,CAAC;AACzC,OAAO,EAAE,sBAAsB,EAAE,MAAM,gCAAgC,CAAC;AAYxE,OAAO,EAAE,sBAAsB,EAAE,CAAC;AAClC,OAAO,EAAE,gCAAgC,EAAE,CAAC;AAC5C,OAAO,EAAE,yBAAyB,EAAE,CAAC;AACrC,OAAO,EAAE,wBAAwB,EAAE,CAAC;AACpC,YAAY,EAAE,sBAAsB,EAAE,CAAC;AACvC,OAAO,EAAE,eAAe,EAAE,CAAC;AAC3B,OAAO,EAAE,eAAe,EAAE,CAAC;AAC3B,OAAO,EAAE,0BAA0B,EAAE,CAAC;AACtC,OAAO,EAAE,sCAAsC,EAAE,CAAC;AAClD,OAAO,EAAE,sBAAsB,EAAE,CAAC;AAClC,OAAO,EAAE,iCAAiC,EAAE,CAAC;AAC7C,OAAO,EAAE,yCAAyC,EAAE,CAAC;AAErD,wBAAgB,wBAAwB,CACtC,6BAA6B,EAAE,MAAM,EACrC,sBAAsB,EAAE,MAAM,GAC7B,MAAM,CAER;AAED;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,wBAAsB,uCAAuC,CAC3D,KAAK,EAAE,MAAM,GACZ,OAAO,CAAC,OAAO,CAAC,CAUlB;AAaD;;;;;;;;;;;;;;GAcG;AACH,wBAAsB,4BAA4B,CAChD,OAAO,EAAE,MAAM,EACf,YAAY,EAAE,oBAAoB,EAAE,GAAG,SAAS,EAChD,KAAK,EAAE,MAAM,EACb,IAAI,EAAE;IACJ,eAAe,EAAE,CACf,IAAI,EAAE,MAAM,EACZ,KAAK,EAAE,MAAM,EACb,OAAO,EAAE,MAAM,KACZ,OAAO,CAAC,MAAM,EAAE,GAAG,IAAI,CAAC,CAAC;IAC9B,uBAAuB,EAAE,CACvB,GAAG,EAAE,oBAAoB,KACtB,OAAO,CAAC,MAAM,EAAE,GAAG,IAAI,CAAC,CAAC;CAC/B,GACA,OAAO,CAAC,MAAM,EAAE,GAAG,IAAI,CAAC,CAI1B;AAED,wBAAgB,qBAAqB,CACnC,OAAO,CAAC,EAAE,sBAAsB,GAC/B,cAAc,CA+tKhB;AAED;;;;GAIG;AACH,eAAO,MAAM,sBAAsB,EAAE,cAAwC,CAAC;AAE9E,OAAO,EAEL,mBAAmB,EACnB,uBAAuB,EAGxB,MAAM,0BAA0B,CAAC;AAElC,OAAO,EAAE,mBAAmB,EAAE,CAAC;AAC/B,OAAO,EAAE,uBAAuB,EAAE,CAAC"}
+{"version":3,"file":"agent-chat-plugin.d.ts","sourceRoot":"","sources":["../../src/server/agent-chat-plugin.ts"],"names":[],"mappings":"AA4IA,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,4BAA4B,CAAC;AAEvE,OAAO,EACL,yBAAyB,EACzB,KAAK,6BAA6B,EACnC,MAAM,+BAA+B,CAAC;AAkCvC,OAAO,EAAE,yBAAyB,EAAE,CAAC;AACrC,YAAY,EAAE,6BAA6B,EAAE,CAAC;AAuB9C,OAAO,EACL,0BAA0B,EAK1B,eAAe,EACf,eAAe,EACf,wBAAwB,EACxB,yBAAyB,EAE1B,MAAM,oCAAoC,CAAC;AAW5C,OAAO,EACL,gCAAgC,EAOjC,MAAM,mCAAmC,CAAC;AAC3C,OAAO,EACL,KAAK,sBAAsB,EAC3B,KAAK,cAAc,EACpB,MAAM,gCAAgC,CAAC;AACxC,OAAO,EAAE,yCAAyC,EAAE,MAAM,qCAAqC,CAAC;AAChG,OAAO,EACL,sBAAsB,EAGvB,MAAM,kCAAkC,CAAC;AAC1C,OAAO,EAAE,iCAAiC,EAAE,MAAM,wCAAwC,CAAC;AAC3F,OAAO,EAEL,sCAAsC,EACvC,MAAM,iCAAiC,CAAC;AACzC,OAAO,EAAE,sBAAsB,EAAE,MAAM,gCAAgC,CAAC;AAYxE,OAAO,EAAE,sBAAsB,EAAE,CAAC;AAClC,OAAO,EAAE,gCAAgC,EAAE,CAAC;AAC5C,OAAO,EAAE,yBAAyB,EAAE,CAAC;AACrC,OAAO,EAAE,wBAAwB,EAAE,CAAC;AACpC,YAAY,EAAE,sBAAsB,EAAE,CAAC;AACvC,OAAO,EAAE,eAAe,EAAE,CAAC;AAC3B,OAAO,EAAE,eAAe,EAAE,CAAC;AAC3B,OAAO,EAAE,0BAA0B,EAAE,CAAC;AACtC,OAAO,EAAE,sCAAsC,EAAE,CAAC;AAClD,OAAO,EAAE,sBAAsB,EAAE,CAAC;AAClC,OAAO,EAAE,iCAAiC,EAAE,CAAC;AAC7C,OAAO,EAAE,yCAAyC,EAAE,CAAC;AAErD,wBAAgB,wBAAwB,CACtC,6BAA6B,EAAE,MAAM,EACrC,sBAAsB,EAAE,MAAM,GAC7B,MAAM,CAER;AAaD;;;;;;;;;;;;;;GAcG;AACH,wBAAsB,4BAA4B,CAChD,OAAO,EAAE,MAAM,EACf,YAAY,EAAE,oBAAoB,EAAE,GAAG,SAAS,EAChD,KAAK,EAAE,MAAM,EACb,IAAI,EAAE;IACJ,eAAe,EAAE,CACf,IAAI,EAAE,MAAM,EACZ,KAAK,EAAE,MAAM,EACb,OAAO,EAAE,MAAM,KACZ,OAAO,CAAC,MAAM,EAAE,GAAG,IAAI,CAAC,CAAC;IAC9B,uBAAuB,EAAE,CACvB,GAAG,EAAE,oBAAoB,KACtB,OAAO,CAAC,MAAM,EAAE,GAAG,IAAI,CAAC,CAAC;CAC/B,GACA,OAAO,CAAC,MAAM,EAAE,GAAG,IAAI,CAAC,CAI1B;AAED,wBAAgB,qBAAqB,CACnC,OAAO,CAAC,EAAE,sBAAsB,GAC/B,cAAc,CA8sKhB;AAED;;;;GAIG;AACH,eAAO,MAAM,sBAAsB,EAAE,cAAwC,CAAC;AAE9E,OAAO,EAEL,mBAAmB,EACnB,uBAAuB,EAGxB,MAAM,0BAA0B,CAAC;AAElC,OAAO,EAAE,mBAAmB,EAAE,CAAC;AAC/B,OAAO,EAAE,uBAAuB,EAAE,CAAC"}

package/dist/server/agent-chat-plugin.js

@@ -16,7 +16,6 @@ import { buildCurrentTimeUserContext, buildRuntimeContextPrompt, } from "../agen
 import { buildAssistantMessage, buildUserMessage, extractThreadMeta, foldAssistantTurn, mergeThreadDataForClientSave, upsertUserMessage, } from "../agent/thread-data-builder.js";
 import { attachToolSearch } from "../agent/tool-search.js";
 import { readAppStateForCurrentTab } from "../application-state/script-helpers.js";
-import { appStateGet } from "../application-state/store.js";
 import { createThread, forkThread, getThread, registerChatThreadsShareable, resolveThreadAccess, listThreads, searchThreads, renameThread, createThreadShareLink, getThreadByShareToken, getThreadShareState, revokeThreadShareLink, setThreadArchived, setThreadPinned, setThreadScope, updateThreadData, withThreadDataLock, deleteThread, setThreadQueuedMessages, } from "../chat-threads/store.js";
 import { createDbAdminAgentTools } from "../db-admin/agent-tools.js";
 import { verifyInternalToken, extractBearerToken, } from "../integrations/internal-token.js";
@@ -35,7 +34,7 @@ import { captureError } from "./capture-error.js";
 import { getH3App, markDefaultPluginProvided, trackPluginInit, } from "./framework-request-handler.js";
 import { getOrigin } from "./google-oauth.js";
 import { readBody } from "./h3-helpers.js";
-import { FIRST_SESSION_PERSONALIZATION, getModelFamilyOverlay, } from "./prompts/index.js";
+import { getModelFamilyOverlay } from "./prompts/index.js";
 import { mountRealtimeVoiceRoutes } from "./realtime-voice.js";
 import { runWithRequestContext, getRequestContext, getRequestOrgId, getRequestUserEmail, getRequestRunContext, ensureRequestRunContext, } from "./request-context.js";
 export { handleSharedThreadRequest };
@@ -81,39 +80,6 @@ export { finalizeClaimedAgentChatProcessRunFailure };
 export function buildLeanRunPolicyPrompt(codeEditingSurfaceRestriction, prodCodeExecPromptNote) {
     return codeEditingSurfaceRestriction + prodCodeExecPromptNote;
 }
-/**
- * Returns whether `owner` has already finished (or explicitly skipped) the
- * First-Session Personalization flow, via the owner-scoped
- * `application_state` "personalization" flag the agent itself writes
- * (`writeAppState("personalization", { done: true })` — see
- * FIRST_SESSION_PERSONALIZATION in prompts/framework-core.ts).
- *
- * This used to be gated on "does this thread have prior messages", which
- * flips false the instant a second request comes in for the SAME thread —
- * making turn 2's system prompt diverge from turn 1's and invalidating the
- * prompt-cache prefix on every thread's second request. The flow itself
- * spans two turns (turn 1 asks the personalization questions and waits;
- * turn 2 answers them and only then writes the "done" flag), so this flag
- * is still false when BOTH turns' system prompts are assembled — turn 1
- * and turn 2 come out byte-identical. It only flips once the flow
- * completes, and it never flips back, so every later turn (and every
- * later thread the same owner creates) stays consistent from then on. As
- * a bonus, it also fixes a latent waste: the old gate re-included the
- * ~1.5KB block on turn 1 of every new thread a user ever created, even
- * long after they'd completed personalization once.
- */
-export async function hasCompletedFirstSessionPersonalization(owner) {
-    try {
-        const state = await appStateGet(owner, "personalization");
-        return state?.done === true;
-    }
-    catch {
-        // Fail open to "not done" — same default as a brand-new user (block
-        // shown) rather than silently skipping personalization because of a
-        // transient appstate read error.
-        return false;
-    }
-}
 /**
  * In-memory rate-limit tracker for `/generate-title`. Keyed by user email,
  * value is recent invocation timestamps within the rolling window. Stale
@@ -2094,13 +2060,6 @@ Non-code requests are still fine on this surface: read data, navigate the UI, su
                     const codeEditingSurfaceRestriction = shouldBlockInProductCodeEditing(event)
                         ? APP_RENDERED_CHAT_NO_DIRECT_CODE_PROMPT
                         : "";
-                    // Personalization block: included until this owner has finished (or
-                    // skipped) the flow — see hasCompletedFirstSessionPersonalization
-                    // for why this is gated on the owner-scoped appstate flag rather
-                    // than "is this a new thread" (keeps turn 1 and turn 2 identical).
-                    const personalizationBlock = (await hasCompletedFirstSessionPersonalization(owner))
-                        ? ""
-                        : FIRST_SESSION_PERSONALIZATION;
                     // Per-model overlay: nudge GPT/Gemini engines toward our behavioral norms.
                     const modelOverlay = resolveModelOverlay();
                     // Stable-first ordering: base prompt / schema / extra come before
@@ -2139,12 +2098,9 @@ Non-code requests are still fine on this surface: read data, navigate the UI, su
                         extra,
                         modelOverlay,
                         runtimeContext,
-                        additionalFramework: personalizationBlock +
-                            codeEditingSurfaceRestriction +
-                            prodCodeExecPromptNote,
+                        additionalFramework: codeEditingSurfaceRestriction + prodCodeExecPromptNote,
                     });
                     return setSystemPromptOnContext(basePrompt +
-                        personalizationBlock +
                         resources +
                         schemaBlock +
                         codeEditingSurfaceRestriction +
@@ -2343,9 +2299,6 @@ Non-code requests are still fine on this surface: read data, navigate the UI, su
                     systemPrompt: async (event) => {
                         const { owner, extra } = await prepareRun(event);
                         const runtimeContext = runtimeContextForEvent(event);
-                        const personalizationBlock = (await hasCompletedFirstSessionPersonalization(owner))
-                            ? ""
-                            : FIRST_SESSION_PERSONALIZATION;
                         const modelOverlay = resolveModelOverlay();
                         // Stable-first ordering: runtimeContext (day-granular) is
                         // appended LAST so a day rollover invalidates as little of the
@@ -2375,10 +2328,8 @@ Non-code requests are still fine on this surface: read data, navigate the UI, su
                             extra,
                             modelOverlay,
                             runtimeContext,
-                            additionalFramework: personalizationBlock,
                         });
                         return setSystemPromptOnContext(devPrompt +
-                            personalizationBlock +
                             resources +
                             schemaBlock +
                             extra +