@mindstudio-ai/remy 0.1.69 → 0.1.71

package/dist/index.js

@@ -398,6 +398,7 @@ var init_readSpec = __esm({
     init_helpers();
     DEFAULT_MAX_LINES = 500;
     readSpecTool = {
+      clearable: true,
       definition: {
         name: "readSpec",
         description: "Read a spec file from src/ with line numbers. Always read a spec file before editing it. Paths are relative to the project root and must start with src/ (e.g., src/app.md, src/interfaces/web.md).",
@@ -511,6 +512,7 @@ var init_writeSpec = __esm({
     init_helpers();
     init_diff();
     writeSpecTool = {
+      clearable: true,
       definition: {
         name: "writeSpec",
         description: "Create a new spec file or completely overwrite an existing one in src/. Parent directories are created automatically. Use this for new spec files or full rewrites. For targeted changes to existing specs, use editSpec instead.",
@@ -572,6 +574,7 @@ var init_editSpec = __esm({
     init_helpers();
     init_diff();
     editSpecTool = {
+      clearable: true,
       definition: {
         name: "editSpec",
         description: 'Make targeted edits to a spec file by heading path. This is the primary tool for modifying existing specs. Each edit targets a section by its heading hierarchy (e.g., "Vendors > Approval Flow") and applies an operation. Multiple edits are applied in order.',
@@ -714,6 +717,7 @@ var init_listSpecFiles = __esm({
   "src/tools/spec/listSpecFiles.ts"() {
     "use strict";
     listSpecFilesTool = {
+      clearable: false,
       definition: {
         name: "listSpecFiles",
         description: "List all files in the src/ directory (spec files, brand guidelines, interface specs, references). Use this to understand what spec files exist before reading or editing them.",
@@ -747,6 +751,7 @@ var init_clearSyncStatus = __esm({
   "src/tools/spec/clearSyncStatus.ts"() {
     "use strict";
     clearSyncStatusTool = {
+      clearable: false,
       definition: {
         name: "clearSyncStatus",
         description: "Clear the sync status flags after syncing spec and code. Call this after finishing a sync operation.",
@@ -768,6 +773,7 @@ var init_presentSyncPlan = __esm({
   "src/tools/spec/presentSyncPlan.ts"() {
     "use strict";
     presentSyncPlanTool = {
+      clearable: false,
       definition: {
         name: "presentSyncPlan",
         description: "Present a structured sync plan to the user for approval. Write a clear markdown summary of what changed and what you intend to update. The user will see this in a full-screen view and can approve or dismiss. Call this BEFORE making any sync edits.",
@@ -796,6 +802,7 @@ var init_presentPublishPlan = __esm({
   "src/tools/spec/presentPublishPlan.ts"() {
     "use strict";
     presentPublishPlanTool = {
+      clearable: false,
       definition: {
         name: "presentPublishPlan",
         description: "Present a publish changelog to the user for approval. Write a clear markdown summary of what changed since the last deploy. The user will see this in a full-screen view and can approve or dismiss. Call this BEFORE committing or pushing.",
@@ -824,6 +831,7 @@ var init_presentPlan = __esm({
   "src/tools/spec/presentPlan.ts"() {
     "use strict";
     presentPlanTool = {
+      clearable: false,
       definition: {
         name: "presentPlan",
         description: "Present an implementation plan for user approval before making changes. Use this only for large, multi-step changes like new features, new interface types, or when the user explicitly asks to see a plan. Most work should be done autonomously without a plan. Write a clear markdown summary of what you intend to do in plain language \u2014 describe the changes from the user's perspective, not as a list of files and code paths. If the user rejects with feedback, revise and present again.",
@@ -852,19 +860,16 @@ var init_setProjectOnboardingState = __esm({
   "src/tools/common/setProjectOnboardingState.ts"() {
     "use strict";
     setProjectOnboardingStateTool = {
+      clearable: false,
       definition: {
         name: "setProjectOnboardingState",
-        description: "Advance the project onboarding state. Call at natural transition points: before writing the first spec (initialSpecAuthoring), before starting the first code generation (initialCodegen), after the first build succeeds (onboardingFinished). Forward-only progression.",
+        description: "Advance the project onboarding state. Call at natural transition points: after writing the first draft of the spec (initialSpecReview), before starting the first code generation (initialCodegen), after the first build succeeds (onboardingFinished). Forward-only progression.",
         inputSchema: {
           type: "object",
           properties: {
             state: {
               type: "string",
-              enum: [
-                "initialSpecAuthoring",
-                "initialCodegen",
-                "onboardingFinished"
-              ],
+              enum: ["initialSpecReview", "initialCodegen", "onboardingFinished"],
               description: "The onboarding state to advance to."
             }
           },
@@ -884,6 +889,7 @@ var init_promptUser = __esm({
   "src/tools/common/promptUser.ts"() {
     "use strict";
     promptUserTool = {
+      clearable: false,
       definition: {
         name: "promptUser",
         description: 'Ask the user structured questions. Choose type first: "form" for structured intake (5+ questions, takes over screen), "inline" for quick clarifications or confirmations. Blocks until the user responds. Result contains `_dismissed: true` if the user dismisses without answering.',
@@ -1021,6 +1027,7 @@ var init_confirmDestructiveAction = __esm({
   "src/tools/common/confirmDestructiveAction.ts"() {
     "use strict";
     confirmDestructiveActionTool = {
+      clearable: false,
       definition: {
         name: "confirmDestructiveAction",
         description: "Confirm a destructive or irreversible action with the user. Use for things like deleting data, resetting the database, or discarding draft work. Do not use after presentSyncPlan, presentPublishPlan, or presentPlan (those already include approval). Do not use before onboarding state transitions.",
@@ -1144,9 +1151,10 @@ var init_sdkConsultant = __esm({
     "use strict";
     init_runCli();
     askMindStudioSdkTool = {
+      clearable: false,
       definition: {
         name: "askMindStudioSdk",
-        description: "@mindstudio-ai/agent SDK expert. Knows every action, model, connector, and configuration option. Returns architectural guidance and working code. Describe what you want to build, not just what API method you need. Batch related questions into a single query.",
+        description: "@mindstudio-ai/agent backend SDK expert. Knows every backend action, AI model, connector, and configuration option. Returns architectural guidance and working code. Only covers the backend SDK (@mindstudio-ai/agent) \u2014 do NOT use for frontend/interface SDK questions (@mindstudio-ai/interface) like file uploads, auth, or client-side APIs. Describe what you want to build, not just what API method you need. Batch related questions into a single query.",
         inputSchema: {
           type: "object",
           properties: {
@@ -1177,6 +1185,7 @@ var init_searchGoogle = __esm({
     "use strict";
     init_runCli();
     searchGoogleTool = {
+      clearable: false,
       definition: {
         name: "searchGoogle",
         description: "Search Google and return results. Use for research, finding documentation, looking up APIs, or any task where web search would help.",
@@ -1208,6 +1217,7 @@ var init_setProjectMetadata = __esm({
   "src/tools/common/setProjectMetadata.ts"() {
     "use strict";
     setProjectMetadataTool = {
+      clearable: false,
       definition: {
         name: "setProjectMetadata",
         description: "Set project metadata. Can update any combination of: display name, app icon, and Open Graph share image. Provide only the fields you want to change.",
@@ -1253,6 +1263,7 @@ var init_readFile = __esm({
     "use strict";
     DEFAULT_MAX_LINES2 = 500;
     readFileTool = {
+      clearable: true,
       definition: {
         name: "readFile",
         description: "Read a file's contents with line numbers. Always read a file before editing it \u2014 never guess at contents. For large files, consider using symbols first to identify the relevant section, then use offset and maxLines to read just that section. Line numbers in the output correspond to what editFile expects. Defaults to first 500 lines. Use a negative offset to read from the end of the file (e.g., offset: -50 reads the last 50 lines).",
@@ -1321,6 +1332,7 @@ var init_writeFile = __esm({
     "use strict";
     init_diff();
     writeFileTool = {
+      clearable: true,
       definition: {
         name: "writeFile",
         description: "Create a new file or completely overwrite an existing one. Parent directories are created automatically. Use this for new files or full rewrites. For targeted changes to existing files, use editFile instead \u2014 it preserves the parts you don't want to change and avoids errors from forgetting to include unchanged code.",
@@ -1475,6 +1487,7 @@ var init_editFile = __esm({
     init_diff();
     init_helpers2();
     editFileTool = {
+      clearable: true,
       definition: {
         name: "editFile",
         description: "Replace a string in a file. old_string must appear exactly once (minor indentation differences are handled automatically). Set replace_all to true to replace every occurrence at once. For bulk mechanical substitutions (renaming a variable, swapping colors), prefer replace_all. Always read the file first so you know the exact text to match. When editing nested structures (objects, function bodies, arrays, template literals), always include the full enclosing structure in old_string rather than just an inner fragment. Replacing a partial slice from the middle of nested code is the most common source of syntax errors.",
@@ -1568,6 +1581,7 @@ var init_bash = __esm({
     DEFAULT_TIMEOUT_MS = 12e4;
     DEFAULT_MAX_LINES3 = 500;
     bashTool = {
+      clearable: true,
       definition: {
         name: "bash",
         description: "Run a shell command and return stdout + stderr. 120-second timeout by default (configurable). Use for: npm install/build/test, git operations, tsc --noEmit, or any CLI tool. Prefer dedicated tools over bash when available (use grep instead of bash + rg, readFile instead of bash + cat). Output is truncated to 500 lines by default.",
@@ -1657,6 +1671,7 @@ var init_grep = __esm({
     "use strict";
     DEFAULT_MAX = 50;
     grepTool = {
+      clearable: true,
       definition: {
         name: "grep",
         description: "Search file contents for a regex pattern. Returns matching lines with file paths and line numbers (default 50 results). Use this to find where something is used, locate function definitions, or search for patterns across the codebase. For finding a symbol's definition precisely, prefer the definition tool if LSP is available. Automatically excludes node_modules and .git.",
@@ -1718,6 +1733,7 @@ var init_glob = __esm({
     "use strict";
     DEFAULT_MAX2 = 200;
     globTool = {
+      clearable: true,
       definition: {
         name: "glob",
         description: 'Find files matching a glob pattern. Returns matching file paths sorted alphabetically (default 200 results). Use this to discover project structure, find files by name or extension, or check if a file exists. Common patterns: "**/*.ts" (all TypeScript files), "src/**/*.tsx" (React components in src), "*.json" (root-level JSON files). Automatically excludes node_modules and .git.',
@@ -1770,6 +1786,7 @@ var init_listDir = __esm({
   "src/tools/code/listDir.ts"() {
     "use strict";
     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.",
@@ -1811,6 +1828,7 @@ var init_editsFinished = __esm({
   "src/tools/code/editsFinished.ts"() {
     "use strict";
     editsFinishedTool = {
+      clearable: false,
       definition: {
         name: "editsFinished",
         description: "Signal that file edits are complete. Call this after you finish writing/editing files so the live preview updates cleanly. The preview is paused while you edit to avoid showing broken intermediate states \u2014 this unpauses it. If you forget to call this, the preview updates when your turn ends.",
@@ -1891,6 +1909,7 @@ var init_lspDiagnostics = __esm({
     "use strict";
     init_lsp();
     lspDiagnosticsTool = {
+      clearable: true,
       definition: {
         name: "lspDiagnostics",
         description: "Get TypeScript diagnostics (type errors, warnings) for a file, with suggested fixes when available. Use this after editing a file to check for errors.",
@@ -1946,6 +1965,7 @@ var init_restartProcess = __esm({
     "use strict";
     init_lsp();
     restartProcessTool = {
+      clearable: false,
       definition: {
         name: "restartProcess",
         description: "Restart a managed sandbox process. Use this after running npm install or changing package.json to restart the dev server so it picks up new dependencies.",
@@ -1978,6 +1998,7 @@ var init_runScenario = __esm({
   "src/tools/code/runScenario.ts"() {
     "use strict";
     runScenarioTool = {
+      clearable: true,
       definition: {
         name: "runScenario",
         description: "Run a scenario to seed the dev database with test data. Truncates all tables first, then executes the seed function and impersonates the scenario roles. Blocks until complete. Scenario IDs are defined in mindstudio.json. If it fails, check .logs/tunnel.log or .logs/requests.ndjson for details. Return synchronously - no need to sleep before checking results.",
@@ -2005,6 +2026,7 @@ var init_runMethod = __esm({
   "src/tools/code/runMethod.ts"() {
     "use strict";
     runMethodTool = {
+      clearable: true,
       definition: {
         name: "runMethod",
         description: "Run a method in the dev environment and return the result. Use for testing methods after writing or modifying them. Returns output, captured console output, errors with stack traces, and duration. If it fails, check .logs/tunnel.log or .logs/requests.ndjson for more details. Return synchronously - no need to sleep before checking results.",
@@ -2109,6 +2131,7 @@ var init_screenshot2 = __esm({
     "use strict";
     init_screenshot();
     screenshotTool = {
+      clearable: true,
       definition: {
         name: "screenshot",
         description: "Capture a full-height screenshot of the app preview and get a description of what's on screen. Provides static image analysis only, will not capture animations or video. Optionally provide specific questions about what you're looking for. Use a bulleted list to ask many questions at once. To ask additional questions about a screenshot you have already captured, pass its URL as imageUrl to skip recapture.",
@@ -2378,6 +2401,7 @@ async function runSubAgent(config) {
   const fullSystem = `${system}
 
 Current date: ${dateStr}`;
+  const excludeToolsFromClearing = tools2.filter((t) => t.clearable === false).map((t) => t.name);
   let turns = 0;
   const run = async () => {
     const messages = [
@@ -2441,6 +2465,7 @@ ${partial}` : "[INTERRUPTED] Agent was interrupted before producing output.",
             system: fullSystem,
             messages: cleanMessagesForApi(messages),
             tools: tools2,
+            excludeToolsFromClearing,
             signal
           },
           {
@@ -2706,6 +2731,7 @@ var init_tools = __esm({
     "use strict";
     BROWSER_TOOLS = [
       {
+        clearable: true,
         name: "browserCommand",
         description: "Interact with the app's live preview by sending browser commands. Commands execute sequentially with an animated cursor. Always start with a snapshot to see the current state and get ref identifiers. The result includes a snapshot field with the final page state after all steps complete. On error, the failing step has an error field and execution stops. Timeout: 120s.",
         inputSchema: {
@@ -2786,6 +2812,7 @@ var init_tools = __esm({
         }
       },
       {
+        clearable: true,
         name: "screenshotFullPage",
         description: "Capture a full-height screenshot of the current page. Returns a CDN URL with full text analysis and description.",
         inputSchema: {
@@ -2799,6 +2826,7 @@ var init_tools = __esm({
         }
       },
       {
+        clearable: false,
         name: "resetBrowser",
         description: "Reset the browser to a clean state. Call this once after all tests are complete to restore the preview for the user. Fire and forget \u2014 does not wait for the reload to finish.",
         inputSchema: {
@@ -2893,6 +2921,7 @@ var init_browserAutomation = __esm({
     init_logger();
     log4 = createLogger("browser-automation");
     browserAutomationTool = {
+      clearable: true,
       definition: {
         name: "runAutomatedBrowserTest",
         description: "Run an automated browser test against the live preview. Describe what to test \u2014 the agent figures out how. Use after meaningful changes frontend code, to reproduce user-reported issues, or to test end-to-end flows.",
@@ -3027,6 +3056,7 @@ var init_searchGoogle2 = __esm({
     "use strict";
     init_runCli();
     definition = {
+      clearable: false,
       name: "searchGoogle",
       description: 'Search Google for web results. Reserch modern design trends in industries or verticals, "best [domain] apps 2026", ui patterns, or find something specific if the the user has an explicit reference. Searching for and reading case studies is a great way to get information and context about a project\'s domain. Prioritize authoritative sources like Figma and other design leaders, avoid random blog spam. Pick one or more URLs from the results and then use `scrapeWebUrl` to get their text content.',
       inputSchema: {
@@ -3065,6 +3095,7 @@ var init_scrapeWebUrl = __esm({
     "use strict";
     init_runCli();
     definition2 = {
+      clearable: false,
       name: "scrapeWebUrl",
       description: "Fetch the content of a web page as markdown. Use when reading sites from search results or specific things the user wants to incorporate.",
       inputSchema: {
@@ -3139,6 +3170,7 @@ Identify the specific design moves that make this page interesting and unique, d
 Respond only with your analysis as Markdown and absolutely no other text. Do not use emojis - use unicode if you need symbols.
 `;
     definition3 = {
+      clearable: false,
       name: "analyzeDesign",
       description: "Analyze the visual design of a website or image URL. Websites are automatically screenshotted first. Provides static image analysis only, will not capture animations or video. If no prompt is provided, performs a full design reference analysis (mood, color, typography, layout, distinctiveness). Provide a custom prompt to ask a specific design question instead. Use a bulleted list to ask many questions at once.",
       inputSchema: {
@@ -3182,6 +3214,7 @@ var init_analyzeImage2 = __esm({
     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.";
     definition4 = {
+      clearable: true,
       name: "analyzeImage",
       description: "Analyze an image by URL using a vision model. Provides static image analysis only, will not capture animations or video. Returns an objective description of what is visible \u2014 shapes, colors, layout, text, artifacts. Use for factual inventory of image contents, not for subjective design judgment - the vision model providing the analysis has no sense of design. You are the design expert - use the analysis tool for factual inventory, then apply your own expertise for quality and suitability assessments. Optionally provide specific questions about what you're looking for. Use a bulleted list to ask many questions at once. If you are analyzing a screenshot of the app preview, you can reuse the same screenshot URL multiple times to ask multiple questions.",
       inputSchema: {
@@ -3249,6 +3282,7 @@ var init_screenshot3 = __esm({
     init_analyzeImage();
     init_browserAutomation();
     definition5 = {
+      clearable: true,
       name: "screenshot",
       description: "Capture a full-height screenshot of the current app preview. Returns a CDN URL along with visual analysis. Use to review the current state of the UI being built. Remember, the screenshot analysis is not overly precise - for example, it cannot reliably identify specific fonts by name \u2014 it can only describe what letterforms look like.",
       inputSchema: {
@@ -3449,6 +3483,7 @@ var init_generateImages = __esm({
     "use strict";
     init_imageGenerator();
     definition6 = {
+      clearable: false,
       name: "generateImages",
       description: "Generate images. Returns CDN URLs with a quality analysis for each image. Produces high-quality results for everything from photorealistic images and abstract/creative visuals. Pass multiple prompts to generate in parallel. No need to analyze images separately after generating \u2014 the analysis is included.",
       inputSchema: {
@@ -3502,6 +3537,7 @@ var init_editImages = __esm({
     "use strict";
     init_imageGenerator();
     definition7 = {
+      clearable: false,
       name: "editImages",
       description: "Edit or transform existing images. Provide one or more source image URLs as reference and a prompt describing the desired edit. Use for compositing, style transfer, subject transformation, blending multiple references, or incorporating one or more references into something new. Returns CDN URLs with analysis.",
       inputSchema: {
@@ -3623,15 +3659,19 @@ function loadPlatformBrief() {
   return `<platform_brief>
 ## What is a MindStudio app?
 
-A MindStudio app is a managed TypeScript project with three layers: a spec (natural language in src/), a backend contract (methods, tables, roles in dist/), and one or more interfaces (web, API, bots, cron, etc.). The spec is the source of truth; code is derived from it.
+A MindStudio app is a managed full-stack TypeScript project with three layers: a spec (natural language in src/), a backend contract (methods, tables, roles in dist/), and one or more interfaces (web, API, bots, cron, etc.). The spec is the source of truth; code is derived from it.
+
+This is a capable, stable platform used in production by 100k+ users. Build with confidence \u2014 you're building production-grade apps, not fragile prototypes.
 
 ## What people build
 
-- Business tools \u2014 dashboards, admin panels, approval workflows, data entry apps, internal tools with role-based access
-- AI-powered apps \u2014 chatbots, content generators, document processors, image/video tools, AI agents that take actions
+- Business tools \u2014 client portals, approval workflows, admin panels with role-based access
+- AI-powered apps \u2014 document processors, image/video tools, content generators, conversational agents that take actions
+- 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
-- Creative/interactive projects \u2014 games, interactive visualizations, generative art, portfolio sites
+- 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
 
@@ -3656,13 +3696,12 @@ Each interface type invokes the same backend methods. Methods don't know which i
 TypeScript running in a sandboxed environment. Any npm package can be installed. Key capabilities:
 
 - Managed SQLite database with typed schemas and automatic migrations. Define a TypeScript interface, push, and the platform handles diffing and migrating.
-- Built-in role-based auth. Define roles in the manifest, gate methods with auth.requireRole(). Platform handles sessions, tokens, user resolution.
-- Sandboxed execution with npm packages pre-installed.
+- Built-in app-managed auth. Opt-in via manifest \u2014 developer builds login UI, platform handles verification codes (email/SMS), cookie sessions, and role enforcement. Backend methods use auth.requireRole() for access control.
 - Git-native deployment. Push to default branch to deploy.
 
 ## MindStudio SDK
 
-The first-party SDK (@mindstudio-ai/agent) provides 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, and much more) with zero configuration \u2014 credentials are handled automatically in the execution environment. No API keys needed.
+The first-party SDK (@mindstudio-ai/agent) provides 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, and much more) with zero configuration \u2014 credentials are handled automatically in the execution environment. No API keys needed. This SDK is robust and battle-tested in production.
 
 ## What MindStudio apps are NOT good for
 
@@ -3910,6 +3949,7 @@ var init_designExpert = __esm({
 Visual design expert. Describe the situation and what you need \u2014 the agent decides what to deliver. It reads the spec files automatically. Include relevant user requirements and context it can't get from the spec, but do not list specific deliverables or tell it how to do its job. Do not suggest implementation details or ideas - only relay what is needed.
 `.trim();
     designExpertTool = {
+      clearable: false,
       definition: {
         name: "visualDesignExpert",
         description: DESCRIPTION,
@@ -4244,6 +4284,7 @@ var init_productVision = __esm({
     init_prompt3();
     init_history();
     productVisionTool = {
+      clearable: false,
       definition: {
         name: "productVision",
         description: "Owns the product roadmap. Reads spec and roadmap files automatically. Creates, updates, and deletes roadmap items in src/roadmap/. Describe the situation and what needs to happen.",
@@ -4409,6 +4450,7 @@ var init_codeSanityCheck = __esm({
     init_tools4();
     BASE_PROMPT3 = readAsset("subagents/codeSanityCheck", "prompt.md");
     codeSanityCheckTool = {
+      clearable: false,
       definition: {
         name: "codeSanityCheck",
         description: 'Quick sanity check on an approach before building. Reviews architecture, package choices, and flags potential issues. Usually responds with "looks good." Occasionally catches something important. Readonly \u2014 can search the web and read code but cannot modify anything.',
@@ -4464,6 +4506,7 @@ var init_scrapeWebUrl2 = __esm({
     "use strict";
     init_runCli();
     scrapeWebUrlTool = {
+      clearable: false,
       definition: {
         name: "scrapeWebUrl",
         description: "Scrape the content of a web page. Returns the HTML of the page as markdown text. Optionally capture a screenshot if you need see the visual design. Use this when you need to fetch or analyze content from a website",
@@ -4512,7 +4555,7 @@ function executeTool(name, input, context) {
   }
   return tool.execute(input, context);
 }
-var ALL_TOOLS;
+var ALL_TOOLS, CLEARABLE_TOOLS;
 var init_tools5 = __esm({
   "src/tools/index.ts"() {
     "use strict";
@@ -4587,6 +4630,9 @@ var init_tools5 = __esm({
       lspDiagnosticsTool,
       restartProcessTool
     ];
+    CLEARABLE_TOOLS = new Set(
+      ALL_TOOLS.filter((t) => t.clearable).map((t) => t.definition.name)
+    );
   }
 });
 
@@ -4901,6 +4947,7 @@ async function runTurn(params) {
     onBackgroundComplete
   } = params;
   const tools2 = getToolDefinitions(onboardingState);
+  const excludeToolsFromClearing = tools2.filter((t) => !CLEARABLE_TOOLS.has(t.name)).map((t) => t.name);
   log6.info("Turn started", {
     requestId,
     model,
@@ -4910,11 +4957,17 @@ async function runTurn(params) {
     }
   });
   onEvent({ type: "turn_started" });
+  const hasText = userMessage.trim().length > 0;
+  const hasAttachments = attachments && attachments.length > 0;
+  if (!hasText && !hasAttachments) {
+    onEvent({ type: "error", error: "Empty message" });
+    return;
+  }
   const userMsg = { role: "user", content: userMessage };
   if (hidden) {
     userMsg.hidden = true;
   }
-  if (attachments && attachments.length > 0) {
+  if (hasAttachments) {
     userMsg.attachments = attachments;
   }
   state.messages.push(userMsg);
@@ -5040,6 +5093,7 @@ async function runTurn(params) {
           system,
           messages: cleanMessagesForApi(state.messages),
           tools: tools2,
+          excludeToolsFromClearing,
           signal
         },
         {
@@ -5358,6 +5412,7 @@ var init_agent = __esm({
     init_statusWatcher();
     init_errors();
     init_cleanMessages();
+    init_tools5();
     log6 = createLogger("agent");
     EXTERNAL_TOOLS = /* @__PURE__ */ new Set([
       "promptUser",
@@ -5698,7 +5753,7 @@ var init_config = __esm({
 });
 
 // src/compaction/index.ts
-async function compactConversation(state, apiConfig) {
+async function compactConversation(state, apiConfig, system, tools2) {
   const insertionIndex = findSafeInsertionPoint(state.messages);
   const summaries = [];
   const tasks = [];
@@ -5712,7 +5767,9 @@ async function compactConversation(state, apiConfig) {
         apiConfig,
         "conversation",
         CONVERSATION_SUMMARY_PROMPT,
-        conversationMessages
+        conversationMessages,
+        system,
+        tools2
       ).then((text) => {
         if (text) {
           summaries.push({ name: "conversation", text });
@@ -5732,7 +5789,9 @@ async function compactConversation(state, apiConfig) {
           apiConfig,
           name,
           SUBAGENT_SUMMARY_PROMPT,
-          subagentMessages
+          subagentMessages,
+          system,
+          tools2
         ).then((text) => {
           if (text) {
             summaries.push({ name, text });
@@ -5859,22 +5918,33 @@ function serializeForSummary(messages) {
     return `[${msg.role}]: ${parts.join("\n")}`;
   }).join("\n\n");
 }
-async function generateSummary(apiConfig, name, systemPrompt, messagesToSummarize) {
+async function generateSummary(apiConfig, name, compactionPrompt, messagesToSummarize, mainSystem, mainTools) {
   const serialized = serializeForSummary(messagesToSummarize);
   if (!serialized.trim()) {
     return null;
   }
   log8.info("Generating summary", {
     name,
-    messageCount: messagesToSummarize.length
+    messageCount: messagesToSummarize.length,
+    cacheReuse: !!mainSystem
   });
   let summaryText = "";
+  const useMainCache = !!mainSystem;
+  const system = useMainCache ? mainSystem : compactionPrompt;
+  const tools2 = useMainCache ? mainTools ?? [] : [];
+  const userContent = useMainCache ? `${compactionPrompt}
+
+---
+
+Conversation to summarize:
+
+${serialized}` : serialized;
   for await (const event of streamChat({
     ...apiConfig,
     subAgentId: "conversationSummarizer",
-    system: systemPrompt,
-    messages: [{ role: "user", content: serialized }],
-    tools: []
+    system,
+    messages: [{ role: "user", content: userContent }],
+    tools: tools2
   })) {
     if (event.type === "text") {
       summaryText += event.text;
@@ -6088,6 +6158,7 @@ async function startHeadless(opts = {}) {
   let currentAbort = null;
   let currentRequestId;
   let completedEmitted = false;
+  let turnStart = 0;
   const EXTERNAL_TOOL_TIMEOUT_MS = 3e5;
   const pendingTools = /* @__PURE__ */ new Map();
   const earlyResults = /* @__PURE__ */ new Map();
@@ -6200,8 +6271,8 @@ ${xmlParts}
   function onEvent(e) {
     const rid = currentRequestId;
     switch (e.type) {
-      // Suppressed — caller already knows the request started
       case "turn_started":
+        emit("turn_started", {}, rid);
         return;
       // Terminal events — translate to `completed`
       case "turn_done":
@@ -6220,7 +6291,11 @@ ${xmlParts}
           writeFileSync(".remy-stats.json", JSON.stringify(sessionStats));
         } catch {
         }
-        emit("completed", { success: true }, rid);
+        emit(
+          "completed",
+          { success: true, durationMs: Date.now() - turnStart },
+          rid
+        );
         setTimeout(() => {
           applyPendingBlockUpdates();
           flushBackgroundQueue();
@@ -6360,7 +6435,7 @@ ${xmlParts}
     currentRequestId = requestId;
     currentAbort = new AbortController();
     completedEmitted = false;
-    const turnStart = Date.now();
+    turnStart = Date.now();
     const attachments = parsed.attachments;
     if (attachments?.length) {
       console.warn(
@@ -6505,7 +6580,9 @@ ${xmlParts}
         writeFileSync(".remy-stats.json", JSON.stringify(sessionStats));
       } catch {
       }
-      compactConversation(state, config).then(() => {
+      const compactSystem = buildSystemPrompt("onboardingFinished");
+      const compactTools = getToolDefinitions("onboardingFinished");
+      compactConversation(state, config, compactSystem, compactTools).then(() => {
         saveSession(state);
         emit("compaction_complete", {}, requestId);
         emit("completed", { success: true }, requestId);
@@ -6564,6 +6641,7 @@ var init_headless = __esm({
     init_config();
     init_prompt4();
     init_compaction();
+    init_tools5();
     init_lsp();
     init_agent();
     init_session();