@mindstudio-ai/remy 0.1.109 → 0.1.111

package/dist/headless.js

@@ -414,7 +414,7 @@ ${isLspConfigured() ? `<typescript_lsp>
 <conversation_summaries>
 Your conversation history may include <prior_conversation_summary> blocks in the user's messages. These are automated summaries of earlier messages that have been compacted to save context space. The user does not see this summary, they see the full conversation history in their UI. Treat the summary as ground truth for what happened before, but do not reference it directly to the user ("as mentioned in the summary..."). Just continue naturally as if you remember the prior work.
 
-Old tool results are periodically cleared from the conversation to save context space. This is automatic and expected \u2014 you don't need to note down or preserve information from tool results. If you need to reference something from an earlier tool call, just re-read the file or re-run the query, or use your .remy-notes.md file.
+Old tool results are periodically cleared from the conversation to save context space. This is automatic and expected \u2014 you don't need to note down or preserve information from tool results. If you need to reference something from an earlier tool call, just re-read the file or re-run the query.
 </conversation_summaries>
 
 <project_onboarding>
@@ -2235,11 +2235,62 @@ var globTool = {
 
 // src/tools/code/listDir.ts
 import fs12 from "fs/promises";
+import path7 from "path";
+var EXCLUDE = /* @__PURE__ */ new Set([".git", "node_modules"]);
+var MAX_CHILDREN = 15;
+async function readAndSort(dirPath) {
+  const entries = await fs12.readdir(dirPath, { withFileTypes: true });
+  return entries.filter((e) => !EXCLUDE.has(e.name)).sort((a, b) => {
+    if (a.isDirectory() && !b.isDirectory()) {
+      return -1;
+    }
+    if (!a.isDirectory() && b.isDirectory()) {
+      return 1;
+    }
+    return a.name.localeCompare(b.name);
+  });
+}
+async function collapsePath(basePath, name) {
+  let display = name;
+  let current = path7.join(basePath, name);
+  for (; ; ) {
+    let children;
+    try {
+      children = await readAndSort(current);
+    } catch {
+      break;
+    }
+    if (children.length === 1 && children[0].isDirectory()) {
+      display += "/" + children[0].name;
+      current = path7.join(current, children[0].name);
+    } else {
+      break;
+    }
+  }
+  return [display, current];
+}
+function formatSize(bytes) {
+  if (bytes < 1e3) {
+    return `${bytes} B`;
+  }
+  if (bytes < 1e6) {
+    return `${(bytes / 1e3).toFixed(1)} kB`;
+  }
+  return `${(bytes / 1e6).toFixed(1)} MB`;
+}
+async function formatFile(dirPath, name, indent) {
+  try {
+    const stat = await fs12.stat(path7.join(dirPath, name));
+    return `${indent}${name}${" ".repeat(Math.max(1, 30 - indent.length - name.length))}${formatSize(stat.size)}`;
+  } catch {
+    return `${indent}${name}`;
+  }
+}
 var listDirTool = {
   clearable: true,
   definition: {
     name: "listDir",
-    description: "List the contents of a directory. Shows entries with / suffix for directories, sorted directories-first then alphabetically. Use this for a quick overview of a directory's contents. For finding files across the whole project, use glob instead.",
+    description: "List the contents of a directory with one level of subdirectory expansion. Shows file sizes and collapses single-child directory chains (a/b/c/ shown as one entry). Use this for a quick overview of a directory's structure. For finding files across the whole project, use glob instead.",
     inputSchema: {
       type: "object",
       properties: {
@@ -2253,16 +2304,34 @@ var listDirTool = {
   async execute(input) {
     const dirPath = input.path || ".";
     try {
-      const entries = await fs12.readdir(dirPath, { withFileTypes: true });
-      const lines = entries.filter((e) => e.name !== ".git" && e.name !== "node_modules").sort((a, b) => {
-        if (a.isDirectory() && !b.isDirectory()) {
-          return -1;
-        }
-        if (!a.isDirectory() && b.isDirectory()) {
-          return 1;
+      const entries = await readAndSort(dirPath);
+      const lines = [];
+      for (const entry of entries) {
+        if (entry.isDirectory()) {
+          const [displayName, finalPath] = await collapsePath(
+            dirPath,
+            entry.name
+          );
+          lines.push(`${displayName}/`);
+          try {
+            const children = await readAndSort(finalPath);
+            const capped = children.slice(0, MAX_CHILDREN);
+            for (const child of capped) {
+              if (child.isDirectory()) {
+                lines.push(`  ${child.name}/`);
+              } else {
+                lines.push(await formatFile(finalPath, child.name, "  "));
+              }
+            }
+            if (children.length > MAX_CHILDREN) {
+              lines.push(`  ... and ${children.length - MAX_CHILDREN} more`);
+            }
+          } catch {
+          }
+        } else {
+          lines.push(await formatFile(dirPath, entry.name, ""));
         }
-        return a.name.localeCompare(b.name);
-      }).map((e) => e.isDirectory() ? `${e.name}/` : e.name);
+      }
       return lines.join("\n") || "(empty directory)";
     } catch (err) {
       return `Error listing directory: ${err.message}`;
@@ -2455,26 +2524,44 @@ async function analyzeImage(params) {
 var SCREENSHOT_ANALYSIS_PROMPT = `Describe everything visible on screen from top to bottom \u2014 every element, its position, its size relative to the viewport, its colors, its content. Be comprehensive, thorough, and spatial. After the inventory, note anything that looks visually broken (overlapping elements, clipped text, misaligned components).
 
 Respond only with your analysis as Markdown and absolutely no other text. Do not use emojis - use unicode if you need symbols.`;
+var TEXT_WRAP_DISCLAIMER = `Note: ignore text wrapping issues. Screenshots occasionally show text wrapping onto an extra line compared to the live page \u2014 most noticeable in buttons, badges, and headings. This is a known limitation of SVG foreignObject rendering used the DOM-to-image capture library that took the screenshot. The browser's SVG renderer computes slightly wider text metrics than the HTML layout engine, so text that fits on one line in the live DOM can overflow by a fraction of a pixel in the capture - this is not a real issue.`;
+function buildScreenshotAnalysisPrompt(opts) {
+  let p = opts?.prompt || SCREENSHOT_ANALYSIS_PROMPT;
+  if (opts?.styleMap) {
+    p += `
+
+The following styleMap describes the computed layout state at the moment of capture. Use it to verify typography, spacing, overflow, and element dimensions \u2014 it is more accurate than visual estimation from the image.
+
+<style_map>
+${opts.styleMap}
+</style_map>`;
+  }
+  p += `
+
+${TEXT_WRAP_DISCLAIMER}`;
+  return p;
+}
 async function captureAndAnalyzeScreenshot(promptOrOptions) {
   let prompt;
   let existingUrl;
   let onLog;
-  let path9;
+  let path10;
   if (typeof promptOrOptions === "object" && promptOrOptions !== null) {
     prompt = promptOrOptions.prompt;
     existingUrl = promptOrOptions.imageUrl;
-    path9 = promptOrOptions.path;
+    path10 = promptOrOptions.path;
     onLog = promptOrOptions.onLog;
   } else {
     prompt = promptOrOptions;
   }
   let url;
+  let styleMap;
   if (existingUrl) {
     url = existingUrl;
   } else {
     const ssResult = await sidecarRequest(
       "/screenshot-full-page",
-      path9 ? { path: path9 } : void 0,
+      path10 ? { path: path10 } : void 0,
       { timeout: 12e4 }
     );
     url = ssResult?.url || ssResult?.screenshotUrl;
@@ -2483,20 +2570,21 @@ async function captureAndAnalyzeScreenshot(promptOrOptions) {
         `No URL in sidecar response. The browser may not be ready yet. Response: ${JSON.stringify(ssResult)}`
       );
     }
+    styleMap = ssResult?.styleMap;
   }
   if (prompt === false) {
     return url;
   }
-  let analysisPrompt = prompt || SCREENSHOT_ANALYSIS_PROMPT;
-  analysisPrompt += `
-Note: ignore text wrapping issues. Screenshots occasionally show text wrapping onto an extra line compared to the live page \u2014 most noticeable in buttons, badges, and headings. This is a known limitation of SVG foreignObject rendering used the DOM-to-image capture library that took the screenshot. The browser's SVG renderer computes slightly wider text metrics than the HTML layout engine, so text that fits on one line in the live DOM can overflow by a fraction of a pixel in the capture - this is not a real issue.
-`;
+  const analysisPrompt = buildScreenshotAnalysisPrompt({
+    prompt: prompt || void 0,
+    styleMap
+  });
   const analysis = await analyzeImage({
     prompt: analysisPrompt,
     imageUrl: url,
     onLog
   });
-  return JSON.stringify({ url, analysis });
+  return JSON.stringify({ url, analysis, ...styleMap ? { styleMap } : {} });
 }
 
 // src/tools/code/screenshot.ts
