@axiom-lattice/core 2.1.97 → 2.1.98

package/dist/index.mjs

@@ -9858,10 +9858,10 @@ import { tool as tool51 } from "langchain";
 import z54 from "zod";
 var questionSchema = z54.object({
   question: z54.string().describe("The question text to ask the user"),
-  options: z54.array(z54.string()).optional().default([]).describe("List of EXACT, selectable values. Maximum 3 options allowed. DO NOT include any 'placeholder' options that require the user to type (e.g., do NOT add 'Enter manual value'). If manual input is needed, set allowOther to true instead. For file_upload questions, pass an empty array."),
-  type: z54.enum(["single", "multiple", "file_upload"]).describe("Whether the question allows single selection, multiple selections, or expects a file upload. file_upload questions render a file picker component and the uploaded file path is returned as the answer."),
+  options: z54.array(z54.string()).optional().default([]).describe("List of EXACT, selectable values. Maximum 3 options allowed. DO NOT include placeholder values like 'Other' or 'Enter manually'. For free-text with predefined choices, use allowOther=true (works with 'single' and 'multiple'). For pure free-text without choices, use type='input' instead. For file_upload and input, pass an empty array."),
+  type: z54.enum(["single", "multiple", "file_upload", "input"]).describe("The question format. 'single' = pick one from options (default, see tool description for guidance). 'multiple' = pick several from options. 'input' = free-text field (only when options cannot express the answer). 'file_upload' = file picker."),
   required: z54.boolean().optional().default(false).describe("Whether this question must be answered"),
-  allowOther: z54.boolean().optional().default(true).describe("Set to true to append an 'Other' option that opens a free-text input field. Use this for open-ended answers or when the 3 options cannot cover all possibilities.")
+  allowOther: z54.boolean().optional().default(true).describe("Set to true to append an 'Other' checkbox with a free-text input field. Works with 'single' and 'multiple' types. Use for open-ended answers or when the options cannot cover all possibilities. Not applicable for 'input' or 'file_upload' types.")
 });
 var inputSchema = z54.object({
   questions: z54.array(questionSchema).min(1, "At least one question is required").describe("A structured sequence of clarification questions. Use these to gather missing parameters or disambiguate user intent before proceeding.")
@@ -9873,7 +9873,7 @@ function createAskUserToClarifyTool() {
     },
     {
       name: "ask_user_to_clarify",
-      description: "Prompts the user to choose from a list of predefined values, provide custom input, or upload a file. USE CASES: 1. Use 'options' ONLY for distinct, mutually exclusive choices (e.g., ['Standard', 'Express']). 2. Set 'allowOther: true' ONLY when you need to capture free-text information that doesn't fit into the predefined options. 3. Use type: 'file_upload' to ask the user to upload a file \u2014 options can be an empty array for this type. IMPORTANT: Never put placeholders like 'Please specify' or 'Other' inside the 'options' list. ",
+      description: "Ask the user clarifying questions using the most appropriate question type. TYPE SELECTION GUIDE (in priority order \u2014 prefer earlier types when possible):\n1. type: 'single' \u2014 DEFAULT for most cases. Use when the user must pick ONE from a known set (e.g., ['Yes', 'No'], ['Standard', 'Express', 'Priority']). Max 3 options. Best UX: click, no typing.\n2. type: 'multiple' \u2014 Use when the user can select SEVERAL from a known set (e.g., ['Email', 'SMS', 'Push']).\n3. type: 'input' \u2014 Use when the answer is purely free-text and CANNOT be enumerated (e.g., name, email, arbitrary description). Only use this when 'single' + options is not feasible.\n4. type: 'file_upload' \u2014 Use ONLY when the user needs to upload a file. Do NOT use for text input.\n\nallowOther: true \u2014 Escape hatch for 'single' and 'multiple' types. Adds an 'Other' checkbox with a text field. Use when the options MIGHT not cover everything. Do NOT set allowOther on 'input' or 'file_upload' types.\n\nANTI-PATTERNS: Never put 'Other' or 'Enter manually' inside the options array. Never use 'input' when 'single' + options would work. Never use 'file_upload' for text input.",
       schema: inputSchema
     }
   );
@@ -9950,7 +9950,11 @@ function createAskUserClarifyMiddleware() {
           parts.push(...answer.selectedOptions ?? []);
         }
         if (answer.otherText && answer.otherText.trim() !== "") {
-          parts.push(`Other: ${answer.otherText.trim()}`);
+          if (question.type === "input") {
+            parts.push(answer.otherText.trim());
+          } else {
+            parts.push(`Other: ${answer.otherText.trim()}`);
+          }
         }
         if (answer.filePath && answer.filePath.trim() !== "") {
           parts.push(`File: ${answer.filePath.trim()}`);
@@ -15946,17 +15950,17 @@ function getAsyncPromptText() {
 
 ## Async Task Usage
 
-When tasks are independent and can run in parallel, use \`async: true\` to launch
-background tasks. The task returns immediately with a task ID.
+**IMPORTANT: Only use \`async: true\` when the USER explicitly requests it.** Do NOT set \`async: true\` on your own initiative, even if tasks appear independent or parallelizable. The user must explicitly ask for background/async execution, for example: "run this in the background", "do this asynchronously", "fire and forget", or "let me know when it's done".
 
-CRITICAL: After launching with \`async: true\`, move on immediately.
-- NEVER call check_async_task or list_async_tasks right after starting a task.
+If the user does NOT explicitly request async execution, always use \`async: false\` (the default) so the task runs synchronously and the result is available immediately.
+
+When \`async: true\` IS explicitly requested by the user:
+- The task returns immediately with a task ID.
+- Move on immediately after launching. NEVER call check_async_task or list_async_tasks right after starting a task.
 - NEVER poll for task completion. The result will arrive as a notification.
 - Only check task status when the USER explicitly asks for an update.
-- If you receive an [Async task completed] notification, read it and incorporate
-  the result into your next response. Do not then call check_async_task repeatedly.
-- Task statuses in conversation history are stale \u2014 always use fresh tool calls
-  when the user asks.
+- If you receive an [Async task completed] notification, read it and incorporate the result into your next response. Do not then call check_async_task repeatedly.
+- Task statuses in conversation history are stale \u2014 always use fresh tool calls when the user asks.
 - Use cancel_async_task if the user wants to stop a running task.
 - Keep the full task_id: never truncate or abbreviate it.`;
 }
@@ -21848,7 +21852,10 @@ registerToolLattice(
   },
   async (input, exeConfig) => {
     try {
-      const tenantId = getTenantId(exeConfig);
+      const parentRunConfig = exeConfig?.configurable?.runConfig || {};
+      const tenantId = parentRunConfig.tenantId || "default";
+      const workspaceId = parentRunConfig.workspaceId;
+      const projectId = parentRunConfig.projectId;
       const { id, message } = input;
       const store = getAssistStore();
       const existing = await store.getAssistantById(tenantId, id);
@@ -21859,7 +21866,9 @@ registerToolLattice(
       const agent = new Agent({
         tenant_id: tenantId,
         assistant_id: id,
-        thread_id: threadId
+        thread_id: threadId,
+        workspace_id: workspaceId,
+        project_id: projectId
       });
       const result = await agent.invokeWithState({ input: { message } });
       return JSON.stringify({ agentId: id, threadId, result });