@polka-codes/core 0.1.6 → 0.1.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@polka-codes/core",
-  "version": "0.1.6",
+  "version": "0.1.8",
   "license": "AGPL-3.0",
   "type": "module",
   "exports": {
@@ -10,6 +10,9 @@
     }
   },
   "files": ["dist"],
+  "scripts": {
+    "build": "bun build src/index.ts --outdir dist"
+  },
   "dependencies": {
     "@anthropic-ai/sdk": "^0.33.1",
     "openai": "^4.77.4",

package/dist/Agent/AgentBase.d.ts

@@ -1,49 +0,0 @@
-import type Anthropic from "@anthropic-ai/sdk";
-import type { AiServiceBase, MessageParam } from "../AiService/index.js";
-import type { Logger } from "../logger.js";
-import { type ToolHandler, type ToolInfo } from "../tools/index.js";
-export type TaskEvent = {
-    kind: string;
-    info: TaskInfo;
-    newText?: string;
-    tool?: string;
-    userContent?: UserContent;
-};
-type UserContent = Array<Anthropic.TextBlockParam | Anthropic.ImageBlockParam | Anthropic.ToolUseBlockParam | Anthropic.ToolResultBlockParam>;
-export type TaskEventCallback = (event: TaskEvent) => void | Promise<void>;
-export type TaskInfo = {
-    options: {
-        maxIterations: number;
-    };
-    messages: MessageParam[];
-    inputTokens: number;
-    outputTokens: number;
-    cacheWriteTokens: number;
-    cacheReadTokens: number;
-    totalCost: number | undefined;
-};
-export type AgentBaseConfig = {
-    systemPrompt: string;
-    tools: ToolInfo[];
-    toolNamePrefix: string;
-    toolHandler: ToolHandler;
-    customInstructions?: string[];
-};
-export declare abstract class AgentBase {
-    #private;
-    protected readonly ai: AiServiceBase;
-    protected readonly config: Readonly<AgentBaseConfig>;
-    protected readonly logger: Logger;
-    constructor(ai: AiServiceBase, config: AgentBaseConfig, logger: Logger);
-    startTask({ task, context, maxIterations, callback, }: {
-        task: string;
-        context?: string;
-        maxIterations: number;
-        callback: TaskEventCallback;
-    }): Promise<TaskInfo>;
-    get model(): {
-        id: string;
-        info: import("../AiService/index.js").ModelInfo;
-    };
-}
-export {};

package/dist/Agent/AgentBase.js

@@ -1,158 +0,0 @@
-import { ToolResponseType } from "../tools/index.js";
-import { parseAssistantMessage } from "./parseAssistantMessage.js";
-import { responsePrompts } from "./prompts.js";
-export class AgentBase {
-    ai;
-    config;
-    logger;
-    constructor(ai, config, logger) {
-        this.ai = ai;
-        this.config = config;
-        this.logger = logger;
-    }
-    async startTask({ task, context, maxIterations = 50, callback = () => { }, }) {
-        const taskInfo = {
-            options: {
-                maxIterations,
-            },
-            messages: [],
-            inputTokens: 0,
-            outputTokens: 0,
-            cacheWriteTokens: 0,
-            cacheReadTokens: 0,
-            totalCost: 0,
-        };
-        let text = `<task>${task}</task>`;
-        if (context) {
-            text += `\n<context>${context}</context>`;
-        }
-        let nextRequest = [
-            {
-                type: "text",
-                text,
-            },
-        ];
-        let iterations = 0;
-        while (nextRequest) {
-            if (iterations >= taskInfo.options.maxIterations) {
-                callback({ kind: "max_iterations_reached", info: taskInfo });
-                break;
-            }
-            const response = await this.#request(taskInfo, nextRequest, callback);
-            nextRequest = await this.#handleResponse(taskInfo, response, callback);
-            ++iterations;
-        }
-        callback({ kind: "end_task", info: taskInfo });
-        return taskInfo;
-    }
-    async #request(info, userContent, callback) {
-        await callback({ kind: "start_request", info, userContent });
-        info.messages.push({
-            role: "user",
-            content: userContent,
-        });
-        this.logger.trace(info.messages, "Sending messages to AI");
-        // TODO: use a truncated messages if needed to avoid exceeding the token limit
-        const stream = this.ai.send(this.config.systemPrompt, info.messages);
-        let currentAssistantMessage = "";
-        for await (const chunk of stream) {
-            switch (chunk.type) {
-                case "usage":
-                    info.inputTokens = chunk.inputTokens;
-                    info.outputTokens = chunk.outputTokens;
-                    info.cacheWriteTokens = chunk.cacheWriteTokens ?? 0;
-                    info.cacheReadTokens = chunk.cacheReadTokens ?? 0;
-                    info.totalCost = chunk.totalCost;
-                    await callback({ kind: "usage", info });
-                    break;
-                case "text":
-                    currentAssistantMessage += chunk.text;
-                    await callback({ kind: "text", info, newText: chunk.text });
-                    break;
-            }
-        }
-        // TODO: error handling
-        if (!currentAssistantMessage) {
-            throw new Error("No assistant message received");
-        }
-        info.messages.push({
-            role: "assistant",
-            content: currentAssistantMessage,
-        });
-        const ret = parseAssistantMessage(currentAssistantMessage, this.config.tools, this.config.toolNamePrefix);
-        await callback({ kind: "end_request", info });
-        return ret;
-    }
-    async #handleResponse(info, response, callback) {
-        const toolReponses = [];
-        for (const content of response) {
-            switch (content.type) {
-                case "text":
-                    // no need to handle text content
-                    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 ToolResponseType.Reply:
-                            // reply to the tool use
-                            await callback({ kind: "tool_reply", info, tool: content.name });
-                            toolReponses.push({ tool: content.name, response: toolResp.message });
-                            break;
-                        case ToolResponseType.Exit:
-                            // task completed
-                            return undefined;
-                        case ToolResponseType.Invalid:
-                            // tell AI about the invalid arguments
-                            await callback({ kind: "tool_invalid", info, tool: content.name });
-                            toolReponses.push({ tool: content.name, response: toolResp.message });
-                            break;
-                        case ToolResponseType.Error:
-                            // tell AI about the error
-                            await callback({ kind: "tool_error", info, tool: content.name });
-                            toolReponses.push({ tool: content.name, response: toolResp.message });
-                            break;
-                        case ToolResponseType.Interrupted:
-                            // the execution is killed
-                            await callback({ kind: "tool_interrupted", info, tool: content.name });
-                            return undefined;
-                    }
-                    break;
-                }
-            }
-        }
-        if (toolReponses.length === 0) {
-            // TODO: in interactive mode, we just wait for user to provide the next input
-            // we need to convert the loop to a state machine
-            return [
-                {
-                    type: "text",
-                    text: responsePrompts.requireUseTool,
-                },
-            ];
-        }
-        const finalResp = toolReponses.map(({ tool, response }) => responsePrompts.toolResults(tool, response)).join("\n");
-        return [
-            {
-                type: "text",
-                text: finalResp,
-            },
-        ];
-    }
-    async #invokeTool(name, args) {
-        try {
-            return await this.config.toolHandler(name, args);
-        }
-        catch (error) {
-            return {
-                type: ToolResponseType.Error,
-                message: responsePrompts.errorInvokeTool(name, error),
-                canRetry: false,
-            };
-        }
-    }
-    get model() {
-        return this.ai.model;
-    }
-}
-//# sourceMappingURL=AgentBase.js.map

