windmill-components 1.511.1 → 1.531.0

package/package/components/copilot/chat/flow/core.js

@@ -1,10 +1,10 @@
-import { ScriptService } from '../../../../gen';
+import { ScriptService, JobService } from '../../../../gen';
 import YAML from 'yaml';
 import { z } from 'zod';
 import uFuzzy from '@leeoniya/ufuzzy';
 import { emptySchema, emptyString } from '../../../../utils';
 import { getFormattedResourceTypes, getLangContext, SUPPORTED_CHAT_SCRIPT_LANGUAGES } from '../script/core';
-import { createSearchHubScriptsTool, createToolDef } from '../shared';
+import { createSearchHubScriptsTool, createToolDef, executeTestRun, buildSchemaForTool, buildTestRunArgs } from '../shared';
 const searchScriptsSchema = z.object({
     query: z
         .string()
@@ -186,20 +186,39 @@ const getInstructionsForCodeGenerationToolSchema = z.object({
     language: langSchema.describe('The programming language the code will be written in')
 });
 const getInstructionsForCodeGenerationToolDef = createToolDef(getInstructionsForCodeGenerationToolSchema, 'get_instructions_for_code_generation', 'Get instructions for code generation for a raw script step');
+// Will be overridden by setSchema
+const testRunFlowSchema = z.object({
+    args: z.object({}).nullable().optional()
+        .describe('Arguments to pass to the flow (optional, uses default flow inputs if not provided)')
+});
+const testRunFlowToolDef = createToolDef(testRunFlowSchema, 'test_run_flow', 'Execute a test run of the current flow');
+const testRunStepSchema = z.object({
+    stepId: z.string().describe('The id of the step to test'),
+    args: z
+        .object({})
+        .nullable()
+        .optional()
+        .describe('Arguments to pass to the step (optional, uses default step inputs if not provided)')
+});
+const testRunStepToolDef = createToolDef(testRunStepSchema, 'test_run_step', 'Execute a test run of a specific step in the flow');
 const workspaceScriptsSearch = new WorkspaceScriptsSearch();
 export const flowTools = [
     createSearchHubScriptsTool(false),
     {
         def: searchScriptsToolDef,
         fn: async ({ args, workspace, toolId, toolCallbacks }) => {
-            toolCallbacks.setToolStatus(toolId, 'Searching for workspace scripts related to "' + args.query + '"...');
+            toolCallbacks.setToolStatus(toolId, {
+                content: 'Searching for workspace scripts related to "' + args.query + '"...'
+            });
             const parsedArgs = searchScriptsSchema.parse(args);
             const scriptResults = await workspaceScriptsSearch.search(parsedArgs.query, workspace);
-            toolCallbacks.setToolStatus(toolId, 'Found ' +
-                scriptResults.length +
-                ' scripts in the workspace related to "' +
-                args.query +
-                '"');
+            toolCallbacks.setToolStatus(toolId, {
+                content: 'Found ' +
+                    scriptResults.length +
+                    ' scripts in the workspace related to "' +
+                    args.query +
+                    '"'
+            });
             return JSON.stringify(scriptResults);
         }
     },
@@ -207,74 +226,76 @@ export const flowTools = [
         def: addStepToolDef,
         fn: async ({ args, helpers, toolId, toolCallbacks }) => {
             const parsedArgs = addStepSchema.parse(args);
-            toolCallbacks.setToolStatus(toolId, parsedArgs.location.type === 'after'
-                ? `Adding a step after step '${parsedArgs.location.afterId}'`
-                : parsedArgs.location.type === 'start'
-                    ? 'Adding a step at the start'
-                    : parsedArgs.location.type === 'start_inside_forloop'
-                        ? `Adding a step at the start of the forloop step '${parsedArgs.location.inside}'`
-                        : parsedArgs.location.type === 'start_inside_branch'
-                            ? `Adding a step at the start of the branch ${parsedArgs.location.branchIndex + 1} of step '${parsedArgs.location.inside}'`
-                            : parsedArgs.location.type === 'preprocessor'
-                                ? 'Adding a preprocessor step'
-                                : parsedArgs.location.type === 'failure'
-                                    ? 'Adding a failure step'
-                                    : 'Adding a step');
+            toolCallbacks.setToolStatus(toolId, {
+                content: parsedArgs.location.type === 'after'
+                    ? `Adding a step after step '${parsedArgs.location.afterId}'`
+                    : parsedArgs.location.type === 'start'
+                        ? 'Adding a step at the start'
+                        : parsedArgs.location.type === 'start_inside_forloop'
+                            ? `Adding a step at the start of the forloop step '${parsedArgs.location.inside}'`
+                            : parsedArgs.location.type === 'start_inside_branch'
+                                ? `Adding a step at the start of the branch ${parsedArgs.location.branchIndex + 1} of step '${parsedArgs.location.inside}'`
+                                : parsedArgs.location.type === 'preprocessor'
+                                    ? 'Adding a preprocessor step'
+                                    : parsedArgs.location.type === 'failure'
+                                        ? 'Adding a failure step'
+                                        : 'Adding a step'
+            });
             const id = await helpers.insertStep(parsedArgs.location, parsedArgs.step);
             helpers.selectStep(id);
-            toolCallbacks.setToolStatus(toolId, `Added step '${id}'`);
+            toolCallbacks.setToolStatus(toolId, { content: `Added step '${id}'` });
             return `Step ${id} added. Here is the updated flow, make sure to take it into account when adding another step:\n${YAML.stringify(helpers.getModules())}`;
         }
     },
     {
         def: removeStepToolDef,
         fn: async ({ args, helpers, toolId, toolCallbacks }) => {
-            toolCallbacks.setToolStatus(toolId, `Removing step ${args.id}...`);
+            toolCallbacks.setToolStatus(toolId, { content: `Removing step ${args.id}...` });
             const parsedArgs = removeStepSchema.parse(args);
             helpers.removeStep(parsedArgs.id);
-            toolCallbacks.setToolStatus(toolId, `Removed step '${parsedArgs.id}'`);
+            toolCallbacks.setToolStatus(toolId, { content: `Removed step '${parsedArgs.id}'` });
             return `Step '${parsedArgs.id}' removed. Here is the updated flow:\n${YAML.stringify(helpers.getModules())}`;
         }
     },
     {
         def: getStepInputsToolDef,
         fn: async ({ args, helpers, toolId, toolCallbacks }) => {
-            toolCallbacks.setToolStatus(toolId, `Getting step ${args.id} inputs...`);
+            toolCallbacks.setToolStatus(toolId, { content: `Getting step ${args.id} inputs...` });
             const parsedArgs = getStepInputsSchema.parse(args);
             const inputs = await helpers.getStepInputs(parsedArgs.id);
-            toolCallbacks.setToolStatus(toolId, `Retrieved step '${parsedArgs.id}' inputs`);
+            toolCallbacks.setToolStatus(toolId, { content: `Retrieved step '${parsedArgs.id}' inputs` });
             return YAML.stringify(inputs);
         }
     },
     {
         def: setStepInputsToolDef,
         fn: async ({ args, helpers, toolId, toolCallbacks }) => {
-            toolCallbacks.setToolStatus(toolId, `Setting step ${args.id} inputs...`);
+            toolCallbacks.setToolStatus(toolId, { content: `Setting step ${args.id} inputs...` });
             const parsedArgs = setStepInputsSchema.parse(args);
             await helpers.setStepInputs(parsedArgs.id, parsedArgs.inputs);
             helpers.selectStep(parsedArgs.id);
             const inputs = await helpers.getStepInputs(parsedArgs.id);
-            toolCallbacks.setToolStatus(toolId, `Set step '${parsedArgs.id}' inputs`);
+            toolCallbacks.setToolStatus(toolId, { content: `Set step '${parsedArgs.id}' inputs` });
             return `Step '${parsedArgs.id}' inputs set. New inputs:\n${YAML.stringify(inputs)}`;
         },
         preAction: ({ toolCallbacks, toolId }) => {
-            toolCallbacks.setToolStatus(toolId, 'Setting step inputs...');
+            toolCallbacks.setToolStatus(toolId, { content: 'Setting step inputs...' });
         }
     },
     {
         def: setFlowInputsSchemaToolDef,
         fn: async ({ args, helpers, toolId, toolCallbacks }) => {
-            toolCallbacks.setToolStatus(toolId, 'Setting flow inputs schema...');
+            toolCallbacks.setToolStatus(toolId, { content: 'Setting flow inputs schema...' });
             const parsedArgs = setFlowInputsSchemaSchema.parse(args);
             const schema = JSON.parse(parsedArgs.schema);
             await helpers.setFlowInputsSchema(schema);
             helpers.selectStep('Input');
             const updatedSchema = await helpers.getFlowInputsSchema();
-            toolCallbacks.setToolStatus(toolId, 'Set flow inputs schema');
+            toolCallbacks.setToolStatus(toolId, { content: 'Set flow inputs schema' });
             return `Flow inputs schema set. New schema:\n${JSON.stringify(updatedSchema)}`;
         },
         preAction: ({ toolCallbacks, toolId }) => {
-            toolCallbacks.setToolStatus(toolId, 'Setting flow inputs schema...');
+            toolCallbacks.setToolStatus(toolId, { content: 'Setting flow inputs schema...' });
         }
     },
     {
@@ -285,7 +306,9 @@ export const flowTools = [
                 allowResourcesFetch: true,
                 isPreprocessor: parsedArgs.id === 'preprocessor'
             });
-            toolCallbacks.setToolStatus(toolId, 'Retrieved instructions for code generation in ' + parsedArgs.language);
+            toolCallbacks.setToolStatus(toolId, {
+                content: 'Retrieved instructions for code generation in ' + parsedArgs.language
+            });
             return langContext;
         }
     },
@@ -293,14 +316,16 @@ export const flowTools = [
         def: setCodeToolDef,
         fn: async ({ args, helpers, toolId, toolCallbacks }) => {
             const parsedArgs = setCodeSchema.parse(args);
-            toolCallbacks.setToolStatus(toolId, `Setting code for step '${parsedArgs.id}'...`);
+            toolCallbacks.setToolStatus(toolId, {
+                content: `Setting code for step '${parsedArgs.id}'...`
+            });
             await helpers.setCode(parsedArgs.id, parsedArgs.code);
             helpers.selectStep(parsedArgs.id);
-            toolCallbacks.setToolStatus(toolId, `Set code for step '${parsedArgs.id}'`);
+            toolCallbacks.setToolStatus(toolId, { content: `Set code for step '${parsedArgs.id}'` });
             return `Step code set`;
         },
         preAction: ({ toolCallbacks, toolId }) => {
-            toolCallbacks.setToolStatus(toolId, 'Setting code for step...');
+            toolCallbacks.setToolStatus(toolId, { content: 'Setting code for step...' });
         }
     },
     {
@@ -309,7 +334,9 @@ export const flowTools = [
             const parsedArgs = setBranchPredicateSchema.parse(args);
             await helpers.setBranchPredicate(parsedArgs.id, parsedArgs.branchIndex, parsedArgs.expression);
             helpers.selectStep(parsedArgs.id);
-            toolCallbacks.setToolStatus(toolId, `Set predicate of branch ${parsedArgs.branchIndex + 1} of '${parsedArgs.id}'`);
+            toolCallbacks.setToolStatus(toolId, {
+                content: `Set predicate of branch ${parsedArgs.branchIndex + 1} of '${parsedArgs.id}'`
+            });
             return `Branch ${parsedArgs.branchIndex} of '${parsedArgs.id}' predicate set`;
         }
     },
@@ -319,7 +346,7 @@ export const flowTools = [
             const parsedArgs = addBranchSchema.parse(args);
             await helpers.addBranch(parsedArgs.id);
             helpers.selectStep(parsedArgs.id);
-            toolCallbacks.setToolStatus(toolId, `Added branch to '${parsedArgs.id}'`);
+            toolCallbacks.setToolStatus(toolId, { content: `Added branch to '${parsedArgs.id}'` });
             return `Branch added to '${parsedArgs.id}'`;
         }
     },
