@mastra/code-sdk 0.0.0-livekit-beta-v3-20260709031728

package/dist/agents/prompts/agent-instructions.d.ts

@@ -0,0 +1,20 @@
+/**
+ * Load project and global agent instruction files (AGENTS.md, CLAUDE.md).
+ * Prefers AGENTS.md over CLAUDE.md when multiple exist at the same location.
+ */
+export interface InstructionSource {
+    path: string;
+    content: string;
+    scope: 'global' | 'project';
+}
+/**
+ * Load all agent instruction files from global and project locations.
+ * Returns an array of instruction sources, with global ones first.
+ */
+export declare function loadAgentInstructions(projectPath: string, configDirName?: string): InstructionSource[];
+export declare function getStaticallyLoadedInstructionPaths(projectPath: string): string[];
+/**
+ * Format loaded instructions into a string for the system prompt.
+ */
+export declare function formatAgentInstructions(sources: InstructionSource[]): string;
+//# sourceMappingURL=agent-instructions.d.ts.map

package/dist/agents/prompts/agent-instructions.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"agent-instructions.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/agent-instructions.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAmBH,MAAM,WAAW,iBAAiB;IAChC,IAAI,EAAE,MAAM,CAAC;IACb,OAAO,EAAE,MAAM,CAAC;IAChB,KAAK,EAAE,QAAQ,GAAG,SAAS,CAAC;CAC7B;AAgBD;;;GAGG;AACH,wBAAgB,qBAAqB,CAAC,WAAW,EAAE,MAAM,EAAE,aAAa,SAAqB,GAAG,iBAAiB,EAAE,CAiDlH;AAED,wBAAgB,mCAAmC,CAAC,WAAW,EAAE,MAAM,GAAG,MAAM,EAAE,CAEjF;AAED;;GAEG;AACH,wBAAgB,uBAAuB,CAAC,OAAO,EAAE,iBAAiB,EAAE,GAAG,MAAM,CAS5E"}

package/dist/agents/prompts/agent-instructions.js

@@ -0,0 +1,82 @@
+import { existsSync, readFileSync } from "node:fs";
+import { homedir } from "node:os";
+import { join, normalize } from "node:path";
+import { DEFAULT_CONFIG_DIR } from "../../constants.js";
+const INSTRUCTION_FILES = ["AGENTS.md", "CLAUDE.md"];
+const PROJECT_LOCATIONS = [
+  "",
+  // project root
+  ".claude",
+  ".mastracode"
+];
+const GLOBAL_LOCATIONS = [".claude", ".mastracode", ".config/claude", ".config/mastracode"];
+function findInstructionFile(basePath) {
+  for (const filename of INSTRUCTION_FILES) {
+    const fullPath = join(basePath, filename);
+    if (existsSync(fullPath)) {
+      return fullPath;
+    }
+  }
+  return null;
+}
+function loadAgentInstructions(projectPath, configDirName = DEFAULT_CONFIG_DIR) {
+  const sources = [];
+  const home = homedir();
+  const projectLocations = PROJECT_LOCATIONS.map((loc) => loc === ".mastracode" ? configDirName : loc);
+  const globalLocations = GLOBAL_LOCATIONS.map((loc) => {
+    if (loc === ".mastracode") return configDirName;
+    if (loc === ".config/mastracode") return ".config/" + configDirName.replace(/^\./, "");
+    return loc;
+  });
+  for (const location of globalLocations) {
+    const basePath = join(home, location);
+    const filePath = findInstructionFile(basePath);
+    if (filePath) {
+      try {
+        const content = readFileSync(filePath, "utf-8").trim();
+        if (content) {
+          sources.push({ path: filePath, content, scope: "global" });
+          break;
+        }
+      } catch {
+      }
+    }
+  }
+  for (const location of projectLocations) {
+    const basePath = location ? join(projectPath, location) : projectPath;
+    const filePath = findInstructionFile(basePath);
+    if (filePath) {
+      try {
+        const content = readFileSync(filePath, "utf-8").trim();
+        if (content) {
+          sources.push({ path: filePath, content, scope: "project" });
+          break;
+        }
+      } catch {
+      }
+    }
+  }
+  return sources;
+}
+function getStaticallyLoadedInstructionPaths(projectPath) {
+  return loadAgentInstructions(projectPath).map((source) => normalize(source.path));
+}
+function formatAgentInstructions(sources) {
+  if (sources.length === 0) return "";
+  const sections = sources.map((source) => {
+    const label = source.scope === "global" ? "Global" : "Project";
+    return `<!-- ${label} instructions from ${source.path} -->
+${source.content}`;
+  });
+  return `
+# Agent Instructions
+
+${sections.join("\n\n")}
+`;
+}
+export {
+  formatAgentInstructions,
+  getStaticallyLoadedInstructionPaths,
+  loadAgentInstructions
+};
+//# sourceMappingURL=agent-instructions.js.map