package/dist/Agent/AgentBase.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"AgentBase.js","sourceRoot":"","sources":["../../src/Agent/AgentBase.ts"],"names":[],"mappings":"AAGA,OAAO,EAAsD,gBAAgB,EAAE,MAAM,UAAU,CAAA;AAC/F,OAAO,EAAgC,qBAAqB,EAAE,MAAM,yBAAyB,CAAA;AAC7F,OAAO,EAAE,eAAe,EAAE,MAAM,WAAW,CAAA;AAoC3C,MAAM,OAAgB,SAAS;IACV,EAAE,CAAe;IACjB,MAAM,CAA2B;IACjC,MAAM,CAAQ;IAEjC,YAAY,EAAiB,EAAE,MAAuB,EAAE,MAAc;QACpE,IAAI,CAAC,EAAE,GAAG,EAAE,CAAA;QACZ,IAAI,CAAC,MAAM,GAAG,MAAM,CAAA;QACpB,IAAI,CAAC,MAAM,GAAG,MAAM,CAAA;IACtB,CAAC;IAED,KAAK,CAAC,SAAS,CAAC,EACd,IAAI,EACJ,OAAO,EACP,aAAa,GAAG,EAAE,EAClB,QAAQ,GAAG,GAAG,EAAE,GAAE,CAAC,GACoE;QACvF,MAAM,QAAQ,GAAa;YACzB,OAAO,EAAE;gBACP,aAAa;aACd;YACD,QAAQ,EAAE,EAAE;YACZ,WAAW,EAAE,CAAC;YACd,YAAY,EAAE,CAAC;YACf,gBAAgB,EAAE,CAAC;YACnB,eAAe,EAAE,CAAC;YAClB,SAAS,EAAE,CAAC;SACb,CAAA;QAED,IAAI,IAAI,GAAG,SAAS,IAAI,SAAS,CAAA;QAEjC,IAAI,OAAO,EAAE,CAAC;YACZ,IAAI,IAAI,cAAc,OAAO,YAAY,CAAA;QAC3C,CAAC;QAED,IAAI,WAAW,GAA4B;YACzC;gBACE,IAAI,EAAE,MAAM;gBACZ,IAAI;aACL;SACF,CAAA;QAED,IAAI,UAAU,GAAG,CAAC,CAAA;QAClB,OAAO,WAAW,EAAE,CAAC;YACnB,IAAI,UAAU,IAAI,QAAQ,CAAC,OAAO,CAAC,aAAa,EAAE,CAAC;gBACjD,QAAQ,CAAC,EAAE,IAAI,EAAE,wBAAwB,EAAE,IAAI,EAAE,QAAQ,EAAE,CAAC,CAAA;gBAC5D,MAAK;YACP,CAAC;YACD,MAAM,QAAQ,GAAG,MAAM,IAAI,CAAC,QAAQ,CAAC,QAAQ,EAAE,WAAW,EAAE,QAAQ,CAAC,CAAA;YACrE,WAAW,GAAG,MAAM,IAAI,CAAC,eAAe,CAAC,QAAQ,EAAE,QAAQ,EAAE,QAAQ,CAAC,CAAA;YACtE,EAAE,UAAU,CAAA;QACd,CAAC;QAED,QAAQ,CAAC,EAAE,IAAI,EAAE,UAAU,EAAE,IAAI,EAAE,QAAQ,EAAE,CAAC,CAAA;QAC9C,OAAO,QAAQ,CAAA;IACjB,CAAC;IAED,KAAK,CAAC,QAAQ,CAAC,IAAc,EAAE,WAAwB,EAAE,QAA2B;QAClF,MAAM,QAAQ,CAAC,EAAE,IAAI,EAAE,eAAe,EAAE,IAAI,EAAE,WAAW,EAAE,CAAC,CAAA;QAE5D,IAAI,CAAC,QAAQ,CAAC,IAAI,CAAC;YACjB,IAAI,EAAE,MAAM;YACZ,OAAO,EAAE,WAAW;SACrB,CAAC,CAAA;QAEF,IAAI,CAAC,MAAM,CAAC,KAAK,CAAC,IAAI,CAAC,QAAQ,EAAE,wBAAwB,CAAC,CAAA;QAC1D,8EAA8E;QAC9E,MAAM,MAAM,GAAG,IAAI,CAAC,EAAE,CAAC,IAAI,CAAC,IAAI,CAAC,MAAM,CAAC,YAAY,EAAE,IAAI,CAAC,QAAQ,CAAC,CAAA;QACpE,IAAI,uBAAuB,GAAG,EAAE,CAAA;QAEhC,IAAI,KAAK,EAAE,MAAM,KAAK,IAAI,MAAM,EAAE,CAAC;YACjC,QAAQ,KAAK,CAAC,IAAI,EAAE,CAAC;gBACnB,KAAK,OAAO;oBACV,IAAI,CAAC,WAAW,GAAG,KAAK,CAAC,WAAW,CAAA;oBACpC,IAAI,CAAC,YAAY,GAAG,KAAK,CAAC,YAAY,CAAA;oBACtC,IAAI,CAAC,gBAAgB,GAAG,KAAK,CAAC,gBAAgB,IAAI,CAAC,CAAA;oBACnD,IAAI,CAAC,eAAe,GAAG,KAAK,CAAC,eAAe,IAAI,CAAC,CAAA;oBACjD,IAAI,CAAC,SAAS,GAAG,KAAK,CAAC,SAAS,CAAA;oBAChC,MAAM,QAAQ,CAAC,EAAE,IAAI,EAAE,OAAO,EAAE,IAAI,EAAE,CAAC,CAAA;oBACvC,MAAK;gBACP,KAAK,MAAM;oBACT,uBAAuB,IAAI,KAAK,CAAC,IAAI,CAAA;oBACrC,MAAM,QAAQ,CAAC,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,OAAO,EAAE,KAAK,CAAC,IAAI,EAAE,CAAC,CAAA;oBAC3D,MAAK;YACT,CAAC;QACH,CAAC;QAED,uBAAuB;QAEvB,IAAI,CAAC,uBAAuB,EAAE,CAAC;YAC7B,MAAM,IAAI,KAAK,CAAC,+BAA+B,CAAC,CAAA;QAClD,CAAC;QAED,IAAI,CAAC,QAAQ,CAAC,IAAI,CAAC;YACjB,IAAI,EAAE,WAAW;YACjB,OAAO,EAAE,uBAAuB;SACjC,CAAC,CAAA;QAEF,MAAM,GAAG,GAAG,qBAAqB,CAAC,uBAAuB,EAAE,IAAI,CAAC,MAAM,CAAC,KAAK,EAAE,IAAI,CAAC,MAAM,CAAC,cAAc,CAAC,CAAA;QAEzG,MAAM,QAAQ,CAAC,EAAE,IAAI,EAAE,aAAa,EAAE,IAAI,EAAE,CAAC,CAAA;QAE7C,OAAO,GAAG,CAAA;IACZ,CAAC;IAED,KAAK,CAAC,eAAe,CACnB,IAAc,EACd,QAAmC,EACnC,QAA2B;QAE3B,MAAM,YAAY,GAAyC,EAAE,CAAA;QAC7D,KAAK,MAAM,OAAO,IAAI,QAAQ,EAAE,CAAC;YAC/B,QAAQ,OAAO,CAAC,IAAI,EAAE,CAAC;gBACrB,KAAK,MAAM;oBACT,iCAAiC;oBACjC,MAAK;gBACP,KAAK,UAAU,CAAC,CAAC,CAAC;oBAChB,MAAM,QAAQ,CAAC,EAAE,IAAI,EAAE,UAAU,EAAE,IAAI,EAAE,IAAI,EAAE,OAAO,CAAC,IAAI,EAAE,CAAC,CAAA;oBAC9D,MAAM,QAAQ,GAAG,MAAM,IAAI,CAAC,WAAW,CAAC,OAAO,CAAC,IAAI,EAAE,OAAO,CAAC,MAAM,CAAC,CAAA;oBACrE,QAAQ,QAAQ,CAAC,IAAI,EAAE,CAAC;wBACtB,KAAK,gBAAgB,CAAC,KAAK;4BACzB,wBAAwB;4BACxB,MAAM,QAAQ,CAAC,EAAE,IAAI,EAAE,YAAY,EAAE,IAAI,EAAE,IAAI,EAAE,OAAO,CAAC,IAAI,EAAE,CAAC,CAAA;4BAChE,YAAY,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,OAAO,CAAC,IAAI,EAAE,QAAQ,EAAE,QAAQ,CAAC,OAAO,EAAE,CAAC,CAAA;4BACrE,MAAK;wBACP,KAAK,gBAAgB,CAAC,IAAI;4BACxB,iBAAiB;4BACjB,OAAO,SAAS,CAAA;wBAClB,KAAK,gBAAgB,CAAC,OAAO;4BAC3B,sCAAsC;4BACtC,MAAM,QAAQ,CAAC,EAAE,IAAI,EAAE,cAAc,EAAE,IAAI,EAAE,IAAI,EAAE,OAAO,CAAC,IAAI,EAAE,CAAC,CAAA;4BAClE,YAAY,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,OAAO,CAAC,IAAI,EAAE,QAAQ,EAAE,QAAQ,CAAC,OAAO,EAAE,CAAC,CAAA;4BACrE,MAAK;wBACP,KAAK,gBAAgB,CAAC,KAAK;4BACzB,0BAA0B;4BAC1B,MAAM,QAAQ,CAAC,EAAE,IAAI,EAAE,YAAY,EAAE,IAAI,EAAE,IAAI,EAAE,OAAO,CAAC,IAAI,EAAE,CAAC,CAAA;4BAChE,YAAY,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,OAAO,CAAC,IAAI,EAAE,QAAQ,EAAE,QAAQ,CAAC,OAAO,EAAE,CAAC,CAAA;4BACrE,MAAK;wBACP,KAAK,gBAAgB,CAAC,WAAW;4BAC/B,0BAA0B;4BAC1B,MAAM,QAAQ,CAAC,EAAE,IAAI,EAAE,kBAAkB,EAAE,IAAI,EAAE,IAAI,EAAE,OAAO,CAAC,IAAI,EAAE,CAAC,CAAA;4BACtE,OAAO,SAAS,CAAA;oBACpB,CAAC;oBACD,MAAK;gBACP,CAAC;YACH,CAAC;QACH,CAAC;QAED,IAAI,YAAY,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;YAC9B,6EAA6E;YAC7E,iDAAiD;YACjD,OAAO;gBACL;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE,eAAe,CAAC,cAAc;iBACrC;aACF,CAAA;QACH,CAAC;QAED,MAAM,SAAS,GAAG,YAAY,CAAC,GAAG,CAAC,CAAC,EAAE,IAAI,EAAE,QAAQ,EAAE,EAAE,EAAE,CAAC,eAAe,CAAC,WAAW,CAAC,IAAI,EAAE,QAAQ,CAAC,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAA;QAClH,OAAO;YACL;gBACE,IAAI,EAAE,MAAM;gBACZ,IAAI,EAAE,SAAS;aAChB;SACF,CAAA;IACH,CAAC;IAED,KAAK,CAAC,WAAW,CAAC,IAAY,EAAE,IAA4B;QAC1D,IAAI,CAAC;YACH,OAAO,MAAM,IAAI,CAAC,MAAM,CAAC,WAAW,CAAC,IAAI,EAAE,IAAI,CAAC,CAAA;QAClD,CAAC;QAAC,OAAO,KAAK,EAAE,CAAC;YACf,OAAO;gBACL,IAAI,EAAE,gBAAgB,CAAC,KAAK;gBAC5B,OAAO,EAAE,eAAe,CAAC,eAAe,CAAC,IAAI,EAAE,KAAK,CAAC;gBACrD,QAAQ,EAAE,KAAK;aAChB,CAAA;QACH,CAAC;IACH,CAAC;IAED,IAAI,KAAK;QACP,OAAO,IAAI,CAAC,EAAE,CAAC,KAAK,CAAA;IACtB,CAAC;CACF"}

