@mastra/editor 0.9.1-alpha.1 → 0.10.0-alpha.2

package/dist/ee/index.d.cts

@@ -0,0 +1,77 @@
+import { IAgentBuilder, AgentBuilderOptions } from '@mastra/core/agent-builder/ee';
+import { Agent } from '@mastra/core/agent';
+
+/**
+ * Concrete implementation of the Agent Builder EE feature.
+ * Instantiated by MastraEditor.resolveBuilder() when builder config is enabled.
+ *
+ * The constructor performs fail-fast validation of the admin's model policy
+ * (Phase 4) so misconfiguration is caught at boot, not at first request.
+ *
+ * Feature toggles use **default-on semantics**: omitted keys resolve to
+ * `true`. Admins opt out by setting a key to `false`. The resolved features
+ * are computed once in the constructor (after validation) and returned
+ * verbatim by {@link getFeatures} so all downstream consumers (server route,
+ * UI hooks, policy derivation) see the same effective values.
+ */
+declare class EditorAgentBuilder implements IAgentBuilder {
+    private readonly options;
+    private readonly modelPolicyWarnings;
+    /** Non-fatal warnings for browser config issues (surfaced alongside model policy warnings). */
+    private readonly browserConfigWarnings;
+    /**
+     * Resolved (default-on normalized) features. Computed once in the
+     * constructor; `undefined` only if the builder was constructed with
+     * `enabled: false` (we still allocate features for the OFF path so callers
+     * can introspect, but we keep the field optional to preserve the existing
+     * API contract where `getFeatures()` may legitimately return `undefined`
+     * if no `features` was provided AND no defaults could be applied).
+     *
+     * In practice this is always populated: `resolveAgentFeatures` returns a
+     * fully-populated object regardless of input.
+     */
+    private readonly resolvedFeatures;
+    constructor(options?: AgentBuilderOptions);
+    get enabled(): boolean;
+    getFeatures(): AgentBuilderOptions['features'];
+    getConfiguration(): AgentBuilderOptions['configuration'];
+    getRegistries(): AgentBuilderOptions['registries'];
+    getModelPolicyWarnings(): string[];
+    /**
+     * True when `configuration.agent.browser` declares a provider. The
+     * EditorAgentBuilder does NOT verify the provider is registered with the
+     * Mastra instance — that cross-validation lives in `MastraEditor.resolveBuilder`
+     * because only the editor knows the registered browser providers.
+     */
+    private hasValidBrowserConfig;
+    /**
+     * Browser config validation only runs for **explicit** `browser: true`.
+     * With default-on semantics, an omitted `browser` no longer means "admin
+     * opted in" — it means "admin didn't opt out". The default-on path is
+     * resolved later by `resolveAgentFeatures`, which already gates `browser`
+     * on `hasValidBrowserConfig`. We don't want to spam every default-config
+     * deployment with warnings.
+     */
+    private validateBrowserConfig;
+    private validateModelPolicy;
+}
+
+/**
+ * Agent Builder Agent
+ *
+ * Audience: non-technical users (Product, founders, operators, business stakeholders).
+ * Goal: turn a plain-language description of a desired outcome into a fully
+ * configured, production-quality agent — name, description, model, capabilities,
+ * and system prompt — without asking the user follow-up questions.
+ *
+ * Capability tools the playground UI injects as client tools:
+ * - set-agent-name, set-agent-description, set-agent-instructions, set-agent-workspace-id (always on)
+ * - set-agent-tools (gated by features.tools)
+ * - set-agent-skills (gated by features.skills + skills available)
+ * - set-agent-model (gated by features.model + models available)
+ * - set-agent-browser-enabled (gated by features.browser)
+ * - createSkillTool (gated by features.skills) — only when a needed capability does not exist
+ */
+declare function createBuilderAgent(): Agent;
+
+export { EditorAgentBuilder, createBuilderAgent };

package/dist/ee/index.d.ts