package/dist/agents/prompts/agent-instructions.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../../src/agents/prompts/agent-instructions.ts"],"sourcesContent":["/**\n * Load project and global agent instruction files (AGENTS.md, CLAUDE.md).\n * Prefers AGENTS.md over CLAUDE.md when multiple exist at the same location.\n */\n\nimport { existsSync, readFileSync } from 'node:fs';\nimport { homedir } from 'node:os';\nimport { join, normalize } from 'node:path';\nimport { DEFAULT_CONFIG_DIR } from '../../constants.js';\n\n// Filenames to check, in order of preference\nconst INSTRUCTION_FILES = ['AGENTS.md', 'CLAUDE.md'];\n\n// Locations to scan (relative to project root or home)\nconst PROJECT_LOCATIONS = [\n  '', // project root\n  '.claude',\n  '.mastracode',\n];\n\nconst GLOBAL_LOCATIONS = ['.claude', '.mastracode', '.config/claude', '.config/mastracode'];\n\nexport interface InstructionSource {\n  path: string;\n  content: string;\n  scope: 'global' | 'project';\n}\n\n/**\n * Find the first existing instruction file at a given base path.\n * Prefers AGENTS.md over CLAUDE.md.\n */\nfunction findInstructionFile(basePath: string): string | null {\n  for (const filename of INSTRUCTION_FILES) {\n    const fullPath = join(basePath, filename);\n    if (existsSync(fullPath)) {\n      return fullPath;\n    }\n  }\n  return null;\n}\n\n/**\n * Load all agent instruction files from global and project locations.\n * Returns an array of instruction sources, with global ones first.\n */\nexport function loadAgentInstructions(projectPath: string, configDirName = DEFAULT_CONFIG_DIR): InstructionSource[] {\n  const sources: InstructionSource[] = [];\n  const home = homedir();\n\n  // Derive location arrays from the base constants, substituting the config dir name\n  const projectLocations = PROJECT_LOCATIONS.map(loc => (loc === '.mastracode' ? configDirName : loc));\n  const globalLocations = GLOBAL_LOCATIONS.map(loc => {\n    if (loc === '.mastracode') return configDirName;\n    // XDG-style path (~/.config/<name>): strip the leading dot since the\n    // .config/ prefix already signals a hidden/config directory.\n    if (loc === '.config/mastracode') return '.config/' + configDirName.replace(/^\\./, '');\n    return loc;\n  });\n\n  // Load global instructions first\n  for (const location of globalLocations) {\n    const basePath = join(home, location);\n    const filePath = findInstructionFile(basePath);\n    if (filePath) {\n      try {\n        const content = readFileSync(filePath, 'utf-8').trim();\n        if (content) {\n          sources.push({ path: filePath, content, scope: 'global' });\n          break; // Only use first found global instruction file\n        }\n      } catch {\n        // Skip unreadable files\n      }\n    }\n  }\n\n  // Load project instructions\n  for (const location of projectLocations) {\n    const basePath = location ? join(projectPath, location) : projectPath;\n    const filePath = findInstructionFile(basePath);\n    if (filePath) {\n      try {\n        const content = readFileSync(filePath, 'utf-8').trim();\n        if (content) {\n          sources.push({ path: filePath, content, scope: 'project' });\n          break; // Only use first found project instruction file\n        }\n      } catch {\n        // Skip unreadable files\n      }\n    }\n  }\n\n  return sources;\n}\n\nexport function getStaticallyLoadedInstructionPaths(projectPath: string): string[] {\n  return loadAgentInstructions(projectPath).map(source => normalize(source.path));\n}\n\n/**\n * Format loaded instructions into a string for the system prompt.\n */\nexport function formatAgentInstructions(sources: InstructionSource[]): string {\n  if (sources.length === 0) return '';\n\n  const sections = sources.map(source => {\n    const label = source.scope === 'global' ? 'Global' : 'Project';\n    return `<!-- ${label} instructions from ${source.path} -->\\n${source.content}`;\n  });\n\n  return `\\n# Agent Instructions\\n\\n${sections.join('\\n\\n')}\\n`;\n}\n"],"mappings":"AAKA,SAAS,YAAY,oBAAoB;AACzC,SAAS,eAAe;AACxB,SAAS,MAAM,iBAAiB;AAChC,SAAS,0BAA0B;AAGnC,MAAM,oBAAoB,CAAC,aAAa,WAAW;AAGnD,MAAM,oBAAoB;AAAA,EACxB;AAAA;AAAA,EACA;AAAA,EACA;AACF;AAEA,MAAM,mBAAmB,CAAC,WAAW,eAAe,kBAAkB,oBAAoB;AAY1F,SAAS,oBAAoB,UAAiC;AAC5D,aAAW,YAAY,mBAAmB;AACxC,UAAM,WAAW,KAAK,UAAU,QAAQ;AACxC,QAAI,WAAW,QAAQ,GAAG;AACxB,aAAO;AAAA,IACT;AAAA,EACF;AACA,SAAO;AACT;AAMO,SAAS,sBAAsB,aAAqB,gBAAgB,oBAAyC;AAClH,QAAM,UAA+B,CAAC;AACtC,QAAM,OAAO,QAAQ;AAGrB,QAAM,mBAAmB,kBAAkB,IAAI,SAAQ,QAAQ,gBAAgB,gBAAgB,GAAI;AACnG,QAAM,kBAAkB,iBAAiB,IAAI,SAAO;AAClD,QAAI,QAAQ,cAAe,QAAO;AAGlC,QAAI,QAAQ,qBAAsB,QAAO,aAAa,cAAc,QAAQ,OAAO,EAAE;AACrF,WAAO;AAAA,EACT,CAAC;AAGD,aAAW,YAAY,iBAAiB;AACtC,UAAM,WAAW,KAAK,MAAM,QAAQ;AACpC,UAAM,WAAW,oBAAoB,QAAQ;AAC7C,QAAI,UAAU;AACZ,UAAI;AACF,cAAM,UAAU,aAAa,UAAU,OAAO,EAAE,KAAK;AACrD,YAAI,SAAS;AACX,kBAAQ,KAAK,EAAE,MAAM,UAAU,SAAS,OAAO,SAAS,CAAC;AACzD;AAAA,QACF;AAAA,MACF,QAAQ;AAAA,MAER;AAAA,IACF;AAAA,EACF;AAGA,aAAW,YAAY,kBAAkB;AACvC,UAAM,WAAW,WAAW,KAAK,aAAa,QAAQ,IAAI;AAC1D,UAAM,WAAW,oBAAoB,QAAQ;AAC7C,QAAI,UAAU;AACZ,UAAI;AACF,cAAM,UAAU,aAAa,UAAU,OAAO,EAAE,KAAK;AACrD,YAAI,SAAS;AACX,kBAAQ,KAAK,EAAE,MAAM,UAAU,SAAS,OAAO,UAAU,CAAC;AAC1D;AAAA,QACF;AAAA,MACF,QAAQ;AAAA,MAER;AAAA,IACF;AAAA,EACF;AAEA,SAAO;AACT;AAEO,SAAS,oCAAoC,aAA+B;AACjF,SAAO,sBAAsB,WAAW,EAAE,IAAI,YAAU,UAAU,OAAO,IAAI,CAAC;AAChF;AAKO,SAAS,wBAAwB,SAAsC;AAC5E,MAAI,QAAQ,WAAW,EAAG,QAAO;AAEjC,QAAM,WAAW,QAAQ,IAAI,YAAU;AACrC,UAAM,QAAQ,OAAO,UAAU,WAAW,WAAW;AACrD,WAAO,QAAQ,KAAK,sBAAsB,OAAO,IAAI;AAAA,EAAS,OAAO,OAAO;AAAA,EAC9E,CAAC;AAED,SAAO;AAAA;AAAA;AAAA,EAA6B,SAAS,KAAK,MAAM,CAAC;AAAA;AAC3D;","names":[]}

package/dist/agents/prompts/build.d.ts

