mastracode 0.13.1-alpha.2 → 0.14.0-alpha.4

package/CHANGELOG.md

@@ -1,5 +1,37 @@
 # mastracode
 
+## 0.14.0-alpha.4
+
+### Minor Changes
+
+- Added `/browser set` command for configuring browser profile, executable path, storage state, and CDP URL. Updated the interactive wizard with advanced options for custom browsers and CDP connections. ([#15194](https://github.com/mastra-ai/mastra/pull/15194))
+
+### Patch Changes
+
+- Improved Mastra Code prompt guidance for autonomous decisions and blocked work. ([#15352](https://github.com/mastra-ai/mastra/pull/15352))
+
+- Improved observational memory summaries to use caveman-style custom instructions for terser stored observations. ([#15359](https://github.com/mastra-ai/mastra/pull/15359))
+
+- Updated dependencies [[`8687969`](https://github.com/mastra-ai/mastra/commit/86879696b80f87269bec34fd17fa377bce3a5892), [`cbdf3e1`](https://github.com/mastra-ai/mastra/commit/cbdf3e12b3d0c30a6e5347be658e2009648c130a), [`8fe46d3`](https://github.com/mastra-ai/mastra/commit/8fe46d354027f3f0f0846e64219772348de106dd), [`18c67db`](https://github.com/mastra-ai/mastra/commit/18c67dbb9c9ebc26f26f65f7d3ff836e5691ef46), [`190f452`](https://github.com/mastra-ai/mastra/commit/190f45258b0640e2adfc8219fa3258cdc5b8f071), [`8dcc77e`](https://github.com/mastra-ai/mastra/commit/8dcc77e78a5340f5848f74b9e9f1b3da3513c1f5), [`aa67fc5`](https://github.com/mastra-ai/mastra/commit/aa67fc59ee8a5eeff1f23eb05970b8d7a536c8ff), [`fa8140b`](https://github.com/mastra-ai/mastra/commit/fa8140bcd4251d2e3ac85fdc5547dfc4f372b5be), [`190f452`](https://github.com/mastra-ai/mastra/commit/190f45258b0640e2adfc8219fa3258cdc5b8f071), [`a6b7d82`](https://github.com/mastra-ai/mastra/commit/a6b7d820d5028da1284899baf3a7318b5d573f42), [`8ce5d0d`](https://github.com/mastra-ai/mastra/commit/8ce5d0dab0e13ee9ce01562fc434523e93a71ef9), [`7e7bf60`](https://github.com/mastra-ai/mastra/commit/7e7bf606886bf374a6f9d4ca9b09dd83d0533372), [`184907d`](https://github.com/mastra-ai/mastra/commit/184907d775d8609c03c26e78ccaf37315f3aa287), [`18c67db`](https://github.com/mastra-ai/mastra/commit/18c67dbb9c9ebc26f26f65f7d3ff836e5691ef46), [`5f3d4dd`](https://github.com/mastra-ai/mastra/commit/5f3d4ddf237241f4b238ac062ac61eadabed0770), [`0c4cd13`](https://github.com/mastra-ai/mastra/commit/0c4cd131931c04ac5405373c932a242dbe88edd6), [`190f452`](https://github.com/mastra-ai/mastra/commit/190f45258b0640e2adfc8219fa3258cdc5b8f071), [`b16a753`](https://github.com/mastra-ai/mastra/commit/b16a753d5748440248d7df82e29bb987a9c8386c)]:
+  - @mastra/stagehand@0.2.0-alpha.0
+  - @mastra/core@1.25.0-alpha.3
+  - @mastra/agent-browser@0.2.0-alpha.0
+  - @mastra/pg@1.9.1-alpha.1
+  - @mastra/libsql@1.8.1-alpha.1
+  - @mastra/mcp@1.5.0-alpha.0
+
+## 0.14.0-alpha.3
+
+### Minor Changes
+
+- Added /api-keys command to manage API keys for model providers. You can add, update, or remove keys directly, or access it from the settings menu. ([#15014](https://github.com/mastra-ai/mastra/pull/15014))
+
+### Patch Changes
+
+- Updated dependencies [[`f5e254f`](https://github.com/mastra-ai/mastra/commit/f5e254f2984c4aae25e26a34ac2e2bbd637b27a6), [`6544c97`](https://github.com/mastra-ai/mastra/commit/6544c974182bccfb31f48efff07671ac528d1533)]:
+  - @mastra/pg@1.9.1-alpha.0
+  - @mastra/libsql@1.8.1-alpha.0
+
 ## 0.13.1-alpha.2
 
 ### Patch Changes

package/dist/agents/memory.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"memory.d.ts","sourceRoot":"","sources":["../../src/agents/memory.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,8BAA8B,CAAC;AACnE,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,sBAAsB,CAAC;AACjE,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,qBAAqB,CAAC;AAExD,OAAO,EAAE,MAAM,EAAE,MAAM,gBAAgB,CAAC;AA4CxC;;;;GAIG;AACH,wBAAgB,gBAAgB,CAAC,OAAO,EAAE,oBAAoB,EAAE,MAAM,CAAC,EAAE,YAAY,IAC3E,oBAAoB;IAAE,cAAc,EAAE,cAAc,CAAA;CAAE,YAiD/D"}
+{"version":3,"file":"memory.d.ts","sourceRoot":"","sources":["../../src/agents/memory.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,8BAA8B,CAAC;AACnE,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,sBAAsB,CAAC;AACjE,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,qBAAqB,CAAC;AAExD,OAAO,EAAE,MAAM,EAAE,MAAM,gBAAgB,CAAC;AAoExC;;;;GAIG;AACH,wBAAgB,gBAAgB,CAAC,OAAO,EAAE,oBAAoB,EAAE,MAAM,CAAC,EAAE,YAAY,IAC3E,oBAAoB;IAAE,cAAc,EAAE,cAAc,CAAA;CAAE,YAmD/D"}

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

@@ -1 +1 @@
-{"version":3,"file":"base.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/base.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,MAAM,WAAW,aAAa;IAC5B,WAAW,EAAE,MAAM,CAAC;IACpB,WAAW,EAAE,MAAM,CAAC;IACpB,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,QAAQ,EAAE,MAAM,CAAC;IACjB,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,UAAU,CAAC,EAAE;QAAE,KAAK,EAAE,MAAM,CAAC;QAAC,IAAI,EAAE,MAAM,CAAC;QAAC,UAAU,EAAE,MAAM,CAAA;KAAE,GAAG,IAAI,CAAC;IACxE,YAAY,EAAE,MAAM,CAAC;CACtB;AAED,wBAAgB,eAAe,CAAC,GAAG,EAAE,aAAa,GAAG,MAAM,CA6H1D"}
+{"version":3,"file":"base.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/base.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,MAAM,WAAW,aAAa;IAC5B,WAAW,EAAE,MAAM,CAAC;IACpB,WAAW,EAAE,MAAM,CAAC;IACpB,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,QAAQ,EAAE,MAAM,CAAC;IACjB,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,UAAU,CAAC,EAAE;QAAE,KAAK,EAAE,MAAM,CAAC;QAAC,IAAI,EAAE,MAAM,CAAC;QAAC,UAAU,EAAE,MAAM,CAAA;KAAE,GAAG,IAAI,CAAC;IACxE,YAAY,EAAE,MAAM,CAAC;CACtB;AAED,wBAAgB,eAAe,CAAC,GAAG,EAAE,aAAa,GAAG,MAAM,CAwH1D"}

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

@@ -8,5 +8,5 @@ import type { PromptContext } from './index.js';
  * 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 task_write to track your steps\n- Work on ONE step at a time \u2014 complete it and verify it works before moving on\n- If the approach is risky or ambiguous, ask the user before proceeding\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. **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 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- Use task_check to ensure all tracked tasks are done\n\n**Don't mark something as done until you've verified 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 stuck after 2 attempts, tell the user what you've tried\n\n## Git in Build Mode\n\n- Don't commit unless asked \u2014 just report what you changed\n- Before committing, verify the code compiles and passes lint\n- Use descriptive branch names: `feat/...`, `fix/...`, `refactor/...`\n";
+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 task_write to track your steps\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 Prove that it works. 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- Use task_check 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

@@ -1 +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,m8DAkD3B,CAAC"}
+{"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,6lEAkD3B,CAAC"}

package/dist/{chunk-XV3GXFJW.js → chunk-56R7RUUI.js}

@@ -1,10 +1,10 @@
-import { loadSettings, MEMORY_GATEWAY_PROVIDER, getAvailableModePacks, getAvailableOmPacks, resolveModelDefaults, resolveOmModel, mastra, releaseThreadLock, acquireThreadLock, getCustomProviderId, toCustomProviderModelId, saveSettings } from './chunk-EHH67Q47.js';
-import { AuthStorage, detectProject, getResourceIdOverride, getStorageConfig, getVectorDatabasePath, getCurrentGitBranch, getOmScope, getDatabasePath } from './chunk-WGXQUI3D.js';
+import { loadSettings, MEMORY_GATEWAY_PROVIDER, getAvailableModePacks, getAvailableOmPacks, resolveModelDefaults, resolveOmModel, mastra, releaseThreadLock, acquireThreadLock, getCustomProviderId, toCustomProviderModelId, saveSettings } from './chunk-AMPURF4V.js';
+import { AuthStorage, detectProject, getResourceIdOverride, getStorageConfig, getVectorDatabasePath, getCurrentGitBranch, getOmScope, getDatabasePath } from './chunk-XV4ZDFJA.js';
 import { MC_TOOLS, getToolCategory, TOOL_NAME_OVERRIDES } from './chunk-JP7WKMD4.js';
 import { Agent } from '@mastra/core/agent';
 import { taskCheckTool, taskWriteTool, Harness } from '@mastra/core/harness';
 import { GatewayRegistry, PROVIDER_REGISTRY, ModelRouterLanguageModel, GATEWAY_AUTH_HEADER, MastraGateway, ModelsDevGateway, NetlifyGateway } from '@mastra/core/llm';
-import { AgentsMDInjector } from '@mastra/core/processors';
+import { PrefillErrorHandler, AgentsMDInjector } from '@mastra/core/processors';
 import { createTool } from '@mastra/core/tools';
 import { tavily } from '@tavily/core';
 import { z } from 'zod';
@@ -42,6 +42,12 @@ Current mode: ${ctx.mode}
 
 ${ctx.toolGuidance}
 
+# Memory Style
+- Your memory system may contain observations or reflections written in terse caveman-speak to reduce token usage.
+- Treat that compressed memory style as storage format only.
+- Do NOT imitate or adopt caveman-speak in your user-facing responses unless the user explicitly asks for that style.
+- Use the memory content for facts and context, but respond in your normal clear professional style by default.
+
 # How to Work on Tasks
 
 ## Start by Understanding
@@ -49,16 +55,6 @@ ${ctx.toolGuidance}
 - For unfamiliar codebases, check git log to understand recent changes and patterns.
 - Identify existing conventions (naming, structure, error handling) and follow them.
 
-## Work Incrementally
-- Focus on ONE thing at a time. Complete it fully before moving to the next.
-- Leave the codebase in a clean state after each change \u2014 no half-implemented features.
-- For multi-step tasks, use tasks to track progress and ensure nothing is missed.
-
-## Verify Before Moving On
-- After each change, verify it works. Don't assume \u2014 actually test it.
-- Run the relevant tests, check for type errors, or manually verify the behavior.
-- If something breaks, fix it immediately. Don't pile more changes on top of broken code.
-
 # Coding Philosophy
 
 - **Avoid over-engineering.** Only make changes that are directly requested or clearly necessary.
@@ -73,8 +69,7 @@ ${ctx.toolGuidance}
 ## Hard Rules
 - NEVER run destructive commands (\`push --force\`, \`reset --hard\`, \`clean -fd\`) unless explicitly requested.
 - NEVER use interactive flags (\`git rebase -i\`, \`git add -i\`) \u2014 TTY input isn't supported.
-- NEVER commit or push unless the user explicitly asks.
-- NEVER force push to \`main\` or \`master\` without warning the user first.
+- NEVER force push to \`main\` or \`master\` without asking the user first.
 - Avoid \`git commit --amend\` unless the commit was just created and hasn't been pushed.
 
 ## Secrets
@@ -84,7 +79,7 @@ Don't commit files likely to contain secrets (\`.env\`, \`*.key\`, \`credentials
 Write commit messages that explain WHY, not just WHAT. Match the repo's existing style. Include \`Co-Authored-By: Mastra Code${ctx.modelId ? ` (${ctx.modelId})` : ""} <noreply@mastra.ai>\` in the message body.
 
 ## Pull Requests
-Use \`gh pr create\`. Include a summary of what changed and a test plan.
+Use \`gh pr create\`. Include a summary of what changed and a test plan. Word the pull request title/description to explain the entire unit of work being shipped, worded to explain it to someone who doesn't know anything about the work being shipped. Do not add details of fixes that were needed along the way.
 
 # Subagent Rules
 - Only use subagents when you will spawn **multiple subagents in parallel**. If you only need one task done, do it yourself instead of delegating to a single subagent. Exception: the **audit-tests** subagent may be used on its own.
@@ -94,11 +89,10 @@ Use \`gh pr create\`. Include a summary of what changed and a test plan.
 - NEVER guess file paths or function signatures. Use search_content/find_files to find them.
 - NEVER make up URLs. Only use URLs the user provides or that you find in the codebase.
 - When referencing code locations, include the file path and line number.
-- If you're unsure about something, ask the user rather than guessing.
 
 # File Access & Sandbox
 
-By default, you can only access files within the current project directory. If you get a "Permission denied" or "Access denied" error when trying to read, write, or access files outside the project root, do NOT keep retrying. Instead, use the \`request_access\` tool to request access to the external directory. Only tell the user to run \`/sandbox\` themselves if the tool is unavailable or the request cannot be made from the current context.
+By default, you can only access files within the current project directory. If you get a "Permission denied" or "Access denied" error when trying to read, write, or access files outside the project root, do NOT keep retrying. Instead, use the \`request_access\` tool to request access to the external directory.
 
 You are an autonomous AI assistant with strong common sense reasoning capabilities. Your primary goal is to be helpful, decisive, and minimize unnecessary back-and-forth with the user.
 
@@ -111,7 +105,7 @@ You are an autonomous AI assistant with strong common sense reasoning capabiliti
 **Common Sense Reasoning**
 - Apply implicit knowledge about how the world works (cause-and-effect, social norms, practical constraints)
 - Consider the user's likely intent, not just literal words
-- Use your internal reasoning tokens to evaluate multiple interpretations before choosing the most sensible one
+- Make reasonable assumptions when the most sensible path is clear, but ask the user when ambiguity is material and could change the outcome.
 - Bias towards action, but be flexible in your rules. If you think the user would want you to ask them, then do! Especially if they've previously stated a preference that you do in the specific situation.
 
 **Decision Framework**
@@ -146,6 +140,7 @@ Only if all are "no" \u2192 THEN ask the user
 - Information available through reasonable inference
 - Choices where any reasonable option works
 - Things you can reasonably assume based on context
+- When common sense applies or the answer is obvious
 
 # Tone and Style
 - Your output is displayed in a terminal so long output text will be hard for the user to read. Keep responses short/concise and to the point, the user will ask questions if they need you to expand on anything. Be critical of yourself and don't add filler sentences, say what you mean, and say it quickly, while remaining friendly.
@@ -186,7 +181,7 @@ You are in BUILD mode. You have full access to all tools and can read, write, ed
 **For non-trivial tasks** (3+ files, architectural decisions, unclear requirements):
 - Use task_write to track your steps
 - Work on ONE step at a time \u2014 complete it and verify it works before moving on
-- If the approach is risky or ambiguous, ask the user before proceeding
+- If multiple approaches are plausible and the choice would materially affect scope, behavior, or risk, stop and ask the user
 
 ## The Implementation Loop
 
@@ -195,9 +190,10 @@ 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. **Clean up** \u2014 Ensure no broken code, no debug statements, no half-done features.
+4. **Prove** \u2014 Prove that it works. 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 working.
+Only move to the next change after the current one is verified and proved to be working.
 
 ## Verification is Required
 
@@ -207,7 +203,7 @@ Before considering any task complete:
 - If there are no automated tests, manually verify the behavior works as expected
 - Use task_check to ensure all tracked tasks are done
 
-**Don't mark something as done until you've verified it actually works.**
+**Don't mark something as done until you've verified and proved it actually works.**
 
 ## Error Recovery
 
@@ -216,11 +212,10 @@ When something breaks:
 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 stuck after 2 attempts, tell the user what you've tried
+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
 
-- Don't commit unless asked \u2014 just report what you changed
 - Before committing, verify the code compiles and passes lint
 - Use descriptive branch names: \`feat/...\`, \`fix/...\`, \`refactor/...\`
 `;
@@ -1388,6 +1383,28 @@ function getReflectorModel({ requestContext }) {
     requestContext
   });
 }
+var CAVEMAN_OM_INSTRUCTION = `Respond terse like smart caveman. All technical substance stay. Only fluff die.
+
+Use full caveman compression style.
+
+Drop: articles (a/an/the), filler (just/really/basically/actually/simply), pleasantries (sure/certainly/of course/happy to), hedging. Fragments OK. Short synonyms (big not extensive, fix not "implement a solution for"). Technical terms exact. Code blocks unchanged. Errors quoted exact. Leave out the words "agent" and "assistant" at the start of each observation line, it is assumed each line is referring to the assistant unless it specifically says it was about the user. Leave out parenthesis and other text characters like * that would not contribute to understanding the observations.
+
+Pattern: \`[thing] [action] [reason]. [next step]\`
+
+Not: "Sure! I'd be happy to help you with that. The issue you're experiencing is likely caused by..."
+Yes: "Bug in auth middleware. Token expiry check use < not <=. Fix:"
+
+Example 1
+\u{1F534} 14:31 user asks why React component rerenders
+\u{1F7E1} 14:32 saw inline object prop create new ref each render, cause rerender
+\u2705 14:34 fixed render issue by wrap object in useMemo
+
+Example 2
+\u{1F7E1} 15:10 explained pool reuse DB connections, skip repeat handshake overhead
+
+Don't say "Agent did x", say "did x". It will be assumed the agent did what was observed. The who should only be specified for the user or other third parties: "user asked x"
+
+Drop caveman for: security warnings, irreversible action confirmations, multi-step sequences where fragment order risks misread, user asks to clarify or repeats question, and anything that requires remembering verbatim content. Resume caveman after clear part done`;
 function getDynamicMemory(storage, vector) {
   return ({ requestContext }) => {
     const state = getHarnessState(requestContext);
@@ -1417,13 +1434,14 @@ function getDynamicMemory(storage, vector) {
             blockAfter: 2,
             previousObserverTokens: observerPreviousObservationTokens,
             threadTitle: true,
-            instruction: 'Messages wrapped in <system-reminder type="dynamic-agents-md" ...>...</system-reminder> are ephemeral project-context instructions injected from files on disk. Do NOT observe or extract information from these messages \u2014 they are reloaded automatically when needed and should not be stored in memory.'
+            instruction: 'Messages wrapped in <system-reminder type="dynamic-agents-md" ...>...</system-reminder> are ephemeral project-context instructions injected from files on disk. Do NOT observe or extract information from these messages \u2014 they are reloaded automatically when needed and should not be stored in memory.\n\n' + CAVEMAN_OM_INSTRUCTION
           },
           reflection: {
             bufferActivation: isResourceScope ? void 0 : 1 / 2,
             blockAfter: 1.1,
             model: getReflectorModel,
-            observationTokens: refThreshold
+            observationTokens: refThreshold,
+            instruction: CAVEMAN_OM_INSTRUCTION
           }
         }
       }
@@ -2707,7 +2725,8 @@ async function createMastraCode(config) {
           return getStaticallyLoadedInstructionPaths(projectPath);
         }
       })
-    ]
+    ],
+    errorProcessors: [new PrefillErrorHandler()]
   });
   const defaultSubagents = [exploreSubagent, planSubagent, executeSubagent];
   const defaultModes = [
@@ -2922,5 +2941,5 @@ async function createMastraCode(config) {
 }
 
 export { createAuthStorage, createMastraCode };
-//# sourceMappingURL=chunk-XV3GXFJW.js.map
-//# sourceMappingURL=chunk-XV3GXFJW.js.map
+//# sourceMappingURL=chunk-56R7RUUI.js.map
+//# sourceMappingURL=chunk-56R7RUUI.js.map