@@ -0,0 +1,77 @@
+import { IAgentBuilder, AgentBuilderOptions } from '@mastra/core/agent-builder/ee';
+import { Agent } from '@mastra/core/agent';
+
+/**
+ * Concrete implementation of the Agent Builder EE feature.
+ * Instantiated by MastraEditor.resolveBuilder() when builder config is enabled.
+ *
+ * The constructor performs fail-fast validation of the admin's model policy
+ * (Phase 4) so misconfiguration is caught at boot, not at first request.
+ *
+ * Feature toggles use **default-on semantics**: omitted keys resolve to
+ * `true`. Admins opt out by setting a key to `false`. The resolved features
+ * are computed once in the constructor (after validation) and returned
+ * verbatim by {@link getFeatures} so all downstream consumers (server route,
+ * UI hooks, policy derivation) see the same effective values.
+ */
+declare class EditorAgentBuilder implements IAgentBuilder {
+    private readonly options;
+    private readonly modelPolicyWarnings;
+    /** Non-fatal warnings for browser config issues (surfaced alongside model policy warnings). */
+    private readonly browserConfigWarnings;
+    /**
+     * Resolved (default-on normalized) features. Computed once in the
+     * constructor; `undefined` only if the builder was constructed with
+     * `enabled: false` (we still allocate features for the OFF path so callers
+     * can introspect, but we keep the field optional to preserve the existing
+     * API contract where `getFeatures()` may legitimately return `undefined`
+     * if no `features` was provided AND no defaults could be applied).
+     *
+     * In practice this is always populated: `resolveAgentFeatures` returns a
+     * fully-populated object regardless of input.
+     */
+    private readonly resolvedFeatures;
+    constructor(options?: AgentBuilderOptions);
+    get enabled(): boolean;
+    getFeatures(): AgentBuilderOptions['features'];
+    getConfiguration(): AgentBuilderOptions['configuration'];
+    getRegistries(): AgentBuilderOptions['registries'];
+    getModelPolicyWarnings(): string[];
+    /**
+     * True when `configuration.agent.browser` declares a provider. The
+     * EditorAgentBuilder does NOT verify the provider is registered with the
+     * Mastra instance — that cross-validation lives in `MastraEditor.resolveBuilder`
+     * because only the editor knows the registered browser providers.
+     */
+    private hasValidBrowserConfig;
+    /**
+     * Browser config validation only runs for **explicit** `browser: true`.
+     * With default-on semantics, an omitted `browser` no longer means "admin
+     * opted in" — it means "admin didn't opt out". The default-on path is
+     * resolved later by `resolveAgentFeatures`, which already gates `browser`
+     * on `hasValidBrowserConfig`. We don't want to spam every default-config
+     * deployment with warnings.
+     */
+    private validateBrowserConfig;
+    private validateModelPolicy;
+}
+
+/**
+ * Agent Builder Agent
+ *
+ * Audience: non-technical users (Product, founders, operators, business stakeholders).
+ * Goal: turn a plain-language description of a desired outcome into a fully
+ * configured, production-quality agent — name, description, model, capabilities,
+ * and system prompt — without asking the user follow-up questions.
+ *
+ * Capability tools the playground UI injects as client tools:
+ * - set-agent-name, set-agent-description, set-agent-instructions, set-agent-workspace-id (always on)
+ * - set-agent-tools (gated by features.tools)
+ * - set-agent-skills (gated by features.skills + skills available)
+ * - set-agent-model (gated by features.model + models available)
+ * - set-agent-browser-enabled (gated by features.browser)
+ * - createSkillTool (gated by features.skills) — only when a needed capability does not exist
+ */
+declare function createBuilderAgent(): Agent;
+
+export { EditorAgentBuilder, createBuilderAgent };

package/dist/ee/index.js

