@amical/aiagent-sdk 0.1.0 → 0.1.2

package/src/prompt/WebPromptManager.ts

@@ -1,277 +0,0 @@
-import { IPromptManager } from "./index";
-import { defaultTools } from "@/shared/tools";
-
-export class WebPromptManager implements IPromptManager {
-
-
-  async getSystemPrompt(context: { cwd: string; os: string; shell: string; skills: any; customInstructions?: string; allowDefaultTools?: string[]; customTools?: any[]; }): Promise<string> {
-    let prompt = `# Role
-you are a highly skilled software engineer AI running in a Node.js/Desktop environment.
-You have FULL access to the local file system and can execute arbitrary shell commands on the user's machine.
-
-# Capabilities & Rules
-1. **File System**: You can read, write, create, and delete files/directories anywhere accessible to the user process. Always use absolute paths or paths relative to the Current Working Directory.
-2. **Terminal**: You can execute system commands (e.g., git, npm, python, file manipulation) directly.
-3. **Context**: You are running on a real machine, meaning you have access to real environment variables, local servers (localhost), and local network.
-4. **Destructive Actions**: Be extremely careful when executing commands that modify system state or delete files. Double-check paths and commands before execution.
-5. **Step-by-step**: Use tools one at a time. Do not assume the outcome of any tool use. Each step must be informed by the previous step's result.
-6. **Verification**: Always verify the result of your actions (e.g., run tests, compile code, list directories) before proceeding to the next step or completing the task.
-7. **Communication**: Be concise and technical. Formulate your output strictly according to the tools' XML specification.
-
-TOOL USE
-
-You have access to a set of tools that are executed upon the user's approval. You can use one tool per message, and will receive the result of that tool use in the user's response. You use tools step-by-step to accomplish a given task, with each tool use informed by the result of the previous tool use.
-
-# Tool Use Formatting
-
-Tool use is formatted using XML-style tags. The tool name is enclosed in opening and closing tags, and each parameter is similarly enclosed within its own set of tags. Here's the structure:
-
-<tool_name>
-<parameter1_name>value1</parameter1_name>
-<parameter2_name>value2</parameter2_name>
-...
-</tool_name>
-
-For example:
-
-<agent_read_file>
-<path>src/main.js</path>
-<task_progress>
-Checklist here (optional)
-</task_progress>
-</agent_read_file>
-
-Always adhere to this format for the tool use to ensure proper parsing and execution.
-`;
-
-    const skillsPrompt = await this.getSkillsPrompt(context.skills);
-    if (skillsPrompt) {
-      prompt += `\n${skillsPrompt}\n`;
-    }
-
-    prompt += `\n${this.getToolInstructions(context)}\n`;
-
-    const envPrompt = this.getEnvironmentInfoPrompt(context);
-    if (envPrompt) {
-      prompt += `\n${envPrompt}\n`;
-    }
-
-    if (context.customInstructions) {
-      prompt += `\n# User Custom Instructions\n${context.customInstructions}\n`;
-    }
-
-    return prompt;
-  }
-
-  getEnvironmentInfoPrompt(context: { cwd: string; os: string; shell: string }): string {
-    let environmentPrompt = `<environment_details>
-  # Environment Info
-- **Current Working Directory**: \`${context.cwd}\`
-- **Operating System**: \`${context.os}\`\n`;
-    if (context.shell) {
-      environmentPrompt += `- **Current Shell**: \`${context.shell}\`\n`;
-    }
-    return environmentPrompt + `\n</environment_details>`;
-  }
-
-  async getSkillsPrompt(skills: any[]): Promise<string> {
-    if (!skills || skills.length === 0) return "";
-
-    try {
-      let prompt = `# Available Skills\n`;
-      prompt += `You have access to the following skills. You can use the \`agent_load_skill\` tool to load any of them when needed.\n`;
-      for (const skill of skills) {
-        if (skill && skill.name && skill.description) {
-          prompt += `- **${skill.name}**: ${skill.description}\n`;
-        }
-      }
-      return prompt;
-    } catch (e) {
-      // Directory might not exist or not accessible
-      return "";
-    }
-  }
-
-  getToolInstructions(context: { cwd: string; os: string; allowDefaultTools?: string[]; customTools?: any[] }): string {
-    const allowDefaultTools = context.allowDefaultTools;
-    const customTools = context.customTools || [];
-    // 可用
-    let useDefaultTools = [...defaultTools] as any[];
-    if (allowDefaultTools) {
-      useDefaultTools = defaultTools.filter((tool: any) => allowDefaultTools.includes(tool.name));
-    }
-    return `# Available Tools
-You can use the following tools by formatting your output as XML blocks. Only use ONE tool per message, and ALWAYS wait for the user's response with the execution result before proceeding.
-
-${[...useDefaultTools, ...customTools].map((tool: any) => {
-  return `### ${tool.name}
-Description: ${tool.description}
-Parameters: 
-${Object.entries(tool.params  as Record<string, string>).map(([name, description]) => `- ${name}: ${description.replaceAll('${context.cwd}', context.cwd)}`).join('\n')}
-- task_progress: (optional) A checklist showing task progress after this tool use is completed. The task_progress parameter must be included as a separate parameter inside of the parent tool call, it must be separate from other parameters such as content, arguments, etc. (See 'UPDATING TASK PROGRESS' section for more details)
-Usage: 
-<${tool.name}>
-${Object.entries(tool.params  as Record<string, string>).map(([name, description]) => `<${name}>${description.replaceAll('${context.cwd}', context.cwd)}</${name}>`).join('\n')}
-<task_progress>Checklist here (optional)</task_progress>
-</${tool.name}>
-`;
-}).join('\n')}
-
-# Tool Use Examples
-${useDefaultTools.filter(item => Boolean(item.example)).map((item: any) => item.example).join('\n')}}
-
-# Tool Use Guidelines
-
-1. In <thinking> tags, assess what information you already have and what information you need to proceed with the task.
-2. Choose the most appropriate tool based on the task and the tool descriptions provided. Assess if you need additional information to proceed, and which of the available tools would be most effective for gathering this information. For example using the list_files tool is more effective than running a command like \`ls\` in the terminal. It's critical that you think about each available tool and use the one that best fits the current step in the task.
-3. If multiple actions are needed, use one tool at a time per message to accomplish the task iteratively, with each tool use being informed by the result of the previous tool use. Do not assume the outcome of any tool use. Each step must be informed by the previous step's result.
-4. Formulate your tool use using the XML format specified for each tool.
-5. After each tool use, the user will respond with the result of that tool use. This result will provide you with the necessary information to continue your task or make further decisions. This response may include:
-  - Information about whether the tool succeeded or failed, along with any reasons for failure.
-  - Linter errors that may have arisen due to the changes you made, which you'll need to address.
-  - New terminal output in reaction to the changes, which you may need to consider or act upon.
-  - Any other relevant feedback or information related to the tool use.
-6. ALWAYS wait for user confirmation after each tool use before proceeding. Never assume the success of a tool use without explicit confirmation of the result from the user.
-
-It is crucial to proceed step-by-step, waiting for the user's message after each tool use before moving forward with the task. This approach allows you to:
-1. Confirm the success of each step before proceeding.
-2. Address any issues or errors that arise immediately.
-3. Adapt your approach based on new information or unexpected results.
-4. Ensure that each action builds correctly on the previous ones.
-
-By waiting for and carefully considering the user's response after each tool use, you can react accordingly and make informed decisions about how to proceed with the task. This iterative process helps ensure the overall success and accuracy of your work.
-
-====
-
-UPDATING TASK PROGRESS
-
-You can track and communicate your progress on the overall task using the task_progress parameter supported by every tool call. Using task_progress ensures you remain on task, and stay focused on completing the user's objective. This parameter can be used in any mode, and with any tool call.
-
-- When switching from PLAN MODE to ACT MODE, you must create a comprehensive todo list for the task using the task_progress parameter
-- Todo list updates should be done silently using the task_progress parameter - do not announce these updates to the user
-- Use standard Markdown checklist format: "- [ ]" for incomplete items and "- [x]" for completed items
-- Keep items focused on meaningful progress milestones rather than minor technical details. The checklist should not be so granular that minor implementation details clutter the progress tracking.
-- For simple tasks, short checklists with even a single item are acceptable. For complex tasks, avoid making the checklist too long or verbose.
-- If you are creating this checklist for the first time, and the tool use completes the first step in the checklist, make sure to mark it as completed in your task_progress parameter.
-- Provide the whole checklist of steps you intend to complete in the task, and keep the checkboxes updated as you make progress. It's okay to rewrite this checklist as needed if it becomes invalid due to scope changes or new information.
-- If a checklist is being used, be sure to update it any time a step has been completed.
-- The system will automatically include todo list context in your prompts when appropriate - these reminders are important.
-
-Example:
-<agent_execute_command>
-<command>npm install react</command>
-<requires_approval>false</requires_approval>
-<task_progress>
-- [x] Set up project structure
-- [x] Install dependencies
-- [ ] Create components
-- [ ] Test application
-</task_progress>
-</agent_execute_command>
-
-====
-
-EDITING FILES
-
-You have access to two tools for working with files: **agent_write_to_file** and **agent_replace_in_file**. Understanding their roles and selecting the right one for the job will help ensure efficient and accurate modifications.
-
-# agent_write_to_file
-
-## Purpose
-
-- Create a new file, or overwrite the entire contents of an existing file.
-
-## When to Use
-
-- Initial file creation, such as when scaffolding a new project.  
-- Overwriting large boilerplate files where you want to replace the entire content at once.
-- When the complexity or number of changes would make agent_replace_in_file unwieldy or error-prone.
-- When you need to completely restructure a file's content or change its fundamental organization.
-
-## Important Considerations
-
-- Using agent_write_to_file requires providing the file's complete final content.  
-- If you only need to make small changes to an existing file, consider using agent_replace_in_file instead to avoid unnecessarily rewriting the entire file.
-- While agent_write_to_file should not be your default choice, don't hesitate to use it when the situation truly calls for it.
-
-# agent_replace_in_file
-
-## Purpose
-
-- Make targeted edits to specific parts of an existing file without overwriting the entire file.
-
-## When to Use
-
-- Small, localized changes like updating a few lines, function implementations, changing variable names, modifying a section of text, etc.
-- Targeted improvements where only specific portions of the file's content needs to be altered.
-- Especially useful for long files where much of the file will remain unchanged.
-
-## Advantages
-
-- More efficient for minor edits, since you don't need to supply the entire file content.  
-- Reduces the chance of errors that can occur when overwriting large files.
-
-# Choosing the Appropriate Tool
-
-- **Default to agent_replace_in_file** for most changes. It's the safer, more precise option that minimizes potential issues.
-- **Use agent_write_to_file** when:
-  - Creating new files
-  - The changes are so extensive that using agent_replace_in_file would be more complex or risky
-  - You need to completely reorganize or restructure a file
-  - The file is relatively small and the changes affect most of its content
-  - You're generating boilerplate or template files
-
-# Auto-formatting Considerations
-
-- After using either agent_write_to_file or agent_replace_in_file, the user's editor may automatically format the file
-- This auto-formatting may modify the file contents, for example:
-  - Breaking single lines into multiple lines
-  - Adjusting indentation to match project style (e.g. 2 spaces vs 4 spaces vs tabs)
-  - Converting single quotes to double quotes (or vice versa based on project preferences)
-  - Organizing imports (e.g. sorting, grouping by type)
-  - Adding/removing trailing commas in objects and arrays
-  - Enforcing consistent brace style (e.g. same-line vs new-line)
-  - Standardizing semicolon usage (adding or removing based on style)
-- The agent_write_to_file and agent_replace_in_file tool responses will include the final state of the file after any auto-formatting
-- Use this final state as your reference point for any subsequent edits. This is ESPECIALLY important when crafting SEARCH blocks for replace_in_file which require the content to match what's in the file exactly.
-
-# Workflow Tips
-
-1. Before editing, assess the scope of your changes and decide which tool to use.
-2. For targeted edits, apply agent_replace_in_file with carefully crafted SEARCH/REPLACE blocks. If you need multiple changes, you can stack multiple SEARCH/REPLACE blocks within a single agent_replace_in_file call.
-3. IMPORTANT: When you determine that you need to make several changes to the same file, prefer to use a single replace_in_file call with multiple SEARCH/REPLACE blocks. DO NOT prefer to make multiple successive replace_in_file calls for the same file. For example, if you were to add a component to a file, you would use a single replace_in_file call with a SEARCH/REPLACE block to add the import statement and another SEARCH/REPLACE block to add the component usage, rather than making one replace_in_file call for the import statement and then another separate replace_in_file call for the component usage.
-4. For major overhauls or initial file creation, rely on agent_write_to_file.
-5. Once the file has been edited with either agent_write_to_file or agent_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 agent_write_to_file and agent_replace_in_file, you can make your file editing process smoother, safer, and more efficient.
-
-====
-`;
-  }
-
-  getNoUseToolInstructions(context: any): string {
-    return `[ERROR] You did not use a tool in your previous response! Please retry with a tool use.
-
-# Reminder: Instructions for Tool Use
-Tool uses are formatted using XML-style tags. The tool name is enclosed in opening and closing tags, and each parameter is similarly enclosed within its own set of tags. Here's the structure:
-<tool_name>
-<parameter1_name>value1</parameter1_name>
-<parameter2_name>value2</parameter2_name>
-...
-</tool_name>
-For example:
-<agent_attempt_completion>
-<result>
-I have completed the task...
-</result>
-</agent_attempt_completion>
-Always adhere to this format for all tool uses to ensure proper parsing and execution.
-
-# Next Steps
-
-If you have completed the user's task, use the attempt_completion tool. 
-If you require additional information from the user, use the ask_followup_question tool. 
-Otherwise, if you have not completed the task and do not need additional information, then proceed with the next step of the task. 
-(This is an automated message, so do not respond to it conversationally.)
-${this?.getEnvironmentInfoPrompt?.(context)}`;
-  }
-}