@@ -0,0 +1,12 @@
+/**
+ * Build mode prompt — full tool access, make changes and verify.
+ */
+import type { PromptContext } from './index.js';
+/**
+ * Dynamic build mode prompt function.
+ * When an approved plan exists in state, prepends it so the agent
+ * knows exactly what to implement.
+ */
+export declare function buildModePromptFn(ctx: PromptContext): string;
+export declare const buildModePrompt = "\n# Build Mode\n\nYou are in BUILD mode. You have full access to all tools and can read, write, edit, and execute commands.\n\n## Working Style\n\n**For simple tasks** (typo fixes, small edits, single-file changes):\n- Just do it. No need to explain your plan first.\n\n**For non-trivial tasks** (3+ files, architectural decisions, unclear requirements):\n- Use the available task-management tools to create and update your task list\n- Work on ONE step at a time \u2014 complete it and verify it works before moving on\n- If multiple approaches are plausible and the choice would materially affect scope, behavior, or risk, stop and ask the user\n\n## The Implementation Loop\n\nFor each change you make:\n\n1. **Understand** \u2014 Read the relevant code. Check how similar things are done elsewhere.\n2. **Implement** \u2014 Make the change. Follow existing patterns and conventions.\n3. **Verify** \u2014 Test that it works. Don't assume \u2014 actually run it.\n4. **Prove** \u2014 Proactively prove that the change is good, makes sense in context, is a positive contribution, and works fully. The burden of proof is on YOU.\n5. **Clean up** \u2014 Ensure no broken code, no debug statements, no half-done features.\n\nOnly move to the next change after the current one is verified and proved to be working.\n\n## Verification is Required\n\nBefore considering any task complete:\n- Run relevant tests (check package.json for test scripts)\n- For TypeScript, run `tsc --noEmit` to catch type errors\n- If there are no automated tests, manually verify the behavior works as expected\n- Confirm the result makes sense in the codebase and improves the requested behavior\n- Use available task-checking tools to ensure all tracked tasks are done\n\n**Don't mark something as done until you've verified and proved it actually works.**\n\n## Error Recovery\n\nWhen something breaks:\n1. Read the full error output carefully \u2014 don't guess\n2. Find the root cause, not just the symptom\n3. Fix it properly \u2014 no casts or suppressions to hide errors\n4. Re-run to confirm the fix\n5. If progress is blocked after reasonable attempts, briefly explain the blocker, what you've tried, and the next best option\n\n## Git in Build Mode\n\n- Before committing, verify the code compiles and passes lint\n- Use descriptive branch names: `feat/...`, `fix/...`, `refactor/...`\n";
+//# sourceMappingURL=build.d.ts.map

package/dist/agents/prompts/build.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"build.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/build.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,YAAY,CAAC;AAEhD;;;;GAIG;AACH,wBAAgB,iBAAiB,CAAC,GAAG,EAAE,aAAa,GAAG,MAAM,CAiB5D;AAED,eAAO,MAAM,eAAe,00EAmD3B,CAAC"}

package/dist/agents/prompts/build.js

@@ -0,0 +1,73 @@
+function buildModePromptFn(ctx) {
+  if (ctx.activePlan) {
+    return `# Approved Plan
+
+**${ctx.activePlan.title}**
+
+${ctx.activePlan.plan}
+
+---
+
+Implement the approved plan above. Follow the steps in order and verify each step works before moving on.
+
+` + buildModePrompt;
+  }
+  return buildModePrompt;
+}
+const buildModePrompt = `
+# Build Mode
+
+You are in BUILD mode. You have full access to all tools and can read, write, edit, and execute commands.
+
+## Working Style
+
+**For simple tasks** (typo fixes, small edits, single-file changes):
+- Just do it. No need to explain your plan first.
+
+**For non-trivial tasks** (3+ files, architectural decisions, unclear requirements):
+- Use the available task-management tools to create and update your task list
+- Work on ONE step at a time \u2014 complete it and verify it works before moving on
+- If multiple approaches are plausible and the choice would materially affect scope, behavior, or risk, stop and ask the user
+
+## The Implementation Loop
+
+For each change you make:
+
+1. **Understand** \u2014 Read the relevant code. Check how similar things are done elsewhere.
+2. **Implement** \u2014 Make the change. Follow existing patterns and conventions.
+3. **Verify** \u2014 Test that it works. Don't assume \u2014 actually run it.
+4. **Prove** \u2014 Proactively prove that the change is good, makes sense in context, is a positive contribution, and works fully. The burden of proof is on YOU.
+5. **Clean up** \u2014 Ensure no broken code, no debug statements, no half-done features.
+
+Only move to the next change after the current one is verified and proved to be working.
+
+## Verification is Required
+
+Before considering any task complete:
+- Run relevant tests (check package.json for test scripts)
+- For TypeScript, run \`tsc --noEmit\` to catch type errors
+- If there are no automated tests, manually verify the behavior works as expected
+- Confirm the result makes sense in the codebase and improves the requested behavior
+- Use available task-checking tools to ensure all tracked tasks are done
+
+**Don't mark something as done until you've verified and proved it actually works.**
+
+## Error Recovery
+
+When something breaks:
+1. Read the full error output carefully \u2014 don't guess
+2. Find the root cause, not just the symptom
+3. Fix it properly \u2014 no casts or suppressions to hide errors
+4. Re-run to confirm the fix
+5. If progress is blocked after reasonable attempts, briefly explain the blocker, what you've tried, and the next best option
+
+## Git in Build Mode
+
+- Before committing, verify the code compiles and passes lint
+- Use descriptive branch names: \`feat/...\`, \`fix/...\`, \`refactor/...\`
+`;
+export {
+  buildModePrompt,
+  buildModePromptFn
+};
+//# sourceMappingURL=build.js.map

package/dist/agents/prompts/build.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../../src/agents/prompts/build.ts"],"sourcesContent":["/**\n * Build mode prompt — full tool access, make changes and verify.\n */\n\nimport type { PromptContext } from './index.js';\n\n/**\n * Dynamic build mode prompt function.\n * When an approved plan exists in state, prepends it so the agent\n * knows exactly what to implement.\n */\nexport function buildModePromptFn(ctx: PromptContext): string {\n  if (ctx.activePlan) {\n    return (\n      `# Approved Plan\n\n**${ctx.activePlan.title}**\n\n${ctx.activePlan.plan}\n\n---\n\nImplement the approved plan above. Follow the steps in order and verify each step works before moving on.\n\n` + buildModePrompt\n    );\n  }\n  return buildModePrompt;\n}\n\nexport const buildModePrompt = `\n# Build Mode\n\nYou are in BUILD mode. You have full access to all tools and can read, write, edit, and execute commands.\n\n## Working Style\n\n**For simple tasks** (typo fixes, small edits, single-file changes):\n- Just do it. No need to explain your plan first.\n\n**For non-trivial tasks** (3+ files, architectural decisions, unclear requirements):\n- Use the available task-management tools to create and update your task list\n- Work on ONE step at a time — complete it and verify it works before moving on\n- If multiple approaches are plausible and the choice would materially affect scope, behavior, or risk, stop and ask the user\n\n## The Implementation Loop\n\nFor each change you make:\n\n1. **Understand** — Read the relevant code. Check how similar things are done elsewhere.\n2. **Implement** — Make the change. Follow existing patterns and conventions.\n3. **Verify** — Test that it works. Don't assume — actually run it.\n4. **Prove** — Proactively prove that the change is good, makes sense in context, is a positive contribution, and works fully. The burden of proof is on YOU.\n5. **Clean up** — Ensure no broken code, no debug statements, no half-done features.\n\nOnly move to the next change after the current one is verified and proved to be working.\n\n## Verification is Required\n\nBefore considering any task complete:\n- Run relevant tests (check package.json for test scripts)\n- For TypeScript, run \\`tsc --noEmit\\` to catch type errors\n- If there are no automated tests, manually verify the behavior works as expected\n- Confirm the result makes sense in the codebase and improves the requested behavior\n- Use available task-checking tools to ensure all tracked tasks are done\n\n**Don't mark something as done until you've verified and proved it actually works.**\n\n## Error Recovery\n\nWhen something breaks:\n1. Read the full error output carefully — don't guess\n2. Find the root cause, not just the symptom\n3. Fix it properly — no casts or suppressions to hide errors\n4. Re-run to confirm the fix\n5. If progress is blocked after reasonable attempts, briefly explain the blocker, what you've tried, and the next best option\n\n## Git in Build Mode\n\n- Before committing, verify the code compiles and passes lint\n- Use descriptive branch names: \\`feat/...\\`, \\`fix/...\\`, \\`refactor/...\\`\n`;\n"],"mappings":"AAWO,SAAS,kBAAkB,KAA4B;AAC5D,MAAI,IAAI,YAAY;AAClB,WACE;AAAA;AAAA,IAEF,IAAI,WAAW,KAAK;AAAA;AAAA,EAEtB,IAAI,WAAW,IAAI;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,IAMjB;AAAA,EAEF;AACA,SAAO;AACT;AAEO,MAAM,kBAAkB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;","names":[]}

