@mastra/editor 0.11.0-alpha.2 → 0.11.0-alpha.3

package/CHANGELOG.md

@@ -1,5 +1,40 @@
 # @mastra/editor
 
+## 0.11.0-alpha.3
+
+### Minor Changes
+
+- Added agent override support to the agent and editor APIs. ([#17227](https://github.com/mastra-ai/mastra/pull/17227))
+
+  Code-defined agents can now declare which fields Studio may edit with the `editor` option:
+
+  ```ts
+  new Agent({
+    name: 'Weather Agent',
+    model,
+    editor: {
+      instructions: true,
+      tools: { description: true },
+    },
+  });
+  ```
+
+  The editor applies stored overrides only for fields the `editor` config owns, so locked fields keep their code-defined values. Per-agent `editor: false` locks an agent entirely.
+
+  `MastraEditor` accepts a `source` setting that picks the editing experience:
+
+  ```ts
+  new MastraEditor({ source: 'code' });
+  ```
+
+  - `source: 'code'` — the editor auto-wires a `FilesystemStore` (defaulting to `./mastra/editor/`, overridable with `codePath`) when no editor storage is supplied, and persists overrides as deterministic per-agent JSON files.
+  - `source: 'db'` (default) — keeps the existing storage-backed flow against whatever storage the project has configured.
+
+### Patch Changes
+
+- Updated dependencies [[`a18775a`](https://github.com/mastra-ai/mastra/commit/a18775a693172546ee2378d39b67d4e32895b251), [`1baf2d1`](https://github.com/mastra-ai/mastra/commit/1baf2d152c6881338ff8f114633d5316fe13dd15)]:
+  - @mastra/core@1.38.0-alpha.5
+
 ## 0.11.0-alpha.2
 
 ### Minor Changes

package/dist/ee/index.cjs

@@ -160,7 +160,7 @@ var workspace = new import_workspace.Workspace({
 });
 function createBuilderAgent(args) {
   const memory = new import_memory.Memory();
-  return new import_agent.Agent({
+  const config = {
     instructions: `You are the Agent Builder.
 
 Your job: turn a non-technical user's plain-language request into a fully configured, production-quality agent in a single turn.
@@ -296,7 +296,8 @@ The system prompt written into \`set-agent-instructions\` MUST include all of th
     id: "builder-agent",
     name: "Agent Builder Agent",
     description: "An agent that can build agents"
-  });
+  };
+  return new import_agent.Agent(config);
 }
 // Annotate the CommonJS export names for ESM import in node:
 0 && (module.exports = {

package/dist/ee/index.cjs.map

@@ -1 +1 @@
-{"version":3,"sources":["../../src/ee/index.ts","../../src/ee/agent-builder.ts","../../src/ee/agent-builder-agent.ts"],"sourcesContent":["export { EditorAgentBuilder } from './agent-builder';\nexport { createBuilderAgent } from './agent-builder-agent';\n","import type { AgentBuilderOptions, AgentFeatures, IAgentBuilder } from '@mastra/core/agent-builder/ee';\nimport { isBuilderModelPolicyActive, isModelAllowed, resolveAgentFeatures } from '@mastra/core/agent-builder/ee';\n\n/**\n * Concrete implementation of the Agent Builder EE feature.\n * Instantiated by MastraEditor.resolveBuilder() when builder config is enabled.\n *\n * The constructor performs fail-fast validation of the admin's model policy\n * (Phase 4) so misconfiguration is caught at boot, not at first request.\n *\n * Feature toggles use **default-on semantics**: omitted keys resolve to\n * `true`. Admins opt out by setting a key to `false`. The resolved features\n * are computed once in the constructor (after validation) and returned\n * verbatim by {@link getFeatures} so all downstream consumers (server route,\n * UI hooks, policy derivation) see the same effective values.\n */\nexport class EditorAgentBuilder implements IAgentBuilder {\n  private readonly options: AgentBuilderOptions;\n  private readonly modelPolicyWarnings: string[] = [];\n\n  /** Non-fatal warnings for browser config issues (surfaced alongside model policy warnings). */\n  private readonly browserConfigWarnings: string[] = [];\n\n  /**\n   * Resolved (default-on normalized) features. Computed once in the\n   * constructor; `undefined` only if the builder was constructed with\n   * `enabled: false` (we still allocate features for the OFF path so callers\n   * can introspect, but we keep the field optional to preserve the existing\n   * API contract where `getFeatures()` may legitimately return `undefined`\n   * if no `features` was provided AND no defaults could be applied).\n   *\n   * In practice this is always populated: `resolveAgentFeatures` returns a\n   * fully-populated object regardless of input.\n   */\n  private readonly resolvedFeatures: AgentBuilderOptions['features'];\n\n  constructor(options?: AgentBuilderOptions) {\n    // Shallow-clone the paths the validators mutate so we never leak side\n    // effects into the caller's `MastraEditorConfig.builder` object.\n    // `validateBrowserConfig` writes to `features.agent.browser`; nothing\n    // else is mutated, so `configuration` and `registries` stay aliased.\n    const source = options ?? {};\n    this.options = {\n      ...source,\n      features: source.features\n        ? {\n            ...source.features,\n            agent: source.features.agent ? { ...source.features.agent } : undefined,\n          }\n        : undefined,\n    };\n    this.validateModelPolicy();\n    this.validateBrowserConfig();\n    // Resolve features AFTER browser-config validation so that an explicit\n    // `browser: true` with bad config is already mutated to `false` on\n    // `this.options.features.agent.browser`. The resolver then sees the\n    // downgraded value and returns it as-is.\n    this.resolvedFeatures = {\n      agent: resolveAgentFeatures(this.options.features?.agent, {\n        hasBrowserConfig: this.hasValidBrowserConfig(),\n      }),\n    };\n  }\n\n  get enabled(): boolean {\n    return this.options.enabled !== false;\n  }\n\n  getFeatures(): AgentBuilderOptions['features'] {\n    return this.resolvedFeatures;\n  }\n\n  getConfiguration(): AgentBuilderOptions['configuration'] {\n    return this.options.configuration;\n  }\n\n  getRegistries(): AgentBuilderOptions['registries'] {\n    return this.options.registries;\n  }\n\n  getModelPolicyWarnings(): string[] {\n    return [...this.modelPolicyWarnings, ...this.browserConfigWarnings];\n  }\n\n  /**\n   * True when `configuration.agent.browser` declares a provider. The\n   * EditorAgentBuilder does NOT verify the provider is registered with the\n   * Mastra instance — that cross-validation lives in `MastraEditor.resolveBuilder`\n   * because only the editor knows the registered browser providers.\n   */\n  private hasValidBrowserConfig(): boolean {\n    const browserConfig = this.options.configuration?.agent?.browser;\n    return Boolean(browserConfig?.config?.provider);\n  }\n\n  /**\n   * Browser config validation only runs for **explicit** `browser: true`.\n   * With default-on semantics, an omitted `browser` no longer means \"admin\n   * opted in\" — it means \"admin didn't opt out\". The default-on path is\n   * resolved later by `resolveAgentFeatures`, which already gates `browser`\n   * on `hasValidBrowserConfig`. We don't want to spam every default-config\n   * deployment with warnings.\n   */\n  private validateBrowserConfig(): void {\n    const explicitBrowser = this.options.features?.agent?.browser;\n    if (explicitBrowser !== true) return;\n\n    const browserConfig = this.options.configuration?.agent?.browser;\n    if (!browserConfig) {\n      const warning =\n        'Agent Builder browser feature is enabled but no default browser config was provided. ' +\n        'Set `editor.builder.configuration.agent.browser` to a valid browser config ' +\n        '(e.g. `{ type: \"inline\", config: { provider: \"stagehand\" } }`). ' +\n        'The browser toggle will be hidden until a default is configured.';\n      this.browserConfigWarnings.push(warning);\n      // eslint-disable-next-line no-console\n      console.warn(`[mastra:editor:builder] ${warning}`);\n      // Downgrade so the resolved feature ends up `false`.\n      if (this.options.features?.agent) {\n        this.options.features.agent.browser = false;\n      }\n      return;\n    }\n\n    if (!browserConfig.config?.provider) {\n      const warning =\n        'Agent Builder browser config is missing a `provider` field. ' +\n        'Set `editor.builder.configuration.agent.browser.config.provider` ' +\n        '(e.g. `\"stagehand\"`). The browser toggle will be hidden until a provider is configured.';\n      this.browserConfigWarnings.push(warning);\n      // eslint-disable-next-line no-console\n      console.warn(`[mastra:editor:builder] ${warning}`);\n      if (this.options.features?.agent) {\n        this.options.features.agent.browser = false;\n      }\n    }\n  }\n\n  private validateModelPolicy(): void {\n    const enabled = this.options.enabled !== false;\n    // Locked-mode is only triggered by an explicit `model: false` from the\n    // admin. With default-on semantics, an omitted `model` resolves to\n    // `true` (picker visible), which is open mode and has no\n    // locked-mode-default invariant.\n    const explicitModel = this.options.features?.agent?.model;\n    const pickerVisible = explicitModel !== false;\n    const models = this.options.configuration?.agent?.models;\n    const allowed = models?.allowed;\n    const defaultModel = models?.default;\n\n    const active = isBuilderModelPolicyActive({\n      enabled,\n      pickerVisible,\n      allowed,\n      default: defaultModel,\n    });\n\n    if (!active) return;\n\n    // Locked mode (picker hidden) requires an admin-pinned default. Phase 3's\n    // create-path decision matrix relies on this invariant: a locked policy\n    // without a default is unreachable. Only fires when the admin has\n    // explicitly opted out of the picker.\n    if (explicitModel === false && defaultModel === undefined) {\n      throw new Error(\n        'Agent Builder model policy is active in locked mode but no default was set. ' +\n          'Set `editor.builder.configuration.agent.models.default`, or remove ' +\n          '`editor.builder.features.agent.model = false` to allow end-users to pick a model.',\n      );\n    }\n\n    // When an allowlist is set, the default (if any) must satisfy it. An\n    // empty `allowed: []` means \"unrestricted\" so we skip this check.\n    if (defaultModel !== undefined && allowed !== undefined && allowed.length > 0) {\n      if (!isModelAllowed(allowed, defaultModel)) {\n        throw new Error(\n          'Agent Builder default model is not in the allowlist. ' +\n            'Either add it to `editor.builder.configuration.agent.models.allowed` ' +\n            'or change `editor.builder.configuration.agent.models.default`.',\n        );\n      }\n    }\n  }\n}\n\n// AgentFeatures imported for documentation reference in this file's jsdoc.\nexport type { AgentFeatures };\n","import { Agent } from '@mastra/core/agent';\nimport { Memory } from '@mastra/memory';\nimport { Workspace, LocalFilesystem } from '@mastra/core/workspace';\n\nimport path from 'node:path';\nimport { fileURLToPath } from 'node:url';\n\nconst __filename = fileURLToPath(import.meta.url);\nconst __dirname = path.dirname(__filename);\n\nconst workspacePath = path.join(__dirname, 'workspace');\n\nconst workspace = new Workspace({\n  filesystem: new LocalFilesystem({\n    basePath: workspacePath,\n  }),\n  skills: ['skills'],\n});\n\n/**\n * Agent Builder Agent\n *\n * Audience: non-technical users (Product, founders, operators, business stakeholders).\n * Goal: turn a plain-language description of a desired outcome into a fully\n * configured, production-quality agent — name, description, model, capabilities,\n * and system prompt — without asking the user follow-up questions.\n *\n * Capability tools the playground UI injects as client tools:\n * - set-agent-name, set-agent-description, set-agent-instructions, set-agent-workspace-id (always on)\n * - set-agent-tools (gated by features.tools)\n * - set-agent-skills (gated by features.skills + skills available)\n * - set-agent-model (gated by features.model + models available)\n * - set-agent-browser-enabled (gated by features.browser)\n * - createSkillTool (gated by features.skills) — only when a needed capability does not exist\n */\n\nexport function createBuilderAgent(\n  args?: Partial<ConstructorParameters<typeof Agent<'builder-agent'>>[0]>,\n): Agent<'builder-agent'> {\n  const memory = new Memory();\n\n  return new Agent<'builder-agent'>({\n    instructions: `You are the Agent Builder.\n\nYour job: turn a non-technical user's plain-language request into a fully configured, production-quality agent in a single turn.\n\n# Non-negotiables\n\n- Never ask the user follow-up questions. Make the most reasonable assumption and move forward.\n- Never expose internal names, tool ids, file paths, schemas, code, or jargon to the user.\n- Speak only in user-facing capability terms.\n- Always finish the build in the same turn as the request — configure the agent end-to-end and deliver a short summary.\n- Always define the new agent's name, description, model, and system prompt yourself. Do not ask the user for any of these.\n\nExamples of communication style:\n- Bad: \"Added weatherTool to agent-yzx capabilities.\"\n- Good: \"Your new agent can now check the weather for you.\"\n- Bad: \"Calling set-agent-tools with [weatherTool].\"\n- Good: \"Checking what capabilities to bring to your agent…\"\n- Bad: \"Agent created with weatherTool and recipeWorkflow attached.\"\n- Good: \"Your agent can check the weather and suggest recipes that match the day's conditions.\"\n\n# Authoring loop\n\nFollow these five steps in order, every time:\n\n## Step A — Understand the real outcome\n\nAnalyze what the user actually wants to achieve. Focus on the final result, not just the literal wording of the request.\n\nAsk yourself:\n- What should the agent help the user accomplish?\n- Who will use this agent?\n- What decisions should the agent make on its own?\n- What kind of output should the agent produce?\n- What recurring tasks, reasoning, or actions does the agent need to perform?\n\n## Step B — Define the agent's identity\n\nBefore building the agent, define:\n- Agent name: short, memorable, anchored to the outcome. Never \"Agent X\" or generic labels\n- Description: exactly one sentence in plain user-facing language explaining what the agent helps with.\n\nCall \\`set-agent-name\\` and \\`set-agent-description\\` to set the agent's identity. Skip any whose feature is not available in the form snapshot.\n\n## Step C — Decide capabilities\n\nRead the form snapshot already injected into your context. It lists the user's current selections plus the available tools, agents, workflows, stored skills, models, and workspaces.\n\nThen:\n- Pick the *minimum* set of existing tools/agents/workflows/stored skills that satisfies the outcome. Adding irrelevant capabilities makes the agent worse, not better.\n- Prefer existing tools, workflows, agents, and stored skills before creating anything new.\n- \\`set-agent-skills\\` attaches user-available stored skills from the form snapshot.\n- Only call \\`createSkillTool\\` when (a) no existing stored skill matches reusable operating instructions the produced agent needs, AND (b) that operating instruction is genuinely needed for the outcome. Do not use stored skills as a substitute for missing integrations or tools.\n- If a specific external connection is required (e.g. a sheet tool for a spreadsheet-driven outcome) and none is available, the new agent's system prompt must instruct it to refuse cleanly and explain what the user needs to connect.\n\n## Step D — Synthesize the run contract\n\nBefore calling \\`set-agent-instructions\\`, privately write a concrete run contract for the produced agent. The system prompt must instantiate each item:\n\n1. **Trigger / input** — what user request, schedule, event, file, row, ticket, or message starts a run.\n2. **Owned outcome** — the exact result the produced agent is responsible for finishing.\n3. **Available capabilities** — only capabilities actually attached or already available from the form snapshot, described in user-facing outcome terms.\n4. **Missing-capability fallback** — what the produced agent does when a required integration, workspace, credential, or source is absent.\n5. **Done criteria** — verifiable conditions that prove the job is finished, including tool confirmation or an explicit \"not run\" reason when verification is impossible.\n6. **Final response format** — the receipt, summary, draft, diff summary, report, or confirmation the user receives.\n\n## Step E — Write the agent\n\nCall the capability tools. Skip any whose feature is not available in the form snapshot.\n\n1. \\`set-agent-model\\` — pick the best model for the use case from the available models list. Rules:\n   - Choose only a model id that appears in the available models list. Never invent, assume, or copy example model ids.\n   - For coding, reasoning-heavy, or planning agents, prefer the most capable available model.\n   - For short, simple, structured, or high-volume tasks, prefer a lower-latency/lower-cost available model when quality will not materially suffer.\n   - If several plausible models are available, choose the newest or strongest option based on the metadata visible in the snapshot.\n2. \\`set-agent-tools\\` — attach the minimum set chosen in Step C. Also use \\`set-agent-skills\\` and \\`set-agent-browser-enabled\\` only when applicable and supported by the snapshot.\n3. \\`set-agent-instructions\\` — write the new agent's system prompt from scratch, tailored to the user's specific outcome and the run contract from Step D.\n\nBefore calling \\`set-agent-instructions\\`, self-audit the draft. It must pass every check:\n- No placeholders remain (no \\`<...>\\`, \"TBD\", \"TODO\", \"your tool\", or generic policy gaps).\n- No internal tool ids, file paths, schemas, or builder-only terms appear.\n- No generic \"helpful assistant\" identity remains.\n- No unsupported capabilities are promised.\n- Completion criteria are present, concrete, and tool-aware.\n- Refusal / fallback path is present for missing integrations, credentials, permissions, workspace, or sources.\n- Final response format is specified.\n\n## Step F — Confirm the agent configuration to the user\n\nEnd your turn with one short, friendly paragraph confirming that the agent has been configured and is ready to use.\n\nUse this shape:\n\n\"Your agent, [Agent Name], has been configured with its initial parameters. It can now [plain-language outcome]. You can adjust its instructions, inputs, or connected capabilities whenever your needs change.\"\n\nDo not mention internal capability names, tools, workflows, skills, or configuration steps.\n\nGood:\n\"Your agent, Sales Drop Watcher, has been configured with its initial parameters. It can now review your weekly sales sheet, flag accounts that dropped more than 10%, and prepare follow-up drafts for each one. You can adjust its instructions, thresholds, or connected data sources whenever your needs change.\"\n\nBad:\n\"Agent created with sheetsTool, scoringWorkflow, and emailSkill attached.\"\n\nBad:\n\"I configured the sheets integration and called set-agent-instructions.\"\n\n# Quality bar for the produced agent's system prompt\n\nThe system prompt written into \\`set-agent-instructions\\` MUST include all of the following:\n\n1. **Role and outcome.** Define what the agent is and the concrete result it owns.\n2. **Trigger and input.** Define what starts a run and what input the agent expects.\n3. **Decision rules.** Explain how the agent resolves ambiguity, what defaults it should apply, and what it should skip without asking the user.\n4. **Capability awareness.** Describe only the tools, integrations, workspaces, or data sources the agent actually has, phrased in terms of what they let the agent accomplish.\n5. **Missing-capability fallback.** Explain what the agent should do when a required integration, credential, permission, workspace, or source is unavailable.\n6. **Completion criteria.** Define exactly when the task is done in observable, verifiable terms.\n7. **Final response format.** Specify the exact shape of the agent's final answer, report, draft, receipt, or confirmation.\n8. **Communication style.** Require plain language, short answers, no jargon, and structure only when useful.\n9. **Refusal rules.** State what the agent must refuse and how it should explain the refusal clearly.\n10. **Worked example.** Include at least one short input → output example showing a complete successful run.\n\n# Hard rules\n\n- If the user's request requires CLI or local-machine actions and no workspace is connected, refuse in plain language and tell the user they need to connect a workspace first.\n- Never reveal that you are calling configuration tools. Describe progress only in terms of the user's intended outcome.\n- Never produce a system prompt without explicit completion criteria.\n- Never attach a capability \"just in case.\" Every tool, agent, workflow, or skill must directly support the requested outcome.\n- The final message to the user must be concise, friendly, and focused on what the configured agent can now do.\n- The final message should make clear that the agent starts with initial parameters and can be adjusted later.`,\n    model: 'openai/gpt-5.5',\n    memory,\n    workspace,\n    ...(args || {}),\n    id: 'builder-agent',\n    name: 'Agent Builder Agent',\n    description: 'An agent that can build agents',\n  });\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;;;ACCA,gBAAiF;AAe1E,IAAM,qBAAN,MAAkD;AAAA,EAoBvD,YAAY,SAA+B;AAlB3C,SAAiB,sBAAgC,CAAC;AAGlD;AAAA,SAAiB,wBAAkC,CAAC;AAoBlD,UAAM,SAAS,WAAW,CAAC;AAC3B,SAAK,UAAU;AAAA,MACb,GAAG;AAAA,MACH,UAAU,OAAO,WACb;AAAA,QACE,GAAG,OAAO;AAAA,QACV,OAAO,OAAO,SAAS,QAAQ,EAAE,GAAG,OAAO,SAAS,MAAM,IAAI;AAAA,MAChE,IACA;AAAA,IACN;AACA,SAAK,oBAAoB;AACzB,SAAK,sBAAsB;AAK3B,SAAK,mBAAmB;AAAA,MACtB,WAAO,gCAAqB,KAAK,QAAQ,UAAU,OAAO;AAAA,QACxD,kBAAkB,KAAK,sBAAsB;AAAA,MAC/C,CAAC;AAAA,IACH;AAAA,EACF;AAAA,EAEA,IAAI,UAAmB;AACrB,WAAO,KAAK,QAAQ,YAAY;AAAA,EAClC;AAAA,EAEA,cAA+C;AAC7C,WAAO,KAAK;AAAA,EACd;AAAA,EAEA,mBAAyD;AACvD,WAAO,KAAK,QAAQ;AAAA,EACtB;AAAA,EAEA,gBAAmD;AACjD,WAAO,KAAK,QAAQ;AAAA,EACtB;AAAA,EAEA,yBAAmC;AACjC,WAAO,CAAC,GAAG,KAAK,qBAAqB,GAAG,KAAK,qBAAqB;AAAA,EACpE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAQQ,wBAAiC;AACvC,UAAM,gBAAgB,KAAK,QAAQ,eAAe,OAAO;AACzD,WAAO,QAAQ,eAAe,QAAQ,QAAQ;AAAA,EAChD;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAUQ,wBAA8B;AACpC,UAAM,kBAAkB,KAAK,QAAQ,UAAU,OAAO;AACtD,QAAI,oBAAoB,KAAM;AAE9B,UAAM,gBAAgB,KAAK,QAAQ,eAAe,OAAO;AACzD,QAAI,CAAC,eAAe;AAClB,YAAM,UACJ;AAIF,WAAK,sBAAsB,KAAK,OAAO;AAEvC,cAAQ,KAAK,2BAA2B,OAAO,EAAE;AAEjD,UAAI,KAAK,QAAQ,UAAU,OAAO;AAChC,aAAK,QAAQ,SAAS,MAAM,UAAU;AAAA,MACxC;AACA;AAAA,IACF;AAEA,QAAI,CAAC,cAAc,QAAQ,UAAU;AACnC,YAAM,UACJ;AAGF,WAAK,sBAAsB,KAAK,OAAO;AAEvC,cAAQ,KAAK,2BAA2B,OAAO,EAAE;AACjD,UAAI,KAAK,QAAQ,UAAU,OAAO;AAChC,aAAK,QAAQ,SAAS,MAAM,UAAU;AAAA,MACxC;AAAA,IACF;AAAA,EACF;AAAA,EAEQ,sBAA4B;AAClC,UAAM,UAAU,KAAK,QAAQ,YAAY;AAKzC,UAAM,gBAAgB,KAAK,QAAQ,UAAU,OAAO;AACpD,UAAM,gBAAgB,kBAAkB;AACxC,UAAM,SAAS,KAAK,QAAQ,eAAe,OAAO;AAClD,UAAM,UAAU,QAAQ;AACxB,UAAM,eAAe,QAAQ;AAE7B,UAAM,aAAS,sCAA2B;AAAA,MACxC;AAAA,MACA;AAAA,MACA;AAAA,MACA,SAAS;AAAA,IACX,CAAC;AAED,QAAI,CAAC,OAAQ;AAMb,QAAI,kBAAkB,SAAS,iBAAiB,QAAW;AACzD,YAAM,IAAI;AAAA,QACR;AAAA,MAGF;AAAA,IACF;AAIA,QAAI,iBAAiB,UAAa,YAAY,UAAa,QAAQ,SAAS,GAAG;AAC7E,UAAI,KAAC,0BAAe,SAAS,YAAY,GAAG;AAC1C,cAAM,IAAI;AAAA,UACR;AAAA,QAGF;AAAA,MACF;AAAA,IACF;AAAA,EACF;AACF;;;ACvLA,mBAAsB;AACtB,oBAAuB;AACvB,uBAA2C;AAE3C,uBAAiB;AACjB,sBAA8B;AAL9B;AAOA,IAAM,iBAAa,+BAAc,YAAY,GAAG;AAChD,IAAM,YAAY,iBAAAA,QAAK,QAAQ,UAAU;AAEzC,IAAM,gBAAgB,iBAAAA,QAAK,KAAK,WAAW,WAAW;AAEtD,IAAM,YAAY,IAAI,2BAAU;AAAA,EAC9B,YAAY,IAAI,iCAAgB;AAAA,IAC9B,UAAU;AAAA,EACZ,CAAC;AAAA,EACD,QAAQ,CAAC,QAAQ;AACnB,CAAC;AAmBM,SAAS,mBACd,MACwB;AACxB,QAAM,SAAS,IAAI,qBAAO;AAE1B,SAAO,IAAI,mBAAuB;AAAA,IAChC,cAAc;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;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;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,IAgId,OAAO;AAAA,IACP;AAAA,IACA;AAAA,IACA,GAAI,QAAQ,CAAC;AAAA,IACb,IAAI;AAAA,IACJ,MAAM;AAAA,IACN,aAAa;AAAA,EACf,CAAC;AACH;","names":["path"]}
+{"version":3,"sources":["../../src/ee/index.ts","../../src/ee/agent-builder.ts","../../src/ee/agent-builder-agent.ts"],"sourcesContent":["export { EditorAgentBuilder } from './agent-builder';\nexport { createBuilderAgent } from './agent-builder-agent';\n","import type { AgentBuilderOptions, AgentFeatures, IAgentBuilder } from '@mastra/core/agent-builder/ee';\nimport { isBuilderModelPolicyActive, isModelAllowed, resolveAgentFeatures } from '@mastra/core/agent-builder/ee';\n\n/**\n * Concrete implementation of the Agent Builder EE feature.\n * Instantiated by MastraEditor.resolveBuilder() when builder config is enabled.\n *\n * The constructor performs fail-fast validation of the admin's model policy\n * (Phase 4) so misconfiguration is caught at boot, not at first request.\n *\n * Feature toggles use **default-on semantics**: omitted keys resolve to\n * `true`. Admins opt out by setting a key to `false`. The resolved features\n * are computed once in the constructor (after validation) and returned\n * verbatim by {@link getFeatures} so all downstream consumers (server route,\n * UI hooks, policy derivation) see the same effective values.\n */\nexport class EditorAgentBuilder implements IAgentBuilder {\n  private readonly options: AgentBuilderOptions;\n  private readonly modelPolicyWarnings: string[] = [];\n\n  /** Non-fatal warnings for browser config issues (surfaced alongside model policy warnings). */\n  private readonly browserConfigWarnings: string[] = [];\n\n  /**\n   * Resolved (default-on normalized) features. Computed once in the\n   * constructor; `undefined` only if the builder was constructed with\n   * `enabled: false` (we still allocate features for the OFF path so callers\n   * can introspect, but we keep the field optional to preserve the existing\n   * API contract where `getFeatures()` may legitimately return `undefined`\n   * if no `features` was provided AND no defaults could be applied).\n   *\n   * In practice this is always populated: `resolveAgentFeatures` returns a\n   * fully-populated object regardless of input.\n   */\n  private readonly resolvedFeatures: AgentBuilderOptions['features'];\n\n  constructor(options?: AgentBuilderOptions) {\n    // Shallow-clone the paths the validators mutate so we never leak side\n    // effects into the caller's `MastraEditorConfig.builder` object.\n    // `validateBrowserConfig` writes to `features.agent.browser`; nothing\n    // else is mutated, so `configuration` and `registries` stay aliased.\n    const source = options ?? {};\n    this.options = {\n      ...source,\n      features: source.features\n        ? {\n            ...source.features,\n            agent: source.features.agent ? { ...source.features.agent } : undefined,\n          }\n        : undefined,\n    };\n    this.validateModelPolicy();\n    this.validateBrowserConfig();\n    // Resolve features AFTER browser-config validation so that an explicit\n    // `browser: true` with bad config is already mutated to `false` on\n    // `this.options.features.agent.browser`. The resolver then sees the\n    // downgraded value and returns it as-is.\n    this.resolvedFeatures = {\n      agent: resolveAgentFeatures(this.options.features?.agent, {\n        hasBrowserConfig: this.hasValidBrowserConfig(),\n      }),\n    };\n  }\n\n  get enabled(): boolean {\n    return this.options.enabled !== false;\n  }\n\n  getFeatures(): AgentBuilderOptions['features'] {\n    return this.resolvedFeatures;\n  }\n\n  getConfiguration(): AgentBuilderOptions['configuration'] {\n    return this.options.configuration;\n  }\n\n  getRegistries(): AgentBuilderOptions['registries'] {\n    return this.options.registries;\n  }\n\n  getModelPolicyWarnings(): string[] {\n    return [...this.modelPolicyWarnings, ...this.browserConfigWarnings];\n  }\n\n  /**\n   * True when `configuration.agent.browser` declares a provider. The\n   * EditorAgentBuilder does NOT verify the provider is registered with the\n   * Mastra instance — that cross-validation lives in `MastraEditor.resolveBuilder`\n   * because only the editor knows the registered browser providers.\n   */\n  private hasValidBrowserConfig(): boolean {\n    const browserConfig = this.options.configuration?.agent?.browser;\n    return Boolean(browserConfig?.config?.provider);\n  }\n\n  /**\n   * Browser config validation only runs for **explicit** `browser: true`.\n   * With default-on semantics, an omitted `browser` no longer means \"admin\n   * opted in\" — it means \"admin didn't opt out\". The default-on path is\n   * resolved later by `resolveAgentFeatures`, which already gates `browser`\n   * on `hasValidBrowserConfig`. We don't want to spam every default-config\n   * deployment with warnings.\n   */\n  private validateBrowserConfig(): void {\n    const explicitBrowser = this.options.features?.agent?.browser;\n    if (explicitBrowser !== true) return;\n\n    const browserConfig = this.options.configuration?.agent?.browser;\n    if (!browserConfig) {\n      const warning =\n        'Agent Builder browser feature is enabled but no default browser config was provided. ' +\n        'Set `editor.builder.configuration.agent.browser` to a valid browser config ' +\n        '(e.g. `{ type: \"inline\", config: { provider: \"stagehand\" } }`). ' +\n        'The browser toggle will be hidden until a default is configured.';\n      this.browserConfigWarnings.push(warning);\n      // eslint-disable-next-line no-console\n      console.warn(`[mastra:editor:builder] ${warning}`);\n      // Downgrade so the resolved feature ends up `false`.\n      if (this.options.features?.agent) {\n        this.options.features.agent.browser = false;\n      }\n      return;\n    }\n\n    if (!browserConfig.config?.provider) {\n      const warning =\n        'Agent Builder browser config is missing a `provider` field. ' +\n        'Set `editor.builder.configuration.agent.browser.config.provider` ' +\n        '(e.g. `\"stagehand\"`). The browser toggle will be hidden until a provider is configured.';\n      this.browserConfigWarnings.push(warning);\n      // eslint-disable-next-line no-console\n      console.warn(`[mastra:editor:builder] ${warning}`);\n      if (this.options.features?.agent) {\n        this.options.features.agent.browser = false;\n      }\n    }\n  }\n\n  private validateModelPolicy(): void {\n    const enabled = this.options.enabled !== false;\n    // Locked-mode is only triggered by an explicit `model: false` from the\n    // admin. With default-on semantics, an omitted `model` resolves to\n    // `true` (picker visible), which is open mode and has no\n    // locked-mode-default invariant.\n    const explicitModel = this.options.features?.agent?.model;\n    const pickerVisible = explicitModel !== false;\n    const models = this.options.configuration?.agent?.models;\n    const allowed = models?.allowed;\n    const defaultModel = models?.default;\n\n    const active = isBuilderModelPolicyActive({\n      enabled,\n      pickerVisible,\n      allowed,\n      default: defaultModel,\n    });\n\n    if (!active) return;\n\n    // Locked mode (picker hidden) requires an admin-pinned default. Phase 3's\n    // create-path decision matrix relies on this invariant: a locked policy\n    // without a default is unreachable. Only fires when the admin has\n    // explicitly opted out of the picker.\n    if (explicitModel === false && defaultModel === undefined) {\n      throw new Error(\n        'Agent Builder model policy is active in locked mode but no default was set. ' +\n          'Set `editor.builder.configuration.agent.models.default`, or remove ' +\n          '`editor.builder.features.agent.model = false` to allow end-users to pick a model.',\n      );\n    }\n\n    // When an allowlist is set, the default (if any) must satisfy it. An\n    // empty `allowed: []` means \"unrestricted\" so we skip this check.\n    if (defaultModel !== undefined && allowed !== undefined && allowed.length > 0) {\n      if (!isModelAllowed(allowed, defaultModel)) {\n        throw new Error(\n          'Agent Builder default model is not in the allowlist. ' +\n            'Either add it to `editor.builder.configuration.agent.models.allowed` ' +\n            'or change `editor.builder.configuration.agent.models.default`.',\n        );\n      }\n    }\n  }\n}\n\n// AgentFeatures imported for documentation reference in this file's jsdoc.\nexport type { AgentFeatures };\n","import { Agent } from '@mastra/core/agent';\nimport type { AgentConfig } from '@mastra/core/agent';\nimport { Memory } from '@mastra/memory';\nimport { Workspace, LocalFilesystem } from '@mastra/core/workspace';\n\nimport path from 'node:path';\nimport { fileURLToPath } from 'node:url';\n\nconst __filename = fileURLToPath(import.meta.url);\nconst __dirname = path.dirname(__filename);\n\nconst workspacePath = path.join(__dirname, 'workspace');\n\nconst workspace = new Workspace({\n  filesystem: new LocalFilesystem({\n    basePath: workspacePath,\n  }),\n  skills: ['skills'],\n});\n\n/**\n * Agent Builder Agent\n *\n * Audience: non-technical users (Product, founders, operators, business stakeholders).\n * Goal: turn a plain-language description of a desired outcome into a fully\n * configured, production-quality agent — name, description, model, capabilities,\n * and system prompt — without asking the user follow-up questions.\n *\n * Capability tools the playground UI injects as client tools:\n * - set-agent-name, set-agent-description, set-agent-instructions, set-agent-workspace-id (always on)\n * - set-agent-tools (gated by features.tools)\n * - set-agent-skills (gated by features.skills + skills available)\n * - set-agent-model (gated by features.model + models available)\n * - set-agent-browser-enabled (gated by features.browser)\n * - createSkillTool (gated by features.skills) — only when a needed capability does not exist\n */\n\nexport function createBuilderAgent(args?: Partial<AgentConfig<'builder-agent'>>): Agent<'builder-agent'> {\n  const memory = new Memory();\n\n  const config: AgentConfig<'builder-agent'> = {\n    instructions: `You are the Agent Builder.\n\nYour job: turn a non-technical user's plain-language request into a fully configured, production-quality agent in a single turn.\n\n# Non-negotiables\n\n- Never ask the user follow-up questions. Make the most reasonable assumption and move forward.\n- Never expose internal names, tool ids, file paths, schemas, code, or jargon to the user.\n- Speak only in user-facing capability terms.\n- Always finish the build in the same turn as the request — configure the agent end-to-end and deliver a short summary.\n- Always define the new agent's name, description, model, and system prompt yourself. Do not ask the user for any of these.\n\nExamples of communication style:\n- Bad: \"Added weatherTool to agent-yzx capabilities.\"\n- Good: \"Your new agent can now check the weather for you.\"\n- Bad: \"Calling set-agent-tools with [weatherTool].\"\n- Good: \"Checking what capabilities to bring to your agent…\"\n- Bad: \"Agent created with weatherTool and recipeWorkflow attached.\"\n- Good: \"Your agent can check the weather and suggest recipes that match the day's conditions.\"\n\n# Authoring loop\n\nFollow these five steps in order, every time:\n\n## Step A — Understand the real outcome\n\nAnalyze what the user actually wants to achieve. Focus on the final result, not just the literal wording of the request.\n\nAsk yourself:\n- What should the agent help the user accomplish?\n- Who will use this agent?\n- What decisions should the agent make on its own?\n- What kind of output should the agent produce?\n- What recurring tasks, reasoning, or actions does the agent need to perform?\n\n## Step B — Define the agent's identity\n\nBefore building the agent, define:\n- Agent name: short, memorable, anchored to the outcome. Never \"Agent X\" or generic labels\n- Description: exactly one sentence in plain user-facing language explaining what the agent helps with.\n\nCall \\`set-agent-name\\` and \\`set-agent-description\\` to set the agent's identity. Skip any whose feature is not available in the form snapshot.\n\n## Step C — Decide capabilities\n\nRead the form snapshot already injected into your context. It lists the user's current selections plus the available tools, agents, workflows, stored skills, models, and workspaces.\n\nThen:\n- Pick the *minimum* set of existing tools/agents/workflows/stored skills that satisfies the outcome. Adding irrelevant capabilities makes the agent worse, not better.\n- Prefer existing tools, workflows, agents, and stored skills before creating anything new.\n- \\`set-agent-skills\\` attaches user-available stored skills from the form snapshot.\n- Only call \\`createSkillTool\\` when (a) no existing stored skill matches reusable operating instructions the produced agent needs, AND (b) that operating instruction is genuinely needed for the outcome. Do not use stored skills as a substitute for missing integrations or tools.\n- If a specific external connection is required (e.g. a sheet tool for a spreadsheet-driven outcome) and none is available, the new agent's system prompt must instruct it to refuse cleanly and explain what the user needs to connect.\n\n## Step D — Synthesize the run contract\n\nBefore calling \\`set-agent-instructions\\`, privately write a concrete run contract for the produced agent. The system prompt must instantiate each item:\n\n1. **Trigger / input** — what user request, schedule, event, file, row, ticket, or message starts a run.\n2. **Owned outcome** — the exact result the produced agent is responsible for finishing.\n3. **Available capabilities** — only capabilities actually attached or already available from the form snapshot, described in user-facing outcome terms.\n4. **Missing-capability fallback** — what the produced agent does when a required integration, workspace, credential, or source is absent.\n5. **Done criteria** — verifiable conditions that prove the job is finished, including tool confirmation or an explicit \"not run\" reason when verification is impossible.\n6. **Final response format** — the receipt, summary, draft, diff summary, report, or confirmation the user receives.\n\n## Step E — Write the agent\n\nCall the capability tools. Skip any whose feature is not available in the form snapshot.\n\n1. \\`set-agent-model\\` — pick the best model for the use case from the available models list. Rules:\n   - Choose only a model id that appears in the available models list. Never invent, assume, or copy example model ids.\n   - For coding, reasoning-heavy, or planning agents, prefer the most capable available model.\n   - For short, simple, structured, or high-volume tasks, prefer a lower-latency/lower-cost available model when quality will not materially suffer.\n   - If several plausible models are available, choose the newest or strongest option based on the metadata visible in the snapshot.\n2. \\`set-agent-tools\\` — attach the minimum set chosen in Step C. Also use \\`set-agent-skills\\` and \\`set-agent-browser-enabled\\` only when applicable and supported by the snapshot.\n3. \\`set-agent-instructions\\` — write the new agent's system prompt from scratch, tailored to the user's specific outcome and the run contract from Step D.\n\nBefore calling \\`set-agent-instructions\\`, self-audit the draft. It must pass every check:\n- No placeholders remain (no \\`<...>\\`, \"TBD\", \"TODO\", \"your tool\", or generic policy gaps).\n- No internal tool ids, file paths, schemas, or builder-only terms appear.\n- No generic \"helpful assistant\" identity remains.\n- No unsupported capabilities are promised.\n- Completion criteria are present, concrete, and tool-aware.\n- Refusal / fallback path is present for missing integrations, credentials, permissions, workspace, or sources.\n- Final response format is specified.\n\n## Step F — Confirm the agent configuration to the user\n\nEnd your turn with one short, friendly paragraph confirming that the agent has been configured and is ready to use.\n\nUse this shape:\n\n\"Your agent, [Agent Name], has been configured with its initial parameters. It can now [plain-language outcome]. You can adjust its instructions, inputs, or connected capabilities whenever your needs change.\"\n\nDo not mention internal capability names, tools, workflows, skills, or configuration steps.\n\nGood:\n\"Your agent, Sales Drop Watcher, has been configured with its initial parameters. It can now review your weekly sales sheet, flag accounts that dropped more than 10%, and prepare follow-up drafts for each one. You can adjust its instructions, thresholds, or connected data sources whenever your needs change.\"\n\nBad:\n\"Agent created with sheetsTool, scoringWorkflow, and emailSkill attached.\"\n\nBad:\n\"I configured the sheets integration and called set-agent-instructions.\"\n\n# Quality bar for the produced agent's system prompt\n\nThe system prompt written into \\`set-agent-instructions\\` MUST include all of the following:\n\n1. **Role and outcome.** Define what the agent is and the concrete result it owns.\n2. **Trigger and input.** Define what starts a run and what input the agent expects.\n3. **Decision rules.** Explain how the agent resolves ambiguity, what defaults it should apply, and what it should skip without asking the user.\n4. **Capability awareness.** Describe only the tools, integrations, workspaces, or data sources the agent actually has, phrased in terms of what they let the agent accomplish.\n5. **Missing-capability fallback.** Explain what the agent should do when a required integration, credential, permission, workspace, or source is unavailable.\n6. **Completion criteria.** Define exactly when the task is done in observable, verifiable terms.\n7. **Final response format.** Specify the exact shape of the agent's final answer, report, draft, receipt, or confirmation.\n8. **Communication style.** Require plain language, short answers, no jargon, and structure only when useful.\n9. **Refusal rules.** State what the agent must refuse and how it should explain the refusal clearly.\n10. **Worked example.** Include at least one short input → output example showing a complete successful run.\n\n# Hard rules\n\n- If the user's request requires CLI or local-machine actions and no workspace is connected, refuse in plain language and tell the user they need to connect a workspace first.\n- Never reveal that you are calling configuration tools. Describe progress only in terms of the user's intended outcome.\n- Never produce a system prompt without explicit completion criteria.\n- Never attach a capability \"just in case.\" Every tool, agent, workflow, or skill must directly support the requested outcome.\n- The final message to the user must be concise, friendly, and focused on what the configured agent can now do.\n- The final message should make clear that the agent starts with initial parameters and can be adjusted later.`,\n    model: 'openai/gpt-5.5',\n    memory,\n    workspace,\n    ...(args || {}),\n    id: 'builder-agent',\n    name: 'Agent Builder Agent',\n    description: 'An agent that can build agents',\n  };\n\n  return new Agent<'builder-agent'>(config);\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;;;ACCA,gBAAiF;AAe1E,IAAM,qBAAN,MAAkD;AAAA,EAoBvD,YAAY,SAA+B;AAlB3C,SAAiB,sBAAgC,CAAC;AAGlD;AAAA,SAAiB,wBAAkC,CAAC;AAoBlD,UAAM,SAAS,WAAW,CAAC;AAC3B,SAAK,UAAU;AAAA,MACb,GAAG;AAAA,MACH,UAAU,OAAO,WACb;AAAA,QACE,GAAG,OAAO;AAAA,QACV,OAAO,OAAO,SAAS,QAAQ,EAAE,GAAG,OAAO,SAAS,MAAM,IAAI;AAAA,MAChE,IACA;AAAA,IACN;AACA,SAAK,oBAAoB;AACzB,SAAK,sBAAsB;AAK3B,SAAK,mBAAmB;AAAA,MACtB,WAAO,gCAAqB,KAAK,QAAQ,UAAU,OAAO;AAAA,QACxD,kBAAkB,KAAK,sBAAsB;AAAA,MAC/C,CAAC;AAAA,IACH;AAAA,EACF;AAAA,EAEA,IAAI,UAAmB;AACrB,WAAO,KAAK,QAAQ,YAAY;AAAA,EAClC;AAAA,EAEA,cAA+C;AAC7C,WAAO,KAAK;AAAA,EACd;AAAA,EAEA,mBAAyD;AACvD,WAAO,KAAK,QAAQ;AAAA,EACtB;AAAA,EAEA,gBAAmD;AACjD,WAAO,KAAK,QAAQ;AAAA,EACtB;AAAA,EAEA,yBAAmC;AACjC,WAAO,CAAC,GAAG,KAAK,qBAAqB,GAAG,KAAK,qBAAqB;AAAA,EACpE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAQQ,wBAAiC;AACvC,UAAM,gBAAgB,KAAK,QAAQ,eAAe,OAAO;AACzD,WAAO,QAAQ,eAAe,QAAQ,QAAQ;AAAA,EAChD;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAUQ,wBAA8B;AACpC,UAAM,kBAAkB,KAAK,QAAQ,UAAU,OAAO;AACtD,QAAI,oBAAoB,KAAM;AAE9B,UAAM,gBAAgB,KAAK,QAAQ,eAAe,OAAO;AACzD,QAAI,CAAC,eAAe;AAClB,YAAM,UACJ;AAIF,WAAK,sBAAsB,KAAK,OAAO;AAEvC,cAAQ,KAAK,2BAA2B,OAAO,EAAE;AAEjD,UAAI,KAAK,QAAQ,UAAU,OAAO;AAChC,aAAK,QAAQ,SAAS,MAAM,UAAU;AAAA,MACxC;AACA;AAAA,IACF;AAEA,QAAI,CAAC,cAAc,QAAQ,UAAU;AACnC,YAAM,UACJ;AAGF,WAAK,sBAAsB,KAAK,OAAO;AAEvC,cAAQ,KAAK,2BAA2B,OAAO,EAAE;AACjD,UAAI,KAAK,QAAQ,UAAU,OAAO;AAChC,aAAK,QAAQ,SAAS,MAAM,UAAU;AAAA,MACxC;AAAA,IACF;AAAA,EACF;AAAA,EAEQ,sBAA4B;AAClC,UAAM,UAAU,KAAK,QAAQ,YAAY;AAKzC,UAAM,gBAAgB,KAAK,QAAQ,UAAU,OAAO;AACpD,UAAM,gBAAgB,kBAAkB;AACxC,UAAM,SAAS,KAAK,QAAQ,eAAe,OAAO;AAClD,UAAM,UAAU,QAAQ;AACxB,UAAM,eAAe,QAAQ;AAE7B,UAAM,aAAS,sCAA2B;AAAA,MACxC;AAAA,MACA;AAAA,MACA;AAAA,MACA,SAAS;AAAA,IACX,CAAC;AAED,QAAI,CAAC,OAAQ;AAMb,QAAI,kBAAkB,SAAS,iBAAiB,QAAW;AACzD,YAAM,IAAI;AAAA,QACR;AAAA,MAGF;AAAA,IACF;AAIA,QAAI,iBAAiB,UAAa,YAAY,UAAa,QAAQ,SAAS,GAAG;AAC7E,UAAI,KAAC,0BAAe,SAAS,YAAY,GAAG;AAC1C,cAAM,IAAI;AAAA,UACR;AAAA,QAGF;AAAA,MACF;AAAA,IACF;AAAA,EACF;AACF;;;ACvLA,mBAAsB;AAEtB,oBAAuB;AACvB,uBAA2C;AAE3C,uBAAiB;AACjB,sBAA8B;AAN9B;AAQA,IAAM,iBAAa,+BAAc,YAAY,GAAG;AAChD,IAAM,YAAY,iBAAAA,QAAK,QAAQ,UAAU;AAEzC,IAAM,gBAAgB,iBAAAA,QAAK,KAAK,WAAW,WAAW;AAEtD,IAAM,YAAY,IAAI,2BAAU;AAAA,EAC9B,YAAY,IAAI,iCAAgB;AAAA,IAC9B,UAAU;AAAA,EACZ,CAAC;AAAA,EACD,QAAQ,CAAC,QAAQ;AACnB,CAAC;AAmBM,SAAS,mBAAmB,MAAsE;AACvG,QAAM,SAAS,IAAI,qBAAO;AAE1B,QAAM,SAAuC;AAAA,IAC3C,cAAc;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;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;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,IAgId,OAAO;AAAA,IACP;AAAA,IACA;AAAA,IACA,GAAI,QAAQ,CAAC;AAAA,IACb,IAAI;AAAA,IACJ,MAAM;AAAA,IACN,aAAa;AAAA,EACf;AAEA,SAAO,IAAI,mBAAuB,MAAM;AAC1C;","names":["path"]}

package/dist/ee/index.d.cts

@@ -1,5 +1,5 @@
 import { IAgentBuilder, AgentBuilderOptions } from '@mastra/core/agent-builder/ee';
-import { Agent } from '@mastra/core/agent';
+import { AgentConfig, Agent } from '@mastra/core/agent';
 
 /**
  * Concrete implementation of the Agent Builder EE feature.
@@ -72,6 +72,6 @@ declare class EditorAgentBuilder implements IAgentBuilder {
  * - set-agent-browser-enabled (gated by features.browser)
  * - createSkillTool (gated by features.skills) — only when a needed capability does not exist
  */
-declare function createBuilderAgent(args?: Partial<ConstructorParameters<typeof Agent<'builder-agent'>>[0]>): Agent<'builder-agent'>;
+declare function createBuilderAgent(args?: Partial<AgentConfig<'builder-agent'>>): Agent<'builder-agent'>;
 
 export { EditorAgentBuilder, createBuilderAgent };

package/dist/ee/index.d.ts

@@ -1,5 +1,5 @@
 import { IAgentBuilder, AgentBuilderOptions } from '@mastra/core/agent-builder/ee';
-import { Agent } from '@mastra/core/agent';
+import { AgentConfig, Agent } from '@mastra/core/agent';
 
 /**
  * Concrete implementation of the Agent Builder EE feature.
@@ -72,6 +72,6 @@ declare class EditorAgentBuilder implements IAgentBuilder {
  * - set-agent-browser-enabled (gated by features.browser)
  * - createSkillTool (gated by features.skills) — only when a needed capability does not exist
  */
-declare function createBuilderAgent(args?: Partial<ConstructorParameters<typeof Agent<'builder-agent'>>[0]>): Agent<'builder-agent'>;
+declare function createBuilderAgent(args?: Partial<AgentConfig<'builder-agent'>>): Agent<'builder-agent'>;
 
 export { EditorAgentBuilder, createBuilderAgent };

package/dist/ee/index.js

@@ -122,7 +122,7 @@ var workspace = new Workspace({
 });
 function createBuilderAgent(args) {
   const memory = new Memory();
-  return new Agent({
+  const config = {
     instructions: `You are the Agent Builder.
 
 Your job: turn a non-technical user's plain-language request into a fully configured, production-quality agent in a single turn.
@@ -258,7 +258,8 @@ The system prompt written into \`set-agent-instructions\` MUST include all of th
     id: "builder-agent",
     name: "Agent Builder Agent",
     description: "An agent that can build agents"
-  });
+  };
+  return new Agent(config);
 }
 export {
   EditorAgentBuilder,

package/dist/ee/index.js.map

@@ -1 +1 @@
-{"version":3,"sources":["../../src/ee/agent-builder.ts","../../src/ee/agent-builder-agent.ts"],"sourcesContent":["import type { AgentBuilderOptions, AgentFeatures, IAgentBuilder } from '@mastra/core/agent-builder/ee';\nimport { isBuilderModelPolicyActive, isModelAllowed, resolveAgentFeatures } from '@mastra/core/agent-builder/ee';\n\n/**\n * Concrete implementation of the Agent Builder EE feature.\n * Instantiated by MastraEditor.resolveBuilder() when builder config is enabled.\n *\n * The constructor performs fail-fast validation of the admin's model policy\n * (Phase 4) so misconfiguration is caught at boot, not at first request.\n *\n * Feature toggles use **default-on semantics**: omitted keys resolve to\n * `true`. Admins opt out by setting a key to `false`. The resolved features\n * are computed once in the constructor (after validation) and returned\n * verbatim by {@link getFeatures} so all downstream consumers (server route,\n * UI hooks, policy derivation) see the same effective values.\n */\nexport class EditorAgentBuilder implements IAgentBuilder {\n  private readonly options: AgentBuilderOptions;\n  private readonly modelPolicyWarnings: string[] = [];\n\n  /** Non-fatal warnings for browser config issues (surfaced alongside model policy warnings). */\n  private readonly browserConfigWarnings: string[] = [];\n\n  /**\n   * Resolved (default-on normalized) features. Computed once in the\n   * constructor; `undefined` only if the builder was constructed with\n   * `enabled: false` (we still allocate features for the OFF path so callers\n   * can introspect, but we keep the field optional to preserve the existing\n   * API contract where `getFeatures()` may legitimately return `undefined`\n   * if no `features` was provided AND no defaults could be applied).\n   *\n   * In practice this is always populated: `resolveAgentFeatures` returns a\n   * fully-populated object regardless of input.\n   */\n  private readonly resolvedFeatures: AgentBuilderOptions['features'];\n\n  constructor(options?: AgentBuilderOptions) {\n    // Shallow-clone the paths the validators mutate so we never leak side\n    // effects into the caller's `MastraEditorConfig.builder` object.\n    // `validateBrowserConfig` writes to `features.agent.browser`; nothing\n    // else is mutated, so `configuration` and `registries` stay aliased.\n    const source = options ?? {};\n    this.options = {\n      ...source,\n      features: source.features\n        ? {\n            ...source.features,\n            agent: source.features.agent ? { ...source.features.agent } : undefined,\n          }\n        : undefined,\n    };\n    this.validateModelPolicy();\n    this.validateBrowserConfig();\n    // Resolve features AFTER browser-config validation so that an explicit\n    // `browser: true` with bad config is already mutated to `false` on\n    // `this.options.features.agent.browser`. The resolver then sees the\n    // downgraded value and returns it as-is.\n    this.resolvedFeatures = {\n      agent: resolveAgentFeatures(this.options.features?.agent, {\n        hasBrowserConfig: this.hasValidBrowserConfig(),\n      }),\n    };\n  }\n\n  get enabled(): boolean {\n    return this.options.enabled !== false;\n  }\n\n  getFeatures(): AgentBuilderOptions['features'] {\n    return this.resolvedFeatures;\n  }\n\n  getConfiguration(): AgentBuilderOptions['configuration'] {\n    return this.options.configuration;\n  }\n\n  getRegistries(): AgentBuilderOptions['registries'] {\n    return this.options.registries;\n  }\n\n  getModelPolicyWarnings(): string[] {\n    return [...this.modelPolicyWarnings, ...this.browserConfigWarnings];\n  }\n\n  /**\n   * True when `configuration.agent.browser` declares a provider. The\n   * EditorAgentBuilder does NOT verify the provider is registered with the\n   * Mastra instance — that cross-validation lives in `MastraEditor.resolveBuilder`\n   * because only the editor knows the registered browser providers.\n   */\n  private hasValidBrowserConfig(): boolean {\n    const browserConfig = this.options.configuration?.agent?.browser;\n    return Boolean(browserConfig?.config?.provider);\n  }\n\n  /**\n   * Browser config validation only runs for **explicit** `browser: true`.\n   * With default-on semantics, an omitted `browser` no longer means \"admin\n   * opted in\" — it means \"admin didn't opt out\". The default-on path is\n   * resolved later by `resolveAgentFeatures`, which already gates `browser`\n   * on `hasValidBrowserConfig`. We don't want to spam every default-config\n   * deployment with warnings.\n   */\n  private validateBrowserConfig(): void {\n    const explicitBrowser = this.options.features?.agent?.browser;\n    if (explicitBrowser !== true) return;\n\n    const browserConfig = this.options.configuration?.agent?.browser;\n    if (!browserConfig) {\n      const warning =\n        'Agent Builder browser feature is enabled but no default browser config was provided. ' +\n        'Set `editor.builder.configuration.agent.browser` to a valid browser config ' +\n        '(e.g. `{ type: \"inline\", config: { provider: \"stagehand\" } }`). ' +\n        'The browser toggle will be hidden until a default is configured.';\n      this.browserConfigWarnings.push(warning);\n      // eslint-disable-next-line no-console\n      console.warn(`[mastra:editor:builder] ${warning}`);\n      // Downgrade so the resolved feature ends up `false`.\n      if (this.options.features?.agent) {\n        this.options.features.agent.browser = false;\n      }\n      return;\n    }\n\n    if (!browserConfig.config?.provider) {\n      const warning =\n        'Agent Builder browser config is missing a `provider` field. ' +\n        'Set `editor.builder.configuration.agent.browser.config.provider` ' +\n        '(e.g. `\"stagehand\"`). The browser toggle will be hidden until a provider is configured.';\n      this.browserConfigWarnings.push(warning);\n      // eslint-disable-next-line no-console\n      console.warn(`[mastra:editor:builder] ${warning}`);\n      if (this.options.features?.agent) {\n        this.options.features.agent.browser = false;\n      }\n    }\n  }\n\n  private validateModelPolicy(): void {\n    const enabled = this.options.enabled !== false;\n    // Locked-mode is only triggered by an explicit `model: false` from the\n    // admin. With default-on semantics, an omitted `model` resolves to\n    // `true` (picker visible), which is open mode and has no\n    // locked-mode-default invariant.\n    const explicitModel = this.options.features?.agent?.model;\n    const pickerVisible = explicitModel !== false;\n    const models = this.options.configuration?.agent?.models;\n    const allowed = models?.allowed;\n    const defaultModel = models?.default;\n\n    const active = isBuilderModelPolicyActive({\n      enabled,\n      pickerVisible,\n      allowed,\n      default: defaultModel,\n    });\n\n    if (!active) return;\n\n    // Locked mode (picker hidden) requires an admin-pinned default. Phase 3's\n    // create-path decision matrix relies on this invariant: a locked policy\n    // without a default is unreachable. Only fires when the admin has\n    // explicitly opted out of the picker.\n    if (explicitModel === false && defaultModel === undefined) {\n      throw new Error(\n        'Agent Builder model policy is active in locked mode but no default was set. ' +\n          'Set `editor.builder.configuration.agent.models.default`, or remove ' +\n          '`editor.builder.features.agent.model = false` to allow end-users to pick a model.',\n      );\n    }\n\n    // When an allowlist is set, the default (if any) must satisfy it. An\n    // empty `allowed: []` means \"unrestricted\" so we skip this check.\n    if (defaultModel !== undefined && allowed !== undefined && allowed.length > 0) {\n      if (!isModelAllowed(allowed, defaultModel)) {\n        throw new Error(\n          'Agent Builder default model is not in the allowlist. ' +\n            'Either add it to `editor.builder.configuration.agent.models.allowed` ' +\n            'or change `editor.builder.configuration.agent.models.default`.',\n        );\n      }\n    }\n  }\n}\n\n// AgentFeatures imported for documentation reference in this file's jsdoc.\nexport type { AgentFeatures };\n","import { Agent } from '@mastra/core/agent';\nimport { Memory } from '@mastra/memory';\nimport { Workspace, LocalFilesystem } from '@mastra/core/workspace';\n\nimport path from 'node:path';\nimport { fileURLToPath } from 'node:url';\n\nconst __filename = fileURLToPath(import.meta.url);\nconst __dirname = path.dirname(__filename);\n\nconst workspacePath = path.join(__dirname, 'workspace');\n\nconst workspace = new Workspace({\n  filesystem: new LocalFilesystem({\n    basePath: workspacePath,\n  }),\n  skills: ['skills'],\n});\n\n/**\n * Agent Builder Agent\n *\n * Audience: non-technical users (Product, founders, operators, business stakeholders).\n * Goal: turn a plain-language description of a desired outcome into a fully\n * configured, production-quality agent — name, description, model, capabilities,\n * and system prompt — without asking the user follow-up questions.\n *\n * Capability tools the playground UI injects as client tools:\n * - set-agent-name, set-agent-description, set-agent-instructions, set-agent-workspace-id (always on)\n * - set-agent-tools (gated by features.tools)\n * - set-agent-skills (gated by features.skills + skills available)\n * - set-agent-model (gated by features.model + models available)\n * - set-agent-browser-enabled (gated by features.browser)\n * - createSkillTool (gated by features.skills) — only when a needed capability does not exist\n */\n\nexport function createBuilderAgent(\n  args?: Partial<ConstructorParameters<typeof Agent<'builder-agent'>>[0]>,\n): Agent<'builder-agent'> {\n  const memory = new Memory();\n\n  return new Agent<'builder-agent'>({\n    instructions: `You are the Agent Builder.\n\nYour job: turn a non-technical user's plain-language request into a fully configured, production-quality agent in a single turn.\n\n# Non-negotiables\n\n- Never ask the user follow-up questions. Make the most reasonable assumption and move forward.\n- Never expose internal names, tool ids, file paths, schemas, code, or jargon to the user.\n- Speak only in user-facing capability terms.\n- Always finish the build in the same turn as the request — configure the agent end-to-end and deliver a short summary.\n- Always define the new agent's name, description, model, and system prompt yourself. Do not ask the user for any of these.\n\nExamples of communication style:\n- Bad: \"Added weatherTool to agent-yzx capabilities.\"\n- Good: \"Your new agent can now check the weather for you.\"\n- Bad: \"Calling set-agent-tools with [weatherTool].\"\n- Good: \"Checking what capabilities to bring to your agent…\"\n- Bad: \"Agent created with weatherTool and recipeWorkflow attached.\"\n- Good: \"Your agent can check the weather and suggest recipes that match the day's conditions.\"\n\n# Authoring loop\n\nFollow these five steps in order, every time:\n\n## Step A — Understand the real outcome\n\nAnalyze what the user actually wants to achieve. Focus on the final result, not just the literal wording of the request.\n\nAsk yourself:\n- What should the agent help the user accomplish?\n- Who will use this agent?\n- What decisions should the agent make on its own?\n- What kind of output should the agent produce?\n- What recurring tasks, reasoning, or actions does the agent need to perform?\n\n## Step B — Define the agent's identity\n\nBefore building the agent, define:\n- Agent name: short, memorable, anchored to the outcome. Never \"Agent X\" or generic labels\n- Description: exactly one sentence in plain user-facing language explaining what the agent helps with.\n\nCall \\`set-agent-name\\` and \\`set-agent-description\\` to set the agent's identity. Skip any whose feature is not available in the form snapshot.\n\n## Step C — Decide capabilities\n\nRead the form snapshot already injected into your context. It lists the user's current selections plus the available tools, agents, workflows, stored skills, models, and workspaces.\n\nThen:\n- Pick the *minimum* set of existing tools/agents/workflows/stored skills that satisfies the outcome. Adding irrelevant capabilities makes the agent worse, not better.\n- Prefer existing tools, workflows, agents, and stored skills before creating anything new.\n- \\`set-agent-skills\\` attaches user-available stored skills from the form snapshot.\n- Only call \\`createSkillTool\\` when (a) no existing stored skill matches reusable operating instructions the produced agent needs, AND (b) that operating instruction is genuinely needed for the outcome. Do not use stored skills as a substitute for missing integrations or tools.\n- If a specific external connection is required (e.g. a sheet tool for a spreadsheet-driven outcome) and none is available, the new agent's system prompt must instruct it to refuse cleanly and explain what the user needs to connect.\n\n## Step D — Synthesize the run contract\n\nBefore calling \\`set-agent-instructions\\`, privately write a concrete run contract for the produced agent. The system prompt must instantiate each item:\n\n1. **Trigger / input** — what user request, schedule, event, file, row, ticket, or message starts a run.\n2. **Owned outcome** — the exact result the produced agent is responsible for finishing.\n3. **Available capabilities** — only capabilities actually attached or already available from the form snapshot, described in user-facing outcome terms.\n4. **Missing-capability fallback** — what the produced agent does when a required integration, workspace, credential, or source is absent.\n5. **Done criteria** — verifiable conditions that prove the job is finished, including tool confirmation or an explicit \"not run\" reason when verification is impossible.\n6. **Final response format** — the receipt, summary, draft, diff summary, report, or confirmation the user receives.\n\n## Step E — Write the agent\n\nCall the capability tools. Skip any whose feature is not available in the form snapshot.\n\n1. \\`set-agent-model\\` — pick the best model for the use case from the available models list. Rules:\n   - Choose only a model id that appears in the available models list. Never invent, assume, or copy example model ids.\n   - For coding, reasoning-heavy, or planning agents, prefer the most capable available model.\n   - For short, simple, structured, or high-volume tasks, prefer a lower-latency/lower-cost available model when quality will not materially suffer.\n   - If several plausible models are available, choose the newest or strongest option based on the metadata visible in the snapshot.\n2. \\`set-agent-tools\\` — attach the minimum set chosen in Step C. Also use \\`set-agent-skills\\` and \\`set-agent-browser-enabled\\` only when applicable and supported by the snapshot.\n3. \\`set-agent-instructions\\` — write the new agent's system prompt from scratch, tailored to the user's specific outcome and the run contract from Step D.\n\nBefore calling \\`set-agent-instructions\\`, self-audit the draft. It must pass every check:\n- No placeholders remain (no \\`<...>\\`, \"TBD\", \"TODO\", \"your tool\", or generic policy gaps).\n- No internal tool ids, file paths, schemas, or builder-only terms appear.\n- No generic \"helpful assistant\" identity remains.\n- No unsupported capabilities are promised.\n- Completion criteria are present, concrete, and tool-aware.\n- Refusal / fallback path is present for missing integrations, credentials, permissions, workspace, or sources.\n- Final response format is specified.\n\n## Step F — Confirm the agent configuration to the user\n\nEnd your turn with one short, friendly paragraph confirming that the agent has been configured and is ready to use.\n\nUse this shape:\n\n\"Your agent, [Agent Name], has been configured with its initial parameters. It can now [plain-language outcome]. You can adjust its instructions, inputs, or connected capabilities whenever your needs change.\"\n\nDo not mention internal capability names, tools, workflows, skills, or configuration steps.\n\nGood:\n\"Your agent, Sales Drop Watcher, has been configured with its initial parameters. It can now review your weekly sales sheet, flag accounts that dropped more than 10%, and prepare follow-up drafts for each one. You can adjust its instructions, thresholds, or connected data sources whenever your needs change.\"\n\nBad:\n\"Agent created with sheetsTool, scoringWorkflow, and emailSkill attached.\"\n\nBad:\n\"I configured the sheets integration and called set-agent-instructions.\"\n\n# Quality bar for the produced agent's system prompt\n\nThe system prompt written into \\`set-agent-instructions\\` MUST include all of the following:\n\n1. **Role and outcome.** Define what the agent is and the concrete result it owns.\n2. **Trigger and input.** Define what starts a run and what input the agent expects.\n3. **Decision rules.** Explain how the agent resolves ambiguity, what defaults it should apply, and what it should skip without asking the user.\n4. **Capability awareness.** Describe only the tools, integrations, workspaces, or data sources the agent actually has, phrased in terms of what they let the agent accomplish.\n5. **Missing-capability fallback.** Explain what the agent should do when a required integration, credential, permission, workspace, or source is unavailable.\n6. **Completion criteria.** Define exactly when the task is done in observable, verifiable terms.\n7. **Final response format.** Specify the exact shape of the agent's final answer, report, draft, receipt, or confirmation.\n8. **Communication style.** Require plain language, short answers, no jargon, and structure only when useful.\n9. **Refusal rules.** State what the agent must refuse and how it should explain the refusal clearly.\n10. **Worked example.** Include at least one short input → output example showing a complete successful run.\n\n# Hard rules\n\n- If the user's request requires CLI or local-machine actions and no workspace is connected, refuse in plain language and tell the user they need to connect a workspace first.\n- Never reveal that you are calling configuration tools. Describe progress only in terms of the user's intended outcome.\n- Never produce a system prompt without explicit completion criteria.\n- Never attach a capability \"just in case.\" Every tool, agent, workflow, or skill must directly support the requested outcome.\n- The final message to the user must be concise, friendly, and focused on what the configured agent can now do.\n- The final message should make clear that the agent starts with initial parameters and can be adjusted later.`,\n    model: 'openai/gpt-5.5',\n    memory,\n    workspace,\n    ...(args || {}),\n    id: 'builder-agent',\n    name: 'Agent Builder Agent',\n    description: 'An agent that can build agents',\n  });\n}\n"],"mappings":";AACA,SAAS,4BAA4B,gBAAgB,4BAA4B;AAe1E,IAAM,qBAAN,MAAkD;AAAA,EAoBvD,YAAY,SAA+B;AAlB3C,SAAiB,sBAAgC,CAAC;AAGlD;AAAA,SAAiB,wBAAkC,CAAC;AAoBlD,UAAM,SAAS,WAAW,CAAC;AAC3B,SAAK,UAAU;AAAA,MACb,GAAG;AAAA,MACH,UAAU,OAAO,WACb;AAAA,QACE,GAAG,OAAO;AAAA,QACV,OAAO,OAAO,SAAS,QAAQ,EAAE,GAAG,OAAO,SAAS,MAAM,IAAI;AAAA,MAChE,IACA;AAAA,IACN;AACA,SAAK,oBAAoB;AACzB,SAAK,sBAAsB;AAK3B,SAAK,mBAAmB;AAAA,MACtB,OAAO,qBAAqB,KAAK,QAAQ,UAAU,OAAO;AAAA,QACxD,kBAAkB,KAAK,sBAAsB;AAAA,MAC/C,CAAC;AAAA,IACH;AAAA,EACF;AAAA,EAEA,IAAI,UAAmB;AACrB,WAAO,KAAK,QAAQ,YAAY;AAAA,EAClC;AAAA,EAEA,cAA+C;AAC7C,WAAO,KAAK;AAAA,EACd;AAAA,EAEA,mBAAyD;AACvD,WAAO,KAAK,QAAQ;AAAA,EACtB;AAAA,EAEA,gBAAmD;AACjD,WAAO,KAAK,QAAQ;AAAA,EACtB;AAAA,EAEA,yBAAmC;AACjC,WAAO,CAAC,GAAG,KAAK,qBAAqB,GAAG,KAAK,qBAAqB;AAAA,EACpE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAQQ,wBAAiC;AACvC,UAAM,gBAAgB,KAAK,QAAQ,eAAe,OAAO;AACzD,WAAO,QAAQ,eAAe,QAAQ,QAAQ;AAAA,EAChD;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAUQ,wBAA8B;AACpC,UAAM,kBAAkB,KAAK,QAAQ,UAAU,OAAO;AACtD,QAAI,oBAAoB,KAAM;AAE9B,UAAM,gBAAgB,KAAK,QAAQ,eAAe,OAAO;AACzD,QAAI,CAAC,eAAe;AAClB,YAAM,UACJ;AAIF,WAAK,sBAAsB,KAAK,OAAO;AAEvC,cAAQ,KAAK,2BAA2B,OAAO,EAAE;AAEjD,UAAI,KAAK,QAAQ,UAAU,OAAO;AAChC,aAAK,QAAQ,SAAS,MAAM,UAAU;AAAA,MACxC;AACA;AAAA,IACF;AAEA,QAAI,CAAC,cAAc,QAAQ,UAAU;AACnC,YAAM,UACJ;AAGF,WAAK,sBAAsB,KAAK,OAAO;AAEvC,cAAQ,KAAK,2BAA2B,OAAO,EAAE;AACjD,UAAI,KAAK,QAAQ,UAAU,OAAO;AAChC,aAAK,QAAQ,SAAS,MAAM,UAAU;AAAA,MACxC;AAAA,IACF;AAAA,EACF;AAAA,EAEQ,sBAA4B;AAClC,UAAM,UAAU,KAAK,QAAQ,YAAY;AAKzC,UAAM,gBAAgB,KAAK,QAAQ,UAAU,OAAO;AACpD,UAAM,gBAAgB,kBAAkB;AACxC,UAAM,SAAS,KAAK,QAAQ,eAAe,OAAO;AAClD,UAAM,UAAU,QAAQ;AACxB,UAAM,eAAe,QAAQ;AAE7B,UAAM,SAAS,2BAA2B;AAAA,MACxC;AAAA,MACA;AAAA,MACA;AAAA,MACA,SAAS;AAAA,IACX,CAAC;AAED,QAAI,CAAC,OAAQ;AAMb,QAAI,kBAAkB,SAAS,iBAAiB,QAAW;AACzD,YAAM,IAAI;AAAA,QACR;AAAA,MAGF;AAAA,IACF;AAIA,QAAI,iBAAiB,UAAa,YAAY,UAAa,QAAQ,SAAS,GAAG;AAC7E,UAAI,CAAC,eAAe,SAAS,YAAY,GAAG;AAC1C,cAAM,IAAI;AAAA,UACR;AAAA,QAGF;AAAA,MACF;AAAA,IACF;AAAA,EACF;AACF;;;ACvLA,SAAS,aAAa;AACtB,SAAS,cAAc;AACvB,SAAS,WAAW,uBAAuB;AAE3C,OAAO,UAAU;AACjB,SAAS,qBAAqB;AAE9B,IAAM,aAAa,cAAc,YAAY,GAAG;AAChD,IAAM,YAAY,KAAK,QAAQ,UAAU;AAEzC,IAAM,gBAAgB,KAAK,KAAK,WAAW,WAAW;AAEtD,IAAM,YAAY,IAAI,UAAU;AAAA,EAC9B,YAAY,IAAI,gBAAgB;AAAA,IAC9B,UAAU;AAAA,EACZ,CAAC;AAAA,EACD,QAAQ,CAAC,QAAQ;AACnB,CAAC;AAmBM,SAAS,mBACd,MACwB;AACxB,QAAM,SAAS,IAAI,OAAO;AAE1B,SAAO,IAAI,MAAuB;AAAA,IAChC,cAAc;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;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;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,IAgId,OAAO;AAAA,IACP;AAAA,IACA;AAAA,IACA,GAAI,QAAQ,CAAC;AAAA,IACb,IAAI;AAAA,IACJ,MAAM;AAAA,IACN,aAAa;AAAA,EACf,CAAC;AACH;","names":[]}
+{"version":3,"sources":["../../src/ee/agent-builder.ts","../../src/ee/agent-builder-agent.ts"],"sourcesContent":["import type { AgentBuilderOptions, AgentFeatures, IAgentBuilder } from '@mastra/core/agent-builder/ee';\nimport { isBuilderModelPolicyActive, isModelAllowed, resolveAgentFeatures } from '@mastra/core/agent-builder/ee';\n\n/**\n * Concrete implementation of the Agent Builder EE feature.\n * Instantiated by MastraEditor.resolveBuilder() when builder config is enabled.\n *\n * The constructor performs fail-fast validation of the admin's model policy\n * (Phase 4) so misconfiguration is caught at boot, not at first request.\n *\n * Feature toggles use **default-on semantics**: omitted keys resolve to\n * `true`. Admins opt out by setting a key to `false`. The resolved features\n * are computed once in the constructor (after validation) and returned\n * verbatim by {@link getFeatures} so all downstream consumers (server route,\n * UI hooks, policy derivation) see the same effective values.\n */\nexport class EditorAgentBuilder implements IAgentBuilder {\n  private readonly options: AgentBuilderOptions;\n  private readonly modelPolicyWarnings: string[] = [];\n\n  /** Non-fatal warnings for browser config issues (surfaced alongside model policy warnings). */\n  private readonly browserConfigWarnings: string[] = [];\n\n  /**\n   * Resolved (default-on normalized) features. Computed once in the\n   * constructor; `undefined` only if the builder was constructed with\n   * `enabled: false` (we still allocate features for the OFF path so callers\n   * can introspect, but we keep the field optional to preserve the existing\n   * API contract where `getFeatures()` may legitimately return `undefined`\n   * if no `features` was provided AND no defaults could be applied).\n   *\n   * In practice this is always populated: `resolveAgentFeatures` returns a\n   * fully-populated object regardless of input.\n   */\n  private readonly resolvedFeatures: AgentBuilderOptions['features'];\n\n  constructor(options?: AgentBuilderOptions) {\n    // Shallow-clone the paths the validators mutate so we never leak side\n    // effects into the caller's `MastraEditorConfig.builder` object.\n    // `validateBrowserConfig` writes to `features.agent.browser`; nothing\n    // else is mutated, so `configuration` and `registries` stay aliased.\n    const source = options ?? {};\n    this.options = {\n      ...source,\n      features: source.features\n        ? {\n            ...source.features,\n            agent: source.features.agent ? { ...source.features.agent } : undefined,\n          }\n        : undefined,\n    };\n    this.validateModelPolicy();\n    this.validateBrowserConfig();\n    // Resolve features AFTER browser-config validation so that an explicit\n    // `browser: true` with bad config is already mutated to `false` on\n    // `this.options.features.agent.browser`. The resolver then sees the\n    // downgraded value and returns it as-is.\n    this.resolvedFeatures = {\n      agent: resolveAgentFeatures(this.options.features?.agent, {\n        hasBrowserConfig: this.hasValidBrowserConfig(),\n      }),\n    };\n  }\n\n  get enabled(): boolean {\n    return this.options.enabled !== false;\n  }\n\n  getFeatures(): AgentBuilderOptions['features'] {\n    return this.resolvedFeatures;\n  }\n\n  getConfiguration(): AgentBuilderOptions['configuration'] {\n    return this.options.configuration;\n  }\n\n  getRegistries(): AgentBuilderOptions['registries'] {\n    return this.options.registries;\n  }\n\n  getModelPolicyWarnings(): string[] {\n    return [...this.modelPolicyWarnings, ...this.browserConfigWarnings];\n  }\n\n  /**\n   * True when `configuration.agent.browser` declares a provider. The\n   * EditorAgentBuilder does NOT verify the provider is registered with the\n   * Mastra instance — that cross-validation lives in `MastraEditor.resolveBuilder`\n   * because only the editor knows the registered browser providers.\n   */\n  private hasValidBrowserConfig(): boolean {\n    const browserConfig = this.options.configuration?.agent?.browser;\n    return Boolean(browserConfig?.config?.provider);\n  }\n\n  /**\n   * Browser config validation only runs for **explicit** `browser: true`.\n   * With default-on semantics, an omitted `browser` no longer means \"admin\n   * opted in\" — it means \"admin didn't opt out\". The default-on path is\n   * resolved later by `resolveAgentFeatures`, which already gates `browser`\n   * on `hasValidBrowserConfig`. We don't want to spam every default-config\n   * deployment with warnings.\n   */\n  private validateBrowserConfig(): void {\n    const explicitBrowser = this.options.features?.agent?.browser;\n    if (explicitBrowser !== true) return;\n\n    const browserConfig = this.options.configuration?.agent?.browser;\n    if (!browserConfig) {\n      const warning =\n        'Agent Builder browser feature is enabled but no default browser config was provided. ' +\n        'Set `editor.builder.configuration.agent.browser` to a valid browser config ' +\n        '(e.g. `{ type: \"inline\", config: { provider: \"stagehand\" } }`). ' +\n        'The browser toggle will be hidden until a default is configured.';\n      this.browserConfigWarnings.push(warning);\n      // eslint-disable-next-line no-console\n      console.warn(`[mastra:editor:builder] ${warning}`);\n      // Downgrade so the resolved feature ends up `false`.\n      if (this.options.features?.agent) {\n        this.options.features.agent.browser = false;\n      }\n      return;\n    }\n\n    if (!browserConfig.config?.provider) {\n      const warning =\n        'Agent Builder browser config is missing a `provider` field. ' +\n        'Set `editor.builder.configuration.agent.browser.config.provider` ' +\n        '(e.g. `\"stagehand\"`). The browser toggle will be hidden until a provider is configured.';\n      this.browserConfigWarnings.push(warning);\n      // eslint-disable-next-line no-console\n      console.warn(`[mastra:editor:builder] ${warning}`);\n      if (this.options.features?.agent) {\n        this.options.features.agent.browser = false;\n      }\n    }\n  }\n\n  private validateModelPolicy(): void {\n    const enabled = this.options.enabled !== false;\n    // Locked-mode is only triggered by an explicit `model: false` from the\n    // admin. With default-on semantics, an omitted `model` resolves to\n    // `true` (picker visible), which is open mode and has no\n    // locked-mode-default invariant.\n    const explicitModel = this.options.features?.agent?.model;\n    const pickerVisible = explicitModel !== false;\n    const models = this.options.configuration?.agent?.models;\n    const allowed = models?.allowed;\n    const defaultModel = models?.default;\n\n    const active = isBuilderModelPolicyActive({\n      enabled,\n      pickerVisible,\n      allowed,\n      default: defaultModel,\n    });\n\n    if (!active) return;\n\n    // Locked mode (picker hidden) requires an admin-pinned default. Phase 3's\n    // create-path decision matrix relies on this invariant: a locked policy\n    // without a default is unreachable. Only fires when the admin has\n    // explicitly opted out of the picker.\n    if (explicitModel === false && defaultModel === undefined) {\n      throw new Error(\n        'Agent Builder model policy is active in locked mode but no default was set. ' +\n          'Set `editor.builder.configuration.agent.models.default`, or remove ' +\n          '`editor.builder.features.agent.model = false` to allow end-users to pick a model.',\n      );\n    }\n\n    // When an allowlist is set, the default (if any) must satisfy it. An\n    // empty `allowed: []` means \"unrestricted\" so we skip this check.\n    if (defaultModel !== undefined && allowed !== undefined && allowed.length > 0) {\n      if (!isModelAllowed(allowed, defaultModel)) {\n        throw new Error(\n          'Agent Builder default model is not in the allowlist. ' +\n            'Either add it to `editor.builder.configuration.agent.models.allowed` ' +\n            'or change `editor.builder.configuration.agent.models.default`.',\n        );\n      }\n    }\n  }\n}\n\n// AgentFeatures imported for documentation reference in this file's jsdoc.\nexport type { AgentFeatures };\n","import { Agent } from '@mastra/core/agent';\nimport type { AgentConfig } from '@mastra/core/agent';\nimport { Memory } from '@mastra/memory';\nimport { Workspace, LocalFilesystem } from '@mastra/core/workspace';\n\nimport path from 'node:path';\nimport { fileURLToPath } from 'node:url';\n\nconst __filename = fileURLToPath(import.meta.url);\nconst __dirname = path.dirname(__filename);\n\nconst workspacePath = path.join(__dirname, 'workspace');\n\nconst workspace = new Workspace({\n  filesystem: new LocalFilesystem({\n    basePath: workspacePath,\n  }),\n  skills: ['skills'],\n});\n\n/**\n * Agent Builder Agent\n *\n * Audience: non-technical users (Product, founders, operators, business stakeholders).\n * Goal: turn a plain-language description of a desired outcome into a fully\n * configured, production-quality agent — name, description, model, capabilities,\n * and system prompt — without asking the user follow-up questions.\n *\n * Capability tools the playground UI injects as client tools:\n * - set-agent-name, set-agent-description, set-agent-instructions, set-agent-workspace-id (always on)\n * - set-agent-tools (gated by features.tools)\n * - set-agent-skills (gated by features.skills + skills available)\n * - set-agent-model (gated by features.model + models available)\n * - set-agent-browser-enabled (gated by features.browser)\n * - createSkillTool (gated by features.skills) — only when a needed capability does not exist\n */\n\nexport function createBuilderAgent(args?: Partial<AgentConfig<'builder-agent'>>): Agent<'builder-agent'> {\n  const memory = new Memory();\n\n  const config: AgentConfig<'builder-agent'> = {\n    instructions: `You are the Agent Builder.\n\nYour job: turn a non-technical user's plain-language request into a fully configured, production-quality agent in a single turn.\n\n# Non-negotiables\n\n- Never ask the user follow-up questions. Make the most reasonable assumption and move forward.\n- Never expose internal names, tool ids, file paths, schemas, code, or jargon to the user.\n- Speak only in user-facing capability terms.\n- Always finish the build in the same turn as the request — configure the agent end-to-end and deliver a short summary.\n- Always define the new agent's name, description, model, and system prompt yourself. Do not ask the user for any of these.\n\nExamples of communication style:\n- Bad: \"Added weatherTool to agent-yzx capabilities.\"\n- Good: \"Your new agent can now check the weather for you.\"\n- Bad: \"Calling set-agent-tools with [weatherTool].\"\n- Good: \"Checking what capabilities to bring to your agent…\"\n- Bad: \"Agent created with weatherTool and recipeWorkflow attached.\"\n- Good: \"Your agent can check the weather and suggest recipes that match the day's conditions.\"\n\n# Authoring loop\n\nFollow these five steps in order, every time:\n\n## Step A — Understand the real outcome\n\nAnalyze what the user actually wants to achieve. Focus on the final result, not just the literal wording of the request.\n\nAsk yourself:\n- What should the agent help the user accomplish?\n- Who will use this agent?\n- What decisions should the agent make on its own?\n- What kind of output should the agent produce?\n- What recurring tasks, reasoning, or actions does the agent need to perform?\n\n## Step B — Define the agent's identity\n\nBefore building the agent, define:\n- Agent name: short, memorable, anchored to the outcome. Never \"Agent X\" or generic labels\n- Description: exactly one sentence in plain user-facing language explaining what the agent helps with.\n\nCall \\`set-agent-name\\` and \\`set-agent-description\\` to set the agent's identity. Skip any whose feature is not available in the form snapshot.\n\n## Step C — Decide capabilities\n\nRead the form snapshot already injected into your context. It lists the user's current selections plus the available tools, agents, workflows, stored skills, models, and workspaces.\n\nThen:\n- Pick the *minimum* set of existing tools/agents/workflows/stored skills that satisfies the outcome. Adding irrelevant capabilities makes the agent worse, not better.\n- Prefer existing tools, workflows, agents, and stored skills before creating anything new.\n- \\`set-agent-skills\\` attaches user-available stored skills from the form snapshot.\n- Only call \\`createSkillTool\\` when (a) no existing stored skill matches reusable operating instructions the produced agent needs, AND (b) that operating instruction is genuinely needed for the outcome. Do not use stored skills as a substitute for missing integrations or tools.\n- If a specific external connection is required (e.g. a sheet tool for a spreadsheet-driven outcome) and none is available, the new agent's system prompt must instruct it to refuse cleanly and explain what the user needs to connect.\n\n## Step D — Synthesize the run contract\n\nBefore calling \\`set-agent-instructions\\`, privately write a concrete run contract for the produced agent. The system prompt must instantiate each item:\n\n1. **Trigger / input** — what user request, schedule, event, file, row, ticket, or message starts a run.\n2. **Owned outcome** — the exact result the produced agent is responsible for finishing.\n3. **Available capabilities** — only capabilities actually attached or already available from the form snapshot, described in user-facing outcome terms.\n4. **Missing-capability fallback** — what the produced agent does when a required integration, workspace, credential, or source is absent.\n5. **Done criteria** — verifiable conditions that prove the job is finished, including tool confirmation or an explicit \"not run\" reason when verification is impossible.\n6. **Final response format** — the receipt, summary, draft, diff summary, report, or confirmation the user receives.\n\n## Step E — Write the agent\n\nCall the capability tools. Skip any whose feature is not available in the form snapshot.\n\n1. \\`set-agent-model\\` — pick the best model for the use case from the available models list. Rules:\n   - Choose only a model id that appears in the available models list. Never invent, assume, or copy example model ids.\n   - For coding, reasoning-heavy, or planning agents, prefer the most capable available model.\n   - For short, simple, structured, or high-volume tasks, prefer a lower-latency/lower-cost available model when quality will not materially suffer.\n   - If several plausible models are available, choose the newest or strongest option based on the metadata visible in the snapshot.\n2. \\`set-agent-tools\\` — attach the minimum set chosen in Step C. Also use \\`set-agent-skills\\` and \\`set-agent-browser-enabled\\` only when applicable and supported by the snapshot.\n3. \\`set-agent-instructions\\` — write the new agent's system prompt from scratch, tailored to the user's specific outcome and the run contract from Step D.\n\nBefore calling \\`set-agent-instructions\\`, self-audit the draft. It must pass every check:\n- No placeholders remain (no \\`<...>\\`, \"TBD\", \"TODO\", \"your tool\", or generic policy gaps).\n- No internal tool ids, file paths, schemas, or builder-only terms appear.\n- No generic \"helpful assistant\" identity remains.\n- No unsupported capabilities are promised.\n- Completion criteria are present, concrete, and tool-aware.\n- Refusal / fallback path is present for missing integrations, credentials, permissions, workspace, or sources.\n- Final response format is specified.\n\n## Step F — Confirm the agent configuration to the user\n\nEnd your turn with one short, friendly paragraph confirming that the agent has been configured and is ready to use.\n\nUse this shape:\n\n\"Your agent, [Agent Name], has been configured with its initial parameters. It can now [plain-language outcome]. You can adjust its instructions, inputs, or connected capabilities whenever your needs change.\"\n\nDo not mention internal capability names, tools, workflows, skills, or configuration steps.\n\nGood:\n\"Your agent, Sales Drop Watcher, has been configured with its initial parameters. It can now review your weekly sales sheet, flag accounts that dropped more than 10%, and prepare follow-up drafts for each one. You can adjust its instructions, thresholds, or connected data sources whenever your needs change.\"\n\nBad:\n\"Agent created with sheetsTool, scoringWorkflow, and emailSkill attached.\"\n\nBad:\n\"I configured the sheets integration and called set-agent-instructions.\"\n\n# Quality bar for the produced agent's system prompt\n\nThe system prompt written into \\`set-agent-instructions\\` MUST include all of the following:\n\n1. **Role and outcome.** Define what the agent is and the concrete result it owns.\n2. **Trigger and input.** Define what starts a run and what input the agent expects.\n3. **Decision rules.** Explain how the agent resolves ambiguity, what defaults it should apply, and what it should skip without asking the user.\n4. **Capability awareness.** Describe only the tools, integrations, workspaces, or data sources the agent actually has, phrased in terms of what they let the agent accomplish.\n5. **Missing-capability fallback.** Explain what the agent should do when a required integration, credential, permission, workspace, or source is unavailable.\n6. **Completion criteria.** Define exactly when the task is done in observable, verifiable terms.\n7. **Final response format.** Specify the exact shape of the agent's final answer, report, draft, receipt, or confirmation.\n8. **Communication style.** Require plain language, short answers, no jargon, and structure only when useful.\n9. **Refusal rules.** State what the agent must refuse and how it should explain the refusal clearly.\n10. **Worked example.** Include at least one short input → output example showing a complete successful run.\n\n# Hard rules\n\n- If the user's request requires CLI or local-machine actions and no workspace is connected, refuse in plain language and tell the user they need to connect a workspace first.\n- Never reveal that you are calling configuration tools. Describe progress only in terms of the user's intended outcome.\n- Never produce a system prompt without explicit completion criteria.\n- Never attach a capability \"just in case.\" Every tool, agent, workflow, or skill must directly support the requested outcome.\n- The final message to the user must be concise, friendly, and focused on what the configured agent can now do.\n- The final message should make clear that the agent starts with initial parameters and can be adjusted later.`,\n    model: 'openai/gpt-5.5',\n    memory,\n    workspace,\n    ...(args || {}),\n    id: 'builder-agent',\n    name: 'Agent Builder Agent',\n    description: 'An agent that can build agents',\n  };\n\n  return new Agent<'builder-agent'>(config);\n}\n"],"mappings":";AACA,SAAS,4BAA4B,gBAAgB,4BAA4B;AAe1E,IAAM,qBAAN,MAAkD;AAAA,EAoBvD,YAAY,SAA+B;AAlB3C,SAAiB,sBAAgC,CAAC;AAGlD;AAAA,SAAiB,wBAAkC,CAAC;AAoBlD,UAAM,SAAS,WAAW,CAAC;AAC3B,SAAK,UAAU;AAAA,MACb,GAAG;AAAA,MACH,UAAU,OAAO,WACb;AAAA,QACE,GAAG,OAAO;AAAA,QACV,OAAO,OAAO,SAAS,QAAQ,EAAE,GAAG,OAAO,SAAS,MAAM,IAAI;AAAA,MAChE,IACA;AAAA,IACN;AACA,SAAK,oBAAoB;AACzB,SAAK,sBAAsB;AAK3B,SAAK,mBAAmB;AAAA,MACtB,OAAO,qBAAqB,KAAK,QAAQ,UAAU,OAAO;AAAA,QACxD,kBAAkB,KAAK,sBAAsB;AAAA,MAC/C,CAAC;AAAA,IACH;AAAA,EACF;AAAA,EAEA,IAAI,UAAmB;AACrB,WAAO,KAAK,QAAQ,YAAY;AAAA,EAClC;AAAA,EAEA,cAA+C;AAC7C,WAAO,KAAK;AAAA,EACd;AAAA,EAEA,mBAAyD;AACvD,WAAO,KAAK,QAAQ;AAAA,EACtB;AAAA,EAEA,gBAAmD;AACjD,WAAO,KAAK,QAAQ;AAAA,EACtB;AAAA,EAEA,yBAAmC;AACjC,WAAO,CAAC,GAAG,KAAK,qBAAqB,GAAG,KAAK,qBAAqB;AAAA,EACpE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAQQ,wBAAiC;AACvC,UAAM,gBAAgB,KAAK,QAAQ,eAAe,OAAO;AACzD,WAAO,QAAQ,eAAe,QAAQ,QAAQ;AAAA,EAChD;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAUQ,wBAA8B;AACpC,UAAM,kBAAkB,KAAK,QAAQ,UAAU,OAAO;AACtD,QAAI,oBAAoB,KAAM;AAE9B,UAAM,gBAAgB,KAAK,QAAQ,eAAe,OAAO;AACzD,QAAI,CAAC,eAAe;AAClB,YAAM,UACJ;AAIF,WAAK,sBAAsB,KAAK,OAAO;AAEvC,cAAQ,KAAK,2BAA2B,OAAO,EAAE;AAEjD,UAAI,KAAK,QAAQ,UAAU,OAAO;AAChC,aAAK,QAAQ,SAAS,MAAM,UAAU;AAAA,MACxC;AACA;AAAA,IACF;AAEA,QAAI,CAAC,cAAc,QAAQ,UAAU;AACnC,YAAM,UACJ;AAGF,WAAK,sBAAsB,KAAK,OAAO;AAEvC,cAAQ,KAAK,2BAA2B,OAAO,EAAE;AACjD,UAAI,KAAK,QAAQ,UAAU,OAAO;AAChC,aAAK,QAAQ,SAAS,MAAM,UAAU;AAAA,MACxC;AAAA,IACF;AAAA,EACF;AAAA,EAEQ,sBAA4B;AAClC,UAAM,UAAU,KAAK,QAAQ,YAAY;AAKzC,UAAM,gBAAgB,KAAK,QAAQ,UAAU,OAAO;AACpD,UAAM,gBAAgB,kBAAkB;AACxC,UAAM,SAAS,KAAK,QAAQ,eAAe,OAAO;AAClD,UAAM,UAAU,QAAQ;AACxB,UAAM,eAAe,QAAQ;AAE7B,UAAM,SAAS,2BAA2B;AAAA,MACxC;AAAA,MACA;AAAA,MACA;AAAA,MACA,SAAS;AAAA,IACX,CAAC;AAED,QAAI,CAAC,OAAQ;AAMb,QAAI,kBAAkB,SAAS,iBAAiB,QAAW;AACzD,YAAM,IAAI;AAAA,QACR;AAAA,MAGF;AAAA,IACF;AAIA,QAAI,iBAAiB,UAAa,YAAY,UAAa,QAAQ,SAAS,GAAG;AAC7E,UAAI,CAAC,eAAe,SAAS,YAAY,GAAG;AAC1C,cAAM,IAAI;AAAA,UACR;AAAA,QAGF;AAAA,MACF;AAAA,IACF;AAAA,EACF;AACF;;;ACvLA,SAAS,aAAa;AAEtB,SAAS,cAAc;AACvB,SAAS,WAAW,uBAAuB;AAE3C,OAAO,UAAU;AACjB,SAAS,qBAAqB;AAE9B,IAAM,aAAa,cAAc,YAAY,GAAG;AAChD,IAAM,YAAY,KAAK,QAAQ,UAAU;AAEzC,IAAM,gBAAgB,KAAK,KAAK,WAAW,WAAW;AAEtD,IAAM,YAAY,IAAI,UAAU;AAAA,EAC9B,YAAY,IAAI,gBAAgB;AAAA,IAC9B,UAAU;AAAA,EACZ,CAAC;AAAA,EACD,QAAQ,CAAC,QAAQ;AACnB,CAAC;AAmBM,SAAS,mBAAmB,MAAsE;AACvG,QAAM,SAAS,IAAI,OAAO;AAE1B,QAAM,SAAuC;AAAA,IAC3C,cAAc;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;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;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,IAgId,OAAO;AAAA,IACP;AAAA,IACA;AAAA,IACA,GAAI,QAAQ,CAAC;AAAA,IACb,IAAI;AAAA,IACJ,MAAM;AAAA,IACN,aAAa;AAAA,EACf;AAEA,SAAO,IAAI,MAAuB,MAAM;AAC1C;","names":[]}

package/dist/index.cjs

@@ -146,7 +146,7 @@ var init_agent_builder = __esm({
 // src/ee/agent-builder-agent.ts
 function createBuilderAgent(args) {
   const memory = new import_memory2.Memory();
-  return new import_agent3.Agent({
+  const config = {
     instructions: `You are the Agent Builder.
 
 Your job: turn a non-technical user's plain-language request into a fully configured, production-quality agent in a single turn.
@@ -282,7 +282,8 @@ The system prompt written into \`set-agent-instructions\` MUST include all of th
     id: "builder-agent",
     name: "Agent Builder Agent",
     description: "An agent that can build agents"
-  });
+  };
+  return new import_agent3.Agent(config);
 }
 var import_agent3, import_memory2, import_workspace7, import_node_path, import_node_url, import_meta, __filename, __dirname, workspacePath, workspace;
 var init_agent_builder_agent = __esm({
@@ -342,6 +343,7 @@ __export(index_exports, {
 });
 module.exports = __toCommonJS(index_exports);
 var import_processor_provider2 = require("@mastra/core/processor-provider");
+var import_storage = require("@mastra/core/storage");
 var import_tool_provider2 = require("@mastra/core/tool-provider");
 
 // src/namespaces/base.ts
@@ -1045,6 +1047,14 @@ var EditorAgentNamespace = class extends CrudEditorNamespace {
    * Returns the (possibly mutated) agent.
    */
   async applyStoredOverrides(agent, options, requestContext) {
+    const editorConfig = agent.__getEditorConfig?.();
+    if (editorConfig === false) {
+      return agent;
+    }
+    const instructionsEditable = editorConfig === void 0 ? true : editorConfig.instructions === true;
+    const toolsConfig = editorConfig === void 0 ? true : editorConfig.tools;
+    const toolsEditable = toolsConfig === true;
+    const toolDescriptionsEditable = typeof toolsConfig === "object" && toolsConfig !== null && toolsConfig.description === true;
     let storedConfig = null;
     try {
       this.ensureRegistered();
@@ -1066,7 +1076,7 @@ var EditorAgentNamespace = class extends CrudEditorNamespace {
     }
     const fork = agent.__fork();
     this.logger?.debug(`[applyStoredOverrides] Applying stored overrides to code agent "${agent.id}"`);
-    if (storedConfig.instructions !== void 0 && storedConfig.instructions !== null) {
+    if (instructionsEditable && storedConfig.instructions !== void 0 && storedConfig.instructions !== null) {
       const resolved = this.resolveStoredInstructions(storedConfig.instructions);
       if (resolved !== void 0) {
         fork.__updateInstructions(resolved);
@@ -1076,7 +1086,7 @@ var EditorAgentNamespace = class extends CrudEditorNamespace {
     const hasStoredMCPClients = storedConfig.mcpClients != null;
     const hasStoredIntegrationTools = storedConfig.integrationTools != null;
     const hasStoredToolProviders = storedConfig.toolProviders != null && Object.keys(storedConfig.toolProviders).length > 0;
-    if (hasStoredTools || hasStoredMCPClients || hasStoredIntegrationTools || hasStoredToolProviders) {
+    if (toolsEditable && (hasStoredTools || hasStoredMCPClients || hasStoredIntegrationTools || hasStoredToolProviders)) {
       const hasConditionalTools = this.isConditionalVariants(storedConfig.tools);
       const hasConditionalMCPClients = storedConfig.mcpClients != null && this.isConditionalVariants(storedConfig.mcpClients);
       const hasConditionalIntegrationTools = storedConfig.integrationTools != null && this.isConditionalVariants(storedConfig.integrationTools);
@@ -1135,6 +1145,28 @@ var EditorAgentNamespace = class extends CrudEditorNamespace {
         );
         fork.__setTools({ ...codeTools, ...registryTools, ...mcpTools, ...integrationTools });
       }
+    } else if (toolDescriptionsEditable && hasStoredTools) {
+      const hasConditionalTools = this.isConditionalVariants(storedConfig.tools);
+      if (hasConditionalTools) {
+        const originalTools = agent.listTools.bind(agent);
+        const toolsFn = async ({ requestContext: requestContext2 }) => {
+          const codeTools = await originalTools({ requestContext: requestContext2 });
+          const resolvedToolsConfig = this.accumulateObjectVariants(
+            storedConfig.tools,
+            requestContext2.toJSON()
+          );
+          return this.applyStoredToolDescriptions(codeTools, resolvedToolsConfig);
+        };
+        fork.__setTools(toolsFn);
+      } else {
+        const codeTools = await fork.listTools();
+        fork.__setTools(
+          this.applyStoredToolDescriptions(
+            codeTools,
+            storedConfig.tools
+          )
+        );
+      }
     }
     if (storedConfig.resolvedVersionId) {
       const existing = fork.toRawConfig() ?? {};
@@ -1435,6 +1467,20 @@ var EditorAgentNamespace = class extends CrudEditorNamespace {
       return resolveInstructionBlocks(blocks, context, { promptBlocksStorage: promptBlocksStore });
     };
   }
+  applyStoredToolDescriptions(codeTools, storedTools) {
+    if (!storedTools || Array.isArray(storedTools)) {
+      return codeTools;
+    }
+    let nextTools;
+    for (const [toolKey, toolConfig] of Object.entries(storedTools)) {
+      if (!toolConfig.description || !(toolKey in codeTools)) {
+        continue;
+      }
+      nextTools ?? (nextTools = { ...codeTools });
+      nextTools[toolKey] = { ...codeTools[toolKey], description: toolConfig.description };
+    }
+    return nextTools ?? codeTools;
+  }
   /**
    * Resolve stored tool IDs to actual tool instances from Mastra's registry.
    * Applies description overrides from per-tool config when present.
@@ -2549,6 +2595,8 @@ var MastraEditor = class {
     this.__logger = config?.logger;
     this.__toolProviders = config?.toolProviders ?? {};
     this.__processorProviders = { ...import_processor_provider2.BUILT_IN_PROCESSOR_PROVIDERS, ...config?.processorProviders };
+    this.__source = config?.source;
+    this.__codePath = config?.codePath ?? "./mastra/editor";
     this.__filesystems = /* @__PURE__ */ new Map();
     this.__filesystems.set(localFilesystemProvider.id, localFilesystemProvider);
     for (const [id, provider] of Object.entries(config?.filesystems ?? {})) {
@@ -2586,6 +2634,21 @@ var MastraEditor = class {
     if (!this.__logger) {
       this.__logger = mastra.getLogger();
     }
+    if (this.__source === "code") {
+      const filesystemStore = new import_storage.FilesystemStore({ dir: this.__codePath });
+      const existingStorage = mastra.getStorage();
+      if (existingStorage) {
+        mastra.setStorage(
+          new import_storage.MastraCompositeStore({
+            id: `${existingStorage.id}-with-editor-filesystem`,
+            default: existingStorage,
+            editor: filesystemStore
+          })
+        );
+      } else {
+        mastra.setStorage(filesystemStore);
+      }
+    }
     this.ensureBuilderWorkspaces().then(() => this.reconcileBuilderWorkspaces()).catch((err) => {
       this.__logger?.warn("[MastraEditor] Failed to persist/reconcile builder workspaces on startup", {
         error: err
@@ -2734,6 +2797,10 @@ var MastraEditor = class {
       );
     }
   }
+  /** Returns the editor's configured source, or undefined if unset. */
+  getSource() {
+    return this.__source;
+  }
   /** Registered tool providers */
   getToolProvider(id) {
     return this.__toolProviders[id];