@mindstudio-ai/remy 0.1.134 → 0.1.136

package/dist/headless.js

@@ -165,7 +165,12 @@ async function sidecarRequest(endpoint, body = {}, options) {
       log2.error("Sidecar error", { endpoint, status: res.status });
       throw new Error(`Sidecar error: ${res.status}`);
     }
-    return res.json();
+    const data = await res.json();
+    if (data?.success === false) {
+      const code = data.errorCode ? ` [${data.errorCode}]` : "";
+      throw new Error(`${data.error || "Unknown error"}${code}`);
+    }
+    return data;
   } catch (err) {
     if (err.message.startsWith("Sidecar error")) {
       throw err;
@@ -2602,6 +2607,39 @@ async function captureAndAnalyzeScreenshot(promptOrOptions) {
   return JSON.stringify({ url, analysis, ...styleMap ? { styleMap } : {} });
 }
 
+// src/tools/_helpers/browserLock.ts
+var lockQueue = Promise.resolve();
+function acquireBrowserLock() {
+  let release;
+  const next = new Promise((res) => {
+    release = res;
+  });
+  const wait = lockQueue;
+  lockQueue = next;
+  return wait.then(() => release);
+}
+async function checkBrowserConnected() {
+  try {
+    const status = await sidecarRequest(
+      "/browser-status",
+      {},
+      { timeout: 5e3 }
+    );
+    if (!status.connected) {
+      return {
+        connected: false,
+        error: "The browser preview is not connected. The user needs to open the preview."
+      };
+    }
+    return { connected: true };
+  } catch (err) {
+    return {
+      connected: false,
+      error: err?.message || "Could not check browser status. The dev environment may not be running."
+    };
+  }
+}
+
 // src/statusWatcher.ts
 function startStatusWatcher(config) {
   const { apiConfig, getContext, onStatus, interval = 3e3, signal } = config;
@@ -2743,6 +2781,9 @@ ${summaryBlock.text}
         return false;
       }
     }
+    if (msg.role === "assistant" && Array.isArray(msg.content) && msg.content.length === 0) {
+      return false;
+    }
     if (msg.role === "user" && msg.toolCallId && !toolUseIds.has(msg.toolCallId)) {
       return false;
     }
@@ -3300,16 +3341,6 @@ ${appSpec}
 
 // src/subagents/browserAutomation/index.ts
 var log6 = createLogger("browser-automation");
-var lockQueue = Promise.resolve();
-function acquireBrowserLock() {
-  let release;
-  const next = new Promise((res) => {
-    release = res;
-  });
-  const wait = lockQueue;
-  lockQueue = next;
-  return wait.then(() => release);
-}
 var browserAutomationTool = {
   clearable: true,
   definition: {
@@ -3332,17 +3363,9 @@ var browserAutomationTool = {
     }
     const release = await acquireBrowserLock();
     try {
-      try {
-        const status = await sidecarRequest(
-          "/browser-status",
-          {},
-          { timeout: 5e3 }
-        );
-        if (!status.connected) {
-          return "Error: the browser preview is not connected. The user needs to open the preview before browser tests can run.";
-        }
-      } catch {
-        return "Error: could not check browser status. The dev environment may not be running.";
+      const browserStatus = await checkBrowserConnected();
+      if (!browserStatus.connected) {
+        return `Error: ${browserStatus.error}`;
       }
       try {
         await sidecarRequest("/reset-browser", {}, { timeout: 5e3 });
@@ -3516,11 +3539,20 @@ var screenshotTool = {
           ...styleMap ? { styleMap } : {}
         });
       }
-      return await captureAndAnalyzeScreenshot({
-        prompt: input.prompt,
-        path: input.path,
-        onLog: context?.onLog
-      });
+      const release = await acquireBrowserLock();
+      try {
+        const browserStatus = await checkBrowserConnected();
+        if (!browserStatus.connected) {
+          return `Error: ${browserStatus.error}`;
+        }
+        return await captureAndAnalyzeScreenshot({
+          prompt: input.prompt,
+          path: input.path,
+          onLog: context?.onLog
+        });
+      } finally {
+        release();
+      }
     } catch (err) {
       return `Error taking screenshot: ${err.message}`;
     }
@@ -3846,7 +3878,12 @@ async function execute5(input, onLog, context) {
       return `Error taking interactive screenshot: ${err.message}`;
     }
   }
+  const release = await acquireBrowserLock();
   try {
+    const browserStatus = await checkBrowserConnected();
+    if (!browserStatus.connected) {
+      return `Error: ${browserStatus.error}`;
+    }
     return await captureAndAnalyzeScreenshot({
       prompt: input.prompt,
       path: input.path,
@@ -3854,6 +3891,8 @@ async function execute5(input, onLog, context) {
     });
   } catch (err) {
     return `Error taking screenshot: ${err.message}`;
+  } finally {
+    release();
   }
 }
 
@@ -5589,10 +5628,12 @@ async function runTurn(params) {
       saveSession(state);
       return;
     }
-    state.messages.push({
-      role: "assistant",
-      content: [...contentBlocks].sort((a, b) => a.startedAt - b.startedAt)
-    });
+    if (contentBlocks.length > 0) {
+      state.messages.push({
+        role: "assistant",
+        content: [...contentBlocks].sort((a, b) => a.startedAt - b.startedAt)
+      });
+    }
     const toolCalls = getToolCalls(contentBlocks);
     if (stopReason !== "tool_use" || toolCalls.length === 0) {
       statusWatcher.stop();

package/dist/index.js

@@ -1986,7 +1986,12 @@ async function sidecarRequest(endpoint, body = {}, options) {
       log2.error("Sidecar error", { endpoint, status: res.status });
       throw new Error(`Sidecar error: ${res.status}`);
     }
-    return res.json();
+    const data = await res.json();
+    if (data?.success === false) {
+      const code = data.errorCode ? ` [${data.errorCode}]` : "";
+      throw new Error(`${data.error || "Unknown error"}${code}`);
+    }
+    return data;
   } catch (err) {
     if (err.message.startsWith("Sidecar error")) {
       throw err;
@@ -2306,6 +2311,46 @@ Respond only with your analysis as Markdown and absolutely no other text. Do not
   }
 });
 
+// src/tools/_helpers/browserLock.ts
+function acquireBrowserLock() {
+  let release;
+  const next = new Promise((res) => {
+    release = res;
+  });
+  const wait = lockQueue;
+  lockQueue = next;
+  return wait.then(() => release);
+}
+async function checkBrowserConnected() {
+  try {
+    const status = await sidecarRequest(
+      "/browser-status",
+      {},
+      { timeout: 5e3 }
+    );
+    if (!status.connected) {
+      return {
+        connected: false,
+        error: "The browser preview is not connected. The user needs to open the preview."
+      };
+    }
+    return { connected: true };
+  } catch (err) {
+    return {
+      connected: false,
+      error: err?.message || "Could not check browser status. The dev environment may not be running."
+    };
+  }
+}
+var lockQueue;
+var init_browserLock = __esm({
+  "src/tools/_helpers/browserLock.ts"() {
+    "use strict";
+    init_sidecar();
+    lockQueue = Promise.resolve();
+  }
+});
+
 // src/statusWatcher.ts
 function startStatusWatcher(config) {
   const { apiConfig, getContext, onStatus, interval = 3e3, signal } = config;
@@ -2452,6 +2497,9 @@ ${summaryBlock.text}
         return false;
       }
     }
