@polka-codes/core 0.4.3 → 0.4.4

package/dist/index.js

@@ -2877,6 +2877,7 @@ class AiServiceBase {
       totalCost: 0
     };
     let resp = "";
+    let reasoning = "";
     for await (const chunk of stream) {
       switch (chunk.type) {
         case "usage":
@@ -2889,10 +2890,13 @@ class AiServiceBase {
         case "text":
           resp += chunk.text;
           break;
+        case "reasoning":
+          reasoning += chunk.text;
       }
     }
     return {
       response: resp,
+      reasoning,
       usage
     };
   }
@@ -7884,6 +7888,12 @@ class DeepSeekService extends AiServiceBase {
     });
     for await (const chunk of stream) {
       const delta = chunk.choices[0]?.delta;
+      if (delta?.reasoning_content) {
+        yield {
+          type: "reasoning",
+          text: delta.reasoning_content
+        };
+      }
       if (delta?.content) {
         yield {
           type: "text",
@@ -7964,6 +7974,15 @@ var createService = (provider, options) => {
   }
 };
 // src/tool.ts
+var ToolResponseType;
+((ToolResponseType2) => {
+  ToolResponseType2["Reply"] = "Reply";
+  ToolResponseType2["Exit"] = "Exit";
+  ToolResponseType2["Invalid"] = "Invalid";
+  ToolResponseType2["Error"] = "Error";
+  ToolResponseType2["Interrupted"] = "Interrupted";
+  ToolResponseType2["HandOver"] = "HandOver";
+})(ToolResponseType ||= {});
 var getAvailableTools = (provider, allTools) => {
   return allTools.filter((tool) => tool.isAvailable(provider));
 };
@@ -8116,6 +8135,95 @@ By adhering to these guidelines:
 - You confirm each step’s results before proceeding.
 - You provide only the necessary information in user-facing replies to prevent re-interpretation as new commands.`;
 };
+var agentsPrompt = (agents, name) => `
+====
+
+AVAILABLE AGENTS
+
+The following agents are available for task handover:
+${agents.map((agent) => `
+- **${agent.name}**
+  - Responsibilities:
+${agent.responsibilities.map((resp) => `    - ${resp}`).join(`
+`)}`).join(`
+`)}
+
+- **Current Agent Role**
+  You are currently acting as **${name}**. If you identify the task is beyond your current scope, use the handover tool to transition to the other agent. Include sufficient context so the new agent can seamlessly continue the work.
+`;
+var capabilities = (toolNamePrefix) => `
+====
+
+CAPABILITIES
+
+- You have access to a range of tools to aid you in your work. These tools help you effectively accomplish a wide range of tasks, such as writing code, making edits or improvements to existing files, understanding the current state of a project, performing system operations, and much more.
+- When the user initially gives you a task, a recursive list of all filepaths in the current working directory will be included in environment_details. This provides an overview of the project's file structure, offering key insights into the project from directory/file names (how developers conceptualize and organize their code) and file extensions (the language used). This can also guide decision-making on which files to explore further.
+- You can use ${toolNamePrefix}search_files to perform regex searches across files in a specified directory, outputting context-rich results that include surrounding lines. This is particularly useful for understanding code patterns, finding specific implementations, or identifying areas that need refactoring.
+- You can use the ${toolNamePrefix}list_code_definition_names tool to get an overview of source code definitions for all files at the top level of a specified directory. This can be particularly useful when you need to understand the broader context and relationships between certain parts of the code. You may need to call this tool multiple times to understand various parts of the codebase related to the task.
+\t- For example, when asked to make edits or improvements you might analyze the file structure in the initial environment_details to get an overview of the project, then use ${toolNamePrefix}list_code_definition_names to get further insight using source code definitions for files located in relevant directories, then ${toolNamePrefix}read_file to examine the contents of relevant files, analyze the code and suggest improvements or make necessary edits, then use the ${toolNamePrefix}replace_in_file tool to implement changes. If you refactored code that could affect other parts of the codebase, you could use ${toolNamePrefix}search_files to ensure you update other files as needed.
+- You can use the ${toolNamePrefix}execute_command tool to run commands on the user's computer whenever you feel it can help accomplish the user's task. When you need to execute a CLI command, you must provide a clear explanation of what the command does. Prefer to execute complex CLI commands over creating executable scripts, since they are more flexible and easier to run. Interactive and long-running commands are allowed, since the commands are run in the user's VSCode terminal. The user may keep commands running in the background and you will be kept updated on their status along the way. Each command you execute is run in a new terminal instance.`;
+var systemInformation = (info) => `
+====
+
+SYSTEM INFORMATION
+
+Operating System: ${info.os}`;
+var interactiveMode = (interactive) => {
+  if (interactive) {
+    return `
+====
+
+INTERACTIVE MODE
+
+You are in interactive mode. This means you may ask user questions to gather additional information to complete the task.
+`;
+  }
+  return `
+====
+
+NON-INTERACTIVE MODE
+
+You are in non-interactive mode. This means you will not be able to ask user questions to gather additional information to complete the task. You should try to use available tools to accomplish the task. If unable to precede further, you may try to end the task and provide a reason.
+`;
+};
+var customInstructions = (customInstructions2) => {
+  const joined = customInstructions2.join(`
+`);
+  if (joined.trim() === "") {
+    return "";
+  }
+  return `
+====
+
+USER'S CUSTOM INSTRUCTIONS
+
+The following additional instructions are provided by the user, and should be followed to the best of your ability without interfering with the TOOL USE guidelines.
+
+${joined}`;
+};
+var customScripts = (commands) => {
+  const joined = Object.entries(commands).map(([name, command]) => {
+    if (typeof command === "string") {
+      return `- ${name}
+  - Command: \`${command}\``;
+    }
+    return `- ${name}
+  - Command: \`${command.command}\`
+  - Description: ${command.description}`;
+  }).join(`
+`);
+  if (joined.trim() === "") {
+    return "";
+  }
+  return `
+====
+
+USER'S CUSTOM COMMANDS
+
+The following additional commands are provided by the user, and should be followed to the best of your ability without interfering with the TOOL USE guidelines.
+
+${joined}`;
+};
 var responsePrompts = {
   errorInvokeTool: (tool, error) => `An error occurred while invoking the tool "${tool}": ${error}`,
   requireUseTool: "Error: You must use a tool before proceeding",
@@ -8128,20 +8236,34 @@ ${result}
 };
 
 // src/Agent/AgentBase.ts
-var ExitReason;
-((ExitReason2) => {
-  ExitReason2["Completed"] = "Completed";
-  ExitReason2["MaxIterations"] = "MaxIterations";
-  ExitReason2["WaitForUserInput"] = "WaitForUserInput";
-  ExitReason2["Interrupted"] = "Interrupted";
-})(ExitReason ||= {});
+var TaskEventKind;
+((TaskEventKind2) => {
+  TaskEventKind2["StartRequest"] = "StartRequest";
+  TaskEventKind2["EndRequest"] = "EndRequest";
+  TaskEventKind2["Usage"] = "Usage";
+  TaskEventKind2["Text"] = "Text";
+  TaskEventKind2["Reasoning"] = "Reasoning";
+  TaskEventKind2["ToolUse"] = "ToolUse";
+  TaskEventKind2["ToolReply"] = "ToolReply";
+  TaskEventKind2["ToolInvalid"] = "ToolInvalid";
+  TaskEventKind2["ToolError"] = "ToolError";
+  TaskEventKind2["ToolInterrupted"] = "ToolInterrupted";
+  TaskEventKind2["ToolHandOver"] = "ToolHandOver";
+  TaskEventKind2["MaxIterationsReached"] = "MaxIterationsReached";
+  TaskEventKind2["EndTask"] = "EndTask";
+})(TaskEventKind ||= {});
 
 class AgentBase {
   ai;
   config;
   handlers;
-  constructor(ai, config) {
+  constructor(name, ai, config) {
     this.ai = ai;
+    if (config.agents && Object.keys(config.agents).length > 0) {
+      const agents = agentsPrompt(config.agents, name);
+      config.systemPrompt += `
+${agents}`;
+    }
     this.config = config;
     const handlers = {};
     for (const tool of config.tools) {
@@ -8178,24 +8300,26 @@ class AgentBase {
     let nextRequest = userMessage;
     while (nextRequest) {
       if (taskInfo.messages.length > taskInfo.options.maxIterations * 2) {
-        callback({ kind: "max_iterations_reached", info: taskInfo });
-        return ["MaxIterations" /* MaxIterations */, taskInfo];
+        callback({ kind: "MaxIterationsReached" /* MaxIterationsReached */, info: taskInfo });
+        return ["MaxIterations", taskInfo];
       }
       const response = await this.#request(taskInfo, nextRequest, callback);
       const [newMessage, exitReason] = await this.#handleResponse(taskInfo, response, callback);
       if (exitReason) {
+        callback({ kind: "EndTask" /* EndTask */, info: taskInfo });
         return [exitReason, taskInfo];
       }
       nextRequest = newMessage;
     }
-    callback({ kind: "end_task", info: taskInfo });
-    return ["Completed" /* Completed */, taskInfo];
+    callback({ kind: "EndTask" /* EndTask */, info: taskInfo });
+    return [{ type: "Exit" /* Exit */, message: "Task completed successfully" }, taskInfo];
   }
-  async continueTask(userMessage, taskInfo, callback) {
+  async continueTask(userMessage, taskInfo, callback = () => {
+  }) {
     return await this.#processLoop(userMessage, taskInfo, callback);
   }
   async#request(info, userMessage, callback) {
-    await callback({ kind: "start_request", info, userMessage });
+    await callback({ kind: "StartRequest" /* StartRequest */, info, userMessage });
     info.messages.push({
       role: "user",
       content: userMessage
@@ -8210,11 +8334,14 @@ class AgentBase {
           info.cacheWriteTokens = chunk.cacheWriteTokens ?? 0;
           info.cacheReadTokens = chunk.cacheReadTokens ?? 0;
           info.totalCost = chunk.totalCost;
-          await callback({ kind: "usage", info });
+          await callback({ kind: "Usage" /* Usage */, info });
           break;
         case "text":
           currentAssistantMessage += chunk.text;
-          await callback({ kind: "text", info, newText: chunk.text });
+          await callback({ kind: "Text" /* Text */, info, newText: chunk.text });
+          break;
+        case "reasoning":
+          await callback({ kind: "Reasoning" /* Reasoning */, info, newText: chunk.text });
           break;
       }
     }
@@ -8226,41 +8353,53 @@ class AgentBase {
       content: currentAssistantMessage
     });
     const ret = parseAssistantMessage(currentAssistantMessage, this.config.tools, this.config.toolNamePrefix);
-    await callback({ kind: "end_request", info });
+    await callback({ kind: "EndRequest" /* EndRequest */, info });
     return ret;
   }
   async#handleResponse(info, response, callback) {
     const toolReponses = [];
-    for (const content of response) {
-      switch (content.type) {
-        case "text":
-          break;
-        case "tool_use": {
-          await callback({ kind: "tool_use", info, tool: content.name });
-          const toolResp = await this.#invokeTool(content.name, content.params);
-          switch (toolResp.type) {
-            case "Reply" /* Reply */:
-              await callback({ kind: "tool_reply", info, tool: content.name });
-              toolReponses.push({ tool: content.name, response: toolResp.message });
-              break;
-            case "Exit" /* Exit */:
-              return [undefined, "Completed" /* Completed */];
-            case "Invalid" /* Invalid */:
-              await callback({ kind: "tool_invalid", info, tool: content.name });
-              toolReponses.push({ tool: content.name, response: toolResp.message });
-              break;
-            case "Error" /* Error */:
-              await callback({ kind: "tool_error", info, tool: content.name });
-              toolReponses.push({ tool: content.name, response: toolResp.message });
-              break;
-            case "Interrupted" /* Interrupted */:
-              await callback({ kind: "tool_interrupted", info, tool: content.name });
-              return [undefined, "Interrupted" /* Interrupted */];
+    outer:
+      for (const content of response) {
+        switch (content.type) {
+          case "text":
+            break;
+          case "tool_use": {
+            await callback({ kind: "ToolUse" /* ToolUse */, info, tool: content.name });
+            const toolResp = await this.#invokeTool(content.name, content.params);
+            switch (toolResp.type) {
+              case "Reply" /* Reply */:
+                await callback({ kind: "ToolReply" /* ToolReply */, info, tool: content.name });
+                toolReponses.push({ tool: content.name, response: toolResp.message });
+                break;
+              case "Exit" /* Exit */:
+                return [undefined, toolResp];
+              case "Invalid" /* Invalid */:
+                await callback({ kind: "ToolInvalid" /* ToolInvalid */, info, tool: content.name });
+                toolReponses.push({ tool: content.name, response: toolResp.message });
+                break outer;
+              case "Error" /* Error */:
+                await callback({ kind: "ToolError" /* ToolError */, info, tool: content.name });
+                toolReponses.push({ tool: content.name, response: toolResp.message });
+                break outer;
+              case "Interrupted" /* Interrupted */:
+                await callback({ kind: "ToolInterrupted" /* ToolInterrupted */, info, tool: content.name });
+                return [undefined, toolResp];
+              case "HandOver" /* HandOver */:
+                await callback({
+                  kind: "ToolHandOver" /* ToolHandOver */,
+                  info,
+                  tool: content.name,
+                  agentName: toolResp.agentName,
+                  task: toolResp.task,
+                  context: toolResp.context,
+                  files: toolResp.files
+                });
+                return [undefined, toolResp];
+            }
+            break;
           }
-          break;
         }
       }
-    }
     if (toolReponses.length === 0 && !this.config.interactive) {
       return [responsePrompts.requireUseTool, undefined];
     }
@@ -8328,6 +8467,7 @@ __export(exports_allTools, {
   readFile: () => readFile_default,
   listFiles: () => listFiles_default,
   listCodeDefinitionNames: () => listCodeDefinitionNames_default,
+  handOver: () => handOver_default,
   executeCommand: () => executeCommand_default,
   attemptCompletion: () => attemptCompletion_default,
   askFollowupQuestion: () => askFollowupQuestion_default
@@ -8391,14 +8531,14 @@ ${search}`);
 // src/tools/utils/getArg.ts
 var getString = (args, name, defaultValue) => {
   const ret = args[name] ?? defaultValue;
-  if (!ret) {
+  if (ret === undefined) {
     throw new Error(`Missing required argument: ${name}`);
   }
   return ret;
 };
 var getStringArray = (args, name, defaultValue) => {
   const ret = args[name];
-  if (!ret) {
+  if (ret === undefined) {
     if (defaultValue === undefined) {
       throw new Error(`Missing required argument: ${name}`);
     }
@@ -8408,7 +8548,7 @@ var getStringArray = (args, name, defaultValue) => {
 };
 var getBoolean = (args, name, defaultValue) => {
   const ret = args[name];
-  if (!ret) {
+  if (ret === undefined) {
     if (defaultValue === undefined) {
       throw new Error(`Missing required argument: ${name}`);
     }
@@ -8425,7 +8565,7 @@ var getBoolean = (args, name, defaultValue) => {
 };
 var getInt = (args, name, defaultValue) => {
   const ret = args[name];
-  if (!ret) {
+  if (ret === undefined) {
     if (defaultValue === undefined) {
       throw new Error(`Missing required argument: ${name}`);
     }
@@ -9047,6 +9187,81 @@ var writeToFile_default = {
   handler: handler9,
   isAvailable: isAvailable9
 };
+// src/tools/handOver.ts
+var toolInfo10 = {
+  name: "hand_over",
+  description: "Hand over the current task to another agent to complete",
+  parameters: [
+    {
+      name: "agent_name",
+      description: "The name of the agent to hand over the task to",
+      required: true,
+      usageValue: "Name of the target agent"
+    },
+    {
+      name: "task",
+      description: "The task to be completed by the target agent",
+      required: true,
+      usageValue: "Task description"
+    },
+    {
+      name: "context",
+      description: "The context information for the task",
+      required: true,
+      usageValue: "Context information"
+    },
+    {
+      name: "files",
+      description: "The files relevant to the task",
+      required: true,
+      usageValue: "Relevant files"
+    }
+  ],
+  examples: [
+    {
+      description: "Hand over a coding task to the coder agent",
+      parameters: [
+        {
+          name: "agent_name",
+          value: "Coder"
+        },
+        {
+          name: "task",
+          value: "Implement the login feature"
+        },
+        {
+          name: "context",
+          value: "We need a secure login system with email and password"
+        },
+        {
+          name: "files",
+          value: "src/auth/login.ts,src/auth/types.ts"
+        }
+      ]
+    }
+  ]
+};
+var handler10 = async (_provider, args) => {
+  const agentName = getString(args, "agent_name");
+  const task = getString(args, "task");
+  const context = getString(args, "context", undefined);
+  const files = getStringArray(args, "files", []);
+  return {
+    type: "HandOver" /* HandOver */,
+    agentName,
+    task,
+    context,
+    files
+  };
+};
+var isAvailable10 = (_provider) => {
+  return true;
+};
+var handOver_default = {
+  ...toolInfo10,
+  handler: handler10,
+  isAvailable: isAvailable10
+};
 // src/Agent/CoderAgent/prompts.ts
 var basePrompt = "You are a highly skilled software engineer with extensive knowledge in many programming languages, frameworks, design patterns, and best practices.";
 var editingFilesPrompt = (toolNamePrefix) => `
@@ -9110,17 +9325,6 @@ You have access to two tools for working with files: **${toolNamePrefix}write_to
 4. Once the file has been edited with either ${toolNamePrefix}write_to_file or ${toolNamePrefix}replace_in_file, the system will provide you with the final state of the modified file. Use this updated content as the reference point for any subsequent SEARCH/REPLACE operations, since it reflects any auto-formatting or user-applied changes.
 
 By thoughtfully selecting between ${toolNamePrefix}write_to_file and ${toolNamePrefix}replace_in_file, you can make your file editing process smoother, safer, and more efficient.`;
-var capabilities = (toolNamePrefix) => `
-====
-
-CAPABILITIES
-
-- You have access to a range of tools to aid you in your work. These tools help you effectively accomplish a wide range of tasks, such as writing code, making edits or improvements to existing files, understanding the current state of a project, performing system operations, and much more.
-- When the user initially gives you a task, a recursive list of all filepaths in the current working directory will be included in environment_details. This provides an overview of the project's file structure, offering key insights into the project from directory/file names (how developers conceptualize and organize their code) and file extensions (the language used). This can also guide decision-making on which files to explore further.
-- You can use ${toolNamePrefix}search_files to perform regex searches across files in a specified directory, outputting context-rich results that include surrounding lines. This is particularly useful for understanding code patterns, finding specific implementations, or identifying areas that need refactoring.
-- You can use the ${toolNamePrefix}list_code_definition_names tool to get an overview of source code definitions for all files at the top level of a specified directory. This can be particularly useful when you need to understand the broader context and relationships between certain parts of the code. You may need to call this tool multiple times to understand various parts of the codebase related to the task.
-\t- For example, when asked to make edits or improvements you might analyze the file structure in the initial environment_details to get an overview of the project, then use ${toolNamePrefix}list_code_definition_names to get further insight using source code definitions for files located in relevant directories, then ${toolNamePrefix}read_file to examine the contents of relevant files, analyze the code and suggest improvements or make necessary edits, then use the ${toolNamePrefix}replace_in_file tool to implement changes. If you refactored code that could affect other parts of the codebase, you could use ${toolNamePrefix}search_files to ensure you update other files as needed.
-- You can use the ${toolNamePrefix}execute_command tool to run commands on the user's computer whenever you feel it can help accomplish the user's task. When you need to execute a CLI command, you must provide a clear explanation of what the command does. Prefer to execute complex CLI commands over creating executable scripts, since they are more flexible and easier to run. Interactive and long-running commands are allowed, since the commands are run in the user's VSCode terminal. The user may keep commands running in the background and you will be kept updated on their status along the way. Each command you execute is run in a new terminal instance.`;
 var rules = (toolNamePrefix) => `
 ====
 
@@ -9135,7 +9339,9 @@ RULES
 - When creating a new project (such as an app, website, or any software project), organize all new files within a dedicated project directory unless the user specifies otherwise. Use appropriate file paths when creating files, as the ${toolNamePrefix}write_to_file tool will automatically create any necessary directories. Structure the project logically, adhering to best practices for the specific type of project being created. Unless otherwise specified, new projects should be easily run without additional setup, for example most projects can be built in HTML, CSS, and JavaScript - which you can open in a browser.
 - Be sure to consider the type of project (e.g. Python, JavaScript, web application) when determining the appropriate structure and files to include. Also consider what files may be most relevant to accomplishing the task, for example looking at a project's manifest file would help you understand the project's dependencies, which you could incorporate into any code you write.
 - When making changes to code, always consider the context in which the code is being used. Ensure that your changes are compatible with the existing codebase and that they follow the project's coding standards and best practices.
+- **Adhere to any established coding style, linting rules, or naming conventions if they are known or can be inferred from the existing codebase, to maintain consistency.**
 - When you want to modify a file, use the ${toolNamePrefix}replace_in_file or ${toolNamePrefix}write_to_file tool directly with the desired changes. You do not need to display the changes before using the tool.
+- **Do not guess or hallucinate file content that has not been explicitly provided or read. Always read an existing file with \`${toolNamePrefix}read_file\` (or rely on content the user directly provided) before modifying it, unless you are creating a brand-new file.**
 - Do not ask for more information than necessary. Use the tools provided to accomplish the user's request efficiently and effectively. When you've completed your task, you must use the ${toolNamePrefix}attempt_completion tool to present the result to the user.
 - The user may provide a file's contents directly in their message, in which case you shouldn't use the ${toolNamePrefix}read_file tool to get the file contents again since you already have it.
 - Your goal is to try to accomplish the user's task, NOT engage in a back and forth conversation.
@@ -9157,68 +9363,6 @@ You accomplish a given task iteratively, breaking it down into clear steps and w
 3. Remember, you have extensive capabilities with access to a wide range of tools that can be used in powerful and clever ways as necessary to accomplish each goal. Before calling a tool, do some analysis within <thinking></thinking> tags. First, analyze the file structure provided in environment_details to gain context and insights for proceeding effectively. Then, think about which of the provided tools is the most relevant tool to accomplish the user's task. Next, go through each of the required parameters of the relevant tool and determine if the user has directly provided or given enough information to infer a value. When deciding if the parameter can be inferred, carefully consider all the context to see if it supports a specific value. If all of the required parameters are present or can be reasonably inferred, close the thinking tag and proceed with the tool use.
 4. Once you've completed the user's task, you must use the ${toolNamePrefix}attempt_completion tool to present the result of the task to the user.
 5. The user may provide feedback, which you can use to make improvements and try again. But DO NOT continue in pointless back and forth conversations, i.e. don't end your responses with questions or offers for further assistance.`;
-var systemInformation = (info) => `
-====
-
-SYSTEM INFORMATION
-
-Operating System: ${info.os}`;
-var customInstructions = (customInstructions2) => {
-  const joined = customInstructions2.join(`
-`);
-  if (joined.trim() === "") {
-    return "";
-  }
-  return `
-====
-
-USER'S CUSTOM INSTRUCTIONS
-
-The following additional instructions are provided by the user, and should be followed to the best of your ability without interfering with the TOOL USE guidelines.
-
-${joined}`;
-};
-var customScripts = (commands) => {
-  const joined = Object.entries(commands).map(([name, command]) => {
-    if (typeof command === "string") {
-      return `- ${name}
-  - Command: \`${command}\``;
-    }
-    return `- ${name}
-  - Command: \`${command.command}\`
-  - Description: ${command.description}`;
-  }).join(`
-`);
-  if (joined.trim() === "") {
-    return "";
-  }
-  return `
-====
-
-USER'S CUSTOM COMMANDS
-
-The following additional commands are provided by the user, and should be followed to the best of your ability without interfering with the TOOL USE guidelines.
-
-${joined}`;
-};
-var interactiveMode = (interactive) => {
-  if (interactive) {
-    return `
-====
-
-INTERACTIVE MODE
-
-You are in interactive mode. This means you may ask user questions to gather additional information to complete the task.
-`;
-  }
-  return `
-====
-
-NON-INTERACTIVE MODE
-
-You are in non-interactive mode. This means you will not be able to ask user questions to gather additional information to complete the task. You should try to use available tools to accomplish the task. If unable to precede further, you may try to end the task and provide a reason.
-`;
-};
 var fullSystemPrompt = (info, tools, toolNamePrefix, instructions, scripts, interactive) => `
 ${basePrompt}
 ${toolUsePrompt(tools, toolNamePrefix)}
@@ -9241,13 +9385,161 @@ class CoderAgent extends AgentBase {
     const systemPrompt = fullSystemPrompt({
       os: options.os
     }, tools, toolNamePrefix, options.customInstructions ?? [], options.scripts ?? {}, options.interactive);
-    super(options.ai, {
+    super(coderAgentInfo.name, options.ai, {
+      systemPrompt,
+      tools,
+      toolNamePrefix,
+      provider: options.provider,
+      interactive: options.interactive,
+      agents: options.agents
+    });
+  }
+}
+var coderAgentInfo = {
+  name: "Coder",
+  responsibilities: [
+    "Editing and refactoring existing code.",
+    "Creating new features or modules.",
+    "Running tests and analyzing test results.",
+    "Maintaining coding standards, lint rules, and general code quality."
+  ]
+};
+// src/Agent/ArchitectAgent/prompts.ts
+var fullSystemPrompt2 = (info, tools, toolNamePrefix, instructions, scripts, interactive) => `
+# Architect Agent
+
+## Role
+You are the **Architect** agent, responsible for:
+1. **Task Analysis** – Understand requirements.
+2. **File Identification** – Find and select relevant files.
+3. **File Reading** – Use the provided tools to gather information from these files.
+4. **Implementation Plan** – Draft a concise plan detailing steps, resources, and dependencies.
+5. **Review & Improve** – Evaluate and refine the plan.
+6. **Handover** – Provide the final plan, context, and files to the **Coder** agent.
+
+> **Note**: The **Architect** agent must not make any direct modifications. Your role is limited to creating the implementation plan and handing it over to the **Coder** agent, who will perform any actual changes.
+
+## Rules
+1. **Consistency**: Maintain alignment with the user’s instructions and the system’s objectives at all times.
+2. **Relevance**: Only read and use files directly related to the task. Avoid unnecessary or tangential information.
+3. **Conciseness**: Keep all communications and plans succinct, avoiding superfluous or repetitive details.
+4. **Accuracy**: Ensure the information you gather and any conclusions you draw are correct and verifiable.
+5. **Clarity**: Present the final plan and any supporting details in a structured and easily understandable format.
+6. **Minimal Queries**: Ask clarifying questions only when essential, and avoid repeated questioning that does not add value.
+
+## Steps
+1. **Analyze Task**
+   - Gather and understand the user’s requirements.
+   - Note any potential constraints or objectives that may influence the plan.
+
+2. **Identify Relevant Files**
+   - Determine which files or documents are necessary.
+   - Justify why these files are relevant.
+
+3. **Read Files via Tools**
+   - Utilize the provided tools to access and extract information from the identified files.
+   - Summarize key insights or data for the solution.
+
+4. **Create Implementation Plan**
+   - Outline tasks, define milestones, and detail resources or dependencies.
+   - Provide clear, concise instructions for each step.
+
+5. **Review & Improve**
+   - Check the plan for consistency, clarity, and feasibility.
+   - Make adjustments or refinements to ensure accuracy and efficiency.
+
+6. **Handover**
+   - Deliver the final implementation plan, context, and relevant files to the **Coder** agent.
+   - Provide any additional instructions or clarifications needed for successful implementation.
+${toolUsePrompt(tools, toolNamePrefix)}
+${capabilities(toolNamePrefix)}
+${systemInformation(info)}
+${customInstructions(instructions)}
+${customScripts(scripts)}
+${interactiveMode(interactive)}
+`;
+
+// src/Agent/ArchitectAgent/index.ts
+class ArchitectAgent extends AgentBase {
+  constructor(options) {
+    const agentTools = [
+      ...options.additionalTools ?? [],
+      askFollowupQuestion_default,
+      attemptCompletion_default,
+      handOver_default,
+      listCodeDefinitionNames_default,
+      listFiles_default,
+      readFile_default,
+      searchFiles_default
+    ];
+    const tools = getAvailableTools(options.provider, agentTools);
+    const toolNamePrefix = "tool_";
+    const systemPrompt = fullSystemPrompt2({
+      os: options.os
+    }, tools, toolNamePrefix, options.customInstructions ?? [], options.scripts ?? {}, options.interactive);
+    super(architectAgentInfo.name, options.ai, {
       systemPrompt,
       tools,
       toolNamePrefix,
       provider: options.provider,
-      interactive: options.interactive
+      interactive: options.interactive,
+      agents: options.agents
+    });
+  }
+}
+var architectAgentInfo = {
+  name: "Architect",
+  responsibilities: [
+    "Analyzing the user’s overall task and requirements.",
+    "Creating plans and making higher-level decisions about system structure and design.",
+    "Reviewing and analyzing existing code or components for maintainability and scalability.",
+    "Laying out the roadmap for implementation."
+  ]
+};
+// src/Agent/MultiAgent.ts
+class MultiAgent {
+  #config;
+  #activeAgent = null;
+  constructor(config) {
+    this.#config = config;
+  }
+  get model() {
+    return this.#activeAgent?.model;
+  }
+  async#startTask(agentName, task, context, callback) {
+    this.#activeAgent = await this.#config.createAgent(agentName);
+    const [exitReason, info] = await this.#activeAgent.startTask({
+      task,
+      context,
+      callback
     });
+    if (typeof exitReason === "string") {
+      return [exitReason, info];
+    }
+    if (exitReason.type === "HandOver") {
+      const context2 = await this.#config.getContext(agentName, exitReason.context, exitReason.files);
+      const [exitReason2, info2] = await this.#startTask(exitReason.agentName, exitReason.task, context2, callback);
+      info2.inputTokens += info.inputTokens;
+      info2.outputTokens += info.outputTokens;
+      info2.cacheWriteTokens += info.cacheWriteTokens;
+      info2.cacheReadTokens += info.cacheReadTokens;
+      info2.totalCost = (info.totalCost ?? 0) + (info2.totalCost ?? 0);
+      return [exitReason2, info2];
+    }
+    return [exitReason, info];
+  }
+  async startTask(options) {
+    if (this.#activeAgent) {
+      throw new Error("An active agent already exists");
+    }
+    return this.#startTask(options.agentName, options.task, options.context, options.callback);
+  }
+  async continueTask(userMessage, taskInfo, callback = () => {
+  }) {
+    if (!this.#activeAgent) {
+      throw new Error("No active agent");
+    }
+    return this.#activeAgent.continueTask(userMessage, taskInfo, callback);
   }
 }
 // src/AiTool/generateGitCommitMessage.ts
@@ -9425,6 +9717,8 @@ export {
   makeTool,
   listFiles_default as listFiles,
   listCodeDefinitionNames_default as listCodeDefinitionNames,
+  handOver_default as handOver,
+  getAvailableTools,
   generateGithubPullRequestDetails,
   generateGitCommitMessage,
   executeTool,
@@ -9433,14 +9727,19 @@ export {
   deepSeekModels,
   deepSeekDefaultModelId,
   createService,
+  coderAgentInfo,
   attemptCompletion_default as attemptCompletion,
   askFollowupQuestion_default as askFollowupQuestion,
+  architectAgentInfo,
   anthropicModels,
   anthropicDefaultModelId,
   exports_allTools as allTools,
+  ToolResponseType,
+  TaskEventKind,
+  MultiAgent,
   MockProvider,
-  ExitReason,
   CoderAgent,
+  ArchitectAgent,
   AiServiceProvider,
   AgentBase
 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@polka-codes/core",
-  "version": "0.4.3",
+  "version": "0.4.4",
   "license": "AGPL-3.0",
   "type": "module",
   "exports": {