package/dist/agents/prompts/fast.d.ts

@@ -0,0 +1,5 @@
+/**
+ * Fast mode prompt — quick answers and small edits, minimal overhead.
+ */
+export declare const fastModePrompt = "\n# Fast Mode\n\nYou are in FAST mode. Optimize for speed and brevity.\n\n## Rules\n- Keep responses short. Under 200 words unless the task genuinely requires more.\n- Skip planning. Just do the task directly.\n- For questions: give the direct answer, not a tutorial.\n- For edits: make the change, show what you did, move on.\n- Don't explore the codebase more than necessary for the immediate task.\n\n## When to Use Tools vs. Just Answer\n- If the user asks a general programming question, answer directly from knowledge. Don't search the codebase.\n- If the user asks about THIS project's code, use tools to look it up \u2014 don't guess.\n- If the user asks for a quick edit and you know the file, read it and edit it. Don't ask for confirmation.\n- One tool call to read + one to edit is ideal. Minimize round trips.\n";
+//# sourceMappingURL=fast.d.ts.map

package/dist/agents/prompts/fast.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"fast.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/fast.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,eAAO,MAAM,cAAc,6zBAiB1B,CAAC"}

package/dist/agents/prompts/fast.js

@@ -0,0 +1,22 @@
+const fastModePrompt = `
+# Fast Mode
+
+You are in FAST mode. Optimize for speed and brevity.
+
+## Rules
+- Keep responses short. Under 200 words unless the task genuinely requires more.
+- Skip planning. Just do the task directly.
+- For questions: give the direct answer, not a tutorial.
+- For edits: make the change, show what you did, move on.
+- Don't explore the codebase more than necessary for the immediate task.
+
+## When to Use Tools vs. Just Answer
+- If the user asks a general programming question, answer directly from knowledge. Don't search the codebase.
+- If the user asks about THIS project's code, use tools to look it up \u2014 don't guess.
+- If the user asks for a quick edit and you know the file, read it and edit it. Don't ask for confirmation.
+- One tool call to read + one to edit is ideal. Minimize round trips.
+`;
+export {
+  fastModePrompt
+};
+//# sourceMappingURL=fast.js.map

package/dist/agents/prompts/fast.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../../src/agents/prompts/fast.ts"],"sourcesContent":["/**\n * Fast mode prompt — quick answers and small edits, minimal overhead.\n */\n\nexport const fastModePrompt = `\n# Fast Mode\n\nYou are in FAST mode. Optimize for speed and brevity.\n\n## Rules\n- Keep responses short. Under 200 words unless the task genuinely requires more.\n- Skip planning. Just do the task directly.\n- For questions: give the direct answer, not a tutorial.\n- For edits: make the change, show what you did, move on.\n- Don't explore the codebase more than necessary for the immediate task.\n\n## When to Use Tools vs. Just Answer\n- If the user asks a general programming question, answer directly from knowledge. Don't search the codebase.\n- If the user asks about THIS project's code, use tools to look it up — don't guess.\n- If the user asks for a quick edit and you know the file, read it and edit it. Don't ask for confirmation.\n- One tool call to read + one to edit is ideal. Minimize round trips.\n`;\n"],"mappings":"AAIO,MAAM,iBAAiB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;","names":[]}

package/dist/agents/prompts/index.d.ts

@@ -0,0 +1,19 @@
+/**
+ * Prompt system — exports the prompt builder and mode-specific prompts.
+ */
+export { buildModePrompt, buildModePromptFn } from './build.js';
+export { planModePrompt } from './plan.js';
+export { fastModePrompt } from './fast.js';
+import type { PromptContext as BasePromptContext } from '@mastra/core/coding-agent';
+export interface PromptContext extends Omit<BasePromptContext, 'toolGuidance'> {
+    modeId: string;
+    state?: any;
+    currentDate: string;
+    workingDir: string;
+}
+/**
+ * Build the full system prompt for a given mode and context.
+ * Combines the base prompt with mode-specific instructions.
+ */
+export declare function buildFullPrompt(ctx: PromptContext): string;
+//# sourceMappingURL=index.d.ts.map

package/dist/agents/prompts/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/index.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,OAAO,EAAE,eAAe,EAAE,iBAAiB,EAAE,MAAM,YAAY,CAAC;AAChE,OAAO,EAAE,cAAc,EAAE,MAAM,WAAW,CAAC;AAC3C,OAAO,EAAE,cAAc,EAAE,MAAM,WAAW,CAAC;AAG3C,OAAO,KAAK,EAAE,aAAa,IAAI,iBAAiB,EAAE,MAAM,2BAA2B,CAAC;AAUpF,MAAM,WAAW,aAAc,SAAQ,IAAI,CAAC,iBAAiB,EAAE,cAAc,CAAC;IAC5E,MAAM,EAAE,MAAM,CAAC;IACf,KAAK,CAAC,EAAE,GAAG,CAAC;IACZ,WAAW,EAAE,MAAM,CAAC;IACpB,UAAU,EAAE,MAAM,CAAC;CACpB;AAQD;;;GAGG;AACH,wBAAgB,eAAe,CAAC,GAAG,EAAE,aAAa,GAAG,MAAM,CAmD1D"}

package/dist/agents/prompts/index.js