package/src/prompt/index.ts

@@ -1,28 +0,0 @@
-/**
- * 抽象的 System Prompt 管理器。
- * 替代原始项目中复杂的 templates/variants，交由宿主自行提供或使用默认简单实现。
- */
-export interface IPromptManager {
-  /**
-   * 根据当前运行环境与动态参数，获取最终的系统提示词
-   */
-  getSystemPrompt(context: any): Promise<string>;
-
-  /**
-   * 获取特定工具或技能的指令文本
-   */
-  getToolInstructions?(context: any): string;
-
-  /**
-   * 获取环境信息提示词
-   */
-  getEnvironmentInfoPrompt?(context: any): string;
-
-  /**
-   * 获取未使用工具的错误提示词
-   */
-  getNoUseToolInstructions(context: any): string;
-}
-
-export * from './NodePromptManager';
-export * from './WebPromptManager';;

package/src/runtime/nodeRuntime.ts

@@ -1,112 +0,0 @@
-import { IAgentRuntime } from "../runtime";
-import { ClineAgent } from "../agent";
-import { NodeApiHandler, NodeApiHandlerConfig } from "../llm/NodeApiHandler";
-import { NodePromptManager } from "../prompt/NodePromptManager";
-import { NodeMemoryManager } from "../memory/NodeMemoryManager";
-import { AgentDefaultTool } from "../shared/tools";
-import * as fs from "fs/promises";
-import * as os from "os";
-import * as path from "path";
-import { exec } from "child_process";
-import { promisify } from "util";
-import { WebMemoryManager } from "../memory/WebMemoryManager";
-
-const execAsync = promisify(exec);
-
-/**
- * 默认的 Node.js 运行时实现
- */
-export class DefaultNodeRuntime implements IAgentRuntime {
-  fs = {
-    readFile: async (filepath: string) => fs.readFile(filepath, "utf-8"),
-    writeFile: async (filepath: string, content: string) => {
-      await fs.mkdir(path.dirname(filepath), { recursive: true });
-      await fs.writeFile(filepath, content, "utf-8");
-    },
-    deleteFile: (filepath: string) => fs.unlink(filepath),
-    deleteDirectory: (dirpath: string) => fs.rm(dirpath, { recursive: true, force: true }),
-    fileExists: async (filepath: string) => {
-      try {
-        await fs.access(filepath);
-        return true;
-      } catch {
-        return false;
-      }
-    },
-    readDir: (dirpath: string) => fs.readdir(dirpath, { withFileTypes: true }),
-    mkdir: async (dirpath: string) => {
-      await fs.mkdir(dirpath, { recursive: true });
-    }
-  };
-
-  path = {
-    join: (...paths: string[]) => path.join(...paths),
-  };
-
-  env = {
-    get: (key: string) => process.env[key],
-    cwd: () => process.cwd(),
-    osInfo: () => `${os.type()} ${os.release()} ${os.arch()}`,
-    shell: () => process.env.SHELL || process.env.ComSpec || "unknown"
-  };
-
-  terminal = {
-    execCommand: async (command: string, options?: { cwd?: string }) => {
-      try {
-        const { stdout, stderr } = await execAsync(command, { cwd: options?.cwd || process.cwd() });
-        return { stdout, stderr, exitCode: 0 };
-      } catch (err: any) {
-        return { stdout: err.stdout || "", stderr: err.stderr || err.message, exitCode: err.code || 1 };
-      }
-    }
-  };
-}
-
-export interface NodeAgentOptions {
-  apiConfig: NodeApiHandlerConfig;
-  dbPath?: string;
-  customInstructions?: string;
-  customTools?: any[];
-  allowDefaultTools?: string[];
-  memory?: NodeMemoryManager | WebMemoryManager;
-  maxLoopCount?: number;
-}
-
-/**
- * 快速创建 Node 端 Agent 的工厂方法
- */
-export function createNodeAgent(options: NodeAgentOptions): ClineAgent {
-  const runtime = new DefaultNodeRuntime();
-  const api = new NodeApiHandler(options.apiConfig);
-  const memory = options.memory || new NodeMemoryManager(options.dbPath || path.join(runtime.env.cwd(), ".cline_memory.json"));
-  const customTools = options.customTools || [];
-  const customToolNames = new Set<string>(customTools.map((t: any) => t.name));
-
-  const promptManager = new NodePromptManager();
-
-  const agent = new ClineAgent({
-    runtime,
-    api,
-    promptManager,
-    memory,
-    customTools,
-    allowDefaultTools: options.allowDefaultTools,
-    maxLoopCount: options.maxLoopCount,
-    customInstructions: options.customInstructions,
-  });
-
-  agent.onToolCall = async (tool) => {
-    if (customToolNames.has(tool.name)) {
-      const customTool = customTools.find((t: any) => t.name === tool.name);
-      if (customTool.onCall) {
-        return customTool.onCall(tool.params);
-      }
-      return `Error: Custom tool "${tool.name}" does not have an onCall method.`;
-    }
-  };
-
-  return agent;
-}
-
-export * from "../index";
-export * from "../mcp/NodeMcpManager";