package/dist/Agent/CoderAgent/index.d.ts

@@ -1,17 +0,0 @@
-import type { AiServiceBase } from "../../AiService/index.js";
-import { type ToolHandler, type ToolInfo } from "../../tools/index.js";
-import { AgentBase } from "../AgentBase.js";
-export type CoderAgentOptions = {
-    ai: AiServiceBase;
-    os: string;
-    toolHandler: ToolHandler;
-    tools?: ToolInfo[];
-    customInstructions?: string[];
-    commands?: Record<string, string | {
-        command: string;
-        description: string;
-    }>;
-};
-export declare class CoderAgent extends AgentBase {
-    constructor(options: CoderAgentOptions);
-}

package/dist/Agent/CoderAgent/index.js

@@ -1,32 +0,0 @@
-import { createServiceLogger } from "../../logger.js";
-import { allTools } from "../../tools/index.js";
-import { AgentBase } from "../AgentBase.js";
-import { fullSystemPrompt } from "./prompts.js";
-const defaultTools = [
-    allTools.executeCommand,
-    allTools.readFile,
-    allTools.writeToFile,
-    allTools.replaceInFile,
-    allTools.searchFiles,
-    allTools.listFiles,
-    allTools.listCodeDefinitionNames,
-    // allTools.askFollowupQuestion,
-    allTools.attemptCompletion,
-];
-export class CoderAgent extends AgentBase {
-    constructor(options) {
-        const tools = options.tools || defaultTools;
-        const toolNamePrefix = "tool_";
-        const systemPrompt = fullSystemPrompt({
-            os: options.os,
-        }, tools, toolNamePrefix, options.customInstructions ?? [], options.commands ?? {});
-        super(options.ai, {
-            systemPrompt,
-            tools,
-            toolNamePrefix,
-            toolHandler: options.toolHandler,
-            customInstructions: options.customInstructions,
-        }, createServiceLogger("CoderAgent"));
-    }
-}
-//# sourceMappingURL=index.js.map