@@ -0,0 +1,57 @@
+import { buildModePrompt, buildModePromptFn } from "./build.js";
+import { planModePrompt } from "./plan.js";
+import { fastModePrompt } from "./fast.js";
+import { buildBasePrompt } from "@mastra/core/coding-agent";
+import { hasTavilyKey } from "../../tools/index.js";
+import { loadAgentInstructions, formatAgentInstructions } from "./agent-instructions.js";
+import { buildModePromptFn as buildModePromptFn2 } from "./build.js";
+import { fastModePrompt as fastModePrompt2 } from "./fast.js";
+import { modelSpecificPrompts } from "./model.js";
+import { planModePrompt as planModePrompt2 } from "./plan.js";
+import { buildToolGuidance } from "./tool-guidance.js";
+const modePrompts = {
+  build: buildModePromptFn2,
+  plan: planModePrompt2,
+  fast: fastModePrompt2
+};
+function buildFullPrompt(ctx) {
+  const modelId = ctx.modelId;
+  const hasWebSearch = hasTavilyKey() || !!modelId && modelId.startsWith("anthropic/");
+  const deniedTools = /* @__PURE__ */ new Set();
+  const permRules = ctx.state?.permissionRules;
+  if (permRules?.tools) {
+    for (const [name, policy] of Object.entries(permRules.tools)) {
+      if (policy === "deny") deniedTools.add(name);
+    }
+  }
+  const toolGuidance = buildToolGuidance(ctx.modeId, { hasWebSearch, deniedTools });
+  const baseCtx = {
+    projectPath: ctx.workingDir,
+    projectName: ctx.projectName || "unknown",
+    gitBranch: ctx.gitBranch,
+    platform: process.platform,
+    commonBinaries: ctx.commonBinaries,
+    date: ctx.currentDate,
+    mode: ctx.modeId,
+    modelId: ctx.modelId,
+    activePlan: ctx.state?.activePlan,
+    toolGuidance
+  };
+  const base = buildBasePrompt(baseCtx);
+  const entry = modePrompts[ctx.modeId] || modePrompts.build;
+  const modeSpecific = (typeof entry === "function" ? entry(ctx) : entry) ?? "";
+  const modelSpecific = ctx.modelId ? modelSpecificPrompts[ctx.modelId] ?? "" : "";
+  const configDir = ctx.state?.configDir;
+  const instructionSources = loadAgentInstructions(ctx.workingDir, configDir);
+  const instructionsSection = formatAgentInstructions(instructionSources);
+  const sections = [base, instructionsSection.trim(), modelSpecific.trim(), modeSpecific.trim()].filter(Boolean);
+  return sections.join("\n\n");
+}
+export {
+  buildFullPrompt,
+  buildModePrompt,
+  buildModePromptFn,
+  fastModePrompt,
+  planModePrompt
+};
+//# sourceMappingURL=index.js.map

package/dist/agents/prompts/index.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../../src/agents/prompts/index.ts"],"sourcesContent":["/**\n * Prompt system — exports the prompt builder and mode-specific prompts.\n */\n\nexport { buildModePrompt, buildModePromptFn } from './build.js';\nexport { planModePrompt } from './plan.js';\nexport { fastModePrompt } from './fast.js';\n\nimport { buildBasePrompt } from '@mastra/core/coding-agent';\nimport type { PromptContext as BasePromptContext } from '@mastra/core/coding-agent';\nimport { hasTavilyKey } from '../../tools/index.js';\nimport { loadAgentInstructions, formatAgentInstructions } from './agent-instructions.js';\nimport { buildModePromptFn } from './build.js';\nimport { fastModePrompt } from './fast.js';\nimport { modelSpecificPrompts } from './model.js';\nimport { planModePrompt } from './plan.js';\nimport { buildToolGuidance } from './tool-guidance.js';\n\n// Extended prompt context that includes runtime information\nexport interface PromptContext extends Omit<BasePromptContext, 'toolGuidance'> {\n  modeId: string;\n  state?: any;\n  currentDate: string;\n  workingDir: string;\n}\n\nconst modePrompts: Record<string, string | ((ctx: PromptContext) => string)> = {\n  build: buildModePromptFn,\n  plan: planModePrompt,\n  fast: fastModePrompt,\n};\n\n/**\n * Build the full system prompt for a given mode and context.\n * Combines the base prompt with mode-specific instructions.\n */\nexport function buildFullPrompt(ctx: PromptContext): string {\n  // Determine whether web search tools are available\n  const modelId = ctx.modelId;\n  const hasWebSearch = hasTavilyKey() || (!!modelId && modelId.startsWith('anthropic/'));\n\n  // Collect per-tool deny rules so guidance omits denied tools\n  const deniedTools = new Set<string>();\n  const permRules = ctx.state?.permissionRules as { tools?: Record<string, string> } | undefined;\n  if (permRules?.tools) {\n    for (const [name, policy] of Object.entries(permRules.tools)) {\n      if (policy === 'deny') deniedTools.add(name);\n    }\n  }\n\n  // Build mode-aware tool guidance\n  const toolGuidance = buildToolGuidance(ctx.modeId, { hasWebSearch, deniedTools });\n\n  // Map new context to base context\n  const baseCtx: BasePromptContext = {\n    projectPath: ctx.workingDir,\n    projectName: ctx.projectName || 'unknown',\n    gitBranch: ctx.gitBranch,\n    platform: process.platform,\n    commonBinaries: ctx.commonBinaries,\n    date: ctx.currentDate,\n    mode: ctx.modeId,\n    modelId: ctx.modelId,\n    activePlan: ctx.state?.activePlan,\n    toolGuidance,\n  };\n\n  const base = buildBasePrompt(baseCtx);\n  const entry = modePrompts[ctx.modeId] || modePrompts.build;\n  const modeSpecific = (typeof entry === 'function' ? entry(ctx) : entry) ?? '';\n  const modelSpecific = ctx.modelId\n    ? (modelSpecificPrompts[ctx.modelId as keyof typeof modelSpecificPrompts] ?? '')\n    : '';\n\n  // The current task list is carried on the agent state-signal lane (see\n  // TaskStateProcessor) rather than injected into the cached system prompt. This\n  // keeps the prompt prefix stable across task updates (preserving prompt cache)\n  // while still surviving observational-memory truncation.\n\n  // Load and inject agent instructions from AGENTS.md/CLAUDE.md files\n  const configDir = ctx.state?.configDir as string | undefined;\n  const instructionSources = loadAgentInstructions(ctx.workingDir, configDir);\n  const instructionsSection = formatAgentInstructions(instructionSources);\n\n  const sections = [base, instructionsSection.trim(), modelSpecific.trim(), modeSpecific.trim()].filter(Boolean);\n\n  return sections.join('\\n\\n');\n}\n"],"mappings":"AAIA,SAAS,iBAAiB,yBAAyB;AACnD,SAAS,sBAAsB;AAC/B,SAAS,sBAAsB;AAE/B,SAAS,uBAAuB;AAEhC,SAAS,oBAAoB;AAC7B,SAAS,uBAAuB,+BAA+B;AAC/D,SAAS,qBAAAA,0BAAyB;AAClC,SAAS,kBAAAC,uBAAsB;AAC/B,SAAS,4BAA4B;AACrC,SAAS,kBAAAC,uBAAsB;AAC/B,SAAS,yBAAyB;AAUlC,MAAM,cAAyE;AAAA,EAC7E,OAAOF;AAAA,EACP,MAAME;AAAA,EACN,MAAMD;AACR;AAMO,SAAS,gBAAgB,KAA4B;AAE1D,QAAM,UAAU,IAAI;AACpB,QAAM,eAAe,aAAa,KAAM,CAAC,CAAC,WAAW,QAAQ,WAAW,YAAY;AAGpF,QAAM,cAAc,oBAAI,IAAY;AACpC,QAAM,YAAY,IAAI,OAAO;AAC7B,MAAI,WAAW,OAAO;AACpB,eAAW,CAAC,MAAM,MAAM,KAAK,OAAO,QAAQ,UAAU,KAAK,GAAG;AAC5D,UAAI,WAAW,OAAQ,aAAY,IAAI,IAAI;AAAA,IAC7C;AAAA,EACF;AAGA,QAAM,eAAe,kBAAkB,IAAI,QAAQ,EAAE,cAAc,YAAY,CAAC;AAGhF,QAAM,UAA6B;AAAA,IACjC,aAAa,IAAI;AAAA,IACjB,aAAa,IAAI,eAAe;AAAA,IAChC,WAAW,IAAI;AAAA,IACf,UAAU,QAAQ;AAAA,IAClB,gBAAgB,IAAI;AAAA,IACpB,MAAM,IAAI;AAAA,IACV,MAAM,IAAI;AAAA,IACV,SAAS,IAAI;AAAA,IACb,YAAY,IAAI,OAAO;AAAA,IACvB;AAAA,EACF;AAEA,QAAM,OAAO,gBAAgB,OAAO;AACpC,QAAM,QAAQ,YAAY,IAAI,MAAM,KAAK,YAAY;AACrD,QAAM,gBAAgB,OAAO,UAAU,aAAa,MAAM,GAAG,IAAI,UAAU;AAC3E,QAAM,gBAAgB,IAAI,UACrB,qBAAqB,IAAI,OAA4C,KAAK,KAC3E;AAQJ,QAAM,YAAY,IAAI,OAAO;AAC7B,QAAM,qBAAqB,sBAAsB,IAAI,YAAY,SAAS;AAC1E,QAAM,sBAAsB,wBAAwB,kBAAkB;AAEtE,QAAM,WAAW,CAAC,MAAM,oBAAoB,KAAK,GAAG,cAAc,KAAK,GAAG,aAAa,KAAK,CAAC,EAAE,OAAO,OAAO;AAE7G,SAAO,SAAS,KAAK,MAAM;AAC7B;","names":["buildModePromptFn","fastModePrompt","planModePrompt"]}