@@ -3281,7 +3369,9 @@ var browserAutomationTool = {
                   stepType: "analyzeImage",
                   step: {
                     imageUrl: s.result.url,
-                    prompt: SCREENSHOT_ANALYSIS_PROMPT
+                    prompt: buildScreenshotAnalysisPrompt({
+                      styleMap: s.result.styleMap
+                    })
                   }
                 }));
                 const batchResult = await runCli(
@@ -3460,10 +3550,6 @@ __export(analyzeImage_exports, {
   definition: () => definition4,
   execute: () => execute4
 });
-var DEFAULT_PROMPT = `
-Describe everything visible in this image \u2014 every element, its position, its size relative to the frame, its colors, its content. Be comprehensive, thorough and spatial. After the inventory, note anything that looks visually broken (overlapping elements, clipped text, misaligned components).
-
-Respond only with your analysis as Markdown and absolutely no other text. Do not use emojis - use unicode if you need symbols.`;
 var definition4 = {
   clearable: true,
   name: "analyzeImage",
@@ -3485,11 +3571,9 @@ var definition4 = {
 };
 async function execute4(input, onLog) {
   const imageUrl = input.imageUrl;
-  let prompt = input.prompt || DEFAULT_PROMPT;
-  prompt += `
-
-  Note: ignore text wrapping issues. Screenshots occasionally show text wrapping onto an extra line compared to the live page \u2014 most noticeable in buttons, badges, and headings. This is a known limitation of SVG foreignObject rendering used the DOM-to-image capture library that took the screenshot. The browser's SVG renderer computes slightly wider text metrics than the HTML layout engine, so text that fits on one line in the live DOM can overflow by a fraction of a pixel in the capture - this is not a real issue.
-`;
+  const prompt = buildScreenshotAnalysisPrompt({
+    prompt: input.prompt
+  });
   const analysis = await analyzeImage({
     prompt,
     imageUrl,
@@ -3538,13 +3622,26 @@ async function execute5(input, onLog, context) {
         return `Error: browser navigation completed but no screenshot URL was returned. Agent output: ${result}`;
       }
       const url = urlMatch[0];
-      const analysisPrompt = input.prompt || SCREENSHOT_ANALYSIS_PROMPT;
+      let styleMap;
+      try {
+        const parsed = JSON.parse(result);
+        styleMap = parsed?.styleMap;
+      } catch {
+      }
+      const analysisPrompt = buildScreenshotAnalysisPrompt({
+        prompt: input.prompt,
+        styleMap
+      });
       const analysis = await analyzeImage({
         prompt: analysisPrompt,
         imageUrl: url,
         onLog
       });
-      return JSON.stringify({ url, analysis });
+      return JSON.stringify({
+        url,
+        analysis,
+        ...styleMap ? { styleMap } : {}
+      });
     } catch (err) {
       return `Error taking interactive screenshot: ${err.message}`;
     }
@@ -3824,12 +3921,12 @@ async function executeDesignExpertTool(name, input, context, toolCallId, onLog)
 
 // src/subagents/common/context.ts
 import fs14 from "fs";
-import path7 from "path";
+import path8 from "path";
 function walkMdFiles2(dir, skip) {
   const files = [];
   try {
     for (const entry of fs14.readdirSync(dir, { withFileTypes: true })) {
-      const full = path7.join(dir, entry.name);
+      const full = path8.join(dir, entry.name);
       if (entry.isDirectory()) {
         if (!skip?.has(entry.name)) {
           files.push(...walkMdFiles2(full, skip));
@@ -4309,7 +4406,7 @@ var VISION_TOOLS = [
 
 // src/subagents/productVision/executor.ts
 import fs16 from "fs";
-import path8 from "path";
+import path9 from "path";
 var ROADMAP_DIR = "src/roadmap";
 function formatRequires(requires) {
   return requires.length === 0 ? "[]" : `[${requires.map((r) => `"${r}"`).join(", ")}]`;
@@ -4325,7 +4422,7 @@ async function executeVisionTool(name, input) {
         requires,
         body
       } = input;
-      const filePath = path8.join(ROADMAP_DIR, `${slug}.md`);
+      const filePath = path9.join(ROADMAP_DIR, `${slug}.md`);
       try {
         fs16.mkdirSync(ROADMAP_DIR, { recursive: true });
         const oldContent = fs16.existsSync(filePath) ? fs16.readFileSync(filePath, "utf-8") : "";
@@ -4351,7 +4448,7 @@ ${unifiedDiff(filePath, oldContent, content)}`;
     }
     case "updateRoadmapItem": {
       const { slug } = input;
-      const filePath = path8.join(ROADMAP_DIR, `${slug}.md`);
+      const filePath = path9.join(ROADMAP_DIR, `${slug}.md`);
       try {
         if (!fs16.existsSync(filePath)) {
           return `Error: ${filePath} does not exist`;
@@ -4419,7 +4516,7 @@ ${unifiedDiff(filePath, oldContent, content)}`;
     }
     case "deleteRoadmapItem": {
       const { slug } = input;
-      const filePath = path8.join(ROADMAP_DIR, `${slug}.md`);
+      const filePath = path9.join(ROADMAP_DIR, `${slug}.md`);
       try {
         if (!fs16.existsSync(filePath)) {
           return `Error: ${filePath} does not exist`;
@@ -6044,6 +6141,9 @@ ${xmlParts}
       if (pending) {
         pendingTools.delete(id);
         pending.resolve(result);
+      } else if (!running) {
+        log10.info("Late tool_result while idle, dismissing", { id });
+        emit("completed", { success: true }, requestId);
       } else {
         earlyResults.set(id, result);
       }

package/dist/index.js

@@ -1829,15 +1829,66 @@ var init_glob = __esm({
 
 // src/tools/code/listDir.ts
 import fs9 from "fs/promises";
-var listDirTool;
+import path4 from "path";
+async function readAndSort(dirPath) {
+  const entries = await fs9.readdir(dirPath, { withFileTypes: true });
+  return entries.filter((e) => !EXCLUDE.has(e.name)).sort((a, b) => {
+    if (a.isDirectory() && !b.isDirectory()) {
+      return -1;
+    }
+    if (!a.isDirectory() && b.isDirectory()) {
+      return 1;
+    }
+    return a.name.localeCompare(b.name);
+  });
+}
+async function collapsePath(basePath, name) {
+  let display = name;
+  let current = path4.join(basePath, name);
+  for (; ; ) {
+    let children;
+    try {
+      children = await readAndSort(current);
+    } catch {
+      break;
+    }
+    if (children.length === 1 && children[0].isDirectory()) {
+      display += "/" + children[0].name;
+      current = path4.join(current, children[0].name);
+    } else {
+      break;
+    }
+  }
+  return [display, current];
+}
+function formatSize(bytes) {
+  if (bytes < 1e3) {
+    return `${bytes} B`;
+  }
+  if (bytes < 1e6) {
+    return `${(bytes / 1e3).toFixed(1)} kB`;
+  }
+  return `${(bytes / 1e6).toFixed(1)} MB`;
+}
+async function formatFile(dirPath, name, indent) {
+  try {
+    const stat = await fs9.stat(path4.join(dirPath, name));
+    return `${indent}${name}${" ".repeat(Math.max(1, 30 - indent.length - name.length))}${formatSize(stat.size)}`;
+  } catch {
+    return `${indent}${name}`;
+  }
+}
+var EXCLUDE, MAX_CHILDREN, listDirTool;
 var init_listDir = __esm({
   "src/tools/code/listDir.ts"() {
     "use strict";
+    EXCLUDE = /* @__PURE__ */ new Set([".git", "node_modules"]);
+    MAX_CHILDREN = 15;
     listDirTool = {
       clearable: true,
       definition: {
         name: "listDir",
-        description: "List the contents of a directory. Shows entries with / suffix for directories, sorted directories-first then alphabetically. Use this for a quick overview of a directory's contents. For finding files across the whole project, use glob instead.",
+        description: "List the contents of a directory with one level of subdirectory expansion. Shows file sizes and collapses single-child directory chains (a/b/c/ shown as one entry). Use this for a quick overview of a directory's structure. For finding files across the whole project, use glob instead.",
         inputSchema: {
           type: "object",
           properties: {
@@ -1851,16 +1902,34 @@ var init_listDir = __esm({
       async execute(input) {
         const dirPath = input.path || ".";
         try {
-          const entries = await fs9.readdir(dirPath, { withFileTypes: true });
-          const lines = entries.filter((e) => e.name !== ".git" && e.name !== "node_modules").sort((a, b) => {
-            if (a.isDirectory() && !b.isDirectory()) {
-              return -1;
-            }
-            if (!a.isDirectory() && b.isDirectory()) {
-              return 1;
+          const entries = await readAndSort(dirPath);
+          const lines = [];
+          for (const entry of entries) {
+            if (entry.isDirectory()) {
+              const [displayName, finalPath] = await collapsePath(
+                dirPath,
+                entry.name
+              );
+              lines.push(`${displayName}/`);
+              try {
+                const children = await readAndSort(finalPath);
+                const capped = children.slice(0, MAX_CHILDREN);
+                for (const child of capped) {
+                  if (child.isDirectory()) {
+                    lines.push(`  ${child.name}/`);
+                  } else {
+                    lines.push(await formatFile(finalPath, child.name, "  "));
+                  }
+                }
+                if (children.length > MAX_CHILDREN) {
+                  lines.push(`  ... and ${children.length - MAX_CHILDREN} more`);
+                }
+              } catch {
+              }
+            } else {
+              lines.push(await formatFile(dirPath, entry.name, ""));
             }
-            return a.name.localeCompare(b.name);
-          }).map((e) => e.isDirectory() ? `${e.name}/` : e.name);
+          }
           return lines.join("\n") || "(empty directory)";
         } catch (err) {
           return `Error listing directory: ${err.message}`;
@@ -2154,26 +2223,43 @@ var init_analyzeImage = __esm({
 });
 
 // src/tools/_helpers/screenshot.ts
+function buildScreenshotAnalysisPrompt(opts) {
+  let p = opts?.prompt || SCREENSHOT_ANALYSIS_PROMPT;
+  if (opts?.styleMap) {
+    p += `
+
+The following styleMap describes the computed layout state at the moment of capture. Use it to verify typography, spacing, overflow, and element dimensions \u2014 it is more accurate than visual estimation from the image.
+
+<style_map>
+${opts.styleMap}
+</style_map>`;
+  }
+  p += `
+
+${TEXT_WRAP_DISCLAIMER}`;
+  return p;
+}
 async function captureAndAnalyzeScreenshot(promptOrOptions) {
   let prompt;
   let existingUrl;
   let onLog;
-  let path10;
+  let path11;
   if (typeof promptOrOptions === "object" && promptOrOptions !== null) {
     prompt = promptOrOptions.prompt;
     existingUrl = promptOrOptions.imageUrl;
-    path10 = promptOrOptions.path;
+    path11 = promptOrOptions.path;
     onLog = promptOrOptions.onLog;
   } else {
     prompt = promptOrOptions;
   }
   let url;
+  let styleMap;
   if (existingUrl) {
     url = existingUrl;
   } else {
     const ssResult = await sidecarRequest(
       "/screenshot-full-page",
-      path10 ? { path: path10 } : void 0,
+      path11 ? { path: path11 } : void 0,
       { timeout: 12e4 }
     );
     url = ssResult?.url || ssResult?.screenshotUrl;
@@ -2182,22 +2268,23 @@ async function captureAndAnalyzeScreenshot(promptOrOptions) {
         `No URL in sidecar response. The browser may not be ready yet. Response: ${JSON.stringify(ssResult)}`
       );
     }
+    styleMap = ssResult?.styleMap;
   }
   if (prompt === false) {
     return url;
   }
-  let analysisPrompt = prompt || SCREENSHOT_ANALYSIS_PROMPT;
-  analysisPrompt += `
-Note: ignore text wrapping issues. Screenshots occasionally show text wrapping onto an extra line compared to the live page \u2014 most noticeable in buttons, badges, and headings. This is a known limitation of SVG foreignObject rendering used the DOM-to-image capture library that took the screenshot. The browser's SVG renderer computes slightly wider text metrics than the HTML layout engine, so text that fits on one line in the live DOM can overflow by a fraction of a pixel in the capture - this is not a real issue.
-`;
+  const analysisPrompt = buildScreenshotAnalysisPrompt({
+    prompt: prompt || void 0,
+    styleMap
+  });
   const analysis = await analyzeImage({
     prompt: analysisPrompt,
     imageUrl: url,
     onLog
   });
-  return JSON.stringify({ url, analysis });
+  return JSON.stringify({ url, analysis, ...styleMap ? { styleMap } : {} });
 }
-var SCREENSHOT_ANALYSIS_PROMPT;
+var SCREENSHOT_ANALYSIS_PROMPT, TEXT_WRAP_DISCLAIMER;
 var init_screenshot = __esm({
   "src/tools/_helpers/screenshot.ts"() {
     "use strict";
@@ -2206,6 +2293,7 @@ var init_screenshot = __esm({
     SCREENSHOT_ANALYSIS_PROMPT = `Describe everything visible on screen from top to bottom \u2014 every element, its position, its size relative to the viewport, its colors, its content. Be comprehensive, thorough, and spatial. After the inventory, note anything that looks visually broken (overlapping elements, clipped text, misaligned components).
 
 Respond only with your analysis as Markdown and absolutely no other text. Do not use emojis - use unicode if you need symbols.`;
+    TEXT_WRAP_DISCLAIMER = `Note: ignore text wrapping issues. Screenshots occasionally show text wrapping onto an extra line compared to the live page \u2014 most noticeable in buttons, badges, and headings. This is a known limitation of SVG foreignObject rendering used the DOM-to-image capture library that took the screenshot. The browser's SVG renderer computes slightly wider text metrics than the HTML layout engine, so text that fits on one line in the live DOM can overflow by a fraction of a pixel in the capture - this is not a real issue.`;
   }
 });
 
@@ -2917,19 +3005,19 @@ var init_tools = __esm({
 
 // src/assets.ts
 import fs10 from "fs";
-import path4 from "path";
+import path5 from "path";
 function findRoot(start) {
   let dir = start;
-  while (dir !== path4.dirname(dir)) {
-    if (fs10.existsSync(path4.join(dir, "package.json"))) {
+  while (dir !== path5.dirname(dir)) {
+    if (fs10.existsSync(path5.join(dir, "package.json"))) {
       return dir;
     }
-    dir = path4.dirname(dir);
+    dir = path5.dirname(dir);
   }
   return start;
 }
 function assetPath(...segments) {
-  return path4.join(ASSETS_BASE, ...segments);
+  return path5.join(ASSETS_BASE, ...segments);
 }
 function readAsset(...segments) {
   const full = assetPath(...segments);
@@ -2952,9 +3040,9 @@ var init_assets = __esm({
   "src/assets.ts"() {
     "use strict";
     ROOT = findRoot(
-      import.meta.dirname ?? path4.dirname(new URL(import.meta.url).pathname)
+      import.meta.dirname ?? path5.dirname(new URL(import.meta.url).pathname)
     );
-    ASSETS_BASE = fs10.existsSync(path4.join(ROOT, "dist", "prompt")) ? path4.join(ROOT, "dist") : path4.join(ROOT, "src");
+    ASSETS_BASE = fs10.existsSync(path5.join(ROOT, "dist", "prompt")) ? path5.join(ROOT, "dist") : path5.join(ROOT, "src");
   }
 });
 
@@ -3085,7 +3173,9 @@ var init_browserAutomation = __esm({
                       stepType: "analyzeImage",
                       step: {
                         imageUrl: s.result.url,
-                        prompt: SCREENSHOT_ANALYSIS_PROMPT
+                        prompt: buildScreenshotAnalysisPrompt({
+                          styleMap: s.result.styleMap
+                        })
                       }
                     }));
                     const batchResult = await runCli(
@@ -3290,11 +3380,9 @@ __export(analyzeImage_exports, {
 });
 async function execute4(input, onLog) {
   const imageUrl = input.imageUrl;
-  let prompt = input.prompt || DEFAULT_PROMPT;
-  prompt += `
-
-  Note: ignore text wrapping issues. Screenshots occasionally show text wrapping onto an extra line compared to the live page \u2014 most noticeable in buttons, badges, and headings. This is a known limitation of SVG foreignObject rendering used the DOM-to-image capture library that took the screenshot. The browser's SVG renderer computes slightly wider text metrics than the HTML layout engine, so text that fits on one line in the live DOM can overflow by a fraction of a pixel in the capture - this is not a real issue.
-`;
+  const prompt = buildScreenshotAnalysisPrompt({
+    prompt: input.prompt
+  });
   const analysis = await analyzeImage({
     prompt,
     imageUrl,
@@ -3302,15 +3390,12 @@ async function execute4(input, onLog) {
   });
   return JSON.stringify({ url: imageUrl, analysis });
 }
-var DEFAULT_PROMPT, definition4;
+var definition4;
 var init_analyzeImage2 = __esm({
   "src/subagents/designExpert/tools/analyzeImage.ts"() {
     "use strict";
     init_analyzeImage();
-    DEFAULT_PROMPT = `
-Describe everything visible in this image \u2014 every element, its position, its size relative to the frame, its colors, its content. Be comprehensive, thorough and spatial. After the inventory, note anything that looks visually broken (overlapping elements, clipped text, misaligned components).
-
-Respond only with your analysis as Markdown and absolutely no other text. Do not use emojis - use unicode if you need symbols.`;
+    init_screenshot();
     definition4 = {
       clearable: true,
       name: "analyzeImage",
@@ -3351,13 +3436,26 @@ async function execute5(input, onLog, context) {
         return `Error: browser navigation completed but no screenshot URL was returned. Agent output: ${result}`;
       }
       const url = urlMatch[0];
-      const analysisPrompt = input.prompt || SCREENSHOT_ANALYSIS_PROMPT;
+      let styleMap;
+      try {
+        const parsed = JSON.parse(result);
+        styleMap = parsed?.styleMap;
+      } catch {
+      }
+      const analysisPrompt = buildScreenshotAnalysisPrompt({
+        prompt: input.prompt,
+        styleMap
+      });
       const analysis = await analyzeImage({
         prompt: analysisPrompt,
         imageUrl: url,
         onLog
       });
-      return JSON.stringify({ url, analysis });
+      return JSON.stringify({
+        url,
+        analysis,
+        ...styleMap ? { styleMap } : {}
+      });
     } catch (err) {
       return `Error taking interactive screenshot: ${err.message}`;
     }
@@ -3710,12 +3808,12 @@ var init_tools2 = __esm({
 
 // src/subagents/common/context.ts
 import fs12 from "fs";
-import path5 from "path";
+import path6 from "path";
 function walkMdFiles(dir, skip) {
   const files = [];
   try {
     for (const entry of fs12.readdirSync(dir, { withFileTypes: true })) {
-      const full = path5.join(dir, entry.name);
+      const full = path6.join(dir, entry.name);
       if (entry.isDirectory()) {
         if (!skip?.has(entry.name)) {
           files.push(...walkMdFiles(full, skip));
@@ -4263,7 +4361,7 @@ var init_tools3 = __esm({
 
 // src/subagents/productVision/executor.ts
 import fs14 from "fs";
-import path6 from "path";
+import path7 from "path";
 function formatRequires(requires) {
   return requires.length === 0 ? "[]" : `[${requires.map((r) => `"${r}"`).join(", ")}]`;
 }
@@ -4278,7 +4376,7 @@ async function executeVisionTool(name, input) {
         requires,
         body
       } = input;
-      const filePath = path6.join(ROADMAP_DIR, `${slug}.md`);
+      const filePath = path7.join(ROADMAP_DIR, `${slug}.md`);
       try {
         fs14.mkdirSync(ROADMAP_DIR, { recursive: true });
         const oldContent = fs14.existsSync(filePath) ? fs14.readFileSync(filePath, "utf-8") : "";
@@ -4304,7 +4402,7 @@ ${unifiedDiff(filePath, oldContent, content)}`;
     }
     case "updateRoadmapItem": {
       const { slug } = input;
-      const filePath = path6.join(ROADMAP_DIR, `${slug}.md`);
+      const filePath = path7.join(ROADMAP_DIR, `${slug}.md`);
       try {
         if (!fs14.existsSync(filePath)) {
           return `Error: ${filePath} does not exist`;
@@ -4372,7 +4470,7 @@ ${unifiedDiff(filePath, oldContent, content)}`;
     }
     case "deleteRoadmapItem": {
       const { slug } = input;
-      const filePath = path6.join(ROADMAP_DIR, `${slug}.md`);
+      const filePath = path7.join(ROADMAP_DIR, `${slug}.md`);
       try {
         if (!fs14.existsSync(filePath)) {
           return `Error: ${filePath} does not exist`;
@@ -5592,7 +5690,7 @@ var init_agent = __esm({
 
 // src/prompt/static/projectContext.ts
 import fs16 from "fs";
-import path7 from "path";
+import path8 from "path";
 function loadProjectInstructions() {
   for (const file of AGENT_INSTRUCTION_FILES) {
     try {
@@ -5652,7 +5750,7 @@ function walkMdFiles2(dir) {
   try {
     const entries = fs16.readdirSync(dir, { withFileTypes: true });
     for (const entry of entries) {
-      const full = path7.join(dir, entry.name);
+      const full = path8.join(dir, entry.name);
       if (entry.isDirectory()) {
         results.push(...walkMdFiles2(full));
       } else if (entry.name.endsWith(".md")) {
@@ -5828,7 +5926,7 @@ ${isLspConfigured() ? `<typescript_lsp>
 <conversation_summaries>
 Your conversation history may include <prior_conversation_summary> blocks in the user's messages. These are automated summaries of earlier messages that have been compacted to save context space. The user does not see this summary, they see the full conversation history in their UI. Treat the summary as ground truth for what happened before, but do not reference it directly to the user ("as mentioned in the summary..."). Just continue naturally as if you remember the prior work.
 
-Old tool results are periodically cleared from the conversation to save context space. This is automatic and expected \u2014 you don't need to note down or preserve information from tool results. If you need to reference something from an earlier tool call, just re-read the file or re-run the query, or use your .remy-notes.md file.
+Old tool results are periodically cleared from the conversation to save context space. This is automatic and expected \u2014 you don't need to note down or preserve information from tool results. If you need to reference something from an earlier tool call, just re-read the file or re-run the query.
 </conversation_summaries>
 
 <project_onboarding>
@@ -5864,7 +5962,7 @@ var init_prompt4 = __esm({
 
 // src/config.ts
 import fs17 from "fs";
-import path8 from "path";
+import path9 from "path";
 import os from "os";
 function loadConfigFile() {
   try {
@@ -5905,7 +6003,7 @@ var init_config = __esm({
     "use strict";
     init_logger();
     log7 = createLogger("config");
-    CONFIG_PATH = path8.join(
+    CONFIG_PATH = path9.join(
       os.homedir(),
       ".mindstudio-local-tunnel",
       "config.json"
@@ -6688,6 +6786,9 @@ ${xmlParts}
       if (pending) {
         pendingTools.delete(id);
         pending.resolve(result);
+      } else if (!running) {
+        log10.info("Late tool_result while idle, dismissing", { id });
+        emit("completed", { success: true }, requestId);
       } else {
         earlyResults.set(id, result);
       }
@@ -6819,7 +6920,7 @@ var init_headless = __esm({
 import { render } from "ink";
 import os2 from "os";
 import fs18 from "fs";
-import path9 from "path";
+import path10 from "path";
 
 // src/tui/App.tsx
 import { useState as useState2, useCallback, useRef } from "react";
@@ -7138,7 +7239,7 @@ var startupLog = createLogger("startup");
 function printDebugInfo(config) {
   const pkg = JSON.parse(
     fs18.readFileSync(
-      path9.join(import.meta.dirname, "..", "package.json"),
+      path10.join(import.meta.dirname, "..", "package.json"),
       "utf-8"
     )
   );

package/dist/prompt/compiled/design.md

@@ -25,6 +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, use motion, use iOS/macOS design language and patterns.
 
 ## Layout Stability
 

package/dist/prompt/compiled/interfaces.md

@@ -251,7 +251,7 @@ The human-readable spec. Frontmatter contains structured fields; the prose body
 ```yaml
 ---
 name: Todo Assistant
-model: {"model": "claude-4-5-haiku", "temperature": 0.5, "maxResponseTokens": 15000}
+model: {"model": "claude-4-5-haiku", "temperature": 0.5, "maxResponseTokens": 16000}
 description: Conversational agent that helps users manage their to-do list.
 ---
 ```
@@ -282,7 +282,7 @@ dist/interfaces/agent/
   "agent": {
     "model": "claude-4-5-haiku",
     "temperature": 0.5,
-    "maxTokens": 15000,
+    "maxTokens": 16000,
     "systemPrompt": "system.md",
     "tools": [
       { "method": "create-todo", "description": "tools/createTodo.md" },

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

@@ -127,6 +127,7 @@ const { content } = await agent.generateText({
   modelOverride: {
     model: 'claude-sonnet-4-6',
     temperature: 0.7,
+    maxResponseTokens: 16000,
   },
 });
 ```

package/dist/prompt/sources/llms.txt

@@ -136,6 +136,7 @@ const { content } = await agent.generateText({
   modelOverride: {
     model: model.id,
     temperature: 0.7,
+    maxResponseTokens: 16000,
   },
 });
 ```

package/dist/prompt/static/instructions.md

@@ -17,7 +17,7 @@
 - Pushing to main branch will trigger a deploy. The user presses the publish button in the interface to request publishing.
 
 ### Build Notes
-For complex tasks — especially an initial buildout from a spec or making multiple changes in a single turn — write a `.remy-notes.md` scratchpad in the project root. Use it to track progress: a checklist of what's been built and what's remaining. Never include implementation details or other decisions in the notes - it is solely for keeping track of tasks. Read the spec files directly when you need design details, implementation decisions, or other reference materials. Delete the notes file when your work is done.
+For complex tasks — especially an initial buildout from a spec or making multiple changes in a single turn — write a `.remy-notes.md` scratchpad in the project root. Use it to track progress: a checklist of what's been built and what's remaining. Do not include implementation details or other decisions in the notes - it is solely for keeping track of tasks. Read the spec files directly when you need design details, implementation decisions, or other reference materials. Delete the notes file when your work is done.
 
 ## Communication
 The user can already see your tool calls, so most of your work is visible without narration. Focus text output on three things:

package/package.json

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