@mindstudio-ai/remy 0.1.201 → 0.1.203

package/dist/headless.js

@@ -313,6 +313,10 @@ Current date: ${now}
   {{compiled/agent-interfaces.md}}
   </building_agent_interfaces>
 
+  <building_mcp_interfaces>
+  {{compiled/mcp-interfaces.md}}
+  </building_mcp_interfaces>
+
   <media_cdn>
   {{compiled/media-cdn.md}}
   </media_cdn>
@@ -3576,6 +3580,13 @@ var MODEL_SURFACES = {
     modelType: "text",
     userPickable: true
   },
+  copyEditor: {
+    default: "claude-4-6-sonnet",
+    label: "Copy Agent",
+    description: "Tightens prose and copy across your app and its launch materials so it reads sharp and human, never machine-made.",
+    modelType: "text",
+    userPickable: true
+  },
   imageGeneration: {
     default: "seedream-4.5",
     label: "Image Generation",
@@ -4541,28 +4552,12 @@ async function execute7(input, onLog, context) {
   });
 }
 
-// src/subagents/designExpert/tools/index.ts
-var tools = {
-  searchGoogle: searchGoogle_exports,
-  scrapeWebUrl: scrapeWebUrl_exports,
-  analyzeDesign: analyzeDesign_exports,
-  analyzeImage: analyzeImage_exports,
-  screenshot: screenshot_exports,
-  generateImages: generateImages_exports,
-  editImages: editImages_exports
-};
-var DESIGN_EXPERT_TOOLS = [
-  ...COMMON_READ_TOOLS,
-  ...Object.values(tools).map((t) => t.definition)
-];
-async function executeDesignExpertTool(name, input, context, toolCallId, onLog) {
-  const tool = tools[name];
-  if (!tool) {
-    return `Error: unknown tool "${name}"`;
-  }
-  const childContext = context && toolCallId ? deriveContext(context, toolCallId) : context;
-  return tool.execute(input, onLog, childContext);
-}
+// src/subagents/designExpert/tools/polishCopy.ts
+var polishCopy_exports = {};
+__export(polishCopy_exports, {
+  definition: () => definition8,
+  execute: () => execute8
+});
 
 // src/subagents/common/context.ts
 import fs17 from "fs";
@@ -4693,7 +4688,7 @@ This is a capable, stable platform used in production by 100k+ users. Build with
 - Full-stack web apps \u2014 social platforms, membership sites, marketplaces, booking systems, community hubs \u2014 multi-user apps with auth, data, UI
 - Automations with no UI \u2014 cron jobs, webhook handlers, email processors, data sync pipelines
 - Marketing & launch pages \u2014 landing pages, waitlist pages with referral mechanics, product sites with scroll animations
-- Bots \u2014 Discord slash-command bots, Telegram bots, MCP tool servers for AI assistants
+- Agent tools \u2014 MCP tool servers for AI assistants
 - Creative/interactive projects \u2014 browser games with p5.js or Three.js, interactive visualizations, generative art, portfolio sites
 - API services \u2014 backend logic exposed as REST endpoints
 - Simple static sites \u2014 no backend needed, just a web interface with a build step
@@ -4708,8 +4703,6 @@ Each interface type invokes the same backend methods. Methods don't know which i
 - API \u2014 auto-generated REST endpoints for every method
 - Cron \u2014 scheduled jobs on a configurable interval
 - Webhook \u2014 HTTP endpoints that trigger methods
-- Discord \u2014 slash-command bots
-- Telegram \u2014 message-handling bots
 - Email \u2014 inbound email processing
 - MCP \u2014 tool servers for AI assistants
 - Agent \u2014 conversational LLM interface with tool access to backend methods