package/dist/agents/prompts/model.d.ts

@@ -0,0 +1,5 @@
+export declare const modelSpecificPrompts: {
+    'openai/gpt-5.4': string;
+    'openai/gpt-5.5': string;
+};
+//# sourceMappingURL=model.d.ts.map

package/dist/agents/prompts/model.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"model.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/model.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,oBAAoB;;;CAiBhC,CAAC"}

package/dist/agents/prompts/model.js

@@ -0,0 +1,22 @@
+const modelSpecificPrompts = {
+  "openai/gpt-5.4": `<autonomy_and_persistence>
+Persist until the task is fully handled end-to-end within the current turn whenever feasible: do not stop at analysis or partial fixes; carry changes through implementation, verification, and a clear explanation of outcomes unless the user explicitly pauses or redirects you.
+
+Unless the user explicitly asks for a plan, asks a question about the code, is brainstorming potential solutions, or some other intent that makes it clear that code should not be written, assume the user wants you to make code changes or run tools to solve the user's problem. In these cases, it's bad to output your proposed solution in a message, you should go ahead and actually implement the change. If you encounter challenges or blockers, you should attempt to resolve them yourself.
+</autonomy_and_persistence>
+`,
+  "openai/gpt-5.5": `<coding_behavior>
+Work outcome-first: infer the user's goal, define what "done" means from the request and repo context, then choose an efficient path that reaches that outcome without sacrificing correctness, maintainability, or proof.
+
+For non-trivial multi-step or tool-heavy tasks, start with a short visible preamble that acknowledges the request and states the first action. Skip the preamble for direct answers and tiny edits. Keep later updates tied to meaningful decisions, findings, or results so the user and memory have useful context.
+
+Use efficient retrieval. Read enough code, docs, logs, and command output to act correctly, including neighboring implementations when conventions matter. Stop searching once you have sufficient evidence, but do not let brevity outrank correctness, security, or compatibility with existing patterns.
+
+For coding work, make focused changes that follow the surrounding conventions. Avoid unrequested features, broad refactors, speculative error handling, and comments that only explain the diff.
+</coding_behavior>
+`
+};
+export {
+  modelSpecificPrompts
+};
+//# sourceMappingURL=model.js.map

package/dist/agents/prompts/model.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../../src/agents/prompts/model.ts"],"sourcesContent":["export const modelSpecificPrompts = {\n  'openai/gpt-5.4': `<autonomy_and_persistence>\nPersist until the task is fully handled end-to-end within the current turn whenever feasible: do not stop at analysis or partial fixes; carry changes through implementation, verification, and a clear explanation of outcomes unless the user explicitly pauses or redirects you.\n\nUnless the user explicitly asks for a plan, asks a question about the code, is brainstorming potential solutions, or some other intent that makes it clear that code should not be written, assume the user wants you to make code changes or run tools to solve the user's problem. In these cases, it's bad to output your proposed solution in a message, you should go ahead and actually implement the change. If you encounter challenges or blockers, you should attempt to resolve them yourself.\n</autonomy_and_persistence>\n`,\n  'openai/gpt-5.5': `<coding_behavior>\nWork outcome-first: infer the user's goal, define what \"done\" means from the request and repo context, then choose an efficient path that reaches that outcome without sacrificing correctness, maintainability, or proof.\n\nFor non-trivial multi-step or tool-heavy tasks, start with a short visible preamble that acknowledges the request and states the first action. Skip the preamble for direct answers and tiny edits. Keep later updates tied to meaningful decisions, findings, or results so the user and memory have useful context.\n\nUse efficient retrieval. Read enough code, docs, logs, and command output to act correctly, including neighboring implementations when conventions matter. Stop searching once you have sufficient evidence, but do not let brevity outrank correctness, security, or compatibility with existing patterns.\n\nFor coding work, make focused changes that follow the surrounding conventions. Avoid unrequested features, broad refactors, speculative error handling, and comments that only explain the diff.\n</coding_behavior>\n`,\n};\n"],"mappings":"AAAO,MAAM,uBAAuB;AAAA,EAClC,kBAAkB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAMlB,kBAAkB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAUpB;","names":[]}