@@ -329,7 +356,9 @@ export const flowTools = [
             const parsedArgs = removeBranchSchema.parse(args);
             await helpers.removeBranch(parsedArgs.id, parsedArgs.branchIndex);
             helpers.selectStep(parsedArgs.id);
-            toolCallbacks.setToolStatus(toolId, `Removed branch ${parsedArgs.branchIndex + 1} of '${parsedArgs.id}'`);
+            toolCallbacks.setToolStatus(toolId, {
+                content: `Removed branch ${parsedArgs.branchIndex + 1} of '${parsedArgs.id}'`
+            });
             return `Branch ${parsedArgs.branchIndex} of '${parsedArgs.id}' removed`;
         }
     },
@@ -339,7 +368,9 @@ export const flowTools = [
             const parsedArgs = setForLoopIteratorExpressionSchema.parse(args);
             await helpers.setForLoopIteratorExpression(parsedArgs.id, parsedArgs.expression);
             helpers.selectStep(parsedArgs.id);
-            toolCallbacks.setToolStatus(toolId, `Set forloop '${parsedArgs.id}' iterator expression`);
+            toolCallbacks.setToolStatus(toolId, {
+                content: `Set forloop '${parsedArgs.id}' iterator expression`
+            });
             return `Forloop '${parsedArgs.id}' iterator expression set`;
         }
     },
