anycodex 0.0.8 → 0.0.10

package/dist/{chunk-BTDDMBCN.js → chunk-LAUSNF7V.js}

@@ -5,7 +5,7 @@ import {
   SchedulerService,
   Skill,
   ToolRegistry
-} from "./chunk-FSJHVC5R.js";
+} from "./chunk-U6O7ENPZ.js";
 import {
   AISDKError,
   APICallError,
@@ -908,12 +908,6 @@ function o(e, r3) {
   return a3;
 }
 
-// ../agent/dist/index.js
-import { spawn } from "child_process";
-import { pathToFileURL, fileURLToPath } from "url";
-var import_fuzzysort = __toESM(require_fuzzysort(), 1);
-import { createHash } from "crypto";
-
 // ../../node_modules/.pnpm/@ai-sdk+provider-utils@3.0.21_zod@4.1.8/node_modules/@ai-sdk/provider-utils/dist/index.mjs
 function combineHeaders2(...headers) {
   return headers.reduce(
@@ -6264,6 +6258,9 @@ function createAnthropic(options = {}) {
 }
 var anthropic = createAnthropic();
 
+// ../agent/dist/index.js
+import { createHash } from "crypto";
+
 // ../../node_modules/.pnpm/@ai-sdk+google@2.0.54_zod@4.1.8/node_modules/@ai-sdk/google/dist/index.mjs
 var VERSION3 = true ? "2.0.54" : "0.0.0-test";
 var googleErrorDataSchema = lazySchema2(
@@ -13907,6 +13904,9 @@ function createOpenAICompatible(options) {
 }
 
 // ../agent/dist/index.js
+import { spawn } from "child_process";
+import { pathToFileURL, fileURLToPath } from "url";
+var import_fuzzysort = __toESM(require_fuzzysort(), 1);
 import fs from "fs/promises";
 import { existsSync, statSync, readdirSync } from "fs";
 import path from "path";
@@ -13955,440 +13955,190 @@ var Env;
   }
   Env2.remove = remove;
 })(Env || (Env = {}));
-function mimeToModality(mime) {
-  if (mime.startsWith("image/")) return "image";
-  if (mime.startsWith("audio/")) return "audio";
-  if (mime.startsWith("video/")) return "video";
-  if (mime === "application/pdf") return "pdf";
-  return void 0;
-}
-var ProviderTransform;
-((ProviderTransform2) => {
-  ProviderTransform2.OUTPUT_TOKEN_MAX = Flag.OPENCODE_EXPERIMENTAL_OUTPUT_TOKEN_MAX || 32e3;
-  function sdkKey(npm) {
-    switch (npm) {
-      case "@ai-sdk/openai":
-        return "openai";
-      case "@ai-sdk/anthropic":
-        return "anthropic";
-      case "@ai-sdk/google":
-        return "google";
-    }
-    return void 0;
+var Hash;
+((Hash2) => {
+  function fast(input) {
+    return createHash("sha1").update(input).digest("hex");
   }
-  function normalizeMessages(msgs, model, _options) {
-    if (model.api.npm === "@ai-sdk/anthropic") {
-      msgs = msgs.map((msg) => {
-        if (typeof msg.content === "string") {
-          if (msg.content === "") return void 0;
-          return msg;
+  Hash2.fast = fast;
+  function sha256(input) {
+    return createHash("sha256").update(input).digest("hex");
+  }
+  Hash2.sha256 = sha256;
+  function hexToUUID(hex) {
+    return [
+      hex.slice(0, 8),
+      hex.slice(8, 12),
+      hex.slice(12, 16),
+      hex.slice(16, 20),
+      hex.slice(20, 32)
+    ].join("-");
+  }
+  Hash2.hexToUUID = hexToUUID;
+})(Hash || (Hash = {}));
+var anthropicVendor = {
+  id: "anthropic",
+  npms: ["@ai-sdk/anthropic"],
+  bundled: {
+    "@ai-sdk/anthropic": createAnthropic
+  },
+  sdkKeys: {
+    "@ai-sdk/anthropic": "anthropic"
+  },
+  async customLoader() {
+    return {
+      autoload: false,
+      options: {
+        headers: {
+          "anthropic-beta": "claude-code-20250219,interleaved-thinking-2025-05-14,fine-grained-tool-streaming-2025-05-14",
+          "X-App": "cli",
+          "X-Stainless-Lang": "js",
+          "X-Stainless-Package-Version": "0.70.0",
+          "X-Stainless-OS": process.platform === "darwin" ? "MacOS" : process.platform === "win32" ? "Windows" : "Linux",
+          "X-Stainless-Arch": process.arch === "arm64" ? "arm64" : "x64",
+          "X-Stainless-Runtime": "node",
+          "X-Stainless-Runtime-Version": process.version,
+          "X-Stainless-Retry-Count": "0",
+          "X-Stainless-Timeout": "600",
+          "Anthropic-Dangerous-Direct-Browser-Access": "true"
         }
-        if (!Array.isArray(msg.content)) return msg;
-        const filtered = msg.content.filter((part) => {
-          if (part.type === "text" || part.type === "reasoning") {
-            return part.text !== "";
-          }
-          return true;
-        });
-        if (filtered.length === 0) return void 0;
-        return { ...msg, content: filtered };
-      }).filter((msg) => msg !== void 0 && msg.content !== "");
+      }
+    };
+  },
+  patchRequest({ opts, model, provider }) {
+    if (opts.headers) {
+      const headers = new Headers(opts.headers);
+      headers.set("user-agent", "claude-cli/2.1.77");
+      opts.headers = Object.fromEntries(headers.entries());
+    } else {
+      opts.headers = { "user-agent": "claude-cli/2.1.77" };
     }
-    if (model.api.id.includes("claude")) {
-      return msgs.map((msg) => {
-        if ((msg.role === "assistant" || msg.role === "tool") && Array.isArray(msg.content)) {
-          msg.content = msg.content.map((part) => {
-            if ((part.type === "tool-call" || part.type === "tool-result") && "toolCallId" in part) {
-              return {
-                ...part,
-                toolCallId: part.toolCallId.replace(/[^a-zA-Z0-9_-]/g, "_")
-              };
-            }
-            return part;
-          });
+    if (opts.body && opts.method === "POST") {
+      try {
+        const body = JSON.parse(opts.body);
+        if (!body.metadata?.user_id) {
+          if (!body.metadata) body.metadata = {};
+          const seed = [model.providerID ?? "", provider.key ?? ""].join(":");
+          const clientId = Hash.sha256(seed + ":claude-code-client");
+          const uuid = Hash.hexToUUID(Hash.sha256(seed + ":session"));
+          body.metadata.user_id = `user_${clientId}_account__session_${uuid}`;
         }
-        return msg;
-      });
-    }
-    if (typeof model.capabilities.interleaved === "object" && model.capabilities.interleaved.field) {
-      const field = model.capabilities.interleaved.field;
-      return msgs.map((msg) => {
-        if (msg.role === "assistant" && Array.isArray(msg.content)) {
-          const reasoningParts = msg.content.filter((part) => part.type === "reasoning");
-          const reasoningText = reasoningParts.map((part) => part.text).join("");
-          const filteredContent = msg.content.filter((part) => part.type !== "reasoning");
-          if (reasoningText) {
-            return {
-              ...msg,
-              content: filteredContent,
-              providerOptions: {
-                ...msg.providerOptions,
-                openaiCompatible: {
-                  ...msg.providerOptions?.openaiCompatible,
-                  [field]: reasoningText
-                }
-              }
-            };
+        if (Array.isArray(body.system)) {
+          const alreadyPresent = body.system.some(
+            (entry) => typeof entry.text === "string" && entry.text.startsWith(CLAUDE_CODE_SYSTEM)
+          );
+          if (!alreadyPresent) {
+            body.system.unshift({
+              type: "text",
+              text: CLAUDE_CODE_SYSTEM,
+              cache_control: { type: "ephemeral" }
+            });
           }
-          return { ...msg, content: filteredContent };
         }
-        return msg;
-      });
-    }
-    return msgs;
-  }
-  function applyCaching(msgs, _model) {
-    const system = msgs.filter((msg) => msg.role === "system").slice(0, 2);
-    const final = msgs.filter((msg) => msg.role !== "system").slice(-2);
-    const providerOptions2 = {
-      anthropic: {
-        cacheControl: { type: "ephemeral" }
+        opts.body = JSON.stringify(body);
+      } catch {
       }
-    };
-    for (const msg of i([...system, ...final])) {
-      msg.providerOptions = D(msg.providerOptions ?? {}, providerOptions2);
     }
-    return msgs;
-  }
-  function unsupportedParts(msgs, model) {
-    return msgs.map((msg) => {
-      if (msg.role !== "user" || !Array.isArray(msg.content)) return msg;
-      const filtered = msg.content.map((part) => {
-        if (part.type !== "file" && part.type !== "image") return part;
-        if (part.type === "image") {
-          const imageStr = part.image.toString();
-          if (imageStr.startsWith("data:")) {
-            const match = imageStr.match(/^data:([^;]+);base64,(.*)$/);
-            if (match && (!match[2] || match[2].length === 0)) {
-              return {
-                type: "text",
-                text: "ERROR: Image file is empty or corrupted. Please provide a valid image."
-              };
+  },
+  transform: {
+    message(msgs, model) {
+      if (model.api.npm === "@ai-sdk/anthropic") {
+        msgs = msgs.map((msg) => {
+          if (typeof msg.content === "string") {
+            if (msg.content === "") return void 0;
+            return msg;
+          }
+          if (!Array.isArray(msg.content)) return msg;
+          const filtered = msg.content.filter((part) => {
+            if (part.type === "text" || part.type === "reasoning") {
+              return part.text !== "";
             }
+            return true;
+          });
+          if (filtered.length === 0) return void 0;
+          return { ...msg, content: filtered };
+        }).filter((msg) => msg !== void 0 && msg.content !== "");
+      }
+      if (model.api.id.includes("claude")) {
+        msgs = msgs.map((msg) => {
+          if ((msg.role === "assistant" || msg.role === "tool") && Array.isArray(msg.content)) {
+            msg.content = msg.content.map((part) => {
+              if ((part.type === "tool-call" || part.type === "tool-result") && "toolCallId" in part) {
+                return {
+                  ...part,
+                  toolCallId: part.toolCallId.replace(/[^a-zA-Z0-9_-]/g, "_")
+                };
+              }
+              return part;
+            });
+          }
+          return msg;
+        });
+      }
+      if (model.providerID === "anthropic" || model.api.id.includes("claude") || model.api.npm === "@ai-sdk/anthropic") {
+        const system = msgs.filter((msg) => msg.role === "system").slice(0, 2);
+        const final = msgs.filter((msg) => msg.role !== "system").slice(-2);
+        const providerOptions = {
+          anthropic: {
+            cacheControl: { type: "ephemeral" }
           }
-        }
-        const mime = part.type === "image" ? part.image.toString().split(";")[0].replace("data:", "") : part.mediaType;
-        const filename = part.type === "file" ? part.filename : void 0;
-        const modality = mimeToModality(mime);
-        if (!modality) return part;
-        if (model.capabilities.input[modality]) return part;
-        const name2 = filename ? `"${filename}"` : modality;
-        return {
-          type: "text",
-          text: `ERROR: Cannot read ${name2} (this model does not support ${modality} input). Inform the user.`
-        };
-      });
-      return { ...msg, content: filtered };
-    });
-  }
-  function message(msgs, model, options2) {
-    msgs = unsupportedParts(msgs, model);
-    msgs = normalizeMessages(msgs, model, options2);
-    if (model.providerID === "anthropic" || model.api.id.includes("claude") || model.api.npm === "@ai-sdk/anthropic") {
-      msgs = applyCaching(msgs, model);
-    }
-    const key = sdkKey(model.api.npm);
-    if (key && key !== model.providerID) {
-      const remap = (opts) => {
-        if (!opts) return opts;
-        if (!(model.providerID in opts)) return opts;
-        const result = { ...opts };
-        result[key] = result[model.providerID];
-        delete result[model.providerID];
-        return result;
-      };
-      msgs = msgs.map((msg) => {
-        if (!Array.isArray(msg.content)) return { ...msg, providerOptions: remap(msg.providerOptions) };
-        return {
-          ...msg,
-          providerOptions: remap(msg.providerOptions),
-          content: msg.content.map((part) => ({ ...part, providerOptions: remap(part.providerOptions) }))
         };
-      });
-    }
-    return msgs;
-  }
-  ProviderTransform2.message = message;
-  function temperature(model) {
-    const id = model.id.toLowerCase();
-    if (id.includes("claude")) return void 0;
-    if (id.includes("gemini")) return 1;
-    return void 0;
-  }
-  ProviderTransform2.temperature = temperature;
-  function topP(_model) {
-    return void 0;
-  }
-  ProviderTransform2.topP = topP;
-  function topK(model) {
-    const id = model.id.toLowerCase();
-    if (id.includes("gemini")) return 64;
-    return void 0;
-  }
-  ProviderTransform2.topK = topK;
-  function options(input) {
-    const result = {};
-    const model = input.model;
-    if (model.providerID === "openai" || model.api.npm === "@ai-sdk/openai") {
-      result["store"] = false;
-    }
-    if (model.providerID === "openai" || input.providerOptions?.setCacheKey) {
-      result["promptCacheKey"] = input.sessionID;
-    }
-    if (model.api.npm === "@ai-sdk/anthropic") {
+        for (const msg of i([...system, ...final])) {
+          msg.providerOptions = D(msg.providerOptions ?? {}, providerOptions);
+        }
+      }
+      return msgs;
+    },
+    options({ model }) {
+      if (model.api.npm !== "@ai-sdk/anthropic") return {};
       const isAdaptive = ["opus-4-6", "opus-4.6", "sonnet-4-6", "sonnet-4.6"].some(
         (v) => model.api.id.includes(v)
       );
       if (isAdaptive) {
-        result["thinking"] = { type: "adaptive" };
-      } else {
-        result["thinking"] = {
+        return { thinking: { type: "adaptive" } };
+      }
+      return {
+        thinking: {
           type: "enabled",
           budgetTokens: model.limit.output - 1
-        };
-      }
-    }
-    if (model.api.npm === "@ai-sdk/google") {
-      result["thinkingConfig"] = { includeThoughts: true };
-      if (model.api.id.includes("gemini-3")) {
-        result["thinkingConfig"]["thinkingLevel"] = "high";
-      }
-    }
-    if (model.api.id.includes("gpt-5") && !model.api.id.includes("gpt-5-chat")) {
-      if (!model.api.id.includes("gpt-5-pro")) {
-        result["reasoningEffort"] = "medium";
-        result["reasoningSummary"] = "auto";
-      }
-      if (model.api.id.includes("gpt-5.") && !model.api.id.includes("codex") && !model.api.id.includes("-chat")) {
-        result["textVerbosity"] = "low";
-      }
-    }
-    return result;
-  }
-  ProviderTransform2.options = options;
-  function smallOptions(model) {
-    if (model.providerID === "openai" || model.api.npm === "@ai-sdk/openai") {
-      if (model.api.id.includes("gpt-5")) {
-        if (model.api.id.includes("5.")) return { store: false, reasoningEffort: "low" };
-        return { store: false, reasoningEffort: "minimal" };
-      }
-      return { store: false };
-    }
-    if (model.providerID === "google") {
-      if (model.api.id.includes("gemini-3")) {
-        return { thinkingConfig: { thinkingLevel: "minimal" } };
-      }
-      return { thinkingConfig: { thinkingBudget: 0 } };
-    }
-    return {};
-  }
-  ProviderTransform2.smallOptions = smallOptions;
-  function providerOptions(model, options2) {
-    const key = sdkKey(model.api.npm) ?? model.providerID;
-    return { [key]: options2 };
-  }
-  ProviderTransform2.providerOptions = providerOptions;
-  function maxOutputTokens(model) {
-    return Math.min(model.limit.output, ProviderTransform2.OUTPUT_TOKEN_MAX) || ProviderTransform2.OUTPUT_TOKEN_MAX;
-  }
-  ProviderTransform2.maxOutputTokens = maxOutputTokens;
-  function schema(model, schema2) {
-    if (model.providerID === "google" || model.api.id.includes("gemini")) {
-      const isPlainObject = (node) => typeof node === "object" && node !== null && !Array.isArray(node);
-      const hasCombiner = (node) => isPlainObject(node) && (Array.isArray(node.anyOf) || Array.isArray(node.oneOf) || Array.isArray(node.allOf));
-      const hasSchemaIntent = (node) => {
-        if (!isPlainObject(node)) return false;
-        if (hasCombiner(node)) return true;
-        return [
-          "type",
-          "properties",
-          "items",
-          "prefixItems",
-          "enum",
-          "const",
-          "$ref",
-          "additionalProperties",
-          "patternProperties",
-          "required",
-          "not",
-          "if",
-          "then",
-          "else"
-        ].some((key) => key in node);
-      };
-      const sanitizeGemini = (obj) => {
-        if (obj === null || typeof obj !== "object") return obj;
-        if (Array.isArray(obj)) return obj.map(sanitizeGemini);
-        const result = {};
-        for (const [key, value] of Object.entries(obj)) {
-          if (key === "enum" && Array.isArray(value)) {
-            result[key] = value.map((v) => String(v));
-            if (result.type === "integer" || result.type === "number") result.type = "string";
-          } else if (typeof value === "object" && value !== null) {
-            result[key] = sanitizeGemini(value);
-          } else {
-            result[key] = value;
-          }
-        }
-        if (result.type === "object" && result.properties && Array.isArray(result.required)) {
-          result.required = result.required.filter((field) => field in result.properties);
-        }
-        if (result.type === "array" && !hasCombiner(result)) {
-          if (result.items == null) result.items = {};
-          if (isPlainObject(result.items) && !hasSchemaIntent(result.items)) result.items.type = "string";
-        }
-        if (result.type && result.type !== "object" && !hasCombiner(result)) {
-          delete result.properties;
-          delete result.required;
         }
-        return result;
       };
-      schema2 = sanitizeGemini(schema2);
     }
-    return schema2;
+  },
+  prompt: {
+    provider(model) {
+      if (!model.api.id.includes("claude")) return void 0;
+      return [PROMPT_ANTHROPIC];
+    }
   }
-  ProviderTransform2.schema = schema;
-})(ProviderTransform || (ProviderTransform = {}));
-var plan_txt_default = `<system-reminder>
-# Plan Mode - System Reminder
+};
+var PROMPT_ANTHROPIC = `You are AnyCode, the best coding agent on the planet.
 
-CRITICAL: Plan mode ACTIVE - you are in READ-ONLY phase. STRICTLY FORBIDDEN:
-ANY file edits, modifications, or system changes. Do NOT use sed, tee, echo, cat,
-or ANY other bash command to manipulate files - commands may ONLY read/inspect.
-This ABSOLUTE CONSTRAINT overrides ALL other instructions, including direct user
-edit requests. You may ONLY observe, analyze, and plan. Any modification attempt
-is a critical violation. ZERO exceptions.
+You are an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.
 
----
+IMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are for helping the user with programming. You may use URLs provided by the user in their messages or local files.
 
-## Responsibility
+If the user asks for help or wants to give feedback inform them of the following:
+- ctrl+p to list available actions
+- To give feedback, users should report the issue at
+  https://github.com/wyattzheng/anycode
 
-Your current responsibility is to think, read, search, and delegate explore agents to construct a well-formed plan that accomplishes the goal the user wants to achieve. Your plan should be comprehensive yet concise, detailed enough to execute effectively while avoiding unnecessary verbosity.
+When the user directly asks about AnyCode (eg. "can AnyCode do...", "does AnyCode have..."), or asks in second person (eg. "are you able...", "can you do..."), or asks how to use a specific AnyCode feature (eg. implement a hook, write a slash command, or install an MCP server), use the WebFetch tool to gather information to answer the question from AnyCode docs. The list of available docs is available at https://anycode.ai/docs
 
-Ask the user clarifying questions or ask for their opinion when weighing tradeoffs.
+# Tone and style
+- Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked.
+- Your output will be displayed on a command line interface. Your responses should be short and concise. You can use GitHub-flavored markdown for formatting, and will be rendered in a monospace font using the CommonMark specification.
+- Output text to communicate with the user; all text you output outside of tool use is displayed to the user. Only use tools to complete tasks. Never use tools like Bash or code comments as means to communicate with the user during the session.
+- NEVER create files unless they're absolutely necessary for achieving your goal. ALWAYS prefer editing an existing file to creating a new one. This includes markdown files.
 
-**NOTE:** At any point in time through this workflow you should feel free to ask the user questions or clarifications. Don't make large assumptions about user intent. The goal is to present a well researched plan to the user, and tie any loose ends before implementation begins.
+# Professional objectivity
+Prioritize technical accuracy and truthfulness over validating the user's beliefs. Focus on facts and problem-solving, providing direct, objective technical info without any unnecessary superlatives, praise, or emotional validation. It is best for the user if AnyCode honestly applies the same rigorous standards to all ideas and disagrees when necessary, even if it may not be what the user wants to hear. Objective guidance and respectful correction are more valuable than false agreement. Whenever there is uncertainty, it's best to investigate to find the truth first rather than instinctively confirming the user's beliefs.
 
----
+# Task Management
+You have access to the TodoWrite tools to help you manage and plan tasks. Use these tools VERY frequently to ensure that you are tracking your tasks and giving the user visibility into your progress.
+These tools are also EXTREMELY helpful for planning tasks, and for breaking down larger complex tasks into smaller steps. If you do not use this tool when planning, you may forget to do important tasks - and that is unacceptable.
 
-## Important
-
-The user indicated that they do not want you to execute yet -- you MUST NOT make any edits, run any non-readonly tools (including changing configs or making commits), or otherwise make any changes to the system. This supersedes any other instructions you have received.
-</system-reminder>
-`;
-var build_switch_txt_default = `<system-reminder>
-Your operational mode has changed from plan to build.
-You are no longer in read-only mode.
-You are permitted to make file changes, run shell commands, and utilize your arsenal of tools as needed.
-</system-reminder>
-`;
-var log = Log.create({ module: "hooks" });
-var Hooks;
-((Hooks2) => {
-  const DEFAULT_TIMEOUT = 15;
-  function toSnakeCase(key) {
-    return key.replace(/[A-Z]/g, (ch) => "_" + ch.toLowerCase());
-  }
-  function keysToSnakeCase(obj) {
-    if (obj === null || obj === void 0 || typeof obj !== "object") return obj;
-    if (Array.isArray(obj)) return obj.map(keysToSnakeCase);
-    const out = {};
-    for (const [key, value] of Object.entries(obj)) {
-      out[toSnakeCase(key)] = keysToSnakeCase(value);
-    }
-    return out;
-  }
-  function matchTool(rules, toolName, filePath) {
-    const matched = [];
-    for (const rule of rules) {
-      try {
-        if (!new RegExp(rule.matcher, "i").test(toolName)) continue;
-        if (filePath && rule.ignore?.some((pat) => {
-          try {
-            return new RegExp(pat, "i").test(filePath);
-          } catch {
-            return false;
-          }
-        })) continue;
-        matched.push(...rule.hooks);
-      } catch {
-      }
-    }
-    return matched;
-  }
-  Hooks2.matchTool = matchTool;
-  function execute(hook, payload, cwd) {
-    const timeout = (hook.timeout ?? DEFAULT_TIMEOUT) * 1e3;
-    const payloadStr = JSON.stringify(payload);
-    try {
-      const proc = spawn("bash", ["-c", hook.command], {
-        cwd,
-        stdio: ["pipe", "ignore", "ignore"],
-        env: process.env,
-        detached: true
-      });
-      proc.unref();
-      proc.stdin?.write(payloadStr);
-      proc.stdin?.end();
-      const timer = setTimeout(() => {
-        try {
-          proc.kill("SIGTERM");
-        } catch {
-        }
-      }, timeout);
-      proc.on("exit", () => clearTimeout(timer));
-      proc.on("error", () => clearTimeout(timer));
-    } catch (err) {
-      log.info(`Hook execution failed: ${err}`);
-    }
-  }
-  function runPostToolUse(hooksConfig, toolName, toolInput, toolResponse, sessionID, cwd) {
-    const rules = hooksConfig["PostToolUse"];
-    if (!rules || rules.length === 0) return;
-    const filePath = toolInput?.filePath ?? toolInput?.file_path;
-    const hooks = matchTool(rules, toolName, filePath);
-    if (hooks.length === 0) return;
-    const payload = {
-      session_id: sessionID,
-      cwd,
-      hook_event_name: "PostToolUse",
-      tool_name: toolName,
-      tool_input: keysToSnakeCase(toolInput),
-      tool_response: keysToSnakeCase(toolResponse)
-    };
-    for (const hook of hooks) {
-      execute(hook, payload, cwd);
-    }
-  }
-  Hooks2.runPostToolUse = runPostToolUse;
-})(Hooks || (Hooks = {}));
-var anthropic_txt_default = `You are AnyCode, the best coding agent on the planet.
-
-You are an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.
-
-IMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are for helping the user with programming. You may use URLs provided by the user in their messages or local files.
-
-If the user asks for help or wants to give feedback inform them of the following:
-- ctrl+p to list available actions
-- To give feedback, users should report the issue at
-  https://github.com/wyattzheng/anycode
-
-When the user directly asks about AnyCode (eg. "can AnyCode do...", "does AnyCode have..."), or asks in second person (eg. "are you able...", "can you do..."), or asks how to use a specific AnyCode feature (eg. implement a hook, write a slash command, or install an MCP server), use the WebFetch tool to gather information to answer the question from AnyCode docs. The list of available docs is available at https://anycode.ai/docs
-
-# Tone and style
-- Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked.
-- Your output will be displayed on a command line interface. Your responses should be short and concise. You can use GitHub-flavored markdown for formatting, and will be rendered in a monospace font using the CommonMark specification.
-- Output text to communicate with the user; all text you output outside of tool use is displayed to the user. Only use tools to complete tasks. Never use tools like Bash or code comments as means to communicate with the user during the session.
-- NEVER create files unless they're absolutely necessary for achieving your goal. ALWAYS prefer editing an existing file to creating a new one. This includes markdown files.
-
-# Professional objectivity
-Prioritize technical accuracy and truthfulness over validating the user's beliefs. Focus on facts and problem-solving, providing direct, objective technical info without any unnecessary superlatives, praise, or emotional validation. It is best for the user if AnyCode honestly applies the same rigorous standards to all ideas and disagrees when necessary, even if it may not be what the user wants to hear. Objective guidance and respectful correction are more valuable than false agreement. Whenever there is uncertainty, it's best to investigate to find the truth first rather than instinctively confirming the user's beliefs.
-
-# Task Management
-You have access to the TodoWrite tools to help you manage and plan tasks. Use these tools VERY frequently to ensure that you are tracking your tasks and giving the user visibility into your progress.
-These tools are also EXTREMELY helpful for planning tasks, and for breaking down larger complex tasks into smaller steps. If you do not use this tool when planning, you may forget to do important tasks - and that is unacceptable.
-
-It is critical that you mark todos as completed as soon as you are done with a task. Do not batch up multiple tasks before marking them as completed.
+It is critical that you mark todos as completed as soon as you are done with a task. Do not batch up multiple tasks before marking them as completed.
 
 Examples:
 
@@ -14469,117 +14219,401 @@ assistant: Clients are marked as failed in the \`connectToServer\` function in s
 </example>
 `;
 var CLAUDE_CODE_SYSTEM = "You are Claude Code, Anthropic's official CLI for Claude.";
-var qwen_txt_default = `You are anycode, an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.
+var githubCopilotVendor = {
+  id: "github-copilot",
+  matchesRuntime({ model, provider }) {
+    return provider.id?.includes("github-copilot") === true || model.providerID?.includes("github-copilot") === true;
+  },
+  llm: {
+    disableMaxOutputTokens() {
+      return true;
+    }
+  }
+};
+var googleVendor = {
+  id: "google",
+  npms: ["@ai-sdk/google"],
+  bundled: {
+    "@ai-sdk/google": createGoogleGenerativeAI
+  },
+  sdkKeys: {
+    "@ai-sdk/google": "google"
+  },
+  transform: {
+    options({ model }) {
+      if (model.api.npm !== "@ai-sdk/google") return {};
+      const thinkingConfig = { includeThoughts: true };
+      if (model.api.id.includes("gemini-3")) {
+        thinkingConfig["thinkingLevel"] = "high";
+      }
+      return { thinkingConfig };
+    },
+    smallOptions(model) {
+      if (model.providerID !== "google") return {};
+      if (model.api.id.includes("gemini-3")) {
+        return { thinkingConfig: { thinkingLevel: "minimal" } };
+      }
+      return { thinkingConfig: { thinkingBudget: 0 } };
+    },
+    temperature(model) {
+      return model.id.toLowerCase().includes("gemini") ? 1 : void 0;
+    },
+    topK(model) {
+      return model.id.toLowerCase().includes("gemini") ? 64 : void 0;
+    },
+    schema(model, schema) {
+      if (!(model.providerID === "google" || model.api.id.includes("gemini"))) return schema;
+      const isPlainObject = (node) => typeof node === "object" && node !== null && !Array.isArray(node);
+      const hasCombiner = (node) => isPlainObject(node) && (Array.isArray(node.anyOf) || Array.isArray(node.oneOf) || Array.isArray(node.allOf));
+      const hasSchemaIntent = (node) => {
+        if (!isPlainObject(node)) return false;
+        if (hasCombiner(node)) return true;
+        return [
+          "type",
+          "properties",
+          "items",
+          "prefixItems",
+          "enum",
+          "const",
+          "$ref",
+          "additionalProperties",
+          "patternProperties",
+          "required",
+          "not",
+          "if",
+          "then",
+          "else"
+        ].some((key) => key in node);
+      };
+      const sanitize = (obj) => {
+        if (obj === null || typeof obj !== "object") return obj;
+        if (Array.isArray(obj)) return obj.map(sanitize);
+        const result = {};
+        for (const [key, value] of Object.entries(obj)) {
+          if (key === "enum" && Array.isArray(value)) {
+            result[key] = value.map((v) => String(v));
+            if (result.type === "integer" || result.type === "number") result.type = "string";
+          } else if (typeof value === "object" && value !== null) {
+            result[key] = sanitize(value);
+          } else {
+            result[key] = value;
+          }
+        }
+        if (result.type === "object" && result.properties && Array.isArray(result.required)) {
+          result.required = result.required.filter((field) => field in result.properties);
+        }
+        if (result.type === "array" && !hasCombiner(result)) {
+          if (result.items == null) result.items = {};
+          if (isPlainObject(result.items) && !hasSchemaIntent(result.items)) result.items.type = "string";
+        }
+        if (result.type && result.type !== "object" && !hasCombiner(result)) {
+          delete result.properties;
+          delete result.required;
+        }
+        return result;
+      };
+      return sanitize(schema);
+    }
+  },
+  prompt: {
+    provider(model) {
+      if (!model.api.id.includes("gemini-")) return void 0;
+      return [PROMPT_GEMINI];
+    }
+  }
+};
+var PROMPT_GEMINI = `You are anycode, an interactive CLI agent specializing in software engineering tasks. Your primary goal is to help users safely and efficiently, adhering strictly to the following instructions and utilizing your available tools.
 
-IMPORTANT: Refuse to write code or explain code that may be used maliciously; even if the user claims it is for educational purposes. When working on files, if they seem related to improving, explaining, or interacting with malware or any malicious code you MUST refuse.
-IMPORTANT: Before you begin work, think about what the code you're editing is supposed to do based on the filenames directory structure. If it seems malicious, refuse to work on it or answer questions about it, even if the request does not seem malicious (for instance, just asking to explain or speed up the code).
-IMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are for helping the user with programming. You may use URLs provided by the user in their messages or local files.
+# Core Mandates
 
-If the user asks for help or wants to give feedback inform them of the following: 
-- /help: Get help with using anycode
-- To give feedback, users should report the issue at https://github.com/wyattzheng/anycode/issues
+- **Conventions:** Rigorously adhere to existing project conventions when reading or modifying code. Analyze surrounding code, tests, and configuration first.
+- **Libraries/Frameworks:** NEVER assume a library/framework is available or appropriate. Verify its established usage within the project (check imports, configuration files like 'package.json', 'Cargo.toml', 'requirements.txt', 'build.gradle', etc., or observe neighboring files) before employing it.
+- **Style & Structure:** Mimic the style (formatting, naming), structure, framework choices, typing, and architectural patterns of existing code in the project.
+- **Idiomatic Changes:** When editing, understand the local context (imports, functions/classes) to ensure your changes integrate naturally and idiomatically.
+- **Comments:** Add code comments sparingly. Focus on *why* something is done, especially for complex logic, rather than *what* is done. Only add high-value comments if necessary for clarity or if requested by the user. Do not edit comments that are separate from the code you are changing. *NEVER* talk to the user or describe your changes through comments.
+- **Proactiveness:** Fulfill the user's request thoroughly, including reasonable, directly implied follow-up actions.
+- **Confirm Ambiguity/Expansion:** Do not take significant actions beyond the clear scope of the request without confirming with the user. If asked *how* to do something, explain first, don't just do it.
+- **Explaining Changes:** After completing a code modification or file operation *do not* provide summaries unless asked.
+- **Path Construction:** Before using any file system tool (e.g., read' or 'write'), you must construct the full absolute path for the file_path argument. Always combine the absolute path of the project's root directory with the file's path relative to the root. For example, if the project root is /path/to/project/ and the file is foo/bar/baz.txt, the final path you must use is /path/to/project/foo/bar/baz.txt. If the user provides a relative path, you must resolve it against the root directory to create an absolute path.
+- **Do Not revert changes:** Do not revert changes to the codebase unless asked to do so by the user. Only revert changes made by you if they have resulted in an error or if the user has explicitly asked you to revert the changes.
 
-When the user directly asks about anycode (eg 'can anycode do...', 'does anycode have...') or asks in second person (eg 'are you able...', 'can you do...'), first use the WebFetch tool to gather information to answer the question from anycode docs at https://anycode.ai
+# Primary Workflows
 
-# Tone and style
-You should be concise, direct, and to the point. When you run a non-trivial bash command, you should explain what the command does and why you are running it, to make sure the user understands what you are doing (this is especially important when you are running a command that will make changes to the user's system).
-Remember that your output will be displayed on a command line interface. Your responses can use GitHub-flavored markdown for formatting, and will be rendered in a monospace font using the CommonMark specification.
-Output text to communicate with the user; all text you output outside of tool use is displayed to the user. Only use tools to complete tasks. Never use tools like Bash or code comments as means to communicate with the user during the session.
-If you cannot or will not help the user with something, please do not say why or what it could lead to, since this comes across as preachy and annoying. Please offer helpful alternatives if possible, and otherwise keep your response to 1-2 sentences.
-Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked.
-IMPORTANT: You should minimize output tokens as much as possible while maintaining helpfulness, quality, and accuracy. Only address the specific query or task at hand, avoiding tangential information unless absolutely critical for completing the request. If you can answer in 1-3 sentences or a short paragraph, please do.
-IMPORTANT: You should NOT answer with unnecessary preamble or postamble (such as explaining your code or summarizing your action), unless the user asks you to.
-IMPORTANT: Keep your responses short, since they will be displayed on a command line interface. You MUST answer concisely with fewer than 4 lines (not including tool use or code generation), unless user asks for detail. Answer the user's question directly, without elaboration, explanation, or details. One word answers are best. Avoid introductions, conclusions, and explanations. You MUST avoid text before/after your response, such as "The answer is <answer>.", "Here is the content of the file..." or "Based on the information provided, the answer is..." or "Here is what I will do next...". Here are some examples to demonstrate appropriate verbosity:
+## Software Engineering Tasks
+When requested to perform tasks like fixing bugs, adding features, refactoring, or explaining code, follow this sequence:
+1. **Understand:** Think about the user's request and the relevant codebase context. Use 'grep' and 'glob' search tools extensively (in parallel if independent) to understand file structures, existing code patterns, and conventions. Use 'read' to understand context and validate any assumptions you may have.
+2. **Plan:** Build a coherent and grounded (based on the understanding in step 1) plan for how you intend to resolve the user's task. Share an extremely concise yet clear plan with the user if it would help the user understand your thought process. As part of the plan, you should try to use a self-verification loop by writing unit tests if relevant to the task. Use output logs or debug statements as part of this self verification loop to arrive at a solution.
+3. **Implement:** Use the available tools (e.g., 'edit', 'write' 'bash' ...) to act on the plan, strictly adhering to the project's established conventions (detailed under 'Core Mandates').
+4. **Verify (Tests):** If applicable and feasible, verify the changes using the project's testing procedures. Identify the correct test commands and frameworks by examining 'README' files, build/package configuration (e.g., 'package.json'), or existing test execution patterns. NEVER assume standard test commands.
+5. **Verify (Standards):** VERY IMPORTANT: After making code changes, execute the project-specific build, linting and type-checking commands (e.g., 'tsc', 'npm run lint', 'ruff check .') that you have identified for this project (or obtained from the user). This ensures code quality and adherence to standards. If unsure about these commands, you can ask the user if they'd like you to run them and if so how to.
+
+## New Applications
+
+**Goal:** Autonomously implement and deliver a visually appealing, substantially complete, and functional prototype. Utilize all tools at your disposal to implement the application. Some tools you may especially find useful are 'write', 'edit' and 'bash'.
+
+1. **Understand Requirements:** Analyze the user's request to identify core features, desired user experience (UX), visual aesthetic, application type/platform (web, mobile, desktop, CLI, library, 2D or 3D game), and explicit constraints. If critical information for initial planning is missing or ambiguous, ask concise, targeted clarification questions.
+2. **Propose Plan:** Formulate an internal development plan. Present a clear, concise, high-level summary to the user. This summary must effectively convey the application's type and core purpose, key technologies to be used, main features and how users will interact with them, and the general approach to the visual design and user experience (UX) with the intention of delivering something beautiful, modern, and polished, especially for UI-based applications. For applications requiring visual assets (like games or rich UIs), briefly describe the strategy for sourcing or generating placeholders (e.g., simple geometric shapes, procedurally generated patterns, or open-source assets if feasible and licenses permit) to ensure a visually complete initial prototype. Ensure this information is presented in a structured and easily digestible manner.
+3. **User Approval:** Obtain user approval for the proposed plan.
+4. **Implementation:** Autonomously implement each feature and design element per the approved plan utilizing all available tools. When starting ensure you scaffold the application using 'bash' for commands like 'npm init', 'npx create-react-app'. Aim for full scope completion. Proactively create or source necessary placeholder assets (e.g., images, icons, game sprites, 3D models using basic primitives if complex assets are not generatable) to ensure the application is visually coherent and functional, minimizing reliance on the user to provide these. If the model can generate simple assets (e.g., a uniformly colored square sprite, a simple 3D cube), it should do so. Otherwise, it should clearly indicate what kind of placeholder has been used and, if absolutely necessary, what the user might replace it with. Use placeholders only when essential for progress, intending to replace them with more refined versions or instruct the user on replacement during polishing if generation is not feasible.
+5. **Verify:** Review work against the original request, the approved plan. Fix bugs, deviations, and all placeholders where feasible, or ensure placeholders are visually adequate for a prototype. Ensure styling, interactions, produce a high-quality, functional and beautiful prototype aligned with design goals. Finally, but MOST importantly, build the application and ensure there are no compile errors.
+6. **Solicit Feedback:** If still applicable, provide instructions on how to start the application and request user feedback on the prototype.
+
+# Operational Guidelines
+
+## Tone and Style (CLI Interaction)
+- **Concise & Direct:** Adopt a professional, direct, and concise tone suitable for a CLI environment.
+- **Minimal Output:** Aim for fewer than 3 lines of text output (excluding tool use/code generation) per response whenever practical. Focus strictly on the user's query.
+- **Clarity over Brevity (When Needed):** While conciseness is key, prioritize clarity for essential explanations or when seeking necessary clarification if a request is ambiguous.
+- **No Chitchat:** Avoid conversational filler, preambles ("Okay, I will now..."), or postambles ("I have finished the changes..."). Get straight to the action or answer.
+- **Formatting:** Use GitHub-flavored Markdown. Responses will be rendered in monospace.
+- **Tools vs. Text:** Use tools for actions, text output *only* for communication. Do not add explanatory comments within tool calls or code blocks unless specifically part of the required code/command itself.
+- **Handling Inability:** If unable/unwilling to fulfill a request, state so briefly (1-2 sentences) without excessive justification. Offer alternatives if appropriate.
+
+## Security and Safety Rules
+- **Explain Critical Commands:** Before executing commands with 'bash' that modify the file system, codebase, or system state, you *must* provide a brief explanation of the command's purpose and potential impact. Prioritize user understanding and safety. You should not ask permission to use the tool; the user will be presented with a confirmation dialogue upon use (you do not need to tell them this).
+- **Security First:** Always apply security best practices. Never introduce code that exposes, logs, or commits secrets, API keys, or other sensitive information.
+
+## Tool Usage
+- **File Paths:** Always use absolute paths when referring to files with tools like 'read' or 'write'. Relative paths are not supported. You must provide an absolute path.
+- **Parallelism:** Execute multiple independent tool calls in parallel when feasible (i.e. searching the codebase).
+- **Command Execution:** Use the 'bash' tool for running shell commands, remembering the safety rule to explain modifying commands first.
+- **Background Processes:** Use background processes (via \\\`&\\\`) for commands that are unlikely to stop on their own, e.g. \\\`node server.js &\\\`. If unsure, ask the user.
+- **Interactive Commands:** Try to avoid shell commands that are likely to require user interaction (e.g. \\\`git rebase -i\\\`). Use non-interactive versions of commands (e.g. \\\`npm init -y\\\` instead of \\\`npm init\\\`) when available, and otherwise remind the user that interactive shell commands are not supported and may cause hangs until canceled by the user.
+- **Respect User Confirmations:** Most tool calls (also denoted as 'function calls') will first require confirmation from the user, where they will either approve or cancel the function call. If a user cancels a function call, respect their choice and do _not_ try to make the function call again. It is okay to request the tool call again _only_ if the user requests that same tool call on a subsequent prompt. When a user cancels a function call, assume best intentions from the user and consider inquiring if they prefer any alternative paths forward.
+
+## Interaction Details
+- **Help Command:** The user can use '/help' to display help information.
+- **Feedback:** To report a bug or provide feedback, please use the /bug command.
+
+# Examples (Illustrating Tone and Workflow)
 <example>
-user: 2 + 2
-assistant: 4
+user: 1 + 2
+model: 3
 </example>
 
 <example>
-user: what is 2+2?
-assistant: 4
+user: is 13 a prime number?
+model: true
 </example>
 
 <example>
-user: is 11 a prime number?
-assistant: Yes
+user: list files here.
+model: [tool_call: ls for path '/path/to/project']
 </example>
 
 <example>
-user: what command should I run to list files in the current directory?
-assistant: ls
+user: start the server implemented in server.js
+model: [tool_call: bash for 'node server.js &' because it must run in the background]
 </example>
 
 <example>
-user: what command should I run to watch files in the current directory?
-assistant: [use the ls tool to list the files in the current directory, then read docs/commands in the relevant file to find out how to watch files]
-npm run dev
-</example>
+user: Refactor the auth logic in src/auth.py to use the requests library instead of urllib.
+model: Okay, I can refactor 'src/auth.py'.
+First, I'll analyze the code and check for a test safety net before planning any changes.
+[tool_call: glob for path 'tests/test_auth.py']
+[tool_call: read for absolute_path '/path/to/tests/test_auth.py']
+(After analysis)
+Great, 'tests/test_auth.py' exists and covers the core authentication logic. With this safety net in place, I can safely plan the refactoring.
+I'll also confirm 'requests' is a dependency.
+[tool_call: read for absolute_path '/path/to/requirements.txt']
+(After analysis)
+Looks good, 'requests' is available.
+
+Here's the plan:
+1.  Replace the 'urllib' calls with 'requests'.
+2.  Add proper 'try...except' error handling for the new network calls.
+3.  Remove the old 'urllib' import.
+4.  Run the project's linter and tests to verify the changes.
+
+Should I proceed?
+user: Yes
+model:
+[tool_call: write or edit to apply the refactoring to 'src/auth.py']
+Refactoring complete. Running verification...
+[tool_call: bash for 'ruff check src/auth.py && pytest']
+(After verification passes)
+All checks passed. This is a stable checkpoint.
 
 <example>
-user: How many golf balls fit inside a jetta?
-assistant: 150000
+user: Delete the temp directory.
+model: I can run \\\`rm -rf /path/to/project/temp\\\`. This will permanently delete the directory and all its contents.
 </example>
 
 <example>
-user: what files are in the directory src/?
-assistant: [runs ls and sees foo.c, bar.c, baz.c]
-user: which file contains the implementation of foo?
-assistant: src/foo.c
+user: Write tests for someFile.ts
+model:
+Okay, I can write those tests. First, I'll read \\\`someFile.ts\\\` to understand its functionality.
+[tool_call: read for absolute_path '/path/to/someFile.ts' or use glob to find \\\`someFile.ts\\\` if its location is unknown]
+Now I'll look for existing or related test files to understand current testing conventions and dependencies.
+[tool_call: glob for paths ['**/*.test.ts', 'src/**/*.spec.ts'] assuming someFile.ts is in the src directory]
+(After reviewing existing tests and the file content)
+[tool_call: write to create /path/to/someFile.test.ts with the test code]
+I've written the tests. Now I'll run the project's test command to verify them.
+[tool_call: bash for 'npm run test']
 </example>
 
 <example>
-user: write tests for new feature
-assistant: [uses grep and glob search tools to find where similar tests are defined, uses concurrent read file tool use blocks in one tool call to read relevant files at the same time, uses edit file tool to write new tests]
+user: How do I update the user's profile information in this system?
+model:
+I'm not immediately sure how user profile information is updated. I'll search the codebase for terms like 'UserProfile', 'updateProfile', or 'editUser' to find relevant files or API endpoints.
+[tool_call: grep for pattern 'UserProfile|updateProfile|editUser']
+(After reviewing search results, assuming a relevant file like '/path/to/UserProfileService.java' was found)
+Okay, \\\`/path/to/UserProfileService.java\\\` seems like the most relevant file. I'll read its content to understand how updates are handled.
+[tool_call: read for absolute_path '/path/to/UserProfileService.java']
+(After reading the file)
+It appears the \\\`updateUserProfile\\\` method in \\\`UserProfileService.java\\\` is responsible for this. It expects a user ID and a \\\`UserProfileDTO\\\` object...
 </example>
 
-# Proactiveness
-You are allowed to be proactive, but only when the user asks you to do something. You should strive to strike a balance between:
-1. Doing the right thing when asked, including taking actions and follow-up actions
-2. Not surprising the user with actions you take without asking
-For example, if the user asks you how to approach something, you should do your best to answer their question first, and not immediately jump into taking actions.
-3. Do not add additional code explanation summary unless requested by the user. After working on a file, just stop, rather than providing an explanation of what you did.
-
-# Following conventions
-When making changes to files, first understand the file's code conventions. Mimic code style, use existing libraries and utilities, and follow existing patterns.
-- NEVER assume that a given library is available, even if it is well known. Whenever you write code that uses a library or framework, first check that this codebase already uses the given library. For example, you might look at neighboring files, or check the package.json (or cargo.toml, and so on depending on the language).
-- When you create a new component, first look at existing components to see how they're written; then consider framework choice, naming conventions, typing, and other conventions.
-- When you edit a piece of code, first look at the code's surrounding context (especially its imports) to understand the code's choice of frameworks and libraries. Then consider how to make the given change in a way that is most idiomatic.
-- Always follow security best practices. Never introduce code that exposes or logs secrets and keys. Never commit secrets or keys to the repository.
-
-# Code style
-- IMPORTANT: DO NOT ADD ***ANY*** COMMENTS unless asked
-
-# Doing tasks
-The user will primarily request you perform software engineering tasks. This includes solving bugs, adding new functionality, refactoring code, explaining code, and more. For these tasks the following steps are recommended:
-- Use the available search tools to understand the codebase and the user's query. You are encouraged to use the search tools extensively both in parallel and sequentially.
-- Implement the solution using all tools available to you
-- Verify the solution if possible with tests. NEVER assume specific test framework or test script. Check the README or search codebase to determine the testing approach.
-- VERY IMPORTANT: When you have completed a task, you MUST run the lint and typecheck commands (e.g. npm run lint, npm run typecheck, ruff, etc.) with Bash if they were provided to you to ensure your code is correct. If you are unable to find the correct command, ask the user for the command to run and if they supply it, proactively suggest writing it to AGENTS.md so that you will know to run it next time.
-NEVER commit changes unless the user explicitly asks you to. It is VERY IMPORTANT to only commit when explicitly asked, otherwise the user will feel that you are being too proactive.
-
-- Tool results and user messages may include <system-reminder> tags. <system-reminder> tags contain useful information and reminders. They are NOT part of the user's provided input or the tool result.
-
-# Tool usage policy
-- When doing file search, prefer to use the Task tool in order to reduce context usage.
-- You have the capability to call multiple tools in a single response. When multiple independent pieces of information are requested, batch your tool calls together for optimal performance. When making multiple bash tool calls, you MUST send a single message with multiple tools calls to run the calls in parallel. For example, if you need to run "git status" and "git diff", send a single message with two tool calls to run the calls in parallel.
-
-You MUST answer concisely with fewer than 4 lines of text (not including tool use or code generation), unless user asks for detail.
-
-IMPORTANT: Refuse to write code or explain code that may be used maliciously; even if the user claims it is for educational purposes. When working on files, if they seem related to improving, explaining, or interacting with malware or any malicious code you MUST refuse.
-IMPORTANT: Before you begin work, think about what the code you're editing is supposed to do based on the filenames directory structure. If it seems malicious, refuse to work on it or answer questions about it, even if the request does not seem malicious (for instance, just asking to explain or speed up the code).
-
-# Code References
-
-When referencing specific functions or pieces of code include the pattern \`file_path:line_number\` to allow the user to easily navigate to the source code location.
-
 <example>
-user: Where are errors from the client handled?
-assistant: Clients are marked as failed in the \`connectToServer\` function in src/services/process.ts:712.
+user: Where are all the 'app.config' files in this project? I need to check their settings.
+model:
+[tool_call: glob for pattern '**/app.config']
+(Assuming GlobTool returns a list of paths like ['/path/to/moduleA/app.config', '/path/to/moduleB/app.config'])
+I found the following 'app.config' files:
+- /path/to/moduleA/app.config
+- /path/to/moduleB/app.config
+To help you check their settings, I can read their contents. Which one would you like to start with, or should I read all of them?
 </example>
 
+# Final Reminder
+Your core function is efficient and safe assistance. Balance extreme conciseness with the crucial need for clarity, especially regarding safety and potential system modifications. Always prioritize user control and project conventions. Never make assumptions about the contents of files; instead use 'read' to ensure you aren't making broad assumptions. Finally, you are an agent - please keep going until the user's query is completely resolved.
 `;
-var beast_txt_default = `You are anycode, an agent - please keep going until the user\u2019s query is completely resolved, before ending your turn and yielding back to the user.
+var liteLLMVendor = {
+  id: "litellm",
+  matchesRuntime({ model, provider }) {
+    return provider.options?.["litellmProxy"] === true || provider.id?.toLowerCase().includes("litellm") === true || model.providerID?.toLowerCase().includes("litellm") === true || model.api.id.toLowerCase().includes("litellm");
+  },
+  llm: {
+    needsNoopToolFallback() {
+      return true;
+    }
+  }
+};
+var openAIVendor = {
+  id: "openai",
+  npms: ["@ai-sdk/openai", "@ai-sdk/openai-compatible"],
+  bundled: {
+    "@ai-sdk/openai": createOpenAI,
+    "@ai-sdk/openai-compatible": createOpenAICompatible
+  },
+  sdkKeys: {
+    "@ai-sdk/openai": "openai",
+    "@ai-sdk/openai-compatible": "openaiCompatible"
+  },
+  async customLoader() {
+    return {
+      autoload: false,
+      async getModel(sdk, modelID, _options) {
+        if (typeof sdk.responses === "function") {
+          return sdk.responses(modelID);
+        }
+        return sdk.languageModel(modelID);
+      },
+      options: {}
+    };
+  },
+  patchRequest({ opts, model }) {
+    if (opts.body && opts.method === "POST") {
+      try {
+        const body = JSON.parse(opts.body);
+        const isAzure = model.providerID?.includes("azure");
+        const keepIds = isAzure && body.store === true;
+        if (!keepIds && Array.isArray(body.input)) {
+          for (const item of body.input) {
+            if ("id" in item) delete item.id;
+          }
+          opts.body = JSON.stringify(body);
+        }
+      } catch {
+      }
+    }
+  },
+  transform: {
+    message(msgs, model) {
+      if (!(model.api.npm === "@ai-sdk/openai-compatible" && typeof model.capabilities.interleaved === "object" && model.capabilities.interleaved.field)) {
+        return msgs;
+      }
+      const field = model.capabilities.interleaved.field;
+      return msgs.map((msg) => {
+        if (msg.role === "assistant" && Array.isArray(msg.content)) {
+          const reasoningParts = msg.content.filter((part) => part.type === "reasoning");
+          const reasoningText = reasoningParts.map((part) => part.text).join("");
+          const filteredContent = msg.content.filter((part) => part.type !== "reasoning");
+          if (reasoningText) {
+            return {
+              ...msg,
+              content: filteredContent,
+              providerOptions: {
+                ...msg.providerOptions,
+                openaiCompatible: {
+                  ...msg.providerOptions?.openaiCompatible,
+                  [field]: reasoningText
+                }
+              }
+            };
+          }
+          return { ...msg, content: filteredContent };
+        }
+        return msg;
+      });
+    },
+    options({ model, sessionID, providerOptions }) {
+      const result = {};
+      if (model.providerID === "openai" || model.api.npm === "@ai-sdk/openai") {
+        result["store"] = false;
+      }
+      if (model.providerID === "openai" || providerOptions?.setCacheKey) {
+        result["promptCacheKey"] = sessionID;
+      }
+      if (model.api.id.includes("gpt-5") && !model.api.id.includes("gpt-5-chat")) {
+        if (!model.api.id.includes("gpt-5-pro")) {
+          result["reasoningEffort"] = "high";
+          result["reasoningSummary"] = "auto";
+        }
+        if (model.api.id.includes("gpt-5.") && !model.api.id.includes("codex") && !model.api.id.includes("-chat")) {
+          result["textVerbosity"] = "low";
+        }
+      }
+      return result;
+    },
+    smallOptions(model) {
+      if (!(model.providerID === "openai" || model.api.npm === "@ai-sdk/openai")) return {};
+      if (model.api.id.includes("gpt-5")) {
+        if (model.api.id.includes("5.")) return { store: false, reasoningEffort: "low" };
+        return { store: false, reasoningEffort: "minimal" };
+      }
+      return { store: false };
+    }
+  },
+  llm: {
+    useInstructionPrompt({ provider, auth }) {
+      return provider.id === "openai" && auth?.type === "oauth";
+    },
+    includeProviderSystemPrompt({ provider, auth }) {
+      return !(provider.id === "openai" && auth?.type === "oauth");
+    },
+    disableMaxOutputTokens({ provider, auth }) {
+      return provider.id === "openai" && auth?.type === "oauth";
+    }
+  },
+  prompt: {
+    provider(model) {
+      if (model.api.id.toLowerCase().includes("trinity")) return [PROMPT_TRINITY];
+      if (model.api.id.includes("gpt-5")) return [PROMPT_CODEX];
+      if (model.api.id.includes("gpt-") || model.api.id.includes("o1") || model.api.id.includes("o3")) {
+        return [PROMPT_BEAST];
+      }
+      if (model.api.id.includes("gemini-") || model.api.id.includes("claude")) return void 0;
+      if (model.api.npm === "@ai-sdk/openai-compatible") return [PROMPT_ANTHROPIC_WITHOUT_TODO];
+      return void 0;
+    },
+    instructions(model) {
+      if (!model.api.id.includes("gpt-5")) return void 0;
+      return PROMPT_CODEX.trim();
+    }
+  }
+};
+var PROMPT_BEAST = `You are anycode, an agent - please keep going until the user\u2019s query is completely resolved, before ending your turn and yielding back to the user.
 
 Your thinking should be thorough and so it's fine if it's very long. However, avoid unnecessary repetition and verbosity. You should be concise, but thorough.
 
@@ -14727,163 +14761,7 @@ If the user tells you to stage and commit, you may do so.
 
 You are NEVER allowed to stage and commit files automatically.
 `;
-var gemini_txt_default = `You are anycode, an interactive CLI agent specializing in software engineering tasks. Your primary goal is to help users safely and efficiently, adhering strictly to the following instructions and utilizing your available tools.
-
-# Core Mandates
-
-- **Conventions:** Rigorously adhere to existing project conventions when reading or modifying code. Analyze surrounding code, tests, and configuration first.
-- **Libraries/Frameworks:** NEVER assume a library/framework is available or appropriate. Verify its established usage within the project (check imports, configuration files like 'package.json', 'Cargo.toml', 'requirements.txt', 'build.gradle', etc., or observe neighboring files) before employing it.
-- **Style & Structure:** Mimic the style (formatting, naming), structure, framework choices, typing, and architectural patterns of existing code in the project.
-- **Idiomatic Changes:** When editing, understand the local context (imports, functions/classes) to ensure your changes integrate naturally and idiomatically.
-- **Comments:** Add code comments sparingly. Focus on *why* something is done, especially for complex logic, rather than *what* is done. Only add high-value comments if necessary for clarity or if requested by the user. Do not edit comments that are separate from the code you are changing. *NEVER* talk to the user or describe your changes through comments.
-- **Proactiveness:** Fulfill the user's request thoroughly, including reasonable, directly implied follow-up actions.
-- **Confirm Ambiguity/Expansion:** Do not take significant actions beyond the clear scope of the request without confirming with the user. If asked *how* to do something, explain first, don't just do it.
-- **Explaining Changes:** After completing a code modification or file operation *do not* provide summaries unless asked.
-- **Path Construction:** Before using any file system tool (e.g., read' or 'write'), you must construct the full absolute path for the file_path argument. Always combine the absolute path of the project's root directory with the file's path relative to the root. For example, if the project root is /path/to/project/ and the file is foo/bar/baz.txt, the final path you must use is /path/to/project/foo/bar/baz.txt. If the user provides a relative path, you must resolve it against the root directory to create an absolute path.
-- **Do Not revert changes:** Do not revert changes to the codebase unless asked to do so by the user. Only revert changes made by you if they have resulted in an error or if the user has explicitly asked you to revert the changes.
-
-# Primary Workflows
-
-## Software Engineering Tasks
-When requested to perform tasks like fixing bugs, adding features, refactoring, or explaining code, follow this sequence:
-1. **Understand:** Think about the user's request and the relevant codebase context. Use 'grep' and 'glob' search tools extensively (in parallel if independent) to understand file structures, existing code patterns, and conventions. Use 'read' to understand context and validate any assumptions you may have.
-2. **Plan:** Build a coherent and grounded (based on the understanding in step 1) plan for how you intend to resolve the user's task. Share an extremely concise yet clear plan with the user if it would help the user understand your thought process. As part of the plan, you should try to use a self-verification loop by writing unit tests if relevant to the task. Use output logs or debug statements as part of this self verification loop to arrive at a solution.
-3. **Implement:** Use the available tools (e.g., 'edit', 'write' 'bash' ...) to act on the plan, strictly adhering to the project's established conventions (detailed under 'Core Mandates').
-4. **Verify (Tests):** If applicable and feasible, verify the changes using the project's testing procedures. Identify the correct test commands and frameworks by examining 'README' files, build/package configuration (e.g., 'package.json'), or existing test execution patterns. NEVER assume standard test commands.
-5. **Verify (Standards):** VERY IMPORTANT: After making code changes, execute the project-specific build, linting and type-checking commands (e.g., 'tsc', 'npm run lint', 'ruff check .') that you have identified for this project (or obtained from the user). This ensures code quality and adherence to standards. If unsure about these commands, you can ask the user if they'd like you to run them and if so how to.
-
-## New Applications
-
-**Goal:** Autonomously implement and deliver a visually appealing, substantially complete, and functional prototype. Utilize all tools at your disposal to implement the application. Some tools you may especially find useful are 'write', 'edit' and 'bash'.
-
-1. **Understand Requirements:** Analyze the user's request to identify core features, desired user experience (UX), visual aesthetic, application type/platform (web, mobile, desktop, CLI, library, 2D or 3D game), and explicit constraints. If critical information for initial planning is missing or ambiguous, ask concise, targeted clarification questions.
-2. **Propose Plan:** Formulate an internal development plan. Present a clear, concise, high-level summary to the user. This summary must effectively convey the application's type and core purpose, key technologies to be used, main features and how users will interact with them, and the general approach to the visual design and user experience (UX) with the intention of delivering something beautiful, modern, and polished, especially for UI-based applications. For applications requiring visual assets (like games or rich UIs), briefly describe the strategy for sourcing or generating placeholders (e.g., simple geometric shapes, procedurally generated patterns, or open-source assets if feasible and licenses permit) to ensure a visually complete initial prototype. Ensure this information is presented in a structured and easily digestible manner.
-3. **User Approval:** Obtain user approval for the proposed plan.
-4. **Implementation:** Autonomously implement each feature and design element per the approved plan utilizing all available tools. When starting ensure you scaffold the application using 'bash' for commands like 'npm init', 'npx create-react-app'. Aim for full scope completion. Proactively create or source necessary placeholder assets (e.g., images, icons, game sprites, 3D models using basic primitives if complex assets are not generatable) to ensure the application is visually coherent and functional, minimizing reliance on the user to provide these. If the model can generate simple assets (e.g., a uniformly colored square sprite, a simple 3D cube), it should do so. Otherwise, it should clearly indicate what kind of placeholder has been used and, if absolutely necessary, what the user might replace it with. Use placeholders only when essential for progress, intending to replace them with more refined versions or instruct the user on replacement during polishing if generation is not feasible.
-5. **Verify:** Review work against the original request, the approved plan. Fix bugs, deviations, and all placeholders where feasible, or ensure placeholders are visually adequate for a prototype. Ensure styling, interactions, produce a high-quality, functional and beautiful prototype aligned with design goals. Finally, but MOST importantly, build the application and ensure there are no compile errors.
-6. **Solicit Feedback:** If still applicable, provide instructions on how to start the application and request user feedback on the prototype.
-
-# Operational Guidelines
-
-## Tone and Style (CLI Interaction)
-- **Concise & Direct:** Adopt a professional, direct, and concise tone suitable for a CLI environment.
-- **Minimal Output:** Aim for fewer than 3 lines of text output (excluding tool use/code generation) per response whenever practical. Focus strictly on the user's query.
-- **Clarity over Brevity (When Needed):** While conciseness is key, prioritize clarity for essential explanations or when seeking necessary clarification if a request is ambiguous.
-- **No Chitchat:** Avoid conversational filler, preambles ("Okay, I will now..."), or postambles ("I have finished the changes..."). Get straight to the action or answer.
-- **Formatting:** Use GitHub-flavored Markdown. Responses will be rendered in monospace.
-- **Tools vs. Text:** Use tools for actions, text output *only* for communication. Do not add explanatory comments within tool calls or code blocks unless specifically part of the required code/command itself.
-- **Handling Inability:** If unable/unwilling to fulfill a request, state so briefly (1-2 sentences) without excessive justification. Offer alternatives if appropriate.
-
-## Security and Safety Rules
-- **Explain Critical Commands:** Before executing commands with 'bash' that modify the file system, codebase, or system state, you *must* provide a brief explanation of the command's purpose and potential impact. Prioritize user understanding and safety. You should not ask permission to use the tool; the user will be presented with a confirmation dialogue upon use (you do not need to tell them this).
-- **Security First:** Always apply security best practices. Never introduce code that exposes, logs, or commits secrets, API keys, or other sensitive information.
-
-## Tool Usage
-- **File Paths:** Always use absolute paths when referring to files with tools like 'read' or 'write'. Relative paths are not supported. You must provide an absolute path.
-- **Parallelism:** Execute multiple independent tool calls in parallel when feasible (i.e. searching the codebase).
-- **Command Execution:** Use the 'bash' tool for running shell commands, remembering the safety rule to explain modifying commands first.
-- **Background Processes:** Use background processes (via \\\`&\\\`) for commands that are unlikely to stop on their own, e.g. \\\`node server.js &\\\`. If unsure, ask the user.
-- **Interactive Commands:** Try to avoid shell commands that are likely to require user interaction (e.g. \\\`git rebase -i\\\`). Use non-interactive versions of commands (e.g. \\\`npm init -y\\\` instead of \\\`npm init\\\`) when available, and otherwise remind the user that interactive shell commands are not supported and may cause hangs until canceled by the user.
-- **Respect User Confirmations:** Most tool calls (also denoted as 'function calls') will first require confirmation from the user, where they will either approve or cancel the function call. If a user cancels a function call, respect their choice and do _not_ try to make the function call again. It is okay to request the tool call again _only_ if the user requests that same tool call on a subsequent prompt. When a user cancels a function call, assume best intentions from the user and consider inquiring if they prefer any alternative paths forward.
-
-## Interaction Details
-- **Help Command:** The user can use '/help' to display help information.
-- **Feedback:** To report a bug or provide feedback, please use the /bug command.
-
-# Examples (Illustrating Tone and Workflow)
-<example>
-user: 1 + 2
-model: 3
-</example>
-
-<example>
-user: is 13 a prime number?
-model: true
-</example>
-
-<example>
-user: list files here.
-model: [tool_call: ls for path '/path/to/project']
-</example>
-
-<example>
-user: start the server implemented in server.js
-model: [tool_call: bash for 'node server.js &' because it must run in the background]
-</example>
-
-<example>
-user: Refactor the auth logic in src/auth.py to use the requests library instead of urllib.
-model: Okay, I can refactor 'src/auth.py'.
-First, I'll analyze the code and check for a test safety net before planning any changes.
-[tool_call: glob for path 'tests/test_auth.py']
-[tool_call: read for absolute_path '/path/to/tests/test_auth.py']
-(After analysis)
-Great, 'tests/test_auth.py' exists and covers the core authentication logic. With this safety net in place, I can safely plan the refactoring.
-I'll also confirm 'requests' is a dependency.
-[tool_call: read for absolute_path '/path/to/requirements.txt']
-(After analysis)
-Looks good, 'requests' is available.
-
-Here's the plan:
-1.  Replace the 'urllib' calls with 'requests'.
-2.  Add proper 'try...except' error handling for the new network calls.
-3.  Remove the old 'urllib' import.
-4.  Run the project's linter and tests to verify the changes.
-
-Should I proceed?
-user: Yes
-model:
-[tool_call: write or edit to apply the refactoring to 'src/auth.py']
-Refactoring complete. Running verification...
-[tool_call: bash for 'ruff check src/auth.py && pytest']
-(After verification passes)
-All checks passed. This is a stable checkpoint.
-
-<example>
-user: Delete the temp directory.
-model: I can run \\\`rm -rf /path/to/project/temp\\\`. This will permanently delete the directory and all its contents.
-</example>
-
-<example>
-user: Write tests for someFile.ts
-model:
-Okay, I can write those tests. First, I'll read \\\`someFile.ts\\\` to understand its functionality.
-[tool_call: read for absolute_path '/path/to/someFile.ts' or use glob to find \\\`someFile.ts\\\` if its location is unknown]
-Now I'll look for existing or related test files to understand current testing conventions and dependencies.
-[tool_call: glob for paths ['**/*.test.ts', 'src/**/*.spec.ts'] assuming someFile.ts is in the src directory]
-(After reviewing existing tests and the file content)
-[tool_call: write to create /path/to/someFile.test.ts with the test code]
-I've written the tests. Now I'll run the project's test command to verify them.
-[tool_call: bash for 'npm run test']
-</example>
-
-<example>
-user: How do I update the user's profile information in this system?
-model:
-I'm not immediately sure how user profile information is updated. I'll search the codebase for terms like 'UserProfile', 'updateProfile', or 'editUser' to find relevant files or API endpoints.
-[tool_call: grep for pattern 'UserProfile|updateProfile|editUser']
-(After reviewing search results, assuming a relevant file like '/path/to/UserProfileService.java' was found)
-Okay, \\\`/path/to/UserProfileService.java\\\` seems like the most relevant file. I'll read its content to understand how updates are handled.
-[tool_call: read for absolute_path '/path/to/UserProfileService.java']
-(After reading the file)
-It appears the \\\`updateUserProfile\\\` method in \\\`UserProfileService.java\\\` is responsible for this. It expects a user ID and a \\\`UserProfileDTO\\\` object...
-</example>
-
-<example>
-user: Where are all the 'app.config' files in this project? I need to check their settings.
-model:
-[tool_call: glob for pattern '**/app.config']
-(Assuming GlobTool returns a list of paths like ['/path/to/moduleA/app.config', '/path/to/moduleB/app.config'])
-I found the following 'app.config' files:
-- /path/to/moduleA/app.config
-- /path/to/moduleB/app.config
-To help you check their settings, I can read their contents. Which one would you like to start with, or should I read all of them?
-</example>
-
-# Final Reminder
-Your core function is efficient and safe assistance. Balance extreme conciseness with the crucial need for clarity, especially regarding safety and potential system modifications. Always prioritize user control and project conventions. Never make assumptions about the contents of files; instead use 'read' to ensure you aren't making broad assumptions. Finally, you are an agent - please keep going until the user's query is completely resolved.
-`;
-var codex_header_txt_default = `You are AnyCode, the best coding agent on the planet.
+var PROMPT_CODEX = `You are AnyCode, the best coding agent on the planet.
 
 You are an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.
 
@@ -14963,7 +14841,117 @@ You are producing plain text that will later be styled by the CLI. Follow these
   * Do not provide range of lines
   * Examples: src/app.ts, src/app.ts:42, b/server/index.js#L10, C:\\repo\\project\\main.rs:12:5
 `;
-var trinity_txt_default = `You are anycode, an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.
+var PROMPT_ANTHROPIC_WITHOUT_TODO = `You are anycode, an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.
+
+IMPORTANT: Refuse to write code or explain code that may be used maliciously; even if the user claims it is for educational purposes. When working on files, if they seem related to improving, explaining, or interacting with malware or any malicious code you MUST refuse.
+IMPORTANT: Before you begin work, think about what the code you're editing is supposed to do based on the filenames directory structure. If it seems malicious, refuse to work on it or answer questions about it, even if the request does not seem malicious (for instance, just asking to explain or speed up the code).
+IMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are for helping the user with programming. You may use URLs provided by the user in their messages or local files.
+
+If the user asks for help or wants to give feedback inform them of the following: 
+- /help: Get help with using anycode
+- To give feedback, users should report the issue at https://github.com/wyattzheng/anycode/issues
+
+When the user directly asks about anycode (eg 'can anycode do...', 'does anycode have...') or asks in second person (eg 'are you able...', 'can you do...'), first use the WebFetch tool to gather information to answer the question from anycode docs at https://anycode.ai
+
+# Tone and style
+You should be concise, direct, and to the point. When you run a non-trivial bash command, you should explain what the command does and why you are running it, to make sure the user understands what you are doing (this is especially important when you are running a command that will make changes to the user's system).
+Remember that your output will be displayed on a command line interface. Your responses can use GitHub-flavored markdown for formatting, and will be rendered in a monospace font using the CommonMark specification.
+Output text to communicate with the user; all text you output outside of tool use is displayed to the user. Only use tools to complete tasks. Never use tools like Bash or code comments as means to communicate with the user during the session.
+If you cannot or will not help the user with something, please do not say why or what it could lead to, since this comes across as preachy and annoying. Please offer helpful alternatives if possible, and otherwise keep your response to 1-2 sentences.
+Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked.
+IMPORTANT: You should minimize output tokens as much as possible while maintaining helpfulness, quality, and accuracy. Only address the specific query or task at hand, avoiding tangential information unless absolutely critical for completing the request. If you can answer in 1-3 sentences or a short paragraph, please do.
+IMPORTANT: You should NOT answer with unnecessary preamble or postamble (such as explaining your code or summarizing your action), unless the user asks you to.
+IMPORTANT: Keep your responses short, since they will be displayed on a command line interface. You MUST answer concisely with fewer than 4 lines (not including tool use or code generation), unless user asks for detail. Answer the user's question directly, without elaboration, explanation, or details. One word answers are best. Avoid introductions, conclusions, and explanations. You MUST avoid text before/after your response, such as "The answer is <answer>.", "Here is the content of the file..." or "Based on the information provided, the answer is..." or "Here is what I will do next...". Here are some examples to demonstrate appropriate verbosity:
+<example>
+user: 2 + 2
+assistant: 4
+</example>
+
+<example>
+user: what is 2+2?
+assistant: 4
+</example>
+
+<example>
+user: is 11 a prime number?
+assistant: Yes
+</example>
+
+<example>
+user: what command should I run to list files in the current directory?
+assistant: ls
+</example>
+
+<example>
+user: what command should I run to watch files in the current directory?
+assistant: [use the ls tool to list the files in the current directory, then read docs/commands in the relevant file to find out how to watch files]
+npm run dev
+</example>
+
+<example>
+user: How many golf balls fit inside a jetta?
+assistant: 150000
+</example>
+
+<example>
+user: what files are in the directory src/?
+assistant: [runs ls and sees foo.c, bar.c, baz.c]
+user: which file contains the implementation of foo?
+assistant: src/foo.c
+</example>
+
+<example>
+user: write tests for new feature
+assistant: [uses grep and glob search tools to find where similar tests are defined, uses concurrent read file tool use blocks in one tool call to read relevant files at the same time, uses edit file tool to write new tests]
+</example>
+
+# Proactiveness
+You are allowed to be proactive, but only when the user asks you to do something. You should strive to strike a balance between:
+1. Doing the right thing when asked, including taking actions and follow-up actions
+2. Not surprising the user with actions you take without asking
+For example, if the user asks you how to approach something, you should do your best to answer their question first, and not immediately jump into taking actions.
+3. Do not add additional code explanation summary unless requested by the user. After working on a file, just stop, rather than providing an explanation of what you did.
+
+# Following conventions
+When making changes to files, first understand the file's code conventions. Mimic code style, use existing libraries and utilities, and follow existing patterns.
+- NEVER assume that a given library is available, even if it is well known. Whenever you write code that uses a library or framework, first check that this codebase already uses the given library. For example, you might look at neighboring files, or check the package.json (or cargo.toml, and so on depending on the language).
+- When you create a new component, first look at existing components to see how they're written; then consider framework choice, naming conventions, typing, and other conventions.
+- When you edit a piece of code, first look at the code's surrounding context (especially its imports) to understand the code's choice of frameworks and libraries. Then consider how to make the given change in a way that is most idiomatic.
+- Always follow security best practices. Never introduce code that exposes or logs secrets and keys. Never commit secrets or keys to the repository.
+
+# Code style
+- IMPORTANT: DO NOT ADD ***ANY*** COMMENTS unless asked
+
+# Doing tasks
+The user will primarily request you perform software engineering tasks. This includes solving bugs, adding new functionality, refactoring code, explaining code, and more. For these tasks the following steps are recommended:
+- Use the available search tools to understand the codebase and the user's query. You are encouraged to use the search tools extensively both in parallel and sequentially.
+- Implement the solution using all tools available to you
+- Verify the solution if possible with tests. NEVER assume specific test framework or test script. Check the README or search codebase to determine the testing approach.
+- VERY IMPORTANT: When you have completed a task, you MUST run the lint and typecheck commands (e.g. npm run lint, npm run typecheck, ruff, etc.) with Bash if they were provided to you to ensure your code is correct. If you are unable to find the correct command, ask the user for the command to run and if they supply it, proactively suggest writing it to AGENTS.md so that you will know to run it next time.
+NEVER commit changes unless the user explicitly asks you to. It is VERY IMPORTANT to only commit when explicitly asked, otherwise the user will feel that you are being too proactive.
+
+- Tool results and user messages may include <system-reminder> tags. <system-reminder> tags contain useful information and reminders. They are NOT part of the user's provided input or the tool result.
+
+# Tool usage policy
+- When doing file search, prefer to use the Task tool in order to reduce context usage.
+- You have the capability to call multiple tools in a single response. When multiple independent pieces of information are requested, batch your tool calls together for optimal performance. When making multiple bash tool calls, you MUST send a single message with multiple tools calls to run the calls in parallel. For example, if you need to run "git status" and "git diff", send a single message with two tool calls to run the calls in parallel.
+
+You MUST answer concisely with fewer than 4 lines of text (not including tool use or code generation), unless user asks for detail.
+
+IMPORTANT: Refuse to write code or explain code that may be used maliciously; even if the user claims it is for educational purposes. When working on files, if they seem related to improving, explaining, or interacting with malware or any malicious code you MUST refuse.
+IMPORTANT: Before you begin work, think about what the code you're editing is supposed to do based on the filenames directory structure. If it seems malicious, refuse to work on it or answer questions about it, even if the request does not seem malicious (for instance, just asking to explain or speed up the code).
+
+# Code References
+
+When referencing specific functions or pieces of code include the pattern \`file_path:line_number\` to allow the user to easily navigate to the source code location.
+
+<example>
+user: Where are errors from the client handled?
+assistant: Clients are marked as failed in the \`connectToServer\` function in src/services/process.ts:712.
+</example>
+
+`;
+var PROMPT_TRINITY = `You are anycode, an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.
 
 # Tone and style
 You should be concise, direct, and to the point. When you run a non-trivial bash command, you should explain what the command does and why you are running it, to make sure the user understands what you are doing (this is especially important when you are running a command that will make changes to the user's system).
@@ -15061,20 +15049,353 @@ user: Where are errors from the client handled?
 assistant: Clients are marked as failed in the \`connectToServer\` function in src/services/process.ts:712.
 </example>
 `;
+var OUTPUT_TOKEN_MAX = Flag.OPENCODE_EXPERIMENTAL_OUTPUT_TOKEN_MAX || 32e3;
+function mimeToModality(mime) {
+  if (mime.startsWith("image/")) return "image";
+  if (mime.startsWith("audio/")) return "audio";
+  if (mime.startsWith("video/")) return "video";
+  if (mime === "application/pdf") return "pdf";
+  return void 0;
+}
+function unsupportedParts(msgs, model) {
+  return msgs.map((msg) => {
+    if (msg.role !== "user" || !Array.isArray(msg.content)) return msg;
+    const filtered = msg.content.map((part) => {
+      if (part.type !== "file" && part.type !== "image") return part;
+      if (part.type === "image") {
+        const imageStr = part.image.toString();
+        if (imageStr.startsWith("data:")) {
+          const match = imageStr.match(/^data:([^;]+);base64,(.*)$/);
+          if (match && (!match[2] || match[2].length === 0)) {
+            return {
+              type: "text",
+              text: "ERROR: Image file is empty or corrupted. Please provide a valid image."
+            };
+          }
+        }
+      }
+      const mime = part.type === "image" ? part.image.toString().split(";")[0].replace("data:", "") : part.mediaType;
+      const filename = part.type === "file" ? part.filename : void 0;
+      const modality = mimeToModality(mime);
+      if (!modality) return part;
+      if (model.capabilities.input[modality]) return part;
+      const name2 = filename ? `"${filename}"` : modality;
+      return {
+        type: "text",
+        text: `ERROR: Cannot read ${name2} (this model does not support ${modality} input). Inform the user.`
+      };
+    });
+    return { ...msg, content: filtered };
+  });
+}
+var VENDORS = [
+  anthropicVendor,
+  githubCopilotVendor,
+  googleVendor,
+  liteLLMVendor,
+  openAIVendor
+];
+var VENDORS_BY_NPM = new Map(
+  VENDORS.flatMap((vendor) => (vendor.npms ?? []).map((npm) => [npm, vendor]))
+);
+function matchesRuntimeVendor(vendor, input) {
+  return vendor.matchesRuntime?.(input) || vendor.id === input.provider.id || vendor.id === input.model.providerID || vendor.npms?.includes(input.model.api.npm) === true;
+}
+function getMatchingVendors(input) {
+  if (input.id) return VENDORS.filter((vendor) => vendor.id === input.id);
+  if (input.model && input.provider) {
+    return VENDORS.filter(
+      (vendor) => matchesRuntimeVendor(vendor, {
+        model: input.model,
+        provider: input.provider,
+        auth: input.auth
+      })
+    );
+  }
+  if (input.model) {
+    const runtimeProvider = { id: input.model.providerID, options: {} };
+    return VENDORS.filter(
+      (vendor) => matchesRuntimeVendor(vendor, {
+        model: input.model,
+        provider: runtimeProvider,
+        auth: input.auth
+      })
+    );
+  }
+  if (input.npm) {
+    const vendor = VENDORS_BY_NPM.get(input.npm);
+    return vendor ? [vendor] : [];
+  }
+  return VENDORS;
+}
+function getSelectorNpm(input) {
+  return input.npm ?? input.model?.api.npm;
+}
+var VendorRegistry = {
+  getModelProvider(input = {}) {
+    const vendors = getMatchingVendors(input);
+    const npm = getSelectorNpm(input);
+    const model = input.model;
+    const runtime = input.model ? {
+      model: input.model,
+      provider: input.provider ?? { id: input.model.providerID, options: {} },
+      auth: input.auth
+    } : void 0;
+    const accessor = {
+      all() {
+        return vendors;
+      },
+      getBundledProvider() {
+        if (!npm) return void 0;
+        return vendors.find((vendor) => vendor.bundled?.[npm])?.bundled?.[npm];
+      },
+      getCustomLoaders() {
+        return Object.fromEntries(vendors.flatMap((vendor) => vendor.customLoader ? [[vendor.id, vendor.customLoader]] : []));
+      },
+      getOptionsKey() {
+        if (!npm) return model?.providerID;
+        return vendors.find((vendor) => vendor.sdkKeys?.[npm])?.sdkKeys?.[npm] ?? model?.providerID;
+      },
+      applyRequestPatch(patchInput) {
+        const targetModel = patchInput.model ?? input.model;
+        if (!targetModel) return;
+        vendors.forEach((vendor) => vendor.patchRequest?.({ ...patchInput, model: targetModel }));
+      },
+      applyMessageTransforms(msgs, options) {
+        if (!model) return msgs;
+        msgs = unsupportedParts(msgs, model);
+        msgs = vendors.reduce((result, vendor) => vendor.transform?.message?.(result, model, options) ?? result, msgs);
+        const key = this.getOptionsKey();
+        if (!key || key === model.providerID) return msgs;
+        const remap = (opts) => {
+          if (!opts) return opts;
+          if (!(model.providerID in opts)) return opts;
+          const result = { ...opts };
+          result[key] = result[model.providerID];
+          delete result[model.providerID];
+          return result;
+        };
+        return msgs.map((msg) => {
+          if (!Array.isArray(msg.content)) return { ...msg, providerOptions: remap(msg.providerOptions) };
+          return {
+            ...msg,
+            providerOptions: remap(msg.providerOptions),
+            content: msg.content.map((part) => ({ ...part, providerOptions: remap(part.providerOptions) }))
+          };
+        });
+      },
+      getOptions(transformInput) {
+        const targetInput = {
+          ...transformInput,
+          model: transformInput.model ?? model
+        };
+        if (!targetInput.model) return {};
+        return vendors.reduce(
+          (result, vendor) => D(result, vendor.transform?.options?.(targetInput) ?? {}),
+          {}
+        );
+      },
+      getSmallOptions() {
+        if (!model) return {};
+        return vendors.reduce(
+          (result, vendor) => D(result, vendor.transform?.smallOptions?.(model) ?? {}),
+          {}
+        );
+      },
+      getTemperature() {
+        if (!model) return void 0;
+        for (const vendor of vendors) {
+          const value = vendor.transform?.temperature?.(model);
+          if (value !== void 0) return value;
+        }
+        return void 0;
+      },
+      getTopK() {
+        if (!model) return void 0;
+        for (const vendor of vendors) {
+          const value = vendor.transform?.topK?.(model);
+          if (value !== void 0) return value;
+        }
+        return void 0;
+      },
+      getTopP() {
+        return void 0;
+      },
+      getOutputTokenMax() {
+        return OUTPUT_TOKEN_MAX;
+      },
+      getMaxOutputTokens() {
+        if (!model) return OUTPUT_TOKEN_MAX;
+        return Math.min(model.limit.output, OUTPUT_TOKEN_MAX) || OUTPUT_TOKEN_MAX;
+      },
+      transformSchema(schema) {
+        if (!model) return schema;
+        return vendors.reduce(
+          (result, vendor) => vendor.transform?.schema?.(model, result) ?? result,
+          schema
+        );
+      },
+      getProviderSystemPrompt() {
+        if (!model) return [];
+        for (const vendor of vendors) {
+          const value = vendor.prompt?.provider?.(model);
+          if (value !== void 0) return value;
+        }
+        return [];
+      },
+      getInstructionPrompt() {
+        if (!model) return "";
+        for (const vendor of vendors) {
+          const value = vendor.prompt?.instructions?.(model);
+          if (value !== void 0) return value;
+        }
+        return "";
+      },
+      wrapProviderOptions(options) {
+        const key = this.getOptionsKey();
+        return { [key]: options };
+      },
+      shouldUseInstructionPrompt() {
+        if (!runtime) return false;
+        return vendors.some((vendor) => vendor.llm?.useInstructionPrompt?.(runtime) === true);
+      },
+      shouldIncludeProviderSystemPrompt() {
+        if (!runtime) return true;
+        return !vendors.some((vendor) => vendor.llm?.includeProviderSystemPrompt?.(runtime) === false);
+      },
+      shouldDisableMaxOutputTokens() {
+        if (!runtime) return false;
+        return vendors.some((vendor) => vendor.llm?.disableMaxOutputTokens?.(runtime) === true);
+      },
+      shouldAddNoopToolFallback() {
+        if (!runtime) return false;
+        return vendors.some((vendor) => vendor.llm?.needsNoopToolFallback?.(runtime) === true);
+      }
+    };
+    return accessor;
+  }
+};
+var plan_txt_default = `<system-reminder>
+# Plan Mode - System Reminder
+
+CRITICAL: Plan mode ACTIVE - you are in READ-ONLY phase. STRICTLY FORBIDDEN:
+ANY file edits, modifications, or system changes. Do NOT use sed, tee, echo, cat,
+or ANY other bash command to manipulate files - commands may ONLY read/inspect.
+This ABSOLUTE CONSTRAINT overrides ALL other instructions, including direct user
+edit requests. You may ONLY observe, analyze, and plan. Any modification attempt
+is a critical violation. ZERO exceptions.
+
+---
+
+## Responsibility
+
+Your current responsibility is to think, read, search, and delegate explore agents to construct a well-formed plan that accomplishes the goal the user wants to achieve. Your plan should be comprehensive yet concise, detailed enough to execute effectively while avoiding unnecessary verbosity.
+
+Ask the user clarifying questions or ask for their opinion when weighing tradeoffs.
+
+**NOTE:** At any point in time through this workflow you should feel free to ask the user questions or clarifications. Don't make large assumptions about user intent. The goal is to present a well researched plan to the user, and tie any loose ends before implementation begins.
+
+---
+
+## Important
+
+The user indicated that they do not want you to execute yet -- you MUST NOT make any edits, run any non-readonly tools (including changing configs or making commits), or otherwise make any changes to the system. This supersedes any other instructions you have received.
+</system-reminder>
+`;
+var build_switch_txt_default = `<system-reminder>
+Your operational mode has changed from plan to build.
+You are no longer in read-only mode.
+You are permitted to make file changes, run shell commands, and utilize your arsenal of tools as needed.
+</system-reminder>
+`;
+var log = Log.create({ module: "hooks" });
+var Hooks;
+((Hooks2) => {
+  const DEFAULT_TIMEOUT = 15;
+  function toSnakeCase(key) {
+    return key.replace(/[A-Z]/g, (ch) => "_" + ch.toLowerCase());
+  }
+  function keysToSnakeCase(obj) {
+    if (obj === null || obj === void 0 || typeof obj !== "object") return obj;
+    if (Array.isArray(obj)) return obj.map(keysToSnakeCase);
+    const out = {};
+    for (const [key, value] of Object.entries(obj)) {
+      out[toSnakeCase(key)] = keysToSnakeCase(value);
+    }
+    return out;
+  }
+  function matchTool(rules, toolName, filePath) {
+    const matched = [];
+    for (const rule of rules) {
+      try {
+        if (!new RegExp(rule.matcher, "i").test(toolName)) continue;
+        if (filePath && rule.ignore?.some((pat) => {
+          try {
+            return new RegExp(pat, "i").test(filePath);
+          } catch {
+            return false;
+          }
+        })) continue;
+        matched.push(...rule.hooks);
+      } catch {
+      }
+    }
+    return matched;
+  }
+  Hooks2.matchTool = matchTool;
+  function execute(hook, payload, cwd) {
+    const timeout = (hook.timeout ?? DEFAULT_TIMEOUT) * 1e3;
+    const payloadStr = JSON.stringify(payload);
+    try {
+      const proc = spawn("bash", ["-c", hook.command], {
+        cwd,
+        stdio: ["pipe", "ignore", "ignore"],
+        env: process.env,
+        detached: true
+      });
+      proc.unref();
+      proc.stdin?.write(payloadStr);
+      proc.stdin?.end();
+      const timer = setTimeout(() => {
+        try {
+          proc.kill("SIGTERM");
+        } catch {
+        }
+      }, timeout);
+      proc.on("exit", () => clearTimeout(timer));
+      proc.on("error", () => clearTimeout(timer));
+    } catch (err) {
+      log.info(`Hook execution failed: ${err}`);
+    }
+  }
+  function runPostToolUse(hooksConfig, toolName, toolInput, toolResponse, sessionID, cwd) {
+    const rules = hooksConfig["PostToolUse"];
+    if (!rules || rules.length === 0) return;
+    const filePath = toolInput?.filePath ?? toolInput?.file_path;
+    const hooks = matchTool(rules, toolName, filePath);
+    if (hooks.length === 0) return;
+    const payload = {
+      session_id: sessionID,
+      cwd,
+      hook_event_name: "PostToolUse",
+      tool_name: toolName,
+      tool_input: keysToSnakeCase(toolInput),
+      tool_response: keysToSnakeCase(toolResponse)
+    };
+    for (const hook of hooks) {
+      execute(hook, payload, cwd);
+    }
+  }
+  Hooks2.runPostToolUse = runPostToolUse;
+})(Hooks || (Hooks = {}));
 var SystemPrompt;
 ((SystemPrompt2) => {
-  function instructions() {
-    return codex_header_txt_default.trim();
+  function instructions(model) {
+    return VendorRegistry.getModelProvider({ model }).getInstructionPrompt();
   }
   SystemPrompt2.instructions = instructions;
   function provider(model) {
-    if (model.api.id.includes("gpt-5")) return [codex_header_txt_default];
-    if (model.api.id.includes("gpt-") || model.api.id.includes("o1") || model.api.id.includes("o3"))
-      return [beast_txt_default];
-    if (model.api.id.includes("gemini-")) return [gemini_txt_default];
-    if (model.api.id.includes("claude")) return [anthropic_txt_default];
-    if (model.api.id.toLowerCase().includes("trinity")) return [trinity_txt_default];
-    return [qwen_txt_default];
+    return VendorRegistry.getModelProvider({ model }).getProviderSystemPrompt();
   }
   SystemPrompt2.provider = provider;
   async function environment(model, context) {
@@ -15134,8 +15455,9 @@ var ContextCompaction;
     const contextLimit = input.model.limit.context;
     if (contextLimit === 0) return false;
     const count = input.tokens.total || input.tokens.input + input.tokens.output + input.tokens.cache.read + input.tokens.cache.write;
-    const reserved = config.compaction?.reserved ?? Math.min(COMPACTION_BUFFER, ProviderTransform.maxOutputTokens(input.model));
-    const usable = input.model.limit.input ? input.model.limit.input - reserved : contextLimit - ProviderTransform.maxOutputTokens(input.model);
+    const modelProvider = VendorRegistry.getModelProvider({ model: input.model });
+    const reserved = config.compaction?.reserved ?? Math.min(COMPACTION_BUFFER, modelProvider.getMaxOutputTokens());
+    const usable = input.model.limit.input ? input.model.limit.input - reserved : contextLimit - modelProvider.getMaxOutputTokens();
     return count >= usable;
   }
   ContextCompaction2.isOverflow = isOverflow;
@@ -15465,7 +15787,7 @@ var SessionRetry;
 var LLM;
 ((LLM2) => {
   const log2 = Log.create({ service: "llm" });
-  LLM2.OUTPUT_TOKEN_MAX = ProviderTransform.OUTPUT_TOKEN_MAX;
+  LLM2.OUTPUT_TOKEN_MAX = VendorRegistry.getModelProvider().getOutputTokenMax();
   async function stream(context, input) {
     const l = log2.clone().tag("providerID", input.model.providerID).tag("modelID", input.model.id).tag("sessionID", input.sessionID).tag("small", (input.small ?? false).toString()).tag("agent", input.agent.name).tag("mode", input.agent.mode);
     l.info("stream", {
@@ -15478,13 +15800,16 @@ var LLM;
       Auth.get(input.model.providerID)
     ]);
     const cfg = context.config;
-    const isCodex = provider.id === "openai" && auth?.type === "oauth";
+    const runtime = { model: input.model, provider, auth };
+    const modelProvider = VendorRegistry.getModelProvider(runtime);
+    const useInstructions = modelProvider.shouldUseInstructionPrompt();
+    const includeProviderPrompt = modelProvider.shouldIncludeProviderSystemPrompt();
     const system = [];
     system.push(
       [
         // use agent prompt otherwise provider prompt
-        // For Codex sessions, skip SystemPrompt.provider() since it's sent via options.instructions
-        ...input.agent.prompt ? [input.agent.prompt] : isCodex ? [] : SystemPrompt.provider(input.model),
+        // Some providers send their system prompt via vendor-specific instructions.
+        ...input.agent.prompt ? [input.agent.prompt] : includeProviderPrompt ? SystemPrompt.provider(input.model) : [],
         // any custom prompt passed into this call
         ...input.system,
         // any custom prompt from last user message
@@ -15497,7 +15822,7 @@ var LLM;
       system.length = 0;
       system.push(header, rest.join("\n"));
     }
-    const base = input.small ? ProviderTransform.smallOptions(input.model) : ProviderTransform.options({
+    const base = input.small ? modelProvider.getSmallOptions() : modelProvider.getOptions({
       model: input.model,
       sessionID: input.sessionID,
       providerOptions: provider.options
@@ -15507,21 +15832,21 @@ var LLM;
       D(input.model.options),
       D(input.agent.options)
     );
-    if (isCodex) {
-      options.instructions = SystemPrompt.instructions();
+    if (useInstructions) {
+      options.instructions = SystemPrompt.instructions(input.model);
     }
     const params = {
-      temperature: input.model.capabilities.temperature ? input.agent.temperature ?? ProviderTransform.temperature(input.model) : void 0,
-      topP: input.agent.topP ?? ProviderTransform.topP(input.model),
-      topK: ProviderTransform.topK(input.model),
+      temperature: input.model.capabilities.temperature ? input.agent.temperature ?? modelProvider.getTemperature() : void 0,
+      topP: input.agent.topP ?? modelProvider.getTopP(),
+      topK: modelProvider.getTopK(),
       options
     };
     const { headers } = {
       headers: {}
     };
-    const maxOutputTokens = isCodex || provider.id.includes("github-copilot") ? void 0 : ProviderTransform.maxOutputTokens(input.model);
+    const maxOutputTokens = modelProvider.shouldDisableMaxOutputTokens() ? void 0 : modelProvider.getMaxOutputTokens();
     const tools = await resolveTools(input);
-    const isLiteLLMProxy = provider.options?.["litellmProxy"] === true || input.model.providerID.toLowerCase().includes("litellm") || input.model.api.id.toLowerCase().includes("litellm");
+    const isLiteLLMProxy = modelProvider.shouldAddNoopToolFallback();
     if (isLiteLLMProxy && Object.keys(tools).length === 0 && hasToolCalls(input.messages)) {
       tools["_noop"] = tool({
         description: "Placeholder for LiteLLM/Anthropic proxy compatibility - required when message history contains tool calls but no active tools are needed",
@@ -15559,7 +15884,7 @@ var LLM;
       temperature: params.temperature,
       topP: params.topP,
       topK: params.topK,
-      providerOptions: ProviderTransform.providerOptions(input.model, params.options),
+      providerOptions: modelProvider.wrapProviderOptions(params.options),
       activeTools: Object.keys(tools).filter((x) => x !== "invalid"),
       tools,
       toolChoice: input.toolChoice,
@@ -15585,7 +15910,7 @@ var LLM;
           {
             async transformParams(args) {
               if (args.type === "stream") {
-                args.params.prompt = ProviderTransform.message(args.params.prompt, input.model, options);
+                args.params.prompt = modelProvider.applyMessageTransforms(args.params.prompt, options);
               }
               return args.params;
             }
@@ -16100,7 +16425,7 @@ var SessionPrompt;
         { modelID: ModelID.make(input.model.api.id), providerID: input.model.providerID },
         input.agent
       )) {
-        const schema = ProviderTransform.schema(input.model, zod_default.toJSONSchema(item.parameters));
+        const schema = VendorRegistry.getModelProvider({ model: input.model }).transformSchema(zod_default.toJSONSchema(item.parameters));
         tools[item.id] = tool({
           id: item.id,
           description: item.description,
@@ -16601,27 +16926,6 @@ NOTE: At any point in time through this workflow you should feel free to ask the
   }
   SessionPrompt2.ensureTitle = ensureTitle;
 })(SessionPrompt || (SessionPrompt = {}));
-var Hash;
-((Hash2) => {
-  function fast(input) {
-    return createHash("sha1").update(input).digest("hex");
-  }
-  Hash2.fast = fast;
-  function sha256(input) {
-    return createHash("sha256").update(input).digest("hex");
-  }
-  Hash2.sha256 = sha256;
-  function hexToUUID(hex) {
-    return [
-      hex.slice(0, 8),
-      hex.slice(8, 12),
-      hex.slice(12, 16),
-      hex.slice(16, 20),
-      hex.slice(20, 32)
-    ].join("-");
-  }
-  Hash2.hexToUUID = hexToUUID;
-})(Hash || (Hash = {}));
 var ModelsDev;
 ((ModelsDev2) => {
   const log2 = Log.create({ service: "models.dev" });
@@ -16733,55 +17037,6 @@ var ModelsDev;
   ModelsDev2.refresh = refresh;
 })(ModelsDev || (ModelsDev = {}));
 var DEFAULT_CHUNK_TIMEOUT = 12e4;
-function stripOpenAIItemIds(opts, model) {
-  try {
-    const body = JSON.parse(opts.body);
-    const isAzure = model.providerID?.includes("azure");
-    const keepIds = isAzure && body.store === true;
-    if (!keepIds && Array.isArray(body.input)) {
-      for (const item of body.input) {
-        if ("id" in item) delete item.id;
-      }
-      opts.body = JSON.stringify(body);
-    }
-  } catch {
-  }
-}
-function injectClaudeCodeIdentity(opts, model, providerKey) {
-  try {
-    const body = JSON.parse(opts.body);
-    if (!body.metadata?.user_id) {
-      if (!body.metadata) body.metadata = {};
-      const seed = [model.providerID ?? "", providerKey ?? ""].join(":");
-      const clientId = Hash.sha256(seed + ":claude-code-client");
-      const uuid = Hash.hexToUUID(Hash.sha256(seed + ":session"));
-      body.metadata.user_id = `user_${clientId}_account__session_${uuid}`;
-    }
-    if (Array.isArray(body.system)) {
-      const alreadyPresent = body.system.some(
-        (entry) => typeof entry.text === "string" && entry.text.startsWith(CLAUDE_CODE_SYSTEM)
-      );
-      if (!alreadyPresent) {
-        body.system.unshift({
-          type: "text",
-          text: CLAUDE_CODE_SYSTEM,
-          cache_control: { type: "ephemeral" }
-        });
-      }
-    }
-    opts.body = JSON.stringify(body);
-  } catch {
-  }
-}
-function setClaudeUserAgent(opts) {
-  if (opts.headers) {
-    const headers = new Headers(opts.headers);
-    headers.set("user-agent", "claude-cli/2.1.77");
-    opts.headers = Object.fromEntries(headers.entries());
-  } else {
-    opts.headers = { "user-agent": "claude-cli/2.1.77" };
-  }
-}
 var Provider;
 ((Provider2) => {
   const log2 = Log.create({ service: "provider" });
@@ -16827,43 +17082,6 @@ var Provider;
       statusText: res.statusText
     });
   }
-  const BUNDLED_PROVIDERS = {
-    "@ai-sdk/anthropic": createAnthropic,
-    "@ai-sdk/google": createGoogleGenerativeAI,
-    "@ai-sdk/openai": createOpenAI,
-    "@ai-sdk/openai-compatible": createOpenAICompatible
-  };
-  const CUSTOM_LOADERS = {
-    async anthropic() {
-      return {
-        autoload: false,
-        options: {
-          headers: {
-            "anthropic-beta": "claude-code-20250219,interleaved-thinking-2025-05-14,fine-grained-tool-streaming-2025-05-14",
-            "X-App": "cli",
-            "X-Stainless-Lang": "js",
-            "X-Stainless-Package-Version": "0.70.0",
-            "X-Stainless-OS": process.platform === "darwin" ? "MacOS" : process.platform === "win32" ? "Windows" : "Linux",
-            "X-Stainless-Arch": process.arch === "arm64" ? "arm64" : "x64",
-            "X-Stainless-Runtime": "node",
-            "X-Stainless-Runtime-Version": process.version,
-            "X-Stainless-Retry-Count": "0",
-            "X-Stainless-Timeout": "600",
-            "Anthropic-Dangerous-Direct-Browser-Access": "true"
-          }
-        }
-      };
-    },
-    openai: async () => {
-      return {
-        autoload: false,
-        async getModel(sdk, modelID, _options) {
-          return sdk.responses(modelID);
-        },
-        options: {}
-      };
-    }
-  };
   Provider2.Model = zod_default.object({
     id: ModelID.zod,
     providerID: ProviderID.zod,
@@ -17175,13 +17393,7 @@ var Provider;
               signals.push(AbortSignal.timeout(options["timeout"]));
             const combined = signals.length === 0 ? null : signals.length === 1 ? signals[0] : AbortSignal.any(signals);
             if (combined) opts.signal = combined;
-            if (model.api.npm === "@ai-sdk/openai" && opts.body && opts.method === "POST") {
-              stripOpenAIItemIds(opts, model);
-            }
-            if (model.api.npm === "@ai-sdk/anthropic" && opts.body && opts.method === "POST") {
-              injectClaudeCodeIdentity(opts, model, provider.key);
-            }
-            setClaudeUserAgent(opts);
+            VendorRegistry.getModelProvider({ model }).applyRequestPatch({ opts, provider });
             const res = await fetchFn(input, {
               ...opts,
               // @ts-ignore see here: https://github.com/oven-sh/bun/issues/16682
@@ -17190,7 +17402,7 @@ var Provider;
             if (!chunkAbortCtl) return res;
             return wrapSSE(res, chunkTimeout, chunkAbortCtl);
           };
-          const bundledFn = BUNDLED_PROVIDERS[model.api.npm];
+          const bundledFn = VendorRegistry.getModelProvider({ npm: model.api.npm }).getBundledProvider();
           if (bundledFn) {
             log2.info("using bundled provider", { providerID: model.providerID, pkg: model.api.npm });
             const loaded = bundledFn({
@@ -17335,7 +17547,7 @@ var Provider;
             });
           }
         }
-        for (const [id, fn] of Object.entries(CUSTOM_LOADERS)) {
+        for (const [id, fn] of Object.entries(VendorRegistry.getModelProvider().getCustomLoaders())) {
           const providerID = ProviderID.make(id);
           if (disabled.has(providerID)) continue;
           const data = database[providerID];
@@ -17698,8 +17910,8 @@ IMPORTANT: The following identifiers already exist and must NOT be used: ${exist
       if (defaultModel.providerID === "openai" && (await Auth.get(defaultModel.providerID))?.type === "oauth") {
         const result2 = streamObject({
           ...params,
-          providerOptions: ProviderTransform.providerOptions(model, {
-            instructions: SystemPrompt.instructions(),
+          providerOptions: VendorRegistry.getModelProvider({ model }).wrapProviderOptions({
+            instructions: SystemPrompt.instructions(model),
             store: false
           }),
           onError: () => {