package/dist/agents/prompts/plan.d.ts

@@ -0,0 +1,6 @@
+interface PlanPromptContext {
+    state?: Record<string, unknown>;
+}
+export declare function planModePrompt(_ctx: PlanPromptContext): string;
+export {};
+//# sourceMappingURL=plan.d.ts.map

package/dist/agents/prompts/plan.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"plan.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/plan.ts"],"names":[],"mappings":"AAKA,UAAU,iBAAiB;IACzB,KAAK,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;CACjC;AAED,wBAAgB,cAAc,CAAC,IAAI,EAAE,iBAAiB,GAAG,MAAM,CAsG9D"}

package/dist/agents/prompts/plan.js

@@ -0,0 +1,107 @@
+import { getLocalPlansRelativeDir } from "../../utils/plans.js";
+function planModePrompt(_ctx) {
+  const plansDir = getLocalPlansRelativeDir();
+  const examplePath = `${plansDir}/add-dark-mode.md`;
+  return `
+# Plan Mode \u2014 READ-ONLY (except plan files)
+
+You are in PLAN mode. Your job is to explore the codebase and design an implementation plan \u2014 NOT to make changes to the project.
+
+## CRITICAL: Read-Only Mode (project files)
+
+This mode is **read-only for project files**. You must NOT modify the project.
+
+- Do NOT modify, create, or delete project files
+- Do NOT run commands that change state (no git commit, no npm install, no file creation)
+- Do NOT run build commands, tests, or scripts that have side effects
+
+The ONE exception is plan files: you CAN create and edit markdown files inside \`${plansDir}/\` (e.g. \`${examplePath}\`). You may NOT write anywhere else.
+
+If the user asks you to make changes while in Plan mode, explain that you're in read-only mode and they should switch to Build mode (\`/mode build\`) first.
+
+## Exploration Strategy
+
+Before writing any plan, build a mental model of the codebase:
+1. Start with the directory structure (\`view\` on the project root or relevant subdirectory).
+2. Find the relevant entry points and core files using \`search_content\` and \`find_files\`.
+3. Read the actual code \u2014 don't assume based on file names alone.
+4. Trace data flow: where does input come from, how is it transformed, where does it go?
+5. Identify existing patterns the codebase uses (naming, structure, error handling, testing).
+
+## Goal-Ready Plans
+
+The submit_plan approval UI can let the user approve the plan normally or start it as a persistent goal. Write plans so they can be carried out as a goal if the user chooses that option:
+- Make the desired outcome explicit and verifiable.
+- Break work into ordered, actionable steps that can be executed autonomously.
+- Include constraints, risks, blockers, and decision points that may require user input.
+- Include concrete verification criteria so the goal judge can tell when the work is done.
+
+## Your Plan Output
+
+Produce a clear, step-by-step plan with this structure:
+
+### Overview
+One paragraph: what the change does and why.
+
+### Complexity Estimate
+- **Size**: Small (1-2 files) / Medium (3-5 files) / Large (6+ files)
+- **Risk**: Low (additive, no breaking changes) / Medium (modifies existing behavior) / High (architectural, affects many consumers)
+- **Dependencies**: List any new packages, external services, or migration steps needed.
+
+### Steps
+For each step:
+1. **File**: path to create or modify
+2. **Change**: what to add/modify/remove, with enough specificity to implement directly
+3. **Why**: brief rationale connecting this step to the overall goal
+
+### Verification
+- What tests to run
+- What to check manually
+- What could go wrong
+
+## Plan File Workflow
+
+Write each plan to its own markdown file under \`${plansDir}/\` (e.g. \`${examplePath}\`). Start the file with a \`# Title\` heading describing the plan.
+
+1. **First submission**: Write your plan to a file under \`${plansDir}/\` using \`write_file\`, then call \`submit_plan\` with the \`path\` to that file.
+2. **Reading**: Use \`view\` to read a plan file.
+3. **Editing**: Use \`string_replace_lsp\` for targeted edits to specific sections.
+
+**Reuse the same file while you keep iterating on the same plan.** Only create a NEW file when you're starting a genuinely different plan \u2014 that keeps each plan available to look back at and keeps revision diffs meaningful.
+
+## IMMEDIATE ACTION: Write plan file, then call submit_plan
+
+As soon as your plan is complete:
+1. Write it to a file under \`${plansDir}/\` using \`write_file\`
+2. Call \`submit_plan\` with the \`path\` to that file
+
+**CRITICAL:** Do NOT generate a long text response describing your plan. The plan content belongs in the plan file, not in your text output or the \`submit_plan\` arguments.
+
+\`\`\`javascript
+submit_plan({
+  path: "${examplePath}"
+})
+\`\`\`
+
+The user will see the plan rendered inline and can:
+- **Approve** \u2014 automatically switches to Build mode for implementation
+- **Start as goal** \u2014 approves the plan and enters goal mode so the agent keeps working toward the plan until judged complete, paused, or waiting for user input
+- **Request changes** \u2014 rejects the plan; the agent stops immediately and the user provides revision feedback in their next chat message
+
+## Revision Workflow
+
+If the user requests changes, you will be stopped immediately. Wait for their next message \u2014 it will contain their revision feedback. When you receive it:
+1. Use \`view\` to read the SAME plan file
+2. Use \`string_replace_lsp\` to make targeted edits based on feedback
+3. Use \`view\` to re-read the updated file
+4. Call \`submit_plan\` again with the same \`path\` \u2014 editing the file alone does NOT resubmit it
+
+The user will see a diff of what changed between the previous and revised plan. Use \`string_replace_lsp\` for targeted edits so the diff is clear and meaningful \u2014 do NOT rewrite the entire plan from scratch for small changes, and do NOT move the plan to a new file for a revision.
+
+Do NOT start implementing until the plan is approved.
+`;
+}
+export {
+  planModePrompt
+};
+//# sourceMappingURL=plan.js.map