+    if (msg.role === "assistant" && Array.isArray(msg.content) && msg.content.length === 0) {
+      return false;
+    }
     if (msg.role === "user" && msg.toolCallId && !toolUseIds.has(msg.toolCallId)) {
       return false;
     }
@@ -3079,16 +3127,7 @@ var init_prompt = __esm({
 });
 
 // src/subagents/browserAutomation/index.ts
-function acquireBrowserLock() {
-  let release;
-  const next = new Promise((res) => {
-    release = res;
-  });
-  const wait = lockQueue;
-  lockQueue = next;
-  return wait.then(() => release);
-}
-var log4, lockQueue, browserAutomationTool;
+var log4, browserAutomationTool;
 var init_browserAutomation = __esm({
   "src/subagents/browserAutomation/index.ts"() {
     "use strict";
@@ -3096,11 +3135,11 @@ var init_browserAutomation = __esm({
     init_tools();
     init_prompt();
     init_sidecar();
+    init_browserLock();
     init_screenshot();
     init_runCli();
     init_logger();
     log4 = createLogger("browser-automation");
-    lockQueue = Promise.resolve();
     browserAutomationTool = {
       clearable: true,
       definition: {
@@ -3123,17 +3162,9 @@ var init_browserAutomation = __esm({
         }
         const release = await acquireBrowserLock();
         try {
-          try {
-            const status = await sidecarRequest(
-              "/browser-status",
-              {},
-              { timeout: 5e3 }
-            );
-            if (!status.connected) {
-              return "Error: the browser preview is not connected. The user needs to open the preview before browser tests can run.";
-            }
-          } catch {
-            return "Error: could not check browser status. The dev environment may not be running.";
+          const browserStatus = await checkBrowserConnected();
+          if (!browserStatus.connected) {
+            return `Error: ${browserStatus.error}`;
           }
           try {
             await sidecarRequest("/reset-browser", {}, { timeout: 5e3 });
@@ -3247,6 +3278,7 @@ var init_screenshot2 = __esm({
   "src/tools/code/screenshot.ts"() {
     "use strict";
     init_screenshot();
+    init_browserLock();
     init_analyzeImage();
     init_browserAutomation();
     screenshotTool = {
@@ -3316,11 +3348,20 @@ var init_screenshot2 = __esm({
               ...styleMap ? { styleMap } : {}
             });
           }
-          return await captureAndAnalyzeScreenshot({
-            prompt: input.prompt,
-            path: input.path,
-            onLog: context?.onLog
-          });
+          const release = await acquireBrowserLock();
+          try {
+            const browserStatus = await checkBrowserConnected();
+            if (!browserStatus.connected) {
+              return `Error: ${browserStatus.error}`;
+            }
+            return await captureAndAnalyzeScreenshot({
+              prompt: input.prompt,
+              path: input.path,
+              onLog: context?.onLog
+            });
+          } finally {
+            release();
+          }
         } catch (err) {
           return `Error taking screenshot: ${err.message}`;
         }
@@ -3662,7 +3703,12 @@ async function execute5(input, onLog, context) {
       return `Error taking interactive screenshot: ${err.message}`;
     }
   }
+  const release = await acquireBrowserLock();
   try {
+    const browserStatus = await checkBrowserConnected();
+    if (!browserStatus.connected) {
+      return `Error: ${browserStatus.error}`;
+    }
     return await captureAndAnalyzeScreenshot({
       prompt: input.prompt,
       path: input.path,
@@ -3670,6 +3716,8 @@ async function execute5(input, onLog, context) {
     });
   } catch (err) {
     return `Error taking screenshot: ${err.message}`;
+  } finally {
+    release();
   }
 }
 var definition5;
@@ -3677,6 +3725,7 @@ var init_screenshot3 = __esm({
   "src/subagents/designExpert/tools/screenshot.ts"() {
     "use strict";
     init_screenshot();
+    init_browserLock();
     init_analyzeImage();
     init_browserAutomation();
     definition5 = {
@@ -5651,10 +5700,12 @@ async function runTurn(params) {
       saveSession(state);
       return;
     }
-    state.messages.push({
-      role: "assistant",
-      content: [...contentBlocks].sort((a, b) => a.startedAt - b.startedAt)
-    });
+    if (contentBlocks.length > 0) {
+      state.messages.push({
+        role: "assistant",
+        content: [...contentBlocks].sort((a, b) => a.startedAt - b.startedAt)
+      });
+    }
     const toolCalls = getToolCalls(contentBlocks);
     if (stopReason !== "tool_use" || toolCalls.length === 0) {
       statusWatcher.stop();

package/dist/prompt/.notes.md

@@ -69,7 +69,7 @@ From research into v0, Lovable, Bolt, and Anthropic's `<frontend_aesthetics>` co
 
 ## SDK Usage
 
-The source docs originally showed `mindstudio.executeStep('generateText', ...)` which was wrong. The correct API is `new MindStudioAgent()` with direct method calls (`agent.generateText(...)`, `agent.sendEmail(...)`, etc.). No constructor args needed inside methods — credentials come from the execution environment. We fixed both the compiled fragment and the upstream source doc in youai-api.
+The canonical import pattern for MindStudio app methods is `import { mindstudio } from '@mindstudio-ai/agent'` with `mindstudio.generateText(...)`, `mindstudio.runTask(...)`, etc. The `mindstudio` singleton handles auth automatically. `new MindStudioAgent({ apiKey })` is only for external usage outside MindStudio apps.
 
 The SDK ships `llms.txt` at the package root with full signatures for all 170+ actions. The compiled fragment references this path (`dist/methods/node_modules/@mindstudio-ai/agent/llms.txt`) so the agent knows where to look up specific action details.
 

package/dist/prompt/compiled/auth.md

@@ -343,13 +343,16 @@ Roles are declared in the manifest, stored as an array column on the user table,
 
 Apps without `auth` in the manifest use anonymous guest sessions. No login, no user identity, no roles. This is the default and works fine for single-user apps, internal tools, and simple utilities.
 
-## Designing Auth in Web Interfaces
+## Important: Designing Auth in Web Interfaces
+
 The most imporant user experience consideration with auth is that authentication moments must feel natural and intuitive - they should not feel jarring or surprising. Take care to integrate them into the entire experience when building.
 
 For the overwhelming majority of apps, a user should never land on auth at the root of an app when opening it for the first time (except in cases where the app is, e.g., an internal tool or some other protected experience - and even then it should feel more like a welcome/splash screen than an error state). Users should be able to explore public resources, or at least encounter some kind of landing/introduction moment, before they get hit with a signup/login screen. Make auth feel like a natural moment in the user's journey.
 
 Login and signup screens set the tone for the user's entire experience with the app and are important to get right - they should feel like exciting entry points into the next level of the user journy. A janky login form with misaligned inputs and no feedback dminishes excitement and undermines trust before the user even gets in.
 
+Login and signup are separate moments - even if the underlying code is the same for both. A new user signing up should feel like they are creating a new account. A user logging in should feel like they are being welcomed back. Auth is always a pain for users, even when it's as frictionless as this, so take care to use Sign Up screens as moments to communicate value and help the user get excited about what they are joining.
+
 Consult the `visualDesignExpert` to help you work through authentication at a high level, including when and where to show auth, and the design of specific screens.
 
 ### Rules for Building Auth Screens

package/dist/prompt/compiled/design.md

@@ -25,7 +25,7 @@ Interfaces run fullscreen in the user's browser or a wrapped webview mobile app.
 - **No long scrolling pages.** Use structured layouts: cards, split panes, steppers, tabs, grouped sections that fit the viewport. The interface should feel like an award winning iOS or macOS app, not a document.
 - **On mobile**, scrolling may be necessary, but use sticky headers, fixed CTAs, and anchored navigation to keep key actions within reach. Always use "width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no" to make sure apps feel like apps.
 - Think of every screen as something the user opens, uses, and closes — not something they read.
-- Pay attention to details that will make things feel app-like - set user-select: none on specific app-like layout elements, use motion, use iOS/macOS design language and patterns.
+- Pay attention to details that will make things feel app-like - set user-select: none on specific app-like layout elements like navigation bars, use motion, use iOS/macOS design language and patterns.
 
 ## Layout Stability
 
@@ -50,6 +50,7 @@ Every interface must work on both desktop and mobile. Think about how the app wi
 - Even for mobile-first apps, make sure to set desktop or larger device breakpoints - nothing looks jankier than opening a mobile-designed site in a desktop browser and seeing a full width bottom tab bar with nav icons stretching 1000px wide. Don't make sloppy, amateur mistakes or omissions like this - the user will notice them and be disappointed.
 
 ## Images
+
 The `designExpert` can create and source amazing, high quality images, graphics, illustrations, and logos to use in the interface - both with and without transparency. This is a huge level for upgrading the premium look, feel, and quality of the app. Use image logos directly instead of plain text wordmarks; use images for empty states, onboarding screens, full-screen loading, and more.
 
 ## Forms

package/dist/prompt/compiled/methods.md

@@ -65,38 +65,36 @@ export async function getDashboard(input: {
 
 ## Platform Capabilities
 
-The `@mindstudio-ai/agent` SDK provides access to 200+ AI models and 1,000+ actions (email, SMS, web scraping, file uploads, third-party integrations, and more). Inside a method, create an instance and call actions directly. No constructor arguments needed — credentials are picked up automatically from the execution environment:
+The `@mindstudio-ai/agent` SDK provides access to 200+ AI models and 1,000+ actions (email, SMS, web scraping, file uploads, third-party integrations, and more). Inside a method, use the `mindstudio` singleton — credentials come from the execution environment automatically:
 
 ```typescript
-import { MindStudioAgent } from '@mindstudio-ai/agent';
-
-const agent = new MindStudioAgent();
+import { mindstudio } from '@mindstudio-ai/agent';
 
 // AI text generation
-const { content } = await agent.generateText({
+const { content } = await mindstudio.generateText({
   message: 'Summarize this invoice...',
 });
 
 // AI image generation
-const { imageUrl } = await agent.generateImage({
+const { imageUrl } = await mindstudio.generateImage({
   prompt: 'A professional headshot placeholder',
 });
 
 // Send email
-await agent.sendEmail({
+await mindstudio.sendEmail({
   to: 'user@example.com',
   subject: 'Your invoice',
   body: content,
 });
 
 // Upload files
-const { url } = await agent.uploadFile({
+const { url } = await mindstudio.uploadFile({
   data: buffer,
   fileName: 'report.pdf',
 });
 
 // Web scraping
-const { markdown } = await agent.scrapeUrl({
+const { markdown } = await mindstudio.scrapeUrl({
   url: 'https://example.com',
 });
 
@@ -126,7 +124,7 @@ For errors from external services or internal failures (API calls, AI generation
 
 ```typescript
 try {
-  const result = await agent.generateVideo({ ... });
+  const result = await mindstudio.generateVideo({ ... });
   return { videoUrl: result.url };
 } catch (err) {
   console.error('Video generation failed:', err);
@@ -210,7 +208,7 @@ export async function enrichRestaurant(input: { id: string; name: string }) {
   await Restaurants.update(input.id, { status: 'enriching' });
 
   // Fire — don't await
-  agent.runTask<RestaurantData>({
+  mindstudio.runTask<RestaurantData>({
     prompt: '...',
     input: { name: input.name },
     tools: ['searchGoogle', 'fetchUrl', 'generateImage'],

package/dist/prompt/compiled/msfm.md

@@ -192,13 +192,15 @@ styles:
 ```
 ```
 
-Roadmap item example (one file per feature in `src/roadmap/`):
+Roadmap item examples (one file per feature in `src/roadmap/`):
+
+Built item (status updated to `done` after build, with History appended):
 
 ```markdown
 ---
 name: Share & Export
 type: roadmap
-status: not-started
+status: done
 description: Share haikus as image cards to social media or download as prints.
 requires: []
 effort: medium
@@ -220,3 +222,20 @@ clipboard fallback for unsupported browsers.
 - **2026-03-22** — Built card generation using generateImage.
   Added share button to haiku detail view.
 ```
+
+Unbuilt item:
+
+```markdown
+---
+name: Daily Prompt Engine
+type: roadmap
+status: not-started
+description: A new writing prompt every day, tuned to the user's style and interests.
+requires: []
+effort: small
+---
+
+Generate a personalized daily writing prompt based on the user's past haikus,
+preferred themes, and seasonal context. Surface it as a gentle nudge on the
+home screen, not a notification.
+```

package/dist/prompt/compiled/sdk-actions.md

@@ -6,24 +6,18 @@ There is a huge amount of capability here: hundreds of text generation models (O
 
 ## Usage in Methods
 
-Inside a MindStudio app method, create an instance with no arguments — credentials come from the execution environment:
+Inside a MindStudio app method, use the `mindstudio` singleton — credentials come from the execution environment automatically:
 
 ```typescript
-import { MindStudioAgent } from '@mindstudio-ai/agent';
+import { mindstudio } from '@mindstudio-ai/agent';
 
-const agent = new MindStudioAgent();
-```
-
-Every action is a method on the agent instance:
-
-```typescript
-const { content } = await agent.generateText({ message: 'Summarize this...' });
+const { content } = await mindstudio.generateText({ message: 'Summarize this...' });
 ```
 
 Results are returned flat — output fields at the top level alongside metadata:
 
 ```typescript
-const result = await agent.generateText({ message: 'Hello' });
+const result = await mindstudio.generateText({ message: 'Hello' });
 result.content;              // step-specific output
 result.$billingCost;         // cost in credits (if applicable)
 ```
@@ -104,13 +98,13 @@ For other services, use `runFromConnectorRegistry`:
 
 ```typescript
 // Discover available connectors
-const { connectors } = await agent.listConnectors();
+const { connectors } = await mindstudio.listConnectors();
 
 // Get action details
-const action = await agent.getConnectorAction('hubspot', 'create-contact');
+const action = await mindstudio.getConnectorAction('hubspot', 'create-contact');
 
 // Execute
-const result = await agent.runFromConnectorRegistry({
+const result = await mindstudio.runFromConnectorRegistry({
   serviceId: 'hubspot',
   actionId: 'create-contact',
   input: { email: 'user@example.com', firstName: 'Alice' },
@@ -122,7 +116,7 @@ const result = await agent.runFromConnectorRegistry({
 Override the default model for any AI action. Each model has its own config options (dimensions, seed, inference steps, etc.) so always use `askMindStudioSdk` to look up the correct config before specifying a model override:
 
 ```typescript
-const { content } = await agent.generateText({
+const { content } = await mindstudio.generateText({
   message: 'Hello',
   modelOverride: {
     model: 'claude-sonnet-4-6',
@@ -139,7 +133,7 @@ Make sure to prioritize new, popular models. MindStudio has a ton of models avai
 Run up to 50 actions in parallel:
 
 ```typescript
-const result = await agent.executeStepBatch([
+const result = await mindstudio.executeStepBatch([
   { stepType: 'generateImage', step: { prompt: 'a sunset' } },
   { stepType: 'textToSpeech', step: { text: 'hello world' } },
 ]);

package/dist/prompt/compiled/task-agents.md

@@ -1,4 +1,4 @@
-# Task Agents (`MindStudioAgent runTask`)
+# Task Agents (`mindstudio.runTask`)
 
 A user types the name of a restaurant into your app, or uploads a photo of a storefront. The API call returns early, and in the background, a task agent searches Google, finds the official website, scrapes the address, gets the official social media accounts, and generates a stylized watercolor postcard of the exterior from images it found online. The user gets back a rich, illustrated card with the canonical name, website, address, and a custom image. A few tool calls (some in parallel), fully autonomous.
 
@@ -26,11 +26,9 @@ Run tasks in the background — depending on complexity they can take time to co
 ## Usage
 
 ```typescript
-import { MindStudioAgent } from '@mindstudio-ai/agent';
+import { mindstudio } from '@mindstudio-ai/agent';
 
-const agent = new MindStudioAgent();
-
-const result = await agent.runTask<{
+const result = await mindstudio.runTask<{
   name: string;
   url: string;
   address: string;
@@ -74,7 +72,7 @@ console.log(result.output.photoUrl); // URL to the generated illustration
 `runTask()` can return successfully with garbage output — fields null, data echoed back, or raw text instead of JSON. The result includes `parsedSuccessfully` to make this explicit. Always check it before using the output:
 
 ```typescript
-const result = await agent.runTask<MyType>({ ... });
+const result = await mindstudio.runTask<MyType>({ ... });
 
 if (!result.parsedSuccessfully) {
   console.error('Task output was not valid JSON:', result.outputRaw);
@@ -106,6 +104,10 @@ tools: [
 
 When the model calls a tool, the platform deep-merges the model's arguments with the developer's defaults. The model decides what to do (prompt, query, parameters), the developer controls which model/config to use. If the model needs to search and generate an image and those are independent, it will call both tools in the same turn (parallel execution server-side).
 
+## Voice & Tone in Prompts
+
+When a task agent produces user-facing text, the prompt must include a note voice and tone constraints. Make sure to specify no emojis, em dashes, and other "ai-isms" in the prompt, as well as the desired tone and voice of the output.
+
 ## Options
 
 | Field | Required | Default | Description |
@@ -150,7 +152,7 @@ When something goes wrong, `toolCalls` is the first thing to check. If it's empt
 Pass an `onEvent` callback to get real-time events:
 
 ```typescript
-const result = await agent.runTask({
+const result = await mindstudio.runTask({
   // ... same options ...
   onEvent: (event) => {
     if (event.type === 'text') console.log('Agent:', event.text);
@@ -173,7 +175,7 @@ Without `onEvent`, the SDK uses async polling (returns silently when complete).
 
 ```typescript
 try {
-  const result = await agent.runTask({ ... });
+  const result = await mindstudio.runTask({ ... });
   if (!result.parsedSuccessfully) {
     // Task completed but output wasn't valid JSON
     console.error('Raw output:', result.outputRaw);

package/dist/prompt/static/coding.md

@@ -45,6 +45,9 @@ For multi-step tasks with branching logic (research, enrichment, content pipelin
 - Use container queries for components that need to adapt to their container rather than the viewport.
 - For canvas-based UIs (games, visualizations, interactive graphics): size the canvas to fill its container, account for `devicePixelRatio` for Retina sharpness, and scale all objects relative to the viewport — not in fixed pixel sizes - otherwise they are going to be tiny and unusable.
 
+### Copy & Prose
+- Landing pages, hero sections, onboarding flows, and other long-form prose need a human voice. Write plainly and specifically. Avoid promotional filler, hollow intensifiers, and chatbot enthusiasm. Avoid em dashes, emojis, and other "ai-isms" in your writing.
+
 ### Error Visibility
 - Runtime errors must render visibly on screen, not produce a blank white page. User and agent must be able to visibly debug and spot them.
 
@@ -63,7 +66,7 @@ When integrating with external services that have programmable setup APIs (webho
 Before installing a package you haven't used in this project, do a quick web search to confirm it's still the best option. The JavaScript ecosystem moves fast — the package you remember from training may have been superseded by something smaller, faster, or better maintained. A 10-second search beats debugging a deprecated library.
 
 ### MindStudio SDK CLI
-You have access to the `mindstudio` CLI, which exposes every SDK action as a command-line tool. Use it via bash for one-off tasks: generating images, scraping URLs, sending emails, running AI completions, or anything else the SDK can do. Every JavaScript SDK method has a corresponding CLI command. Run `askMindStudioSdk` to discover commands for CLI usage.
+You have access to the `mindstudio` CLI, which exposes every SDK action as a command-line tool. Use it via bash for one-off tasks: generating images, video, or audio, scraping URLs, sending emails, running AI completions, or anything else the SDK can do. Every JavaScript SDK method has a corresponding CLI command. Run `askMindStudioSdk` to discover commands for CLI usage.
 
 ### Production App Management
 You have access to `mindstudio-prod`, a CLI for managing the user's production MindStudio app. Use it via your bash tool. All output is JSON. Run `mindstudio-prod --help` or `mindstudio-prod <command> --help` to discover usage and available options.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mindstudio-ai/remy",
-  "version": "0.1.134",
+  "version": "0.1.136",
   "description": "MindStudio coding agent",
   "repository": {
     "type": "git",