@agent-native/core 0.7.19 → 0.7.20

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

@@ -4,6 +4,7 @@ import { getH3App, trackPluginInit } from "./framework-request-handler.js";
 import { createProductionAgentHandler, runAgentLoop, actionsToEngineTools, getActiveRunForThreadAsync, abortRun, subscribeToRun, } from "../agent/production-agent.js";
 import { resolveEngine, createAnthropicEngine } from "../agent/engine/index.js";
 import { DEFAULT_MODEL } from "../agent/default-model.js";
+import { attachToolSearch } from "../agent/tool-search.js";
 import { McpClientManager, loadMcpConfig, autoDetectMcpConfig, mcpToolsToActionEntries, syncMcpActionEntries, mountMcpServersRoutes, mountMcpHubRoutes, buildMergedConfig, getHubStatus, isHubServeEnabled, } from "../mcp-client/index.js";
 import { discoverAgents } from "./agent-discovery.js";
 import { loadSchemaPromptBlock } from "./schema-prompt.js";
@@ -40,7 +41,11 @@ function wrapCliScript(tool, cliDefault, opts) {
         run: async (args) => {
             const cliArgs = [];
             for (const [k, v] of Object.entries(args)) {
-                cliArgs.push(`--${k}`, v);
+                const raw = v;
+                const value = raw != null && typeof raw === "object"
+                    ? JSON.stringify(raw)
+                    : String(raw);
+                cliArgs.push(`--${k}`, value);
             }
             return captureCliOutput(() => cliDefault(cliArgs));
         },
@@ -264,6 +269,10 @@ async function createDbScriptEntries() {
                             type: "string",
                             description: "SELECT query to run, e.g. \"SELECT key, value FROM settings WHERE key LIKE 'sql-dashboard-%'\"",
                         },
+                        args: {
+                            type: "string",
+                            description: 'Optional JSON array of positional bind args for parameterized placeholders. Example: \'["draft","form-123"]\'',
+                        },
                         format: {
                             type: "string",
                             description: 'Output format: "json" or "text" (default: text)',
@@ -278,16 +287,28 @@ async function createDbScriptEntries() {
                 },
             }, queryMod.default, { readOnly: true }),
             "db-exec": wrapCliScript({
-                description: "Write to the app's own SQL database ONLY. Runs INSERT / UPDATE / DELETE against the app's internal tables. Writes are auto-scoped to the current user/org, and `owner_email` / `org_id` are auto-injected on INSERT. IMPORTANT: This tool CANNOT write to external data sources like BigQuery, HubSpot, etc. For external services, use the appropriate template action.",
+                description: "Write to the app's own SQL database ONLY. Runs INSERT / UPDATE / DELETE / REPLACE against the app's internal tables. For multiple related writes, pass `statements` so they run sequentially in one transaction instead of issuing several db-exec calls. Writes are auto-scoped to the current user/org, and `owner_email` / `org_id` are auto-injected on INSERT. Schema changes (CREATE/ALTER/DROP) are blocked. IMPORTANT: This tool CANNOT write to external data sources like BigQuery, HubSpot, etc. For external services, use the appropriate template action.",
                 parameters: {
                     type: "object",
                     properties: {
                         sql: {
                             type: "string",
-                            description: "INSERT / UPDATE / DELETE statement. Use parameterized placeholders (?) if possible.",
+                            description: "Single INSERT / UPDATE / DELETE / REPLACE statement. Use parameterized placeholders (?) where possible.",
+                        },
+                        args: {
+                            type: "string",
+                            description: 'Optional JSON array of positional bind args for `sql`. Example: \'["published","form-123"]\'',
+                        },
+                        statements: {
+                            type: "string",
+                            description: 'Optional JSON array of write statements to execute in one transaction. Prefer this over multiple db-exec calls. Example: \'[{"sql":"INSERT INTO notes (id,title) VALUES (?,?)","args":["n1","One"]},{"sql":"UPDATE counters SET value = value + 1 WHERE key = ?","args":["notes"]}]\'',
+                        },
+                        format: {
+                            type: "string",
+                            description: 'Output format: "json" or "text" (default: text)',
+                            enum: ["json", "text"],
                         },
                     },
-                    required: ["sql"],
                 },
             }, execMod.default),
             "db-patch": wrapCliScript({
@@ -617,6 +638,21 @@ async function createAgentEngineScriptEntries() {
         return {};
     }
 }
+/**
+ * Creates the manage-agent-loop-settings tool. Lets the agent inspect and
+ * configure the loop step limit it may hit on long-running work.
+ */
+async function createAgentLoopSettingsScriptEntries() {
+    try {
+        const mod = await import("../scripts/manage-agent-loop-settings.js");
+        return {
+            "manage-agent-loop-settings": { tool: mod.tool, run: mod.run },
+        };
+    }
+    catch {
+        return {};
+    }
+}
 /**
  * Creates the call-agent ActionEntry for cross-agent A2A communication.
  * Binds selfAppId so the agent cannot call itself via call-agent.
@@ -933,6 +969,7 @@ const FRAMEWORK_CORE_COMPACT = `
 8. **\`db-*\` tools are internal only** — \`db-query\`, \`db-exec\`, \`db-patch\` ONLY access the app's own SQL database (settings, application_state, template tables). They CANNOT reach BigQuery, HubSpot, GA4, Jira, or any external data source. If the user asks about a table that is NOT in the app schema (e.g. \`dbt_analytics.*\`, \`dbt_mart.*\`, or any fully-qualified \`project.dataset.table\`), use the appropriate template action instead — \`bigquery\` for warehouse tables, \`ga4-report\` for Google Analytics, \`hubspot-deals\` for HubSpot, etc. **Never use \`db-query\` for external data — it will fail.**
 9. **Never fabricate data** — Do NOT invent numbers, metrics, records, or query results. Do NOT present estimated or example data as if it were real. If a data source is unavailable (missing credentials, connection error, tool failure), say so clearly, note the gap, and work with whatever data you do have. If no data can be retrieved at all, say "I can't retrieve this data right now" and explain why. Presenting made-up data as real is a critical failure — it is worse than admitting the limitation.
 10. **Never fabricate success from tool errors** — When any tool call returns an error (marked \`isError: true\`, contains "Command failed", "Error:", or non-zero exit output), the operation FAILED. Do NOT synthesize a success narrative or describe what the action "would have" produced. Report the failure verbatim from the tool output. This applies especially to \`shell(command="pnpm action ...")\` calls: if the action threw, it did NOT succeed.
+11. **Find tools when unsure** — Use \`tool-search\` to find the exact action/tool for a capability. It searches the live registry, including connected MCP server tools.
 
 ### Resources
 
@@ -1070,11 +1107,12 @@ Your memory index (\`memory/MEMORY.md\`) is loaded at the start of every convers
 
 - \`db-schema\` — refresh the full schema with indexes and foreign keys
 - \`db-query\` — run a SELECT (read-only; results already filtered to the current user/org)
-- \`db-exec\` — run INSERT / UPDATE / DELETE (writes already scoped; owner_email and org_id are auto-injected on INSERT)
+- \`db-exec\` — run INSERT / UPDATE / DELETE / REPLACE (writes already scoped; owner_email and org_id are auto-injected on INSERT). For multiple related writes, use \`statements\` so they run in one transaction instead of separate tool calls. Schema changes are blocked.
 - \`db-patch\` — surgical search-and-replace on a large text column. Use for edits to large fields instead of re-sending multi-kilobyte strings.
 
 ### When to pick which SQL tool
 - Set a short column outright, update multiple columns, or do computed updates → \`db-exec UPDATE\`
+- Insert/update several rows as one logical operation → \`db-exec\` with \`statements: '[{"sql":"...","args":[...]}]'\`
 - Change a small slice of a large text/JSON column → \`db-patch\`
 - A template-specific action exists for the table → use that action (it encodes business rules and pushes live Yjs updates)
 - Read data → \`db-query\`. Never re-add \`WHERE owner_email = ...\` — scoping already applies it.
@@ -1099,6 +1137,7 @@ const FRAMEWORK_CORE = `
 8. **\`db-*\` tools are internal only** — \`db-query\`, \`db-exec\`, \`db-patch\` ONLY access the app's own SQL database (settings, application_state, template tables). They CANNOT reach BigQuery, HubSpot, GA4, Jira, or any external data source. If the user asks about a table that is NOT in the app schema (e.g. \`dbt_analytics.*\`, \`dbt_mart.*\`, or any fully-qualified \`project.dataset.table\`), use the appropriate template action instead — \`bigquery\` for warehouse tables, \`ga4-report\` for Google Analytics, \`hubspot-deals\` for HubSpot, etc. **Never use \`db-query\` for external data — it will fail.**
 9. **Never fabricate data** — Do NOT invent numbers, metrics, records, or query results. Do NOT present estimated or example data as if it were real. If a data source is unavailable (missing credentials, connection error, tool failure), say so clearly, note the gap, and work with whatever data you do have. If no data can be retrieved at all, say "I can't retrieve this data right now" and explain why. Presenting made-up data as real is a critical failure — it is worse than admitting the limitation.
 10. **Never fabricate success from tool errors** — When any tool call returns an error (marked \`isError: true\`, contains "Command failed", "Error:", or non-zero exit output), the operation FAILED. Do NOT synthesize a success narrative, format a result table, or describe what the action "would have" produced. Report the failure verbatim from the tool output. This applies especially to \`shell(command="pnpm action ...")\` calls: if the underlying action threw (visible in the error text), the action did NOT succeed — report the error, do not describe a successful outcome.
+11. **Find tools when unsure** — Use \`tool-search\` to find the exact action/tool for a capability. It searches the live registry, including connected MCP server tools added through config, settings, or the MCP hub.
 
 ### Resources
 
@@ -1733,7 +1772,7 @@ export function createAgentChatPlugin(options) {
             if (!rawActions && Object.keys(templateScripts).length === 0) {
                 try {
                     const { autoDiscoverActions } = await import("./action-discovery.js");
-                    templateScripts = await autoDiscoverActions(process.cwd());
+                    templateScripts = await autoDiscoverActions("auto");
                 }
                 catch {
                     // Filesystem discovery unavailable (serverless bundle) — skip.
@@ -1749,9 +1788,11 @@ export function createAgentChatPlugin(options) {
             const lazyContext = options?.lazyContext !== false && !leanPrompt;
             const urlTools = createUrlTools();
             const engineScripts = await createAgentEngineScriptEntries();
+            const loopSettingsScripts = await createAgentLoopSettingsScriptEntries();
             const chatScripts = {
                 ...(await createChatScriptEntries()),
                 ...engineScripts,
+                ...loopSettingsScripts,
             };
             const callAgentScript = await createCallAgentScriptEntry(options?.appId);
             const browserTools = createBuilderBrowserTool({
@@ -1968,7 +2009,7 @@ export function createAgentChatPlugin(options) {
             // This avoids degenerate empty-object tool calls that Anthropic models
             // sometimes emit for actions with complex schemas. Production keeps the
             // native registration since it has no shell access.
-            const allScripts = canToggle
+            const allScripts = attachToolSearch(canToggle
                 ? {
                     ...resourceScripts,
                     ...docsScripts,
@@ -2002,7 +2043,7 @@ export function createAgentChatPlugin(options) {
                     ...toolActions,
                     ...browserTools,
                     ...devScriptsForA2A,
-                };
+                });
             const { mountA2A } = await import("../a2a/server.js");
             mountA2A(nitroApp, {
                 name: options?.appId
@@ -2157,7 +2198,7 @@ export function createAgentChatPlugin(options) {
                     // to prevent infinite recursive A2A loops (agent calling itself).
                     // In dev mode, template actions are invoked via shell (not native tools),
                     // so they're omitted from the tool registry — see allScripts comment.
-                    const a2aActions = devActive
+                    const a2aActions = attachToolSearch(devActive
                         ? {
                             ...resourceScripts,
                             ...docsScripts,
@@ -2179,7 +2220,7 @@ export function createAgentChatPlugin(options) {
                             ...chatScripts,
                             ...toolActions,
                             ...browserTools,
-                        };
+                        });
                     const a2aTools = actionsToEngineTools(a2aActions);
                     const a2aMessages = [
                         { role: "user", content: [{ type: "text", text }] },
@@ -2276,7 +2317,7 @@ export function createAgentChatPlugin(options) {
                     // Same actions as A2A — without call-agent to prevent loops.
                     // In dev mode, template actions go through shell, not native tools.
                     const devActiveMcp = isDevMode();
-                    const mcpActions = devActiveMcp
+                    const mcpActions = attachToolSearch(devActiveMcp
                         ? {
                             ...resourceScripts,
                             ...docsScripts,
@@ -2296,7 +2337,7 @@ export function createAgentChatPlugin(options) {
                             ...urlTools,
                             ...chatScripts,
                             ...toolActions,
-                        };
+                        });
                     const mcpTools = actionsToEngineTools(mcpActions);
                     const resources = await loadResourcesForPrompt(DEV_MODE_USER_EMAIL, lazyContext);
                     const schemaBlock = lazyContext
@@ -2355,6 +2396,7 @@ export function createAgentChatPlugin(options) {
                 ...discoveredActions,
                 ...templateScripts,
                 ...engineScripts,
+                ...loopSettingsScripts,
             };
             // Framework-level sharing actions — merged with skipExisting semantics so
             // any template that provides a same-named action wins. When templates use
@@ -2599,15 +2641,15 @@ export function createAgentChatPlugin(options) {
             // progress, call-agent, and MCP entries to keep the tool list tight and
             // prevent the LLM from reaching for web-request instead of the
             // template's native actions (e.g. log-meal).
-            const leanActions = {
+            const leanActions = attachToolSearch({
                 ...templateScripts,
                 ...resourceScripts,
                 ...refreshScreenTool,
                 ...urlTools,
                 ...chatScripts,
                 ...toolActions,
-            };
-            const prodActions = {
+            });
+            const prodActions = attachToolSearch({
                 ...templateScripts,
                 ...resourceScripts,
                 ...docsScripts,
@@ -2626,7 +2668,7 @@ export function createAgentChatPlugin(options) {
                 ...toolActions,
                 ...browserTools,
                 ...mcpActionEntries,
-            };
+            });
             // Keep the prod action dict's MCP entries in sync when the manager's
             // server set changes at runtime (e.g. a user adds a remote MCP server
             // through the settings UI). getEngineTools() in production-agent re-reads
@@ -2732,7 +2774,7 @@ export function createAgentChatPlugin(options) {
                 // template's actions as native tools instead of routing through shell.
                 // Templates with structured-arg actions (objects/arrays) need this to
                 // avoid round-tripping JSON through the CLI parser.
-                const devActions = leanPrompt
+                const devActions = attachToolSearch(leanPrompt
                     ? leanActions
                     : devNative
                         ? prodActions
@@ -2752,7 +2794,7 @@ export function createAgentChatPlugin(options) {
                             ...browserTools,
                             ...mcpActionEntries,
                             ...(await createDevScriptRegistry()),
-                        };
+                        });
                 // Keep dev action dict in sync with runtime MCP additions. When
                 // native-actions mode is on (lean or `nativeActionsInDev`), devActions
                 // === prodActions so the prod listener already covers it.