@@ -0,0 +1,253 @@
+// src/ee/agent-builder.ts
+import { isBuilderModelPolicyActive, isModelAllowed, resolveAgentFeatures } from "@mastra/core/agent-builder/ee";
+var EditorAgentBuilder = class {
+  constructor(options) {
+    this.modelPolicyWarnings = [];
+    /** Non-fatal warnings for browser config issues (surfaced alongside model policy warnings). */
+    this.browserConfigWarnings = [];
+    const source = options ?? {};
+    this.options = {
+      ...source,
+      features: source.features ? {
+        ...source.features,
+        agent: source.features.agent ? { ...source.features.agent } : void 0
+      } : void 0
+    };
+    this.validateModelPolicy();
+    this.validateBrowserConfig();
+    this.resolvedFeatures = {
+      agent: resolveAgentFeatures(this.options.features?.agent, {
+        hasBrowserConfig: this.hasValidBrowserConfig()
+      })
+    };
+  }
+  get enabled() {
+    return this.options.enabled !== false;
+  }
+  getFeatures() {
+    return this.resolvedFeatures;
+  }
+  getConfiguration() {
+    return this.options.configuration;
+  }
+  getRegistries() {
+    return this.options.registries;
+  }
+  getModelPolicyWarnings() {
+    return [...this.modelPolicyWarnings, ...this.browserConfigWarnings];
+  }
+  /**
+   * True when `configuration.agent.browser` declares a provider. The
+   * EditorAgentBuilder does NOT verify the provider is registered with the
+   * Mastra instance — that cross-validation lives in `MastraEditor.resolveBuilder`
+   * because only the editor knows the registered browser providers.
+   */
+  hasValidBrowserConfig() {
+    const browserConfig = this.options.configuration?.agent?.browser;
+    return Boolean(browserConfig?.config?.provider);
+  }
+  /**
+   * Browser config validation only runs for **explicit** `browser: true`.
+   * With default-on semantics, an omitted `browser` no longer means "admin
+   * opted in" — it means "admin didn't opt out". The default-on path is
+   * resolved later by `resolveAgentFeatures`, which already gates `browser`
+   * on `hasValidBrowserConfig`. We don't want to spam every default-config
+   * deployment with warnings.
+   */
+  validateBrowserConfig() {
+    const explicitBrowser = this.options.features?.agent?.browser;
+    if (explicitBrowser !== true) return;
+    const browserConfig = this.options.configuration?.agent?.browser;
+    if (!browserConfig) {
+      const warning = 'Agent Builder browser feature is enabled but no default browser config was provided. Set `editor.builder.configuration.agent.browser` to a valid browser config (e.g. `{ type: "inline", config: { provider: "stagehand" } }`). The browser toggle will be hidden until a default is configured.';
+      this.browserConfigWarnings.push(warning);
+      console.warn(`[mastra:editor:builder] ${warning}`);
+      if (this.options.features?.agent) {
+        this.options.features.agent.browser = false;
+      }
+      return;
+    }
+    if (!browserConfig.config?.provider) {
+      const warning = 'Agent Builder browser config is missing a `provider` field. Set `editor.builder.configuration.agent.browser.config.provider` (e.g. `"stagehand"`). The browser toggle will be hidden until a provider is configured.';
+      this.browserConfigWarnings.push(warning);
+      console.warn(`[mastra:editor:builder] ${warning}`);
+      if (this.options.features?.agent) {
+        this.options.features.agent.browser = false;
+      }
+    }
+  }
+  validateModelPolicy() {
+    const enabled = this.options.enabled !== false;
+    const explicitModel = this.options.features?.agent?.model;
+    const pickerVisible = explicitModel !== false;
+    const models = this.options.configuration?.agent?.models;
+    const allowed = models?.allowed;
+    const defaultModel = models?.default;
+    const active = isBuilderModelPolicyActive({
+      enabled,
+      pickerVisible,
+      allowed,
+      default: defaultModel
+    });
+    if (!active) return;
+    if (explicitModel === false && defaultModel === void 0) {
+      throw new Error(
+        "Agent Builder model policy is active in locked mode but no default was set. Set `editor.builder.configuration.agent.models.default`, or remove `editor.builder.features.agent.model = false` to allow end-users to pick a model."
+      );
+    }
+    if (defaultModel !== void 0 && allowed !== void 0 && allowed.length > 0) {
+      if (!isModelAllowed(allowed, defaultModel)) {
+        throw new Error(
+          "Agent Builder default model is not in the allowlist. Either add it to `editor.builder.configuration.agent.models.allowed` or change `editor.builder.configuration.agent.models.default`."
+        );
+      }
+    }
+  }
+};
+
+// src/ee/agent-builder-agent.ts
+import { Agent } from "@mastra/core/agent";
+import { Memory } from "@mastra/memory";
+function createBuilderAgent() {
+  const memory = new Memory();
+  return new Agent({
+    id: "builder-agent",
+    name: "Agent Builder Agent",
+    description: "An agent that can build agents",
+    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.
+
+# Non-negotiables
+
+- Never ask the user follow-up questions. Make the most reasonable assumption and move forward.
+- Never expose internal names, tool ids, file paths, schemas, code, or jargon to the user.
+- Speak only in user-facing capability terms.
+- Always finish the build in the same turn as the request \u2014 configure the agent end-to-end and deliver a short summary.
+- Always define the new agent's name, description, model, and system prompt yourself. Do not ask the user for any of these.
+
+Examples of communication style:
+- Bad: "Added weatherTool to agent-yzx capabilities."
+- Good: "Your new agent can now check the weather for you."
+- Bad: "Calling set-agent-tools with [weatherTool]."
+- Good: "Checking what capabilities to bring to your agent\u2026"
+- Bad: "Agent created with weatherTool and recipeWorkflow attached."
+- Good: "Your agent can check the weather and suggest recipes that match the day's conditions."
+
+# Authoring loop
+
+Follow these five steps in order, every time:
+
+## Step A \u2014 Understand the real outcome
+
+Analyze what the user actually wants to achieve. Focus on the final result, not just the literal wording of the request.
+
+Ask yourself:
+- What should the agent help the user accomplish?
+- Who will use this agent?
+- What decisions should the agent make on its own?
+- What kind of output should the agent produce?
+- What recurring tasks, reasoning, or actions does the agent need to perform?
+
+## Step B \u2014 Define the agent's identity
+
+Before building the agent, define:
+- Agent name: short, memorable, anchored to the outcome. Never "Agent X" or generic labels
+- Description: exactly one sentence in plain user-facing language explaining what the agent helps with.
+
+Call \`set-agent-name\` and \`set-agent-description\` to set the agent's identity. Skip any whose feature is not available in the form snapshot.
+
+## Step C \u2014 Decide capabilities
+
+Read 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.
+
+Then:
+- Pick the *minimum* set of existing tools/agents/workflows/stored skills that satisfies the outcome. Adding irrelevant capabilities makes the agent worse, not better.
+- Prefer existing tools, workflows, agents, and stored skills before creating anything new.
+- \`set-agent-skills\` attaches user-available stored skills from the form snapshot.
+- 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.
+- 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.
+
+## Step D \u2014 Synthesize the run contract
+
+Before calling \`set-agent-instructions\`, privately write a concrete run contract for the produced agent. The system prompt must instantiate each item:
+
+1. **Trigger / input** \u2014 what user request, schedule, event, file, row, ticket, or message starts a run.
+2. **Owned outcome** \u2014 the exact result the produced agent is responsible for finishing.
+3. **Available capabilities** \u2014 only capabilities actually attached or already available from the form snapshot, described in user-facing outcome terms.
+4. **Missing-capability fallback** \u2014 what the produced agent does when a required integration, workspace, credential, or source is absent.
+5. **Done criteria** \u2014 verifiable conditions that prove the job is finished, including tool confirmation or an explicit "not run" reason when verification is impossible.
+6. **Final response format** \u2014 the receipt, summary, draft, diff summary, report, or confirmation the user receives.
+
+## Step E \u2014 Write the agent
+
+Call the capability tools. Skip any whose feature is not available in the form snapshot.
+
+1. \`set-agent-model\` \u2014 pick the best model for the use case from the available models list. Rules:
+   - Choose only a model id that appears in the available models list. Never invent, assume, or copy example model ids.
+   - For coding, reasoning-heavy, or planning agents, prefer the most capable available model.
+   - For short, simple, structured, or high-volume tasks, prefer a lower-latency/lower-cost available model when quality will not materially suffer.
+   - If several plausible models are available, choose the newest or strongest option based on the metadata visible in the snapshot.
+2. \`set-agent-tools\` \u2014 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.
+3. \`set-agent-instructions\` \u2014 write the new agent's system prompt from scratch, tailored to the user's specific outcome and the run contract from Step D.
+
+Before calling \`set-agent-instructions\`, self-audit the draft. It must pass every check:
+- No placeholders remain (no \`<...>\`, "TBD", "TODO", "your tool", or generic policy gaps).
+- No internal tool ids, file paths, schemas, or builder-only terms appear.
+- No generic "helpful assistant" identity remains.
+- No unsupported capabilities are promised.
+- Completion criteria are present, concrete, and tool-aware.
+- Refusal / fallback path is present for missing integrations, credentials, permissions, workspace, or sources.
+- Final response format is specified.
+
+## Step F \u2014 Confirm the agent configuration to the user
+
+End your turn with one short, friendly paragraph confirming that the agent has been configured and is ready to use.
+
+Use this shape:
+
+"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."
+
+Do not mention internal capability names, tools, workflows, skills, or configuration steps.
+
+Good:
+"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."
+
+Bad:
+"Agent created with sheetsTool, scoringWorkflow, and emailSkill attached."
+
+Bad:
+"I configured the sheets integration and called set-agent-instructions."
+
+# Quality bar for the produced agent's system prompt
+
+The system prompt written into \`set-agent-instructions\` MUST include all of the following:
+
+1. **Role and outcome.** Define what the agent is and the concrete result it owns.
+2. **Trigger and input.** Define what starts a run and what input the agent expects.
+3. **Decision rules.** Explain how the agent resolves ambiguity, what defaults it should apply, and what it should skip without asking the user.
+4. **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.
+5. **Missing-capability fallback.** Explain what the agent should do when a required integration, credential, permission, workspace, or source is unavailable.
+6. **Completion criteria.** Define exactly when the task is done in observable, verifiable terms.
+7. **Final response format.** Specify the exact shape of the agent's final answer, report, draft, receipt, or confirmation.
+8. **Communication style.** Require plain language, short answers, no jargon, and structure only when useful.
+9. **Refusal rules.** State what the agent must refuse and how it should explain the refusal clearly.
+10. **Worked example.** Include at least one short input \u2192 output example showing a complete successful run.
+
+# Hard rules
+
+- 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.
+- Never reveal that you are calling configuration tools. Describe progress only in terms of the user's intended outcome.
+- Never produce a system prompt without explicit completion criteria.
+- Never attach a capability "just in case." Every tool, agent, workflow, or skill must directly support the requested outcome.
+- The final message to the user must be concise, friendly, and focused on what the configured agent can now do.
+- The final message should make clear that the agent starts with initial parameters and can be adjusted later.`,
+    model: "openai/gpt-5.5",
+    memory
+  });
+}
+export {
+  EditorAgentBuilder,
+  createBuilderAgent
+};
+//# sourceMappingURL=index.js.map

package/dist/ee/index.js.map

@@ -0,0 +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';\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(): Agent {\n  const memory = new Memory();\n  return new Agent({\n    id: 'builder-agent',\n    name: 'Agent Builder Agent',\n    description: 'An agent that can build agents',\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  });\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;AAmBhB,SAAS,qBAA4B;AAC1C,QAAM,SAAS,IAAI,OAAO;AAC1B,SAAO,IAAI,MAAM;AAAA,IACf,IAAI;AAAA,IACJ,MAAM;AAAA,IACN,aAAa;AAAA,IACb,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,EACF,CAAC;AACH;","names":[]}