package/dist/Agent/CoderAgent/index.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/Agent/CoderAgent/index.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,mBAAmB,EAAE,MAAM,cAAc,CAAA;AAClD,OAAO,EAAmC,QAAQ,EAAE,MAAM,aAAa,CAAA;AACvE,OAAO,EAAE,SAAS,EAAE,MAAM,cAAc,CAAA;AACxC,OAAO,EAAE,gBAAgB,EAAE,MAAM,WAAW,CAAA;AAW5C,MAAM,YAAY,GAAG;IACnB,QAAQ,CAAC,cAAc;IACvB,QAAQ,CAAC,QAAQ;IACjB,QAAQ,CAAC,WAAW;IACpB,QAAQ,CAAC,aAAa;IACtB,QAAQ,CAAC,WAAW;IACpB,QAAQ,CAAC,SAAS;IAClB,QAAQ,CAAC,uBAAuB;IAChC,gCAAgC;IAChC,QAAQ,CAAC,iBAAiB;CAC3B,CAAA;AAED,MAAM,OAAO,UAAW,SAAQ,SAAS;IACvC,YAAY,OAA0B;QACpC,MAAM,KAAK,GAAG,OAAO,CAAC,KAAK,IAAI,YAAY,CAAA;QAC3C,MAAM,cAAc,GAAG,OAAO,CAAA;QAC9B,MAAM,YAAY,GAAG,gBAAgB,CACnC;YACE,EAAE,EAAE,OAAO,CAAC,EAAE;SACf,EACD,KAAK,EACL,cAAc,EACd,OAAO,CAAC,kBAAkB,IAAI,EAAE,EAChC,OAAO,CAAC,QAAQ,IAAI,EAAE,CACvB,CAAA;QAED,KAAK,CACH,OAAO,CAAC,EAAE,EACV;YACE,YAAY;YACZ,KAAK;YACL,cAAc;YACd,WAAW,EAAE,OAAO,CAAC,WAAW;YAChC,kBAAkB,EAAE,OAAO,CAAC,kBAAkB;SAC/C,EACD,mBAAmB,CAAC,YAAY,CAAC,CAClC,CAAA;IACH,CAAC;CACF"}