@@ -4734,6 +4727,103 @@ The first-party SDK (@mindstudio-ai/agent) provides access to 200+ AI models (Op
 </platform_brief>`;
 }
 
+// src/subagents/copyEditor/tools.ts
+var COPY_EDITOR_TOOLS = [...COMMON_READ_TOOLS];
+
+// src/subagents/copyEditor/index.ts
+var BASE_PROMPT2 = readAsset("subagents/copyEditor", "prompt.md");
+var copyEditorTool = {
+  clearable: false,
+  definition: {
+    name: "copyEditor",
+    description: "Hand it user-facing copy and it hands back a sharper version \u2014 better structured for its audience and free of the overused words, telltale constructions, and rhythms that make text read as AI-generated. Think of it as a design expert for words: it elevates how the copy communicates and strips the AI fingerprints, but it never invents facts or claims you didn't give it. Use it on anything users will read: in-app strings, empty states, errors, the Build Overview, deck copy, launch posts, Slack announcements. Readonly.",
+    inputSchema: {
+      type: "object",
+      properties: {
+        task: {
+          type: "string",
+          description: "The copy to polish, plus what it's for \u2014 the medium, the audience, any brand voice. Paste the text verbatim."
+        }
+      },
+      required: ["task"]
+    }
+  },
+  async execute(input, context) {
+    if (!context) {
+      return "Error: copy editor requires execution context";
+    }
+    const specIndex = loadSpecIndex();
+    const parts = [BASE_PROMPT2];
+    parts.push("<!-- cache_breakpoint -->");
+    if (specIndex) {
+      parts.push(specIndex);
+    }
+    const system = parts.join("\n\n");
+    const result = await runSubAgent({
+      system,
+      task: input.task,
+      tools: COPY_EDITOR_TOOLS,
+      externalTools: /* @__PURE__ */ new Set(),
+      executeTool: (name, toolInput) => executeTool(name, toolInput, context),
+      apiConfig: context.apiConfig,
+      model: resolveModel("copyEditor", context.models, context.model),
+      subAgentId: "copyEditor",
+      signal: context.signal,
+      parentToolId: context.toolCallId,
+      requestId: context.requestId,
+      onEvent: context.onEvent,
+      resolveExternalTool: context.resolveExternalTool,
+      toolRegistry: context.toolRegistry
+    });
+    context.subAgentMessages?.set(context.toolCallId, result.messages);
+    return result.text;
+  }
+};
+
+// src/subagents/designExpert/tools/polishCopy.ts
+var definition8 = {
+  clearable: false,
+  name: "polishCopy",
+  description: "Hand off any user-facing copy you've written \u2014 headlines, captions, labels, body text \u2014 and get back a sharper version: better built for its audience and free of the fingerprints that make writing read as AI. It elevates how the copy communicates without inventing facts or claims you didn't give it. Give it the text plus what it's for (where it appears, the audience).",
+  inputSchema: {
+    type: "object",
+    properties: {
+      task: {
+        type: "string",
+        description: "The copy to polish, plus what it's for \u2014 where it appears, the audience, any brand voice."
+      }
+    },
+    required: ["task"]
+  }
+};
+async function execute8(input, _onLog, context) {
+  return copyEditorTool.execute(input, context);
+}
+
+// src/subagents/designExpert/tools/index.ts
+var tools = {
+  searchGoogle: searchGoogle_exports,
+  scrapeWebUrl: scrapeWebUrl_exports,
+  analyzeDesign: analyzeDesign_exports,
+  analyzeImage: analyzeImage_exports,
+  screenshot: screenshot_exports,
+  generateImages: generateImages_exports,
+  editImages: editImages_exports,
+  polishCopy: polishCopy_exports
+};
+var DESIGN_EXPERT_TOOLS = [
+  ...COMMON_READ_TOOLS,
+  ...Object.values(tools).map((t) => t.definition)
+];
+async function executeDesignExpertTool(name, input, context, toolCallId, onLog) {
+  const tool = tools[name];
+  if (!tool) {
+    return `Error: unknown tool "${name}"`;
+  }
+  const childContext = context && toolCallId ? deriveContext(context, toolCallId) : context;
+  return tool.execute(input, onLog, childContext);
+}
+
 // src/subagents/designExpert/data/sampleCache.ts
 import fs18 from "fs";
 var SAMPLE_FILE = ".remy-design-sample.json";
@@ -5173,11 +5263,11 @@ Respond only with the complete HTML file and absolutely no other text. Your resp
 }
 
 // src/subagents/productVision/prompt.ts
-var BASE_PROMPT2 = readAsset("subagents/productVision", "prompt.md");
+var BASE_PROMPT3 = readAsset("subagents/productVision", "prompt.md");
 function getProductVisionPrompt() {
   const specIndex = loadSpecIndex();
   const roadmapIndex = loadRoadmapIndex();
-  const parts = [BASE_PROMPT2, loadPlatformBrief()];
+  const parts = [BASE_PROMPT3, loadPlatformBrief()];
   parts.push("<!-- cache_breakpoint -->");
   if (specIndex) {
     parts.push(specIndex);
@@ -5301,7 +5391,7 @@ var SANITY_CHECK_TOOLS = [
 ];
 
 // src/subagents/codeSanityCheck/index.ts
-var BASE_PROMPT3 = readAsset("subagents/codeSanityCheck", "prompt.md");
+var BASE_PROMPT4 = readAsset("subagents/codeSanityCheck", "prompt.md");
 var codeSanityCheckTool = {
   clearable: false,
   definition: {
@@ -5323,7 +5413,7 @@ var codeSanityCheckTool = {
       return "Error: code sanity check requires execution context";
     }
     const specIndex = loadSpecIndex();
-    const parts = [BASE_PROMPT3, loadPlatformBrief()];
+    const parts = [BASE_PROMPT4, loadPlatformBrief()];
     parts.push("<!-- cache_breakpoint -->");
     if (specIndex) {
       parts.push(specIndex);
@@ -5399,7 +5489,7 @@ var DESIGN_BRIEF = `We are building the Build Overview for this app \u2014 the h
 Take the plain-language copy in <overview_copy> and lay it out and skin it into a single, beautiful, self-contained HTML document in the app's own brand. If <current_overview> is non-empty, use it as your starting point and preserve its established skin, updating only what the copy changed.
 
 ### The single hard rule
-Preserve every fact in <overview_copy> exactly \u2014 every number, name, label, and claim. Do not add, drop, soften, reword, or invent any fact. You own layout, typography, and visual design only; the substance and the words are fixed. A single wrong number breaks this document's entire purpose.
+The copy in <overview_copy> is final \u2014 it was authored and edited before it reached you. Treat it as locked content to typeset, not a draft to improve. Reproduce the words exactly: do not rewrite, rephrase, shorten, expand, reorder, or "polish" them, and do not run them through any copy tool. This is the opposite of your usual role \u2014 here you own layout, typography, and visual design only, and the words (every number, name, label, claim, and sentence) are fixed. A single changed word or wrong number breaks this document's purpose.
 
 ### What it is (and is not)
 - A typeset reference dossier: composed, dense, a little cool \u2014 substantial at a glance, then readable. Density communicates substance; sparse and airy reads as "not much here."
@@ -5438,13 +5528,13 @@ var buildOverviewTool = {
   clearable: false,
   definition: {
     name: "writeBuildOverview",
-    description: "Generate or refresh the Build Overview \u2014 the project's home page in the Spec tab: a single-page, plain-language reference of everything the app actually contains, including the parts the user can't see (data stores, backend operations, access and roles, background jobs, seeded scenarios, the design system). You author the full copy: read the manifest and spec and state, plainly and exactly, what genuinely exists \u2014 real names and accurate counts \u2014 in calm, declarative, present-tense outcome language, with no persuasion or hype. Describe only what exists. Pass the complete copy as `content`; the design expert lays it out and skins it to the app's brand without altering any of your facts. Generate it at the end of a build and refresh it after meaningful work.",
+    description: "Generate or refresh the Build Overview \u2014 the project's home page in the Spec tab: a single-page, plain-language reference of everything the app actually contains, including the parts the user can't see (data stores, backend operations, access and roles, background jobs, seeded scenarios, the design system). You author the full copy: read the manifest and spec and state, plainly and exactly, what genuinely exists \u2014 real names and accurate counts \u2014 in calm, declarative, present-tense outcome language, with no persuasion or hype. Describe only what exists. Pass the complete copy as `content`; the design expert lays it out and skins it to the app's brand using your copy verbatim \u2014 it typesets your words, it does not rewrite them, so polish the copy before you pass it. Generate it at the end of a build and refresh it after meaningful work.",
     inputSchema: {
       type: "object",
       properties: {
         content: {
           type: "string",
-          description: "The full Build Overview copy you authored: everything the app contains, in plain present-tense outcome language, with real names and exact counts. The design expert lays this out and skins it to the brand without changing any fact."
+          description: "The full Build Overview copy you authored: everything the app contains, in plain present-tense outcome language, with real names and exact counts. The design expert lays this out and skins it to the brand verbatim \u2014 it styles your words, it does not rewrite them \u2014 so this should be the final copy."
         }
       },
       required: ["content"]
@@ -5495,6 +5585,7 @@ var ALL_TOOLS = [
   designExpertTool,
   productVisionTool,
   codeSanityCheckTool,
+  copyEditorTool,
   buildOverviewTool,
   compactConversationTool,
   // Post-onboarding
@@ -5531,6 +5622,7 @@ var SUBAGENT_TOOL_NAMES = /* @__PURE__ */ new Set([
   "visualDesignExpert",
   "productVision",
   "codeSanityCheck",
+  "copyEditor",
   "runAutomatedBrowserTest",
   "askMindStudioSdk"
 ]);

package/dist/index.js

@@ -1775,7 +1775,7 @@ var init_compaction = __esm({
     "use strict";
     init_api();
     init_assets();
-    init_tools6();
+    init_tools7();
     init_logger();
     init_usageLedger();
     log2 = createLogger("compaction");
@@ -1967,6 +1967,10 @@ Current date: ${now}
   {{compiled/agent-interfaces.md}}
   </building_agent_interfaces>
 
+  <building_mcp_interfaces>
+  {{compiled/mcp-interfaces.md}}
+  </building_mcp_interfaces>
+
   <media_cdn>
   {{compiled/media-cdn.md}}
   </media_cdn>
@@ -2102,6 +2106,13 @@ var init_surfaces = __esm({
         modelType: "text",
         userPickable: true
       },
+      copyEditor: {
+        default: "claude-4-6-sonnet",
+        label: "Copy Agent",
+        description: "Tightens prose and copy across your app and its launch materials so it reads sharp and human, never machine-made.",
+        modelType: "text",
+        userPickable: true
+      },
       imageGeneration: {
         default: "seedream-4.5",
         label: "Image Generation",
@@ -2201,7 +2212,7 @@ var init_trigger = __esm({
     "use strict";
     init_compaction();
     init_prompt();
-    init_tools6();
+    init_tools7();
     init_logger();
     init_surfaces();
     log3 = createLogger("compaction:trigger");
@@ -5307,44 +5318,6 @@ var init_editImages = __esm({
   }
 });
 
-// src/subagents/designExpert/tools/index.ts
-async function executeDesignExpertTool(name, input, context, toolCallId, onLog) {
-  const tool = tools[name];
-  if (!tool) {
-    return `Error: unknown tool "${name}"`;
-  }
-  const childContext = context && toolCallId ? deriveContext(context, toolCallId) : context;
-  return tool.execute(input, onLog, childContext);
-}
-var tools, DESIGN_EXPERT_TOOLS;
-var init_tools3 = __esm({
-  "src/subagents/designExpert/tools/index.ts"() {
-    "use strict";
-    init_tools6();
-    init_tools2();
-    init_searchGoogle2();
-    init_scrapeWebUrl();
-    init_analyzeDesign();
-    init_analyzeImage2();
-    init_screenshot3();
-    init_generateImages();
-    init_editImages();
-    tools = {
-      searchGoogle: searchGoogle_exports,
-      scrapeWebUrl: scrapeWebUrl_exports,
-      analyzeDesign: analyzeDesign_exports,
-      analyzeImage: analyzeImage_exports,
-      screenshot: screenshot_exports,
-      generateImages: generateImages_exports,
-      editImages: editImages_exports
-    };
-    DESIGN_EXPERT_TOOLS = [
-      ...COMMON_READ_TOOLS,
-      ...Object.values(tools).map((t) => t.definition)
-    ];
-  }
-});
-
 // src/subagents/common/context.ts
 import fs16 from "fs";
 import path7 from "path";
@@ -5474,7 +5447,7 @@ This is a capable, stable platform used in production by 100k+ users. Build with
 - Full-stack web apps \u2014 social platforms, membership sites, marketplaces, booking systems, community hubs \u2014 multi-user apps with auth, data, UI
 - Automations with no UI \u2014 cron jobs, webhook handlers, email processors, data sync pipelines
 - Marketing & launch pages \u2014 landing pages, waitlist pages with referral mechanics, product sites with scroll animations
-- Bots \u2014 Discord slash-command bots, Telegram bots, MCP tool servers for AI assistants
+- Agent tools \u2014 MCP tool servers for AI assistants
 - Creative/interactive projects \u2014 browser games with p5.js or Three.js, interactive visualizations, generative art, portfolio sites
 - API services \u2014 backend logic exposed as REST endpoints
 - Simple static sites \u2014 no backend needed, just a web interface with a build step
@@ -5489,8 +5462,6 @@ Each interface type invokes the same backend methods. Methods don't know which i
 - API \u2014 auto-generated REST endpoints for every method
 - Cron \u2014 scheduled jobs on a configurable interval
 - Webhook \u2014 HTTP endpoints that trigger methods
-- Discord \u2014 slash-command bots
-- Telegram \u2014 message-handling bots
 - Email \u2014 inbound email processing
 - MCP \u2014 tool servers for AI assistants
 - Agent \u2014 conversational LLM interface with tool access to backend methods
@@ -5520,6 +5491,150 @@ var init_context = __esm({
   }
 });
 
+// src/subagents/copyEditor/tools.ts
+var COPY_EDITOR_TOOLS;
+var init_tools3 = __esm({
+  "src/subagents/copyEditor/tools.ts"() {
+    "use strict";
+    init_tools2();
+    COPY_EDITOR_TOOLS = [...COMMON_READ_TOOLS];
+  }
+});
+
+// src/subagents/copyEditor/index.ts
+var BASE_PROMPT2, copyEditorTool;
+var init_copyEditor = __esm({
+  "src/subagents/copyEditor/index.ts"() {
+    "use strict";
+    init_assets();
+    init_runner();
+    init_context();
+    init_tools7();
+    init_tools3();
+    init_surfaces();
+    BASE_PROMPT2 = readAsset("subagents/copyEditor", "prompt.md");
+    copyEditorTool = {
+      clearable: false,
+      definition: {
+        name: "copyEditor",
+        description: "Hand it user-facing copy and it hands back a sharper version \u2014 better structured for its audience and free of the overused words, telltale constructions, and rhythms that make text read as AI-generated. Think of it as a design expert for words: it elevates how the copy communicates and strips the AI fingerprints, but it never invents facts or claims you didn't give it. Use it on anything users will read: in-app strings, empty states, errors, the Build Overview, deck copy, launch posts, Slack announcements. Readonly.",
+        inputSchema: {
+          type: "object",
+          properties: {
+            task: {
+              type: "string",
+              description: "The copy to polish, plus what it's for \u2014 the medium, the audience, any brand voice. Paste the text verbatim."
+            }
+          },
+          required: ["task"]
+        }
+      },
+      async execute(input, context) {
+        if (!context) {
+          return "Error: copy editor requires execution context";
+        }
+        const specIndex = loadSpecIndex();
+        const parts = [BASE_PROMPT2];
+        parts.push("<!-- cache_breakpoint -->");
+        if (specIndex) {
+          parts.push(specIndex);
+        }
+        const system = parts.join("\n\n");
+        const result = await runSubAgent({
+          system,
+          task: input.task,
+          tools: COPY_EDITOR_TOOLS,
+          externalTools: /* @__PURE__ */ new Set(),
+          executeTool: (name, toolInput) => executeTool(name, toolInput, context),
+          apiConfig: context.apiConfig,
+          model: resolveModel("copyEditor", context.models, context.model),
+          subAgentId: "copyEditor",
+          signal: context.signal,
+          parentToolId: context.toolCallId,
+          requestId: context.requestId,
+          onEvent: context.onEvent,
+          resolveExternalTool: context.resolveExternalTool,
+          toolRegistry: context.toolRegistry
+        });
+        context.subAgentMessages?.set(context.toolCallId, result.messages);
+        return result.text;
+      }
+    };
+  }
+});
+
+// src/subagents/designExpert/tools/polishCopy.ts
+var polishCopy_exports = {};
+__export(polishCopy_exports, {
+  definition: () => definition8,
+  execute: () => execute8
+});
+async function execute8(input, _onLog, context) {
+  return copyEditorTool.execute(input, context);
+}
+var definition8;
+var init_polishCopy = __esm({
+  "src/subagents/designExpert/tools/polishCopy.ts"() {
+    "use strict";
+    init_copyEditor();
+    definition8 = {
+      clearable: false,
+      name: "polishCopy",
+      description: "Hand off any user-facing copy you've written \u2014 headlines, captions, labels, body text \u2014 and get back a sharper version: better built for its audience and free of the fingerprints that make writing read as AI. It elevates how the copy communicates without inventing facts or claims you didn't give it. Give it the text plus what it's for (where it appears, the audience).",
+      inputSchema: {
+        type: "object",
+        properties: {
+          task: {
+            type: "string",
+            description: "The copy to polish, plus what it's for \u2014 where it appears, the audience, any brand voice."
+          }
+        },
+        required: ["task"]
+      }
+    };
+  }
+});
+
+// src/subagents/designExpert/tools/index.ts
+async function executeDesignExpertTool(name, input, context, toolCallId, onLog) {
+  const tool = tools[name];
+  if (!tool) {
+    return `Error: unknown tool "${name}"`;
+  }
+  const childContext = context && toolCallId ? deriveContext(context, toolCallId) : context;
+  return tool.execute(input, onLog, childContext);
+}
+var tools, DESIGN_EXPERT_TOOLS;
+var init_tools4 = __esm({
+  "src/subagents/designExpert/tools/index.ts"() {
+    "use strict";
+    init_tools7();
+    init_tools2();
+    init_searchGoogle2();
+    init_scrapeWebUrl();
+    init_analyzeDesign();
+    init_analyzeImage2();
+    init_screenshot3();
+    init_generateImages();
+    init_editImages();
+    init_polishCopy();
+    tools = {
+      searchGoogle: searchGoogle_exports,
+      scrapeWebUrl: scrapeWebUrl_exports,
+      analyzeDesign: analyzeDesign_exports,
+      analyzeImage: analyzeImage_exports,
+      screenshot: screenshot_exports,
+      generateImages: generateImages_exports,
+      editImages: editImages_exports,
+      polishCopy: polishCopy_exports
+    };
+    DESIGN_EXPERT_TOOLS = [
+      ...COMMON_READ_TOOLS,
+      ...Object.values(tools).map((t) => t.definition)
+    ];
+  }
+});
+
 // src/subagents/designExpert/data/sampleCache.ts
 import fs17 from "fs";
 function generateIndices(poolSize, sampleSize) {
@@ -5799,9 +5914,9 @@ var DESCRIPTION, designExpertTool;
 var init_designExpert = __esm({
   "src/subagents/designExpert/index.ts"() {
     "use strict";
-    init_tools6();
+    init_tools7();
     init_runner();
-    init_tools3();
+    init_tools4();
     init_tools2();
     init_prompt3();
     init_history();
@@ -5881,7 +5996,7 @@ Visual design expert. Describe the situation and what you need \u2014 the agent
 
 // src/subagents/productVision/tools.ts
 var VISION_TOOLS;
-var init_tools4 = __esm({
+var init_tools5 = __esm({
   "src/subagents/productVision/tools.ts"() {
     "use strict";
     init_tools2();
@@ -6039,7 +6154,7 @@ var init_executor = __esm({
 function getProductVisionPrompt() {
   const specIndex = loadSpecIndex();
   const roadmapIndex = loadRoadmapIndex();
-  const parts = [BASE_PROMPT2, loadPlatformBrief()];
+  const parts = [BASE_PROMPT3, loadPlatformBrief()];
   parts.push("<!-- cache_breakpoint -->");
   if (specIndex) {
     parts.push(specIndex);
@@ -6049,14 +6164,14 @@ function getProductVisionPrompt() {
   }
   return parts.join("\n\n");
 }
-var BASE_PROMPT2;
+var BASE_PROMPT3;
 var init_prompt4 = __esm({
   "src/subagents/productVision/prompt.ts"() {
     "use strict";
     init_assets();
     init_executor();
     init_context();
-    BASE_PROMPT2 = readAsset("subagents/productVision", "prompt.md");
+    BASE_PROMPT3 = readAsset("subagents/productVision", "prompt.md");
   }
 });
 
@@ -6065,9 +6180,9 @@ var productVisionTool;
 var init_productVision = __esm({
   "src/subagents/productVision/index.ts"() {
     "use strict";
-    init_tools6();
+    init_tools7();
     init_runner();
-    init_tools4();
+    init_tools5();
     init_tools2();
     init_executor();
     init_prompt4();
@@ -6139,7 +6254,7 @@ var init_productVision = __esm({
 
 // src/subagents/codeSanityCheck/tools.ts
 var SANITY_CHECK_TOOLS;
-var init_tools5 = __esm({
+var init_tools6 = __esm({
   "src/subagents/codeSanityCheck/tools.ts"() {
     "use strict";
     init_tools2();
@@ -6194,17 +6309,17 @@ var init_tools5 = __esm({
 });
 
 // src/subagents/codeSanityCheck/index.ts
-var BASE_PROMPT3, codeSanityCheckTool;
+var BASE_PROMPT4, codeSanityCheckTool;
 var init_codeSanityCheck = __esm({
   "src/subagents/codeSanityCheck/index.ts"() {
     "use strict";
     init_assets();
     init_runner();
     init_context();
+    init_tools7();
     init_tools6();
-    init_tools5();
     init_surfaces();
-    BASE_PROMPT3 = readAsset("subagents/codeSanityCheck", "prompt.md");
+    BASE_PROMPT4 = readAsset("subagents/codeSanityCheck", "prompt.md");
     codeSanityCheckTool = {
       clearable: false,
       definition: {
@@ -6226,7 +6341,7 @@ var init_codeSanityCheck = __esm({
           return "Error: code sanity check requires execution context";
         }
         const specIndex = loadSpecIndex();
-        const parts = [BASE_PROMPT3, loadPlatformBrief()];
+        const parts = [BASE_PROMPT4, loadPlatformBrief()];
         parts.push("<!-- cache_breakpoint -->");
         if (specIndex) {
           parts.push(specIndex);
@@ -6316,7 +6431,7 @@ var init_writeBuildOverview = __esm({
 Take the plain-language copy in <overview_copy> and lay it out and skin it into a single, beautiful, self-contained HTML document in the app's own brand. If <current_overview> is non-empty, use it as your starting point and preserve its established skin, updating only what the copy changed.
 
 ### The single hard rule
-Preserve every fact in <overview_copy> exactly \u2014 every number, name, label, and claim. Do not add, drop, soften, reword, or invent any fact. You own layout, typography, and visual design only; the substance and the words are fixed. A single wrong number breaks this document's entire purpose.
+The copy in <overview_copy> is final \u2014 it was authored and edited before it reached you. Treat it as locked content to typeset, not a draft to improve. Reproduce the words exactly: do not rewrite, rephrase, shorten, expand, reorder, or "polish" them, and do not run them through any copy tool. This is the opposite of your usual role \u2014 here you own layout, typography, and visual design only, and the words (every number, name, label, claim, and sentence) are fixed. A single changed word or wrong number breaks this document's purpose.
 
 ### What it is (and is not)
 - A typeset reference dossier: composed, dense, a little cool \u2014 substantial at a glance, then readable. Density communicates substance; sparse and airy reads as "not much here."
@@ -6355,13 +6470,13 @@ Respond only with the complete HTML file and absolutely no other text. Your resp
       clearable: false,
       definition: {
         name: "writeBuildOverview",
-        description: "Generate or refresh the Build Overview \u2014 the project's home page in the Spec tab: a single-page, plain-language reference of everything the app actually contains, including the parts the user can't see (data stores, backend operations, access and roles, background jobs, seeded scenarios, the design system). You author the full copy: read the manifest and spec and state, plainly and exactly, what genuinely exists \u2014 real names and accurate counts \u2014 in calm, declarative, present-tense outcome language, with no persuasion or hype. Describe only what exists. Pass the complete copy as `content`; the design expert lays it out and skins it to the app's brand without altering any of your facts. Generate it at the end of a build and refresh it after meaningful work.",
+        description: "Generate or refresh the Build Overview \u2014 the project's home page in the Spec tab: a single-page, plain-language reference of everything the app actually contains, including the parts the user can't see (data stores, backend operations, access and roles, background jobs, seeded scenarios, the design system). You author the full copy: read the manifest and spec and state, plainly and exactly, what genuinely exists \u2014 real names and accurate counts \u2014 in calm, declarative, present-tense outcome language, with no persuasion or hype. Describe only what exists. Pass the complete copy as `content`; the design expert lays it out and skins it to the app's brand using your copy verbatim \u2014 it typesets your words, it does not rewrite them, so polish the copy before you pass it. Generate it at the end of a build and refresh it after meaningful work.",
         inputSchema: {
           type: "object",
           properties: {
             content: {
               type: "string",
-              description: "The full Build Overview copy you authored: everything the app contains, in plain present-tense outcome language, with real names and exact counts. The design expert lays this out and skins it to the brand without changing any fact."
+              description: "The full Build Overview copy you authored: everything the app contains, in plain present-tense outcome language, with real names and exact counts. The design expert lays this out and skins it to the brand verbatim \u2014 it styles your words, it does not rewrite them \u2014 so this should be the final copy."
             }
           },
           required: ["content"]
@@ -6416,7 +6531,7 @@ function executeTool(name, input, context) {
   return tool.execute(input, context);
 }
 var ALL_TOOLS, CLEARABLE_TOOLS, SUBAGENT_TOOL_NAMES;
-var init_tools6 = __esm({
+var init_tools7 = __esm({
   "src/tools/index.ts"() {
     "use strict";
     init_readSpec();
@@ -6451,6 +6566,7 @@ var init_tools6 = __esm({
     init_designExpert();
     init_productVision();
     init_codeSanityCheck();
+    init_copyEditor();
     init_scrapeWebUrl2();
     init_writeBuildOverview();
     ALL_TOOLS = [
@@ -6465,6 +6581,7 @@ var init_tools6 = __esm({
       designExpertTool,
       productVisionTool,
       codeSanityCheckTool,
+      copyEditorTool,
       buildOverviewTool,
       compactConversationTool,
       // Post-onboarding
@@ -6501,6 +6618,7 @@ var init_tools6 = __esm({
       "visualDesignExpert",
       "productVision",
       "codeSanityCheck",
+      "copyEditor",
       "runAutomatedBrowserTest",
       "askMindStudioSdk"
     ]);
@@ -7700,7 +7818,7 @@ var init_agent = __esm({
   "src/agent.ts"() {
     "use strict";
     init_api();
-    init_tools6();
+    init_tools7();
     init_session();
     init_logger();
     init_usageLedger();
@@ -7708,7 +7826,7 @@ var init_agent = __esm({
     init_statusWatcher();
     init_errors();
     init_cleanMessages();
-    init_tools6();
+    init_tools7();
     init_sentinel();
     init_trigger2();
     init_surfaces();

package/dist/prompt/.notes.md

@@ -145,6 +145,7 @@ The intro framing ("you have a lot on your plate") gives the model permission to
 | `productVision` | Roadmap ownership & product strategy | writeRoadmapItem, updateRoadmapItem, deleteRoadmapItem | Spec files + current roadmap |
 | `sdkConsultant` | MindStudio SDK architecture | None (shells out to `mindstudio ask` CLI) | None (external agent) |
 | `codeSanityCheck` | Pre-build review | readFile, grep, glob, searchGoogle, fetchUrl, askMindStudioSdk, bash (readonly) | Spec files |
+| `copyEditor` | Copy-editing / de-AI-ing prose | readFile, listDir, grep, glob (readonly) | Spec files |
 | `browserAutomation` | Interactive UI testing | browserCommand, screenshotFullPage, setupBrowser | None (interacts with live preview) |
 
 ### Shared infrastructure
@@ -160,6 +161,10 @@ The product vision agent uses third-person construction ("The role of the assist
 
 The sanity check agent is deliberately low-energy. Its prompt says "lgtm" is a complete response and to let most things slide. This prevents it from becoming a bottleneck or scope-creeper. The only things it flags: outdated packages (via web search), missed SDK managed actions, schema decisions that paint into corners, and file organization that's gotten unwieldy. Tech debt is explicitly called out as normal and sometimes useful in fast-moving products.
 
+### Copy editor: polish, never author
+
+The copy editor is the "design expert for words" — a cheap, readonly subagent that rewrites user-facing copy (in-app strings, the Build Overview, deck copy, launch posts, Slack notes) to read human instead of AI-generated, and — the bigger half — to communicate better. Like the design expert (which removes AI-design tells *and* elevates the design), it has two jobs: elevate how the copy lands for its audience (structure, framing, what to lead with, what to cut) and strip the AI tells. The hard guardrail mirrors the design expert's: it changes *how* something is said freely but never invents the substance (no new facts/claims/features) — elevate the form, don't fabricate the content. It lives off the main loop on purpose: asking Remy to also "write differently" mid-task is the wrong cognitive load, and isolation contains the one thing we'd never put in the shared prompt — a prescriptive denylist of AI tells (overused words, tic constructions, metronomic rhythm, the em-dash perception tell). The blast radius of that denylist is bounded to this agent. The design expert can also delegate to it for copy inside layouts.
+
 ### Design expert: runtime-sampled data
 
 The design expert's prompt is dynamically assembled per invocation. It samples 15 random fonts + 5 pairings from the Fontshare catalog and 5 random pre-analyzed design inspiration screenshots from Godly. This prevents the model from developing favorites and ensures it considers different options each time.

package/dist/prompt/compiled/auth.md

@@ -228,7 +228,7 @@ Returns an array of user IDs with the specified role.
 
 ### System Role (Platform Triggers)
 
-When the platform invokes a method on behalf of the app (cron, webhook, email, Discord, Telegram), the execution runs as a system user with `auth.roles: ['system']`. Use `auth.requireRole('system')` to restrict methods to platform triggers only:
+When the platform invokes a method on behalf of the app (cron, webhook, email), the execution runs as a system user with `auth.roles: ['system']`. Use `auth.requireRole('system')` to restrict methods to platform triggers only:
 
 ```typescript
 export async function regenerateCache(input: {}) {

package/dist/prompt/compiled/dev-and-deploy.md

@@ -35,7 +35,7 @@ The platform builds and deploys automatically:
 
 1. **Parse manifest** — read `mindstudio.json` from the commit
 2. **Compile methods** — esbuild bundles each method into a single JS file
-3. **Compile interfaces** — build web SPA (`npm install && npm run build`), generate configs for API/Discord/Telegram/cron/etc.
+3. **Compile interfaces** — build web SPA (`npm install && npm run build`), generate configs for API/cron/webhook/etc.
 4. **Parse table schemas** — TypeScript AST to column definitions, diff against live database
 5. **Compute effects** — roles diff, cron diff, bot command diffs, table DDL
 6. **Apply** — create/update roles, sync bot commands, apply DDL to a staging database copy, swap the live pointer

package/dist/prompt/compiled/interfaces.md

@@ -2,7 +2,7 @@
 
 Interfaces are projections of the backend contract into different modalities. The same methods power all of them. An interface can be as complex and polished as you want, but it's always safe — the backend contract is where anything real happens. The interface can't break business logic or corrupt data.
 
-All external service connections (Discord bot tokens, Telegram bot setup, webhook secrets, email addresses) are configured at the project level by the user through the Remy platform. The agent's job is to write the config files and the methods that handle the requests — not to manage API keys, OAuth flows, or service registration.
+All external service connections (webhook secrets, email addresses) are configured at the project level by the user through the Remy platform. The agent's job is to write the config files and the methods that handle the requests — not to manage API keys, OAuth flows, or service registration.
 
 ## Web Interface
 
@@ -243,53 +243,7 @@ Routes are mounted at `/_/api{path}` (e.g. `DELETE /_/api/vendors/abc123`).
 
 ## Platform-Triggered Interfaces
 
-Discord, Telegram, Cron, Webhook, and Email interfaces are invoked by the platform, not by a user session. Methods called through these interfaces run with `auth.roles: ['system']`. Use `auth.requireRole('system')` to restrict a method to platform triggers only.
-
-## Discord Bot
-
-Slash commands that invoke methods.
-
-### Config (`interface.json`)
-
-```json
-{
-  "discord": {
-    "commands": [
-      {
-        "name": "submit-vendor",
-        "description": "Request a new vendor",
-        "method": "submit-vendor-request"
-      }
-    ],
-    "loadingMessage": "Processing your request..."
-  }
-}
-```
-
-Commands are synced to Discord on deploy.
-
-## Telegram Bot
-
-Bot commands and message handling.
-
-### Config (`interface.json`)
-
-```json
-{
-  "telegram": {
-    "commands": [
-      {
-        "command": "/submit",
-        "description": "Submit a vendor request",
-        "method": "submit-vendor-request"
-      }
-    ],
-    "defaultMethod": "handle-message"
-  }
-}
-```
-
-`defaultMethod` handles free-text messages that don't match a command.
+Cron, Webhook, and Email interfaces are invoked by the platform, not by a user session. Methods called through these interfaces run with `auth.roles: ['system']`. Use `auth.requireRole('system')` to restrict a method to platform triggers only.
 
 ## Cron
 
@@ -422,19 +376,156 @@ Methods invoked through this interface run with `auth.roles: ['system']` (see th
 
 ## MCP (Model Context Protocol)
 
-Expose methods as AI tools.
+Expose the app to *external* AI agents — Claude Desktop, Cursor, other people's agents, anything that speaks MCP. Unlike the agent interface (which *is* an agent — its own LLM, personality, and chat UI), MCP has no model of its own; it's the app projected as an MCP server for an outside AI to drive.
+
+It supports the full MCP surface:
+- **Tools** — methods the agent can call (rich descriptions + machine-readable annotations).
+- **Resources** — read-only app data the agent can pull into context, addressable by URI.
+- **Prompts** — reusable, parameterized prompt templates the server offers.
+- **Instructions** — server-level guidance shown to the calling agent (the toolset's "system prompt").
+
+The platform hosts the server, handles auth like the API interface (optional — keyed or anonymous), and derives every tool's input schema from the method contract. Because the consumer is an external agent with no knowledge of your app, **the descriptions are the product** — see "Building MCP Interfaces" for how to write them.
+
+### Spec: `src/interfaces/mcp.md`
+
+Frontmatter declares the server. The body's intro prose becomes the server `instructions`; `## Tools`, `## Resources`, and `## Prompts` sections declare the rest.
+
+```yaml
+---
+name: Vendor Management
+description: Tools and data for managing vendors and purchase orders.
+type: interface/mcp
+---
+```
+
+```markdown
+This server manages vendors and purchase orders. Read a vendor before updating it; submitted
+requests go through approval before they become active.
+
+## Tools
+
+### Submit a vendor request
+method: submit-vendor-request
+~~~
+Submit a new vendor for approval. Use when the caller wants to add a vendor.
+Do NOT use to modify an existing vendor — that's update-vendor.
+- name: the vendor's legal name
+- contactEmail: billing contact; required for approval routing
+Returns the created vendor's id and its initial "pending" status.
+~~~
+
+### List vendors
+method: list-vendors
+annotations: readOnly
+~~~
+List all vendors, newest first. Read-only.
+~~~
+
+## Resources
+
+- list-vendors → app://vendors — "Vendors" — all vendors (application/json)
+- get-vendor → app://vendors/{id} — "Vendor" — a single vendor by id (application/json)
+
+## Prompts
+
+### draft_vendor_email
+description: Draft an outreach email to a vendor.
+arguments: vendorId (required) — the vendor to contact
+~~~
+Write a warm outreach email to vendor {{vendorId}} introducing our procurement process.
+~~~
+```
+
+Don't hand-author input schemas — the platform derives them. For a resource template, `{param}` in the URI maps to the backing method's input.
+
+### Compiled Output: `dist/interfaces/mcp/`
+
+```
+dist/interfaces/mcp/
+├── interface.json      ← config the platform reads
+├── instructions.md     ← server-level guidance (returned in `initialize`)
+├── tools/
+│   ├── submitVendorRequest.md   ← rich description, one per tool
+│   └── listVendors.md
+└── prompts/
+    └── draftVendorEmail.md      ← prompt template body, one per prompt
+```
+
+Resources carry inline metadata only — no per-resource file.
 
 ### Config (`interface.json`)
 
 ```json
 {
   "mcp": {
-    "methods": ["submit-vendor-request", "list-vendors"]
+    "name": "Vendor Management",
+    "description": "Tools and data for managing vendors and purchase orders.",
+    "instructions": "instructions.md",
+    "tools": [
+      {
+        "method": "submit-vendor-request",
+        "name": "submit_vendor_request",
+        "title": "Submit Vendor Request",
+        "description": "tools/submitVendorRequest.md",
+        "annotations": { "readOnly": false, "destructive": false, "idempotent": false, "openWorld": false }
+      },
+      {
+        "method": "list-vendors",
+        "title": "List Vendors",
+        "description": "tools/listVendors.md",
+        "annotations": { "readOnly": true }
+      }
+    ],
+    "resources": [
+      { "method": "list-vendors", "uri": "app://vendors", "name": "Vendors", "description": "All vendors.", "mimeType": "application/json" },
+      { "method": "get-vendor", "uriTemplate": "app://vendors/{id}", "name": "Vendor", "description": "A single vendor by id.", "mimeType": "application/json" }
+    ],
+    "prompts": [
+      {
+        "name": "draft_vendor_email",
+        "title": "Draft vendor email",
+        "description": "Draft an outreach email to a vendor.",
+        "arguments": [ { "name": "vendorId", "description": "The vendor to contact", "required": true } ],
+        "template": "prompts/draftVendorEmail.md"
+      }
+    ]
   }
 }
 ```
 
-Each listed method becomes an MCP tool. Method names and descriptions from the manifest are used as tool names and descriptions.
+| Field | Description |
+|-------|-------------|
+| `name`, `description` | Server display name + registry metadata (not shown to the calling agent) |
+| `instructions` | Relative path to the server-level guidance returned in `initialize` |
+| `tools[].method` | Method `id` from the manifest (kebab-case) |
+| `tools[].name` | Tool name exposed to clients. Optional — defaults to the method `id`. Must match `[a-zA-Z0-9_-]` and be unique within the server |
+| `tools[].title` | Optional human-friendly display name |
+| `tools[].description` | Relative path to the tool's markdown description |
+| `tools[].annotations` | Optional client hints (auto-call vs. confirm): `readOnly`, `destructive`, `idempotent`, `openWorld` — map to MCP's `readOnlyHint` etc. |
+| `resources[].method` | The read method invoked when the resource is read |
+| `resources[].uri` / `uriTemplate` | A static URI, or a template whose `{param}` maps to the method's input |
+| `resources[].name`, `description`, `mimeType` | Resource metadata |
+| `prompts[].name`, `title`, `description` | Prompt identity + metadata |
+| `prompts[].arguments` | `[{ name, description?, required? }]` |
+| `prompts[].template` | Relative path to the template body (`{{arg}}` placeholders) |
+
+There is no `inputSchema` field — the platform derives each tool's schema from the method's input contract.
+
+### Platform Behavior
+
+- The platform hosts the MCP server and exposes it to external clients. Clients connect at `POST https://{app-host}/_/mcp`.
+- **Auth is optional**, identical to the API interface: a `Bearer` key resolves to a user with full RBAC; with no key, calls run anonymously (no user, no roles). The method is the boundary — gate sensitive tools with `auth.requireRole`/`requireUser`; a public (keyless) server exposes only the un-gated tools.
+- Input schemas are derived automatically from each method's input contract.
+- `tools/list` is static; access is enforced per-method at call time (a gated tool is listed but rejects an unauthorized call).
+- A resource read invokes the backing method (template `{param}`s come from the URI) and returns its output as the resource contents.
+- `prompts/get` fills the template with the provided arguments.
+- `instructions` is returned in the `initialize` response.
+
+### Manifest
+
+```json
+{ "type": "mcp", "path": "dist/interfaces/mcp/interface.json" }
+```
 
 ## Agent (Conversational Interface)
 
@@ -514,8 +605,6 @@ Each interface is declared in `mindstudio.json`:
     { "type": "web", "path": "dist/interfaces/web/web.json" },
     { "type": "api" },
     { "type": "cron", "path": "dist/interfaces/cron/interface.json" },
-    { "type": "discord", "path": "dist/interfaces/discord/interface.json" },
-    { "type": "telegram", "path": "dist/interfaces/telegram/interface.json" },
     { "type": "webhook", "path": "dist/interfaces/webhook/interface.json" },
     { "type": "email", "path": "dist/interfaces/email/interface.json" },
     { "type": "mcp", "path": "dist/interfaces/mcp/interface.json" },

package/dist/prompt/compiled/manifest.md

@@ -111,7 +111,7 @@
 
 | Field | Type | Required | Description |
 |-------|------|----------|-------------|
-| `type` | `string` | Yes | One of: `web`, `api`, `discord`, `telegram`, `cron`, `webhook`, `email`, `mcp`, `agent` |
+| `type` | `string` | Yes | One of: `web`, `api`, `cron`, `webhook`, `email`, `mcp`, `agent` |
 | `path` | `string` | No | Path to the interface config file |
 | `config` | `object` | No | Inline config (alternative to a file) |
 | `enabled` | `boolean` | No | Default `true`. Set `false` to skip during build. |

package/dist/prompt/compiled/mcp-interfaces.md

@@ -0,0 +1,34 @@
+# Building MCP Interfaces
+
+Guidance for exposing an app as an MCP server — a tool / resource / prompt surface for *external* AI agents (Claude Desktop, Cursor, anyone's agent). The contract (spec format, compiled output, `interface.json`) is in the Interfaces doc; this is how to author one well. Unlike the agent interface, there's no LLM, personality, or UI to design — the entire product is the descriptions and the shape of what you expose.
+
+## The descriptions are the product
+
+The calling agent is a stranger with no knowledge of your app. It decides what to invoke entirely from the names, descriptions, and annotations you ship. Follow the same principles as the agent interface's tool descriptions (see "Building Agent Interfaces" — when to use and when not, parameter guidance beyond the schema, what the tool returns) — but write them **self-contained**. An in-app agent tool can lean on the app's framing; an MCP tool can't, because the caller has no context. Spell out what an outsider wouldn't know.
+
+## Curate — not every method is a tool
+
+Expose what an outside agent would actually use. Skip internal helpers, admin-only methods, and batch operations. A focused set of well-described tools beats a large set of thin ones. Note role restrictions in the description — gated tools are listed but reject unauthorized calls at runtime, so set expectations rather than surfacing a raw error.
+
+## Annotations
+
+Annotations are machine-readable hints clients use to decide whether to auto-call a tool or ask the user first. Set them honestly:
+
+- `readOnly` — the tool only reads, never mutates. The highest-value hint: clients auto-call reads without prompting, so set it on every pure read.
+- `destructive` — the tool can delete or overwrite. Clients gate these behind confirmation.
+- `idempotent` — calling twice with the same arguments has the same effect as calling once.
+- `openWorld` — the tool reaches outside the app (external web/services) rather than operating only on app data.
+
+## Tools vs. resources
+
+A **tool** is an action the agent *invokes*; a **resource** is data the agent *reads into context*. A read-only method can be either — expose it as a tool if the agent will call it as a step, as a resource if it's reference data the agent should pull in, and as both when both fit.
+
+Resources are method-backed: a read invokes the method. Use a static `uri` for a fixed collection (`app://vendors`) and a `uriTemplate` when the read takes parameters (`app://vendors/{id}`, where `{id}` maps to the method's input). Keep URIs stable and human-legible.
+
+## Prompts
+
+Prompts are reusable, parameterized templates the server offers to clients — e.g. a "draft a vendor email" starter. Author the template body with `{{arg}}` placeholders and declare its arguments. Offer a prompt when there's a recurring task worth packaging; skip it if a tool already covers the need.
+
+## Server instructions
+
+The spec's intro prose becomes the server `instructions` — toolset-level guidance returned to the calling agent at connect time (its "system prompt"). Put *cross-cutting* guidance here: how the tools fit together, ordering or prerequisites ("read a vendor before updating it"), and norms that apply across the whole toolset. Keep per-tool specifics in the tool descriptions; instructions are for the toolset as a whole.

package/dist/prompt/compiled/methods.md

@@ -1,6 +1,6 @@
 # Methods
 
-A method is a named async function that runs on the platform. It's the universal unit of backend logic — every interface (web, API, Discord, cron, webhook) invokes methods. One file per method, one named export.
+A method is a named async function that runs on the platform. It's the universal unit of backend logic — every interface (web, API, cron, webhook) invokes methods. One file per method, one named export.
 
 ## Writing a Method
 

package/dist/prompt/compiled/platform.md

@@ -41,12 +41,14 @@ my-app/
         package.json
         src/
       api/api.json                       REST API config
-      discord/interface.json             Discord bot config
-      telegram/interface.json            Telegram bot config
       cron/interface.json                cron config
       webhook/interface.json             webhook config
       email/interface.json               email config
-      mcp/interface.json                 MCP config
+      mcp/                               MCP interface
+        interface.json                     MCP config
+        instructions.md                    server instructions
+        tools/                             tool descriptions (one .md per method)
+        prompts/                           prompt templates (one .md per prompt)
       agent/                             agent interface
         agent.json                         agent config
         system.md                          compiled system prompt
@@ -93,7 +95,7 @@ const { vendor } = await api.approveVendor({ vendorId: '...' });
 
 - **Managed databases.** SQLite with typed schemas. Push a schema change and the platform diffs, migrates, and promotes atomically.
 - **Built-in auth.** Opt-in via manifest. Developer builds login UI, platform handles verification codes (email/SMS), cookie sessions, and role enforcement. Backend methods use `auth.requireRole('admin')` for access control.
-- **Multiple interfaces, one codebase.** Web, API, Discord, Telegram, Cron, Webhook, Email, MCP — all invoke the same methods. Methods don't know which interface called them.
+- **Multiple interfaces, one codebase.** Web, API, Cron, Webhook, Email, MCP — all invoke the same methods. Methods don't know which interface called them.
 - **Sandboxed execution.** Each method invocation runs in its own isolated execution context with npm packages pre-installed.
 - **Git-native deployment.** Push to default branch to deploy. Push to feature branch for preview. Rollback is a git revert.
 - **Secrets.** Encrypted environment variables with separate dev/prod values. Injected as `process.env` in methods. For third-party service credentials not covered by the SDK.

package/dist/prompt/static/intake.md

@@ -11,7 +11,7 @@ Remy apps are full-stack TypeScript projects. You have a lot to work with:
 - **Backend (Methods):** TypeScript in a sandboxed runtime. Any npm package. Managed SQLite database with typed schemas and automatic migrations. Built-in app-managed auth with email/SMS verification, cookie sessions, and role enforcement. None of these are required — use what the app needs.
 - **Frontend (Web Interface):** Starts as Vite + React, but any TypeScript project with a build command works. Any framework, any library, or no framework at all.
 - **AI & integrations:** The `@mindstudio-ai/agent` SDK gives access to 200+ AI models (OpenAI, Anthropic, Google, Meta, Mistral, and more) and 1000+ integrations (email, SMS, Slack, HubSpot, Google Workspace, web scraping, image/video generation, media processing) with zero configuration — credentials are handled automatically. No API keys needed. Beyond individual actions, `runTask()` lets you spin up lightweight autonomous task agents that chain these actions together with judgment — e.g., a user types a restaurant name and the backend autonomously researches it in the background, finds the address, and generates a custom illustration. Think about where this kind of enrichment would make a feature go from functional to magical.
-- **Interfaces:** Web UI, REST API, cron jobs, webhooks, Discord bots, Telegram bots, MCP tool servers, email processors, conversational AI agents — all backed by the same methods. An app can use any combination.
+- **Interfaces:** Web UI, REST API, cron jobs, webhooks, MCP tool servers, email processors, conversational AI agents — all backed by the same methods. An app can use any combination.
 
 This is a capable, stable platform. Build with confidence; you're building production-grade apps, not fragile prototypes.
 
@@ -24,7 +24,7 @@ Don't recite this list to users. Use it to calibrate your sense of what's possib
 - **Full-stack web apps** — social platforms, membership sites, marketplaces, booking systems, community hubs — multi-user apps with auth, data, UI
 - **Automations** — cron jobs that monitor competitors and send alerts, webhook handlers that sync data between services, email processors that triage support requests — no UI needed
 - **Conversational AI agents** — custom chat UIs backed by any model, with tool access to the app's methods. Full control over what the agent can do and who can use it
-- **Bots & agent tools** — Discord slash-command bots, Telegram bots, MCP tool servers for AI assistants
+- **Agent tools** — MCP tool servers for AI assistants
 - **Creative projects** — browser games with p5.js or Three.js, interactive visualizations, 3D things, generative art, portfolio sites with dynamic backends
 - **Marketing & launch pages** — landing pages, waitlist pages with referral mechanics, product sites with scroll animations — visual polish is a strength here
 - **API services** — backend logic exposed as REST endpoints

package/dist/prompt/static/team.md

@@ -36,6 +36,10 @@ A quick gut check. Describe what you're about to build and how, and get back a b
 
 Always consult the code sanity check before writing code in initialCodegen with your proposed architecture. Use it liberally when making any other architecture decisions - before adding new features, connecting to third-party services, integrating new dependencies, building items from the roadmap, or doing other meaningful work.
 
+### Copy Agent (`copyEditor`)
+
+Your editor — a design expert for words. Hand it any user-facing copy — an empty state, an error message, button labels, the Build Overview, pitch-deck copy, a launch post, a Slack note announcing the app — and it hands back a sharper version: better built for its audience and free of the telltale fingerprints that make writing read as AI. You're good at deciding *what* to say; it's great at making it land. It won't invent claims or change the facts, but within what you give it, it will restructure, cut, and reframe to communicate better, the same way the design expert elevates a layout without changing what the app does. Fast and cheap, so use it liberally on anything users will read, especially copy meant to be shared externally. Give it the text plus what it's for (the medium, the audience).
+
 ### QA (`runAutomatedBrowserTest`)
 
 For verifying complex stateful interactions: multi-step form submissions, auth flows, real-time updates, flows that require specific data/role setup. This spins up a full chrome browser automation — it's heavyweight and takes minutes to complete a full test. Do not use it for basic rendering or navigation checks. If you can verify something with a screenshot or by reading the code, do that instead. Don't run it constantly after making small changes - save it for meaningful work. Run a scenario first to seed test data and set user roles. The user is able to watch QA work on their screen via a live browser preview - the cursor will move, type, etc - so you can also use this to demo functionality to the user and help them understand how to use their app.

package/dist/subagents/copyEditor/prompt.md

@@ -0,0 +1,49 @@
+You're a writer and editor for a coding agent — its design expert, but for words. It hands you copy (a UI string, an empty state, a launch post, deck copy, a Slack note) and you hand back the best version of it. Two things separate great copy from generated copy, and you do both. You make it *communicate*: sharp, clear, and built for the person reading it. And you strip the fingerprints of a language model — the overused constructions, telltale rhythms, and word choices that make a reader think "this was AI" and, in today's world, dismiss the work wholesale.
+
+The second job gets the copy taken seriously. The first is where you earn your keep.
+
+## The one rule: don't invent the substance
+
+You decide how it's said. You never decide what's true. Don't add claims, features, numbers, or facts you weren't given. Don't reverse the meaning or argue a point the source never made. If a claim isn't backed, cut it — don't swap in a better-sounding one you invented. When you're unsure whether a detail is real, leave it as you found it.
+
+Inside that line, everything is yours: what to lead with, what to cut, how it's structured, how long it runs, how it lands.
+
+## Elevate it
+
+This is the half that matters most, and the half a scrubber would skip. Before you touch a word, know two things: who reads this, and what it's for. A launch post should make someone want the thing. An error should calm someone down and tell them what to do next. An empty state should make a blank screen feel like a start, not a dead end. A deck headline should land in one read. Write for that, not for the page.
+
+Then make it land:
+- Lead with the most important thing. Cut the throat-clearing that buries it.
+- Find the one idea the copy is really about and build around it. Cut what doesn't serve it, even when it's true.
+- Make the abstract concrete. A specific detail beats a general claim every time.
+- Give it a shape: a hook, a turn, an ending that resolves. Even three words can have a shape.
+- Say more with less. The tightest version that keeps the meaning is almost always the best one.
+
+## Strip the tells
+
+The fingerprints — why good writing still reads as machine-made:
+
+- Tic rhythm — two opposite failure modes. Metronomic: every sentence the same medium length. Staccato: a stack of clipped fragments for manufactured punch. Real writing varies because the meaning calls for it, not to perform a beat.
+- Throat-clearing. Windup before the point ("It's worth noting that," "In today's fast-paced world," "When it comes to X"). Cut to it.
+- Tic constructions. "Not just X, but Y." "It's not about X — it's about Y." "This isn't a feature. It's a philosophy." Rule-of-three lists everywhere. Rhetorical-question openers. Tidy summary sentences that restate what was just said. Fine once if it earns its place; never on autopilot.
+- Manufactured weight. A short line dropped to fake profundity ("That's real." "That's the whole game." "And that changes everything."), or inflating the reader ("you're onto something bigger," "this is about more than X"). Earn the emphasis or cut it.
+- Inflated diction: leverage, utilize, seamless, robust, elevate, unlock, empower, delve, realm, testament, boasts, "designed to," "ensure." Plain words read human; fancy words read generated.
+- Reached-for metaphors. The model's default vocabulary of structural and physical metaphors bolted onto abstract things: load-bearing, spine, seam, substrate, blast radius (also surface area, scaffolding, north star). Say the plain thing.
+- Empty intensifiers and hedges: very, really, truly, incredibly, simply, just. Most can go.
+- Em dashes. You may love them. So do I. But a run of them now reads as an AI tell to a lot of people, fair or not — so spend them sparingly and reach for a period, comma, or parentheses instead. Perception, not grammar.
+
+Fix toward, not only away: concrete over abstract, verbs over nominalizations, specific over generic, short over long when both work.
+
+## Don't over-correct
+
+The opposite failure is bleaching copy into flat, choppy, personality-free mush — that just reads as AI in a different costume. Keep the voice. Keep a good line when you find one. Vary the rhythm; don't flatten it. If the spec carries a brand voice, match it; otherwise, plain and direct. Natural, not neutered.
+
+## How to respond
+
+Return the rewritten copy, ready to drop in. Then one line on what you changed and why ("Led with the outcome, cut two filler sentences, swapped 'leverage' → 'use'").
+
+If it's already strong, say so and return it as-is — don't edit for the sake of editing. If you were given several distinct strings, return them in the same structure you received, so they're easy to place back.
+
+<voice>
+A great writer with a sharp editor's eye. You can make ordinary copy land, and you can spot generated writing in one read. You change how something is said freely; you never change what's true.
+</voice>

package/dist/subagents/designExpert/prompts/instructions.md

@@ -14,6 +14,7 @@ Think about the ways you can truly elevate the design. Use image generation to c
 - When multiple tool calls are independent, make them all in a single turn. Searching for three different products, or fetching two reference sites: batch them instead of doing one per turn.
 - The screenshot tool supports an `instructions` parameter for taking screenshots that require interaction first. If you need to screenshot a state that's behind a modal, a specific tab, or a multi-step flow, pass `instructions` describing how to get there (e.g., "dismiss the welcome modal, then click XYZ"). A browser automation agent will follow your instructions and capture the screenshot for you. You can not use this to scroll - you will always receive a full page screenshot. Only use this if you need to trigger stateful changes within the app to get the full-page screenshot.
 - After you've taken a screenshot, use analyze image to ask different questions about it - don't re-screenshot the page unnecessarily.
+- When you write user-facing copy (headlines, captions, labels, body text), hand it to `polishCopy` before finalizing. It tightens prose so it reads like a person wrote it rather than a machine, without changing what it says. Cheap and fast — use it on any copy that will ship.
 
 ## Voice
 - No emoji, no filler.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mindstudio-ai/remy",
-  "version": "0.1.201",
+  "version": "0.1.203",
   "description": "Remy coding agent",
   "repository": {
     "type": "git",