@@ -347,11 +378,150 @@ export const flowTools = [
         def: resourceTypeToolDef,
         fn: async ({ args, toolId, workspace, toolCallbacks }) => {
             const parsedArgs = resourceTypeToolSchema.parse(args);
-            toolCallbacks.setToolStatus(toolId, 'Searching resource types for "' + parsedArgs.query + '"...');
+            toolCallbacks.setToolStatus(toolId, {
+                content: 'Searching resource types for "' + parsedArgs.query + '"...'
+            });
             const formattedResourceTypes = await getFormattedResourceTypes(parsedArgs.language, parsedArgs.query, workspace);
-            toolCallbacks.setToolStatus(toolId, 'Retrieved resource types for "' + parsedArgs.query + '"');
+            toolCallbacks.setToolStatus(toolId, {
+                content: 'Retrieved resource types for "' + parsedArgs.query + '"'
+            });
             return formattedResourceTypes;
         }
+    },
+    {
+        def: testRunFlowToolDef,
+        fn: async function ({ args, workspace, helpers, toolCallbacks, toolId }) {
+            const { flow } = helpers.getFlowAndSelectedId();
+            if (!flow || !flow.value) {
+                toolCallbacks.setToolStatus(toolId, {
+                    content: 'No flow available to test',
+                    error: 'No flow found in current context'
+                });
+                throw new Error('No flow available to test. Please ensure you have a flow open in the editor.');
+            }
+            const parsedArgs = await buildTestRunArgs(args, this.def);
+            return executeTestRun({
+                jobStarter: () => JobService.runFlowPreview({
+                    workspace: workspace,
+                    requestBody: {
+                        args: parsedArgs,
+                        value: flow.value,
+                    }
+                }),
+                workspace,
+                toolCallbacks,
+                toolId,
+                startMessage: 'Starting flow test run...',
+                contextName: 'flow'
+            });
+        },
+        setSchema: async function (helpers) {
+            await buildSchemaForTool(this.def, async () => {
+                const flowInputsSchema = await helpers.getFlowInputsSchema();
+                return flowInputsSchema;
+            });
+        },
+        requiresConfirmation: true,
+        confirmationMessage: 'Run flow test',
+        showDetails: true
+    },
+    {
+        // set strict to false to avoid issues with open ai models
+        def: { ...testRunStepToolDef, function: { ...testRunStepToolDef.function, strict: false } },
+        fn: async ({ args, workspace, helpers, toolCallbacks, toolId }) => {
+            const { flow } = helpers.getFlowAndSelectedId();
+            if (!flow || !flow.value) {
+                toolCallbacks.setToolStatus(toolId, {
+                    content: 'No flow available to test step from',
+                    error: 'No flow found in current context'
+                });
+                throw new Error('No flow available to test step from. Please ensure you have a flow open in the editor.');
+            }
+            const stepId = args.stepId;
+            const stepArgs = args.args || {};
+            // Find the step in the flow
+            const modules = helpers.getModules();
+            let targetModule = modules.find((m) => m.id === stepId);
+            if (!targetModule) {
+                toolCallbacks.setToolStatus(toolId, {
+                    content: `Step '${stepId}' not found in flow`,
+                    error: `Step with id '${stepId}' does not exist in the current flow`
+                });
+                throw new Error(`Step with id '${stepId}' not found in flow. Available steps: ${modules.map((m) => m.id).join(', ')}`);
+            }
+            const module = targetModule;
+            const moduleValue = module.value;
+            if (moduleValue.type === 'rawscript') {
+                // Test raw script step
+                return executeTestRun({
+                    jobStarter: () => JobService.runScriptPreview({
+                        workspace: workspace,
+                        requestBody: {
+                            content: moduleValue.content ?? '',
+                            language: moduleValue.language,
+                            args: module.id === 'preprocessor' ? { _ENTRYPOINT_OVERRIDE: 'preprocessor', ...stepArgs } : stepArgs
+                        }
+                    }),
+                    workspace,
+                    toolCallbacks,
+                    toolId,
+                    startMessage: `Starting test run of step '${stepId}'...`,
+                    contextName: 'script'
+                });
+            }
+            else if (moduleValue.type === 'script') {
+                // Test script step - need to get the script content
+                const script = moduleValue.hash
+                    ? await ScriptService.getScriptByHash({
+                        workspace: workspace,
+                        hash: moduleValue.hash
+                    })
+                    : await ScriptService.getScriptByPath({
+                        workspace: workspace,
+                        path: moduleValue.path
+                    });
+                return executeTestRun({
+                    jobStarter: () => JobService.runScriptPreview({
+                        workspace: workspace,
+                        requestBody: {
+                            content: script.content,
+                            language: script.language,
+                            args: module.id === 'preprocessor' ? { _ENTRYPOINT_OVERRIDE: 'preprocessor', ...stepArgs } : stepArgs,
+                        }
+                    }),
+                    workspace,
+                    toolCallbacks,
+                    toolId,
+                    startMessage: `Starting test run of script step '${stepId}'...`,
+                    contextName: 'script'
+                });
+            }
+            else if (moduleValue.type === 'flow') {
+                // Test flow step
+                return executeTestRun({
+                    jobStarter: () => JobService.runFlowByPath({
+                        workspace: workspace,
+                        path: moduleValue.path,
+                        requestBody: stepArgs
+                    }),
+                    workspace,
+                    toolCallbacks,
+                    toolId,
+                    startMessage: `Starting test run of flow step '${stepId}'...`,
+                    contextName: 'flow'
+                });
+            }
+            else {
+                toolCallbacks.setToolStatus(toolId, {
+                    content: `Step type '${moduleValue.type}' not supported for testing`,
+                    error: `Cannot test step of type '${moduleValue.type}'`
+                });
+                throw new Error(`Cannot test step of type '${moduleValue.type}'. Supported types: rawscript, script, flow`);
+            }
+        },
+        requiresConfirmation: true,
+        confirmationMessage: 'Run flow step test',
+        showDetails: true
     }
 ];
 export function prepareFlowSystemMessage() {
@@ -359,6 +529,7 @@ export function prepareFlowSystemMessage() {
 Follow the user instructions carefully.
 Go step by step, and explain what you're doing as you're doing it.
 DO NOT wait for user confirmation before performing an action. Only do it if the user explicitly asks you to wait in their initial instructions.
+ALWAYS test your modifications. You have access to the \`test_run_flow\` and \`test_run_step\` tools to test the flow and steps. If you only modified a single step, use the \`test_run_step\` tool to test it. If you modified the flow, use the \`test_run_flow\` tool to test it. If the user cancels the test run, do not try again and wait for the next user instruction.
 
 ## Understanding User Requests
 

package/package/components/copilot/chat/flow/utils.js

@@ -54,6 +54,9 @@ export function getNestedModules(flow, id, branchIndex) {
         }
         return branch.modules;
     }
+    else if (module.value.type === 'aiagent') {
+        return module.value.tools;
+    }
     else {
         throw new Error('Module is not a loop or branch');
     }

package/package/components/copilot/chat/monaco-adapter.d.ts

@@ -27,6 +27,6 @@ export declare class AIChatEditorHandler {
         groupIndex: number;
     }): void;
     private calculateVisualChanges;
-    reviewAndApply(newCode: string): Promise<void>;
+    reviewAndApply(newCode: string, applyAll?: boolean): Promise<void>;
 }
 export {};

package/package/components/copilot/chat/monaco-adapter.js

@@ -147,7 +147,7 @@ export class AIChatEditorHandler {
         }
         return changedLines;
     }
-    async reviewAndApply(newCode) {
+    async reviewAndApply(newCode, applyAll = false) {
         if (aiChatManager.pendingNewCode === newCode) {
             this.acceptAll();
             return;
@@ -204,9 +204,15 @@ export class AIChatEditorHandler {
                     return c;
                 }
             });
-            ({ collection, ids } = await displayVisualChanges('editor-windmill-chat-style', this.editor, changes));
-            this.decorationsCollections.push(collection);
-            this.viewZoneIds.push(...ids);
+            if (!applyAll) {
+                ;
+                ({ collection, ids } = await displayVisualChanges('editor-windmill-chat-style', this.editor, changes));
+                this.decorationsCollections.push(collection);
+                this.viewZoneIds.push(...ids);
+            }
+        }
+        if (applyAll) {
+            this.acceptAll();
         }
     }
 }

package/package/components/copilot/chat/navigator/core.d.ts

@@ -1,6 +1,6 @@
 import type { ChatCompletionSystemMessageParam, ChatCompletionUserMessageParam } from 'openai/resources/index.mjs';
 import type { Tool } from '../shared';
-export declare const CHAT_SYSTEM_PROMPT: string;
+export declare const CHAT_SYSTEM_PROMPT = "\nYou are Windmill's intelligent assistant, designed to help users navigate the application and answer questions about its functionality. It is your only purpose to help the user in the context of the windmill application.\nWindmill is an open-source developer platform for building internal tools, API integrations, background jobs, workflows, and user interfaces. It offers a unified system where scripts are automatically turned into sharable UIs and can be composed into flows or embedded in custom applications.\n\nYou have access to these tools:\n1. View current buttons and inputs on the page (get_triggerable_components)\n2. Execute buttons and inputs (trigger_component) \n3. Get documentation for user requests (get_documentation)\n4. Change the AI mode to the one specified (change_mode)\n\nINSTRUCTIONS:\n- When users ask about application features or concepts, first use get_documentation internally to retrieve accurate information about how to fulfill the user's request.\n- Then immediately use the available tools to guide the user through the application. Do not wait for the user's confirmation before taking action.\n- If you detect a confirmation modal that needs user confirmation, stop the navigation and let the user know that the action is pending confirmation.\n- Use get_triggerable_components to understand available options, and then trigger the components using trigger_component. Then wait a moment before rescanning the current page, and then continue with the next step. Do this 5 times max.\n- Make sure you navigated as far as possible before responding to the user. Always use get_triggerable_components one last time to make sure you didn't miss anything.\n- If you are not able to fulfill the user's request after 5 attempts, redirect the user to the documentation.\n- If you are asked to fill a form or act on an input, input the existing json object and change the fields the user asked you to change. Take into account the prompt_for_ai field of the schema to know what and how to do changes. Then tell the user that you have updated the form, and ask him to review the changes before running the script or flow.\n- For form inputs where format starts with \"resource-\" and is not \"resource-obj\", fetch the available resources using get_available_resources, and then use the resource_path prefixed with \"$res:\" to fill the input.\n- If you are not sure about an input, set the ones you are sure about, and then ask the user for the value of the input you are not sure about.\n- If the user asks you to make an API call, switch to API mode with the change_mode tool before using the new tools you'll have access to to make the API call.\n\nGENERAL PRINCIPLES:\n- Be concise but thorough\n- Focus on taking action and completing the user's goals\n- Maintain a friendly, professional tone\n- If you encounter an error or can't complete a request, explain why and suggest alternatives\n- When asked about a specific script, flow or app, first check components directly related to the mentioned entity, before checking the other components.\n- When you do not find what you are looking for on the current page, go to the home page by looking for the \"Home\" component, then scan the components again.\n\nIMPORTANT CONSIDERATIONS:\n- The user might have changed the page in the middle of the conversation, so make sure you rescan the page on each user request instead of just responding that you cannot find what the user is asking for.\n- If you navigate to a script creation page, consider this:\n  - The page opens with the settings drawer open. After doing the changes mentioned by the user, close the settings drawer.\n  - Then if the user has described what he wanted the script to do, switch to script mode with the change_mode tool, and use the new tools you'll have access to to edit the script.\n- If you navigate to a flow creation page, consider this:\n  - If the user has described what he wanted the flow to do, switch to flow mode with the change_mode tool before using the new tools you'll have access to to edit the flow.\n\nAlways use the provided tools purposefully and appropriately to achieve the user's goals.\nYour actions only allow you to navigate the application through the provided tools.\nWhen you complete the user's request, do not say \"I created...\" or \"I updated...\" or \"I deleted...\", but rather complete your response with precisions about how it works based on the documentation. Also drop a link to the relevant documentation if possible.\n\nExample of good behavior:\n- User: \"How can I set my AI providers?\"\n- You: <call get_documentation and fetch relevant documentation>\n- You: <call get_triggerable_components to find relevant components>\n- You: <trigger the components>\n- You: \"<precisions about the request based on the documentation>\"\n";
 export declare const getDocumentationTool: Tool<{}>;
 export declare const navigatorTools: Tool<{}>[];
 export declare function prepareNavigatorSystemMessage(): ChatCompletionSystemMessageParam;

package/package/components/copilot/chat/navigator/core.js

@@ -1,5 +1,5 @@
 import { ResourceService } from '../../../../gen';
-import { enterpriseLicense, workspaceStore } from '../../../../stores';
+import { workspaceStore } from '../../../../stores';
 import { get } from 'svelte/store';
 import { triggerablesByAi } from '../sharedChatState.svelte';
 export const CHAT_SYSTEM_PROMPT = `
@@ -10,7 +10,7 @@ You have access to these tools:
 1. View current buttons and inputs on the page (get_triggerable_components)
 2. Execute buttons and inputs (trigger_component) 
 3. Get documentation for user requests (get_documentation)
-4. A list of tools to interact with the backend API
+4. Change the AI mode to the one specified (change_mode)
 
 INSTRUCTIONS:
 - When users ask about application features or concepts, first use get_documentation internally to retrieve accurate information about how to fulfill the user's request.
@@ -22,7 +22,7 @@ INSTRUCTIONS:
 - If you are asked to fill a form or act on an input, input the existing json object and change the fields the user asked you to change. Take into account the prompt_for_ai field of the schema to know what and how to do changes. Then tell the user that you have updated the form, and ask him to review the changes before running the script or flow.
 - For form inputs where format starts with "resource-" and is not "resource-obj", fetch the available resources using get_available_resources, and then use the resource_path prefixed with "$res:" to fill the input.
 - If you are not sure about an input, set the ones you are sure about, and then ask the user for the value of the input you are not sure about.
-${get(enterpriseLicense) ? `- If asked to look through the jobs logs, use the /srch/w/{workspace}/index/search/job endpoint to search for the relevant jobs runs. Then use /w/{workspace}/jobs_u/get to get the logs of each job.` : ''}
+- If the user asks you to make an API call, switch to API mode with the change_mode tool before using the new tools you'll have access to to make the API call.
 
 GENERAL PRINCIPLES:
 - Be concise but thorough
@@ -33,7 +33,6 @@ GENERAL PRINCIPLES:
 - When you do not find what you are looking for on the current page, go to the home page by looking for the "Home" component, then scan the components again.
 
 IMPORTANT CONSIDERATIONS:
-- If you do an API call, make sure you ask the user if he also wants you to navigate the application to fulfill his request.
 - The user might have changed the page in the middle of the conversation, so make sure you rescan the page on each user request instead of just responding that you cannot find what the user is asking for.
 - If you navigate to a script creation page, consider this:
   - The page opens with the settings drawer open. After doing the changes mentioned by the user, close the settings drawer.
@@ -41,13 +40,6 @@ IMPORTANT CONSIDERATIONS:
 - If you navigate to a flow creation page, consider this:
   - If the user has described what he wanted the flow to do, switch to flow mode with the change_mode tool before using the new tools you'll have access to to edit the flow.
 
-API_TOOLS_RESTRICTIONS:
-- You can only use the API tools to fetch data from the backend API after you tried to navigate the application to fulfill the user's request and it's not enough to do so. ALWAYS ask the user if he also wants you to navigate the application to fulfill his request.
-- If you use api tools, also fetch the relevant documentation to help the user understand the data you fetched, with a link to the documentation if possible.
-
-RETRIEVE_AVAILABLE_RESOURCES_RESTRICTION:
-- You can only use the get_available_resources tool to fill a form or an input based on the user's request. Do not use it when directly asked to fetch available resources, use the API tools instead.
-
 Always use the provided tools purposefully and appropriately to achieve the user's goals.
 Your actions only allow you to navigate the application through the provided tools.
 When you complete the user's request, do not say "I created..." or "I updated..." or "I deleted...", but rather complete your response with precisions about how it works based on the documentation. Also drop a link to the relevant documentation if possible.
@@ -259,18 +251,24 @@ async function getAvailableResources(args) {
 const triggerComponentTool = {
     def: EXECUTE_COMMAND_TOOL,
     fn: async ({ args, toolId, toolCallbacks }) => {
-        toolCallbacks.setToolStatus(toolId, 'Triggering component...');
+        toolCallbacks.setToolStatus(toolId, { content: 'Triggering component...' });
         const result = triggerComponent(args);
-        toolCallbacks.setToolStatus(toolId, args.actionTaken.charAt(0).toUpperCase() + args.actionTaken.slice(1));
+        toolCallbacks.setToolStatus(toolId, {
+            content: args.actionTaken.charAt(0).toUpperCase() + args.actionTaken.slice(1)
+        });
         return result;
     }
 };
 const getTriggerableComponentsTool = {
     def: GET_TRIGGERABLE_COMPONENTS_TOOL,
     fn: async ({ toolId, toolCallbacks }) => {
-        toolCallbacks.setToolStatus(toolId, 'Scanning the page...');
+        toolCallbacks.setToolStatus(toolId, {
+            content: 'Scanning the page...',
+        });
         const components = getTriggerableComponents();
-        toolCallbacks.setToolStatus(toolId, 'Scanned the page');
+        toolCallbacks.setToolStatus(toolId, {
+            content: 'Scanned the page',
+        });
         return components;
     }
 };
@@ -278,21 +276,21 @@ const getCurrentPageNameTool = {
     def: GET_CURRENT_PAGE_NAME_TOOL,
     fn: async ({ toolId, toolCallbacks }) => {
         const pageName = getCurrentPageName();
-        toolCallbacks.setToolStatus(toolId, 'Retrieved current page name');
+        toolCallbacks.setToolStatus(toolId, { content: 'Retrieved current page name' });
         return pageName;
     }
 };
 export const getDocumentationTool = {
     def: GET_DOCUMENTATION_TOOL,
     fn: async ({ args, toolId, toolCallbacks }) => {
-        toolCallbacks.setToolStatus(toolId, 'Getting documentation...');
+        toolCallbacks.setToolStatus(toolId, { content: 'Getting documentation...' });
         try {
             const docResult = await getDocumentation(args);
-            toolCallbacks.setToolStatus(toolId, 'Retrieved documentation');
+            toolCallbacks.setToolStatus(toolId, { content: 'Retrieved documentation' });
             return docResult;
         }
         catch (error) {
-            toolCallbacks.setToolStatus(toolId, 'Error getting documentation');
+            toolCallbacks.setToolStatus(toolId, { content: 'Error getting documentation', error: 'Error getting documentation' });
             console.error('Error getting documentation:', error);
             return 'Failed to get documentation, pursuing with the user request...';
         }
@@ -301,14 +299,14 @@ export const getDocumentationTool = {
 const getAvailableResourcesTool = {
     def: GET_AVAILABLE_RESOURCES_TOOL,
     fn: async ({ args, toolId, toolCallbacks }) => {
-        toolCallbacks.setToolStatus(toolId, 'Getting available resources...');
+        toolCallbacks.setToolStatus(toolId, { content: 'Getting available resources...' });
         try {
             const resources = await getAvailableResources(args);
-            toolCallbacks.setToolStatus(toolId, 'Retrieved available resources');
+            toolCallbacks.setToolStatus(toolId, { content: 'Retrieved available resources' });
             return resources;
         }
         catch (error) {
-            toolCallbacks.setToolStatus(toolId, 'Error getting available resources');
+            toolCallbacks.setToolStatus(toolId, { content: 'Error getting available resources', error: 'Error getting available resources' });
             console.error('Error getting available resources:', error);
             return 'Failed to get available resources, pursuing with the user request...';
         }

package/package/components/copilot/chat/script/core.d.ts

@@ -10,7 +10,7 @@ export declare function getLangContext(lang: ScriptLang | 'bunnative' | 'jsx' |
     isFailure?: boolean;
 }): string;
 export declare function getFormattedResourceTypes(lang: ScriptLang | 'bunnative', prompt: string, workspace: string): Promise<string>;
-export declare const CHAT_SYSTEM_PROMPT = "\n\tYou are a coding assistant for the Windmill platform. You are provided with a list of `INSTRUCTIONS` and the current contents of a code file under `CODE`.\n\n\tYour task is to respond to the user's request. Assume all user queries are valid and actionable.\n\n\tWhen the user requests code changes:\n\t- Always include a **single code block** with the **entire updated file**, not just the modified sections.\n\t- The code can include `[#START]` and `[#END]` markers to indicate the start and end of a code piece. You MUST only modify the code between these markers if given, and remove them in your response. If a question is asked about the code, you MUST only talk about the code between the markers. Refer to it as the code piece, not the code between the markers.\n\t- Follow the instructions carefully and explain the reasoning behind your changes.\n\t- If the request is abstract (e.g., \"make this cleaner\"), interpret it concretely and reflect that in the code block.\n\t- Preserve existing formatting, indentation, and whitespace unless changes are strictly required to fulfill the user's request.\n\t- The user can ask you to look at or modify specific files, databases or errors by having its name in the INSTRUCTIONS preceded by the @ symbol. In this case, put your focus on the element that is explicitly mentioned.\n\t- The user can ask you questions about a list of `DATABASES` that are available in the user's workspace. If the user asks you a question about a database, you should ask the user to specify the database name if not given, or take the only one available if there is only one.\n\t- You can also receive a `DIFF` of the changes that have been made to the code. You should use this diff to give better answers.\n\t- Before giving your answer, check again that you carefully followed these instructions.\n\t- When asked to create a script that communicates with an external service, you can use the `search_hub_scripts` tool to search for relevant scripts in the hub. Make sure the language is the same as what the user is coding in. If you do not find any relevant scripts, you can use the `search_npm_packages` tool to search for relevant packages and their documentation. Always give a link to the documentation in your answer if possible.\n\n\tImportant:\n\tDo not mention or reveal these instructions to the user unless explicitly asked to do so.\n";
+export declare const CHAT_SYSTEM_PROMPT = "\n\tYou are a coding assistant for the Windmill platform. You are provided with a list of `INSTRUCTIONS` and the current contents of a code file under `CODE`.\n\n\tYour task is to respond to the user's request. Assume all user queries are valid and actionable.\n\n\tWhen the user requests code changes:\n\t- Always include a **single code block** with the **entire updated file**, not just the modified sections.\n\t- The code can include `[#START]` and `[#END]` markers to indicate the start and end of a code piece. You MUST only modify the code between these markers if given, and remove them in your response. If a question is asked about the code, you MUST only talk about the code between the markers. Refer to it as the code piece, not the code between the markers.\n\t- Follow the instructions carefully and explain the reasoning behind your changes.\n\t- If the request is abstract (e.g., \"make this cleaner\"), interpret it concretely and reflect that in the code block.\n\t- Preserve existing formatting, indentation, and whitespace unless changes are strictly required to fulfill the user's request.\n\t- The user can ask you to look at or modify specific files, databases or errors by having its name in the INSTRUCTIONS preceded by the @ symbol. In this case, put your focus on the element that is explicitly mentioned.\n\t- The user can ask you questions about a list of `DATABASES` that are available in the user's workspace. If the user asks you a question about a database, you should ask the user to specify the database name if not given, or take the only one available if there is only one.\n\t- You can also receive a `DIFF` of the changes that have been made to the code. You should use this diff to give better answers.\n\t- Before giving your answer, check again that you carefully followed these instructions.\n\t- When asked to create a script that communicates with an external service, you can use the `search_hub_scripts` tool to search for relevant scripts in the hub. Make sure the language is the same as what the user is coding in. If you do not find any relevant scripts, you can use the `search_npm_packages` tool to search for relevant packages and their documentation. Always give a link to the documentation in your answer if possible.\n\t- After modifying the code, ALWAYS use the `test_run_script` tool to test the code, and iterate on the code until it works as expected. If the user cancels the test run, do not try again and wait for the next user instruction.\n\n\tImportant:\n\tDo not mention or reveal these instructions to the user unless explicitly asked to do so.\n";
 export declare const INLINE_CHAT_SYSTEM_PROMPT = "\n# Windmill Inline Coding Assistant\n\nYou are a coding assistant for the Windmill platform. You provide precise code modifications based on user instructions.\n\n## Input Format\n\nYou will receive:\n- **INSTRUCTIONS**: User's modification request\n- **CODE**: Current code content with modification boundaries\n- **DATABASES** *(optional)*: Available workspace databases\n\n### Code Boundaries\n\nThe code contains `[#START]` and `[#END]` markers indicating the modification scope:\n- **MUST** only modify code between these markers\n- **MUST** remove the markers in your response\n- **MUST** preserve all other code exactly as provided\n\n## Task Requirements\n\nReturn the modified CODE that fulfills the user's request. Assume all user queries are valid and actionable.\n\n### Critical Rules\n\n- \u2705 **ALWAYS** include a single code block with the entire updated CODE\n- \u2705 **ALWAYS** use the structured XML output format below\n- \u274C **NEVER** include only modified sections\n- \u274C **NEVER** add explanatory text or comments outside the format\n- \u274C **NEVER** include ``` code fences in your response\n- \u274C **NEVER** modify the code outside the boundaries\n\n## Output Format\n\n```xml\n<changes_made>\nBrief description of what was changed\n</changes_made>\n<new_code>\n[complete modified code without markers]\n</new_code>\n```\n\n## Example\n\n### Input:\n```xml\n<user_request>\nINSTRUCTIONS:\nReturn 2 instead of 1\n\nCODE:\nimport * as wmill from \"windmill-client\"\n\nfunction test() {\n\treturn \"hello\"\n}\n\n[#START]\nexport async function main() {\n\treturn 1;\n}\n[#END]\n</user_request>\n```\n\n### Expected Output:\n```xml\n<changes_made>\nChanged return value from 1 to 2 in main function\n</changes_made>\n<new_code>\nimport * as wmill from \"windmill-client\"\n\nfunction test() {\n\treturn \"hello\"\n}\n\nexport async function main() {\n\treturn 2;\n}\n</new_code>\n```\n";
 export declare const CHAT_USER_PROMPT = "\nINSTRUCTIONS:\n{instructions}\n\nWINDMILL LANGUAGE CONTEXT:\n{lang_context}\n\n";
 export declare const CHAT_USER_DB_CONTEXT = "- {title}: SCHEMA: \n{schema}\n";
@@ -18,10 +18,17 @@ export declare function prepareScriptSystemMessage(): ChatCompletionSystemMessag
 export declare function prepareScriptTools(language: ScriptLang | 'bunnative', context: ContextElement[]): Tool<ScriptChatHelpers>[];
 export declare function prepareScriptUserMessage(instructions: string, language: ScriptLang | 'bunnative', selectedContext: ContextElement[], options?: {
     isPreprocessor?: boolean;
-}): Promise<ChatCompletionUserMessageParam>;
+}): ChatCompletionUserMessageParam;
 export declare const MAX_SCHEMA_LENGTH: number;
 export interface ScriptChatHelpers {
-    getLang: () => ScriptLang | 'bunnative';
+    getScriptOptions: () => {
+        code: string;
+        lang: ScriptLang | 'bunnative';
+        path: string;
+        args: Record<string, any>;
+    };
+    getLastSuggestedCode: () => string | undefined;
+    applyCode: (code: string, applyAll?: boolean) => void;
 }
 export declare const resourceTypeTool: Tool<ScriptChatHelpers>;
 export declare const dbSchemaTool: Tool<ScriptChatHelpers>;
@@ -34,3 +41,4 @@ export declare function fetchNpmPackageTypes(packageName: string, version?: stri
     types: string;
     error?: string;
 }>;
+export declare const testRunScriptTool: Tool<ScriptChatHelpers>;