package/dist/Agent/CoderAgent/prompts.d.ts

@@ -1,20 +0,0 @@
-import type { ToolInfo } from "../../tools/index.js";
-export declare const basePrompt = "You are a highly skilled software engineer with extensive knowledge in many programming languages, frameworks, design patterns, and best practices.";
-export declare const editingFilesPrompt: (toolNamePrefix: string) => string;
-export declare const capabilities: (toolNamePrefix: string) => string;
-export declare const rules: (toolNamePrefix: string) => string;
-export declare const objectives: (toolNamePrefix: string) => string;
-export declare const systemInformation: (info: {
-    os: string;
-}) => string;
-export declare const customInstructions: (customInstructions: string[]) => string;
-export declare const customCommands: (commands: Record<string, string | {
-    command: string;
-    description: string;
-}>) => string;
-export declare const fullSystemPrompt: (info: {
-    os: string;
-}, tools: ToolInfo[], toolNamePrefix: string, instructions: string[], commands: Record<string, string | {
-    command: string;
-    description: string;
-}>) => string;

package/dist/Agent/CoderAgent/prompts.js

@@ -1,165 +0,0 @@
-// source: https://github.com/cline/cline/blob/f6c19c29a64ca84e9360df7ab2c07d128dcebe64/src/core/prompts/system.ts#L1
-import { toolUsePrompt } from "../prompts.js";
-// TODO: restructure the prompts to avoid duplications
-export const basePrompt = "You are a highly skilled software engineer with extensive knowledge in many programming languages, frameworks, design patterns, and best practices.";
-export const editingFilesPrompt = (toolNamePrefix) => `
-====
-
-EDITING FILES
-
-You have access to two tools for working with files: **${toolNamePrefix}write_to_file** and **${toolNamePrefix}replace_in_file**. Understanding their roles and selecting the right one for the job will help ensure efficient and accurate modifications.
-
-# ${toolNamePrefix}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 ${toolNamePrefix}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 ${toolNamePrefix}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 ${toolNamePrefix}replace_in_file instead to avoid unnecessarily rewriting the entire file.
-- While ${toolNamePrefix}write_to_file should not be your default choice, don't hesitate to use it when the situation truly calls for it.
-
-# ${toolNamePrefix}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 ${toolNamePrefix}replace_in_file** for most changes. It's the safer, more precise option that minimizes potential issues.
-- **Use ${toolNamePrefix}write_to_file** when:
-  - Creating new files
-  - The changes are so extensive that using ${toolNamePrefix}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
-
-# Workflow Tips
-
-1. Before editing, assess the scope of your changes and decide which tool to use.
-2. For targeted edits, apply ${toolNamePrefix}replace_in_file with carefully crafted SEARCH/REPLACE blocks. If you need multiple changes, you can stack multiple SEARCH/REPLACE blocks within a single ${toolNamePrefix}replace_in_file call.
-3. For major overhauls or initial file creation, rely on ${toolNamePrefix}write_to_file.
-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.`;
-export const 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.
-	- 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.`;
-export const rules = (toolNamePrefix) => `
-====
-
-RULES
-
-- You may use \`cd\` to enter any child directory within the current working directory. For example, \`cd myChildDir\`. But you may never move to a parent directory or any directory outside your current path. For example, do not use \`cd ..\`, \`cd /\`, or any absolute path.
-- Always work with relative path names, and never use absolute paths.
-- When generating code file, add a comment on top of the file indicating this file is generated by "polka.codes".
-- When generate text file such as README.md, add a footer indicating this file is generated by "polka.codes".
-- Before using the ${toolNamePrefix}execute_command tool, you must first think about the SYSTEM INFORMATION context provided to understand the user's environment and tailor your commands to ensure they are compatible with their system. You must also consider if the command you need to run should be executed in a specific directory outside of the current working directory, and if so prepend with \`cd\`'ing into that directory && then executing the command (as one command). For example, if you needed to run \`npm install\` in a project that's not in the current working directory, you would need to prepend with a \`cd\` i.e. pseudocode for this would be \`cd (path to project) && (command, in this case npm install)\`. However, you can only cd into child directory, but never parent directory or root directory or home directory.
-- When using the ${toolNamePrefix}search_files tool, craft your regex patterns carefully to balance specificity and flexibility. Based on the user's task you may use it to find code patterns, TODO comments, function definitions, or any text-based information across the project. The results include context, so analyze the surrounding code to better understand the matches. Leverage the ${toolNamePrefix}search_files tool in combination with other tools for more comprehensive analysis. For example, use it to find specific code patterns, then use ${toolNamePrefix}read_file to examine the full context of interesting matches before using ${toolNamePrefix}replace_in_file to make informed changes.
-- 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.
-- 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 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.
-- NEVER end ${toolNamePrefix}attempt_completion result with a question or request to engage in further conversation! Formulate the end of your result in a way that is final and does not require further input from the user.
-- You are STRICTLY FORBIDDEN from starting your messages with "Great", "Certainly", "Okay", "Sure". You should NOT be conversational in your responses, but rather direct and to the point. For example you should NOT say "Great, I've updated the CSS" but instead something like "I've updated the CSS". It is important you be clear and technical in your messages.
-- When presented with images, utilize your vision capabilities to thoroughly examine them and extract meaningful information. Incorporate these insights into your thought process as you accomplish the user's task.
-- When using the ${toolNamePrefix}replace_in_file tool, you must include complete lines in your SEARCH blocks, not partial lines. The system requires exact line matches and cannot match partial lines. For example, if you want to match a line containing "const x = 5;", your SEARCH block must include the entire line, not just "x = 5" or other fragments.
-- When using the ${toolNamePrefix}replace_in_file tool, if you use multiple SEARCH/REPLACE blocks, list them in the order they appear in the file. For example if you need to make changes to both line 10 and line 50, first include the SEARCH/REPLACE block for line 10, followed by the SEARCH/REPLACE block for line 50.
-- It is critical you wait for the user's response after each tool use, in order to confirm the success of the tool use. For example, if asked to make a todo app, you would create a file, wait for the user's response it was created successfully, then create another file if needed, wait for the user's response it was created successfully, etc.`;
-export const objectives = (toolNamePrefix) => `
-====
-
-OBJECTIVE
-
-You accomplish a given task iteratively, breaking it down into clear steps and working through them methodically.
-
-1. Analyze the user's task and set clear, achievable goals to accomplish it. Prioritize these goals in a logical order.
-2. Work through these goals sequentially, utilizing available tools one at a time as necessary. Each goal should correspond to a distinct step in your problem-solving process. You will be informed on the work completed and what's remaining as you go.
-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.`;
-export const systemInformation = (info) => `
-====
-
-SYSTEM INFORMATION
-
-Operating System: ${info.os}`;
-export const customInstructions = (customInstructions) => {
-    const joined = customInstructions.join("\n");
-    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}`;
-};
-export const customCommands = (commands) => {
-    const joined = Object.entries(commands)
-        .map(([name, command]) => {
-        if (typeof command === "string") {
-            return `- ${name}\n  - Command: \`${command}\``;
-        }
-        return `- ${name}\n  - Command: \`${command.command}\`\n  - Description: ${command.description}`;
-    })
-        .join("\n");
-    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}`;
-};
-export const fullSystemPrompt = (info, tools, toolNamePrefix, instructions, commands) => `
-${basePrompt}
-${toolUsePrompt(tools, toolNamePrefix)}
-${editingFilesPrompt(toolNamePrefix)}
-${capabilities(toolNamePrefix)}
-${rules(toolNamePrefix)}
-${objectives(toolNamePrefix)}
-${systemInformation(info)}
-${customInstructions(instructions)}
-${customCommands(commands)}
-`;
-//# sourceMappingURL=prompts.js.map

package/dist/Agent/CoderAgent/prompts.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"prompts.js","sourceRoot":"","sources":["../../../src/Agent/CoderAgent/prompts.ts"],"names":[],"mappings":"AAAA,qHAAqH;AAGrH,OAAO,EAAE,aAAa,EAAE,MAAM,YAAY,CAAA;AAE1C,sDAAsD;AAEtD,MAAM,CAAC,MAAM,UAAU,GACrB,qJAAqJ,CAAA;AAEvJ,MAAM,CAAC,MAAM,kBAAkB,GAAG,CAAC,cAAsB,EAAE,EAAE,CAAC;;;;;yDAKL,cAAc,yBAAyB,cAAc;;IAE1G,cAAc;;;;;;;;;;wDAUsC,cAAc;;;;;UAK5D,cAAc;+EACuD,cAAc;UACnF,cAAc;;IAEpB,cAAc;;;;;;;;;;;;;;;;;;;iBAmBD,cAAc;UACrB,cAAc;;8CAEsB,cAAc;;;;;;;;+BAQ7B,cAAc,4JAA4J,cAAc;2DAC5J,cAAc;+CAC1B,cAAc,oBAAoB,cAAc;;oCAE3D,cAAc,qBAAqB,cAAc,8FAA8F,CAAA;AAEnL,MAAM,CAAC,MAAM,YAAY,GAAG,CAAC,cAAsB,EAAE,EAAE,CAAC;;;;;;;gBAOxC,cAAc;oBACV,cAAc;+KAC6I,cAAc,mIAAmI,cAAc,wIAAwI,cAAc,kIAAkI,cAAc;oBAChmB,cAAc,inBAAinB,CAAA;AAEnpB,MAAM,CAAC,MAAM,KAAK,GAAG,CAAC,cAAsB,EAAE,EAAE,CAAC;;;;;;;;;qBAS5B,cAAc;mBAChB,cAAc,oWAAoW,cAAc,mJAAmJ,cAAc,6EAA6E,cAAc;4OACna,cAAc;;;4CAG9M,cAAc,sBAAsB,cAAc;2LAC6F,cAAc;0GAC/F,cAAc;;cAE1G,cAAc;;;mBAGT,cAAc;mBACd,cAAc;wVACuT,CAAA;AAExV,MAAM,CAAC,MAAM,UAAU,GAAG,CAAC,cAAsB,EAAE,EAAE,CAAC;;;;;;;;;;6DAUO,cAAc;sOAC2J,CAAA;AAEtO,MAAM,CAAC,MAAM,iBAAiB,GAAG,CAAC,IAAoB,EAAE,EAAE,CAAC;;;;;oBAKvC,IAAI,CAAC,EAAE,EAAE,CAAA;AAE7B,MAAM,CAAC,MAAM,kBAAkB,GAAG,CAAC,kBAA4B,EAAE,EAAE;IACjE,MAAM,MAAM,GAAG,kBAAkB,CAAC,IAAI,CAAC,IAAI,CAAC,CAAA;IAC5C,IAAI,MAAM,CAAC,IAAI,EAAE,KAAK,EAAE,EAAE,CAAC;QACzB,OAAO,EAAE,CAAA;IACX,CAAC;IAED,OAAO;;;;;;;EAOP,MAAM,EAAE,CAAA;AACV,CAAC,CAAA;AAED,MAAM,CAAC,MAAM,cAAc,GAAG,CAAC,QAA2E,EAAE,EAAE;IAC5G,MAAM,MAAM,GAAG,MAAM,CAAC,OAAO,CAAC,QAAQ,CAAC;SACpC,GAAG,CAAC,CAAC,CAAC,IAAI,EAAE,OAAO,CAAC,EAAE,EAAE;QACvB,IAAI,OAAO,OAAO,KAAK,QAAQ,EAAE,CAAC;YAChC,OAAO,KAAK,IAAI,oBAAoB,OAAO,IAAI,CAAA;QACjD,CAAC;QACD,OAAO,KAAK,IAAI,oBAAoB,OAAO,CAAC,OAAO,wBAAwB,OAAO,CAAC,WAAW,EAAE,CAAA;IAClG,CAAC,CAAC;SACD,IAAI,CAAC,IAAI,CAAC,CAAA;IACb,IAAI,MAAM,CAAC,IAAI,EAAE,KAAK,EAAE,EAAE,CAAC;QACzB,OAAO,EAAE,CAAA;IACX,CAAC;IAED,OAAO;;;;;;;EAOP,MAAM,EAAE,CAAA;AACV,CAAC,CAAA;AAED,MAAM,CAAC,MAAM,gBAAgB,GAAG,CAC9B,IAAoB,EACpB,KAAiB,EACjB,cAAsB,EACtB,YAAsB,EACtB,QAA2E,EAC3E,EAAE,CAAC;EACH,UAAU;EACV,aAAa,CAAC,KAAK,EAAE,cAAc,CAAC;EACpC,kBAAkB,CAAC,cAAc,CAAC;EAClC,YAAY,CAAC,cAAc,CAAC;EAC5B,KAAK,CAAC,cAAc,CAAC;EACrB,UAAU,CAAC,cAAc,CAAC;EAC1B,iBAAiB,CAAC,IAAI,CAAC;EACvB,kBAAkB,CAAC,YAAY,CAAC;EAChC,cAAc,CAAC,QAAQ,CAAC;CACzB,CAAA"}

package/dist/Agent/index.d.ts

@@ -1,2 +0,0 @@
-export * from "./AgentBase.js";
-export * from "./CoderAgent/index.js";

package/dist/Agent/index.js

@@ -1,3 +0,0 @@
-export * from "./AgentBase.js";
-export * from "./CoderAgent/index.js";
-//# sourceMappingURL=index.js.map

package/dist/Agent/index.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/Agent/index.ts"],"names":[],"mappings":"AAAA,cAAc,aAAa,CAAA;AAC3B,cAAc,cAAc,CAAA"}

package/dist/Agent/parseAssistantMessage.d.ts

@@ -1,45 +0,0 @@
-import type { ToolInfo } from "../tools/index.js";
-export interface TextContent {
-    type: "text";
-    content: string;
-}
-export interface ToolUse {
-    type: "tool_use";
-    name: string;
-    params: Record<string, string>;
-}
-export type AssistantMessageContent = TextContent | ToolUse;
-/**
- * Parse an assistant's message into an array of text content and tool use content.
- *
- * @example
- * const tools = [
- *   {
- *     name: "search",
- *     parameters: [
- *       {name: "query", type: "string"}
- *     ]
- *   }
- * ]
- *
- * // Text only
- * parseAssistantMessage("Hello world", tools, "tool_")
- * // Returns: [{type: "text", content: "Hello world"}]
- *
- * // Tool use with parameters
- * parseAssistantMessage(
- *   `Let me search that for you
- *   <tool_search>
- *     <tool_parameter_query>cats</tool_parameter_query>
- *   </tool_search>
- *   Here are the results`,
- *   tools,
- *   "tool_"
- * )
- * // Returns: [
- * //   {type: "text", content: "Let me search that for you"},
- * //   {type: "tool_use", name: "search", params: {query: "cats"}},
- * //   {type: "text", content: "Here are the results"}
- * // ]
- */
-export declare function parseAssistantMessage(assistantMessage: string, tools: ToolInfo[], toolNamePrefix: string): AssistantMessageContent[];

package/dist/Agent/parseAssistantMessage.js

@@ -1,103 +0,0 @@
-/**
- * Parse an assistant's message into an array of text content and tool use content.
- *
- * @example
- * const tools = [
- *   {
- *     name: "search",
- *     parameters: [
- *       {name: "query", type: "string"}
- *     ]
- *   }
- * ]
- *
- * // Text only
- * parseAssistantMessage("Hello world", tools, "tool_")
- * // Returns: [{type: "text", content: "Hello world"}]
- *
- * // Tool use with parameters
- * parseAssistantMessage(
- *   `Let me search that for you
- *   <tool_search>
- *     <tool_parameter_query>cats</tool_parameter_query>
- *   </tool_search>
- *   Here are the results`,
- *   tools,
- *   "tool_"
- * )
- * // Returns: [
- * //   {type: "text", content: "Let me search that for you"},
- * //   {type: "tool_use", name: "search", params: {query: "cats"}},
- * //   {type: "text", content: "Here are the results"}
- * // ]
- */
-export function parseAssistantMessage(assistantMessage, tools, toolNamePrefix) {
-    const parameterPrefix = `${toolNamePrefix}parameter_`;
-    const results = [];
-    // Generate list of possible tool tags
-    const toolTags = tools.map((tool) => `${toolNamePrefix}${tool.name}`);
-    const toolPattern = toolTags.join('|');
-    // Find the outermost tool tag by matching first opening and last closing tags
-    const tagRegex = new RegExp(`<(${toolPattern})>(.*)<\\/\\1>`, 's');
-    const match = assistantMessage.match(tagRegex);
-    if (match) {
-        // Split message into parts
-        const beforeTag = assistantMessage.slice(0, match.index).trim();
-        const fullTagContent = match[0];
-        // Add text before tag if exists
-        if (beforeTag) {
-            results.push({
-                type: 'text',
-                content: beforeTag,
-            });
-        }
-        // Find which tool was used
-        const tagName = match[1];
-        const toolName = tagName.replace(toolNamePrefix, '');
-        const tool = tools.find((t) => t.name === toolName);
-        if (tool) {
-            // Parse parameters using new XML-like syntax
-            const params = {};
-            // Extract parameters while preserving nested content
-            for (const param of tool.parameters) {
-                const paramName = `${parameterPrefix}${param.name}`;
-                const escapedParamName = paramName.replace(/[.*+?^${}()|[\]\\]/g, '\\$&');
-                // Match parameter content non-greedily while preserving nested content
-                const paramPattern = `<${escapedParamName}>([\\s\\S]*?)<\\/${escapedParamName}>`;
-                const paramMatch = fullTagContent.match(new RegExp(paramPattern, 's'));
-                if (paramMatch) {
-                    params[param.name] = paramMatch[1].trim();
-                }
-            }
-            results.push({
-                type: 'tool_use',
-                name: toolName,
-                params,
-            });
-        }
-        else {
-            // Unknown tool - treat as text
-            results.push({
-                type: 'text',
-                content: fullTagContent,
-            });
-        }
-        // Add text after the full tag if exists
-        const afterTag = assistantMessage.slice((match.index ?? 0) + fullTagContent.length).trim();
-        if (afterTag) {
-            results.push({
-                type: 'text',
-                content: afterTag,
-            });
-        }
-    }
-    else {
-        // No tool tags found, treat entire message as text
-        results.push({
-            type: 'text',
-            content: assistantMessage,
-        });
-    }
-    return results;
-}
-//# sourceMappingURL=parseAssistantMessage.js.map