package/src/runtime/web.test.ts

@@ -1,95 +0,0 @@
-import { describe, it, expect, beforeEach } from "vitest";
-import { DefaultWebRuntime } from "./webRuntime";
-
-describe("DefaultWebRuntime (memfs VFS)", () => {
-  let runtime: DefaultWebRuntime;
-
-  beforeEach(() => {
-    runtime = new DefaultWebRuntime();
-  });
-
-  describe("File System Operations", () => {
-    it("should write and read a file successfully", async () => {
-      const filepath = "/workspace/test.txt";
-      const content = "Hello, Web Agent!";
-
-      await runtime.fs.writeFile(filepath, content);
-      
-      const result = await runtime.fs.readFile(filepath);
-      expect(result).toBe(content);
-    });
-
-    it("should auto-create nested directories when writing a file", async () => {
-      const filepath = "/workspace/deep/nested/dir/test.txt";
-      const content = "Deep content";
-
-      await runtime.fs.writeFile(filepath, content);
-      
-      const result = await runtime.fs.readFile(filepath);
-      expect(result).toBe(content);
-    });
-
-    it("should return true for fileExists if file exists", async () => {
-      const filepath = "/workspace/exists.txt";
-      
-      expect(await runtime.fs.fileExists(filepath)).toBe(false);
-      
-      await runtime.fs.writeFile(filepath, "data");
-      
-      expect(await runtime.fs.fileExists(filepath)).toBe(true);
-    });
-
-    it("should throw an error when reading a non-existent file", async () => {
-      await expect(runtime.fs.readFile("/workspace/missing.txt")).rejects.toThrow();
-    });
-
-    it("should list files and directories correctly", async () => {
-      await runtime.fs.writeFile("/workspace/file1.txt", "1");
-      await runtime.fs.writeFile("/workspace/file2.txt", "2");
-      await runtime.fs.mkdir("/workspace/subdir");
-      await runtime.fs.writeFile("/workspace/subdir/file3.txt", "3");
-
-      const list = await runtime.fs.readDir("/workspace");
-      
-      expect(list).toContain("file1.txt");
-      expect(list).toContain("file2.txt");
-      expect(list).toContain("subdir");
-      expect(list.length).toBe(3);
-    });
-
-    it("should explicitly create directories via mkdir", async () => {
-      const dirpath = "/workspace/explicit_dir";
-      await runtime.fs.mkdir(dirpath);
-      
-      // we can test it exists by listing the parent
-      const list = await runtime.fs.readDir("/workspace");
-      expect(list).toContain("explicit_dir");
-    });
-  });
-
-  describe("Environment Operations", () => {
-    it("should return undefined for get()", () => {
-      expect(runtime.env.get("ANY_KEY")).toBeUndefined();
-    });
-
-    it("should return /workspace for cwd()", () => {
-      expect(runtime.env.cwd()).toBe("/workspace");
-    });
-
-    it("should return Web Browser or user agent for osInfo()", () => {
-      expect(runtime.env.osInfo()).toBeTruthy();
-      expect(typeof runtime.env.osInfo()).toBe("string");
-    });
-  });
-
-  describe("Terminal Operations", () => {
-    it("should mock terminal command execution", async () => {
-      const result = await runtime.terminal.execCommand("echo hello");
-      
-      expect(result.exitCode).toBe(0);
-      expect(result.stderr).toBe("");
-      expect(result.stdout).toContain("[Mock]");
-      expect(result.stdout).toContain("echo hello");
-    });
-  });
-});