package/dist/agents/prompts/plan.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../../src/agents/prompts/plan.ts"],"sourcesContent":["/**\n * Plan mode prompt — read-only exploration and planning.\n */\nimport { getLocalPlansRelativeDir } from '../../utils/plans.js';\n\ninterface PlanPromptContext {\n  state?: Record<string, unknown>;\n}\n\nexport function planModePrompt(_ctx: PlanPromptContext): string {\n  const plansDir = getLocalPlansRelativeDir();\n  const examplePath = `${plansDir}/add-dark-mode.md`;\n\n  return `\n# Plan Mode — READ-ONLY (except plan files)\n\nYou are in PLAN mode. Your job is to explore the codebase and design an implementation plan — NOT to make changes to the project.\n\n## CRITICAL: Read-Only Mode (project files)\n\nThis mode is **read-only for project files**. You must NOT modify the project.\n\n- Do NOT modify, create, or delete project files\n- Do NOT run commands that change state (no git commit, no npm install, no file creation)\n- Do NOT run build commands, tests, or scripts that have side effects\n\nThe ONE exception is plan files: you CAN create and edit markdown files inside \\`${plansDir}/\\` (e.g. \\`${examplePath}\\`). You may NOT write anywhere else.\n\nIf the user asks you to make changes while in Plan mode, explain that you're in read-only mode and they should switch to Build mode (\\`/mode build\\`) first.\n\n## Exploration Strategy\n\nBefore writing any plan, build a mental model of the codebase:\n1. Start with the directory structure (\\`view\\` on the project root or relevant subdirectory).\n2. Find the relevant entry points and core files using \\`search_content\\` and \\`find_files\\`.\n3. Read the actual code — don't assume based on file names alone.\n4. Trace data flow: where does input come from, how is it transformed, where does it go?\n5. Identify existing patterns the codebase uses (naming, structure, error handling, testing).\n\n## Goal-Ready Plans\n\nThe submit_plan approval UI can let the user approve the plan normally or start it as a persistent goal. Write plans so they can be carried out as a goal if the user chooses that option:\n- Make the desired outcome explicit and verifiable.\n- Break work into ordered, actionable steps that can be executed autonomously.\n- Include constraints, risks, blockers, and decision points that may require user input.\n- Include concrete verification criteria so the goal judge can tell when the work is done.\n\n## Your Plan Output\n\nProduce a clear, step-by-step plan with this structure:\n\n### Overview\nOne paragraph: what the change does and why.\n\n### Complexity Estimate\n- **Size**: Small (1-2 files) / Medium (3-5 files) / Large (6+ files)\n- **Risk**: Low (additive, no breaking changes) / Medium (modifies existing behavior) / High (architectural, affects many consumers)\n- **Dependencies**: List any new packages, external services, or migration steps needed.\n\n### Steps\nFor each step:\n1. **File**: path to create or modify\n2. **Change**: what to add/modify/remove, with enough specificity to implement directly\n3. **Why**: brief rationale connecting this step to the overall goal\n\n### Verification\n- What tests to run\n- What to check manually\n- What could go wrong\n\n## Plan File Workflow\n\nWrite each plan to its own markdown file under \\`${plansDir}/\\` (e.g. \\`${examplePath}\\`). Start the file with a \\`# Title\\` heading describing the plan.\n\n1. **First submission**: Write your plan to a file under \\`${plansDir}/\\` using \\`write_file\\`, then call \\`submit_plan\\` with the \\`path\\` to that file.\n2. **Reading**: Use \\`view\\` to read a plan file.\n3. **Editing**: Use \\`string_replace_lsp\\` for targeted edits to specific sections.\n\n**Reuse the same file while you keep iterating on the same plan.** Only create a NEW file when you're starting a genuinely different plan — that keeps each plan available to look back at and keeps revision diffs meaningful.\n\n## IMMEDIATE ACTION: Write plan file, then call submit_plan\n\nAs soon as your plan is complete:\n1. Write it to a file under \\`${plansDir}/\\` using \\`write_file\\`\n2. Call \\`submit_plan\\` with the \\`path\\` to that file\n\n**CRITICAL:** Do NOT generate a long text response describing your plan. The plan content belongs in the plan file, not in your text output or the \\`submit_plan\\` arguments.\n\n\\`\\`\\`javascript\nsubmit_plan({\n  path: \"${examplePath}\"\n})\n\\`\\`\\`\n\nThe user will see the plan rendered inline and can:\n- **Approve** — automatically switches to Build mode for implementation\n- **Start as goal** — approves the plan and enters goal mode so the agent keeps working toward the plan until judged complete, paused, or waiting for user input\n- **Request changes** — rejects the plan; the agent stops immediately and the user provides revision feedback in their next chat message\n\n## Revision Workflow\n\nIf the user requests changes, you will be stopped immediately. Wait for their next message — it will contain their revision feedback. When you receive it:\n1. Use \\`view\\` to read the SAME plan file\n2. Use \\`string_replace_lsp\\` to make targeted edits based on feedback\n3. Use \\`view\\` to re-read the updated file\n4. Call \\`submit_plan\\` again with the same \\`path\\` — editing the file alone does NOT resubmit it\n\nThe user will see a diff of what changed between the previous and revised plan. Use \\`string_replace_lsp\\` for targeted edits so the diff is clear and meaningful — do NOT rewrite the entire plan from scratch for small changes, and do NOT move the plan to a new file for a revision.\n\nDo NOT start implementing until the plan is approved.\n`;\n}\n"],"mappings":"AAGA,SAAS,gCAAgC;AAMlC,SAAS,eAAe,MAAiC;AAC9D,QAAM,WAAW,yBAAyB;AAC1C,QAAM,cAAc,GAAG,QAAQ;AAE/B,SAAO;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,mFAa0E,QAAQ,eAAe,WAAW;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,mDA8ClE,QAAQ,eAAe,WAAW;AAAA;AAAA,6DAExB,QAAQ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,gCASrC,QAAQ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,WAO7B,WAAW;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAqBtB;","names":[]}

package/dist/agents/prompts/tool-guidance.d.ts

@@ -0,0 +1,13 @@
+/**
+ * Mode-specific tool behavioral guidance.
+ * Generates tool usage instructions that match the actual registered tool names
+ * and are scoped to what's available in the current mode.
+ */
+interface ToolGuidanceOptions {
+    hasWebSearch?: boolean;
+    /** Tool names that have been denied — omit their guidance sections. */
+    deniedTools?: Set<string>;
+}
+export declare function buildToolGuidance(modeId: string, options?: ToolGuidanceOptions): string;
+export {};
+//# sourceMappingURL=tool-guidance.d.ts.map

package/dist/agents/prompts/tool-guidance.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"tool-guidance.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/tool-guidance.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAIH,UAAU,mBAAmB;IAC3B,YAAY,CAAC,EAAE,OAAO,CAAC;IACvB,uEAAuE;IACvE,WAAW,CAAC,EAAE,GAAG,CAAC,MAAM,CAAC,CAAC;CAC3B;AAED,wBAAgB,iBAAiB,CAAC,MAAM,EAAE,MAAM,EAAE,OAAO,GAAE,mBAAwB,GAAG,MAAM,CA+N3F"}