package/src/runtime/webRuntime.ts

@@ -1,119 +0,0 @@
-import { IAgentRuntime } from "../runtime";
-import { ClineAgent } from "../agent";
-import { WebApiHandler, WebApiHandlerConfig } from "../llm/WebApiHandler";
-import { WebPromptManager } from "../prompt/WebPromptManager";
-import { WebMemoryManager } from "../memory/WebMemoryManager";
-import { AgentDefaultTool } from "../shared/tools";
-import { Volume, createFsFromVolume } from "memfs";
-import path from "path-browserify";
-
-/**
- * 默认的 Web 运行时实现
- * 提供了基于 memfs 的虚拟文件系统和模拟终端。
- * 宿主环境如果使用了 WebContainer 或 OPFS，应覆盖此实现。
- */
-export class DefaultWebRuntime implements IAgentRuntime {
-  private vol = new Volume();
-  private memfs = createFsFromVolume(this.vol).promises;
-
-  fs = {
-    readFile: async (filepath: string) => {
-      const content = await this.memfs.readFile(filepath, "utf-8");
-      return content.toString();
-    },
-    writeFile: async (filepath: string, content: string) => {
-      const dir = filepath.substring(0, filepath.lastIndexOf("/"));
-      if (dir && dir !== filepath) {
-        await this.memfs.mkdir(dir, { recursive: true });
-      }
-      await this.memfs.writeFile(filepath, content);
-    },
-    deleteFile: (filepath: string) => this.memfs.unlink(filepath),
-    deleteDirectory: (dirpath: string) => this.memfs.rm(dirpath, { recursive: true, force: true }),
-    fileExists: async (filepath: string) => {
-      try {
-        await this.memfs.access(filepath);
-        return true;
-      } catch {
-        return false;
-      }
-    },
-    readDir: (dirpath: string) => {
-      return this.memfs.readdir(dirpath, { withFileTypes: true }) as any;
-    },
-    mkdir: async (dirpath: string) => {
-      await this.memfs.mkdir(dirpath, { recursive: true });
-    },
-  };
-
-  path = {
-    join: (...paths: string[]) => path.join(...paths),
-  }
-
-  env = {
-    get: (key: string) => undefined, // 浏览器环境中无系统环境变量
-    cwd: () => "/workspace",
-    osInfo: () => typeof navigator !== "undefined" ? navigator.userAgent : "Web Browser",
-    shell: () => '', // 浏览器环境中无真实 shell
-  };
-
-  terminal = {
-    execCommand: async (command: string, options?: { cwd?: string }) => {
-      // 在纯浏览器环境中，终端被 Mock
-      return {
-        stdout: `[Mock] Command '${command}' executed in browser sandbox.`,
-        stderr: "",
-        exitCode: 0,
-      };
-    }
-  };
-}
-
-export interface WebAgentOptions {
-  apiConfig: WebApiHandlerConfig;
-    dbPath?: string;
-    customInstructions?: string;
-    customTools?: any[];
-    allowDefaultTools?: string[];
-    memory?: WebMemoryManager;
-    maxLoopCount?: number;
-    storageKey?: string;
-}
-
-/**
- * 快速创建 Web 端 Agent 的工厂方法
- */
-export function createWebAgent(options: WebAgentOptions): ClineAgent {
-  const runtime = new DefaultWebRuntime();
-  const api = new WebApiHandler(options.apiConfig);
-  const promptManager = new WebPromptManager();
-  const memory = new WebMemoryManager(options.storageKey || "cline_agent_memory");
-  const customTools = options.customTools || [];
-  const customToolNames = new Set<string>(customTools.map((t: any) => t.name));
-
-  const agent = new ClineAgent({
-    runtime,
-    api,
-    promptManager,
-    memory,
-    customTools,
-    allowDefaultTools: options.allowDefaultTools,
-    maxLoopCount: options.maxLoopCount,
-    customInstructions: options.customInstructions,
-  });
-
-  agent.onToolCall = async (tool) => {
-    if (customToolNames.has(tool.name)) {
-      const customTool = customTools.find((t: any) => t.name === tool.name);
-      if (customTool.onCall) {
-        return customTool.onCall(tool.params);
-      }
-      return `Error: Custom tool "${tool.name}" does not have an onCall method.`;
-    }
-  };
-
-  return agent;
-}
-
-export * from "../index";
-export * from "../mcp/WebMcpManager";

package/src/runtime.ts

@@ -1,46 +0,0 @@
-/**
- * IAgentRuntime 抽象了所有与特定宿主环境（Node.js, Web, VS Code 等）相关的能力。
- * 通过注入 IAgentRuntime，Agent 的核心逻辑可以运行在任何平台上。
- */
-export interface IAgentRuntime {
-  /**
-   * 文件系统相关操作
-   */
-  fs: {
-    readFile(path: string): Promise<string>;
-    writeFile(path: string, content: string): Promise<void>;
-    deleteFile(path: string): Promise<void>;
-    deleteDirectory(path: string): Promise<void>;
-    fileExists(path: string): Promise<boolean>;
-    readDir(path: string): Promise<any[]>;
-    mkdir(path: string): Promise<void>;
-    /**
-     * 跨文件正则搜索
-     * @param path 搜索目录
-     * @param regex 正则表达式字符串
-     * @param filePattern (可选) 文件名匹配模式，比如 '*.ts'
-     * @returns 返回格式化后的包含上下文的搜索结果字符串
-     */
-    searchFiles?(path: string, regex: string, filePattern?: string): Promise<string>;
-  };
-  path: {
-    join(...paths: string[]): string;
-  };
-
-  /**
-   * 环境变量和系统信息
-   */
-  env: {
-    get(key: string): string | undefined;
-    cwd(): string;
-    osInfo(): string; // 比如返回类似 'Windows 10' 或 'Web Browser' 的标识
-    shell(): string; // 返回当前 shell 的类型，比如 'bash', 'zsh', 'cmd', 'powershell'，Web 环境下返回空字符串
-  };
-
-  /**
-   * 终端/命令行相关操作
-   */
-  terminal: {
-    execCommand(command: string, options?: { cwd?: string }): Promise<{ stdout: string; stderr: string; exitCode: number }>;
-  };
-}