@mindstudio-ai/remy 0.1.267 → 0.1.268

package/dist/automatedActions/publish.md

@@ -12,9 +12,9 @@ If approved:
 - Stage and commit any uncommitted changes with a clean, descriptive commit message. If the committed work resolves any open issues (`mindstudio-prod issues`), reference them in the commit message with a closing keyword — `fixes #42`, `closes #7` — so the deploy closes them automatically once it goes live.
 - Push to main
 - Use `mindstudio-prod releases wait` to poll the build until it completes. Let the user know it's deploying, then report back when it's live.
-- Once the deploy is live, give the project's collateral a pass — both hand-offs run in the background, so dispatch them and move on without waiting: call `specSync` with a brief batching everything that changed this session and `refreshBuildOverview: true` (it reconciles the spec, then re-authors the Build Overview from it), and notify `productVision` about what shipped so the roadmap and pitch deck stay current.
+- Once the deploy is live, scale the close-out to what shipped — the changelog you just wrote is the measure. For a meaningful release (new features, interfaces, real behavior changes): dispatch `specSync` with a brief batching everything that changed this session and `refreshBuildOverview: true` (it reconciles the spec, then re-authors the Build Overview from it), and notify `productVision` about what shipped so the roadmap and pitch deck stay current — both run in the background, so hand off and move on without waiting. For a hotfix or small tweak, skip the ceremony: a plain `specSync` (no flag) only if documented behavior actually changed.
 - Once deployed, offer to help with next steps. This includes technical steps likesetting up a custom domain (`mindstudio-prod domains`), checking for errors (`mindstudio-prod requests stats`), seeding production data (`mindstudio-prod db`), managing env vars/secrets, or anything else they need for launch. It also includes going above and beyond and helping holistically. If it's the initial deploy, offer to help create collateral to announce the launch (e.g., an image for sharing on social media, text copy for a post, etc); if it's a meaningful incremental update, an annoucement post or something similar - go above and beyond here to help the user see that you care about the product from end-to-end, not just writing code! They will be appreciative, grateful, and pleased with your creativity here. Refer to the design guidance in the spec for how to talk about the product, and consider consulting the design expert to generate images or other marketing collateral.
 
-After everything is done, call `compactConversation` to summarize the current session and free up context for the next phase of work.
+After everything is done, if this was a meaningful release, call `compactConversation` to summarize the session and free up context for the next phase of work. After a hotfix, don't bother.
 
 If dismissed, acknowledge and do nothing.

package/dist/headless.js

@@ -1043,7 +1043,6 @@ function extractFrontmatter(content) {
 var DEFAULT_MAX_LINES = 500;
 var readSpecTool = {
   definition: {
-    clearable: true,
     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).",
     inputSchema: {
@@ -1157,7 +1156,6 @@ function acquireFileLock(filePath) {
 // src/tools/spec/writeSpec.ts
 var writeSpecTool = {
   definition: {
-    clearable: true,
     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.",
     inputSchema: {
@@ -1295,7 +1293,6 @@ function formatOccurrenceError(count, lines, filePath) {
 // src/tools/spec/editSpec.ts
 var editSpecTool = {
   definition: {
-    clearable: true,
     name: "editSpec",
     description: "Make a targeted find/replace edit to a spec file (src/*.md). old_string must appear exactly once (minor indentation differences are handled automatically); set replace_all to true to replace every occurrence. Read the file with readSpec first so you match the exact text, and include the full enclosing structure rather than an inner fragment. The file's YAML frontmatter (the leading --- \u2026 --- block, which holds required fields like name) is protected \u2014 an edit that would remove or malform it is refused. For a full rewrite, use writeSpec.",
     inputSchema: {
@@ -1400,7 +1397,6 @@ import fs9 from "fs/promises";
 import path6 from "path";
 var listSpecFilesTool = {
   definition: {
-    clearable: false,
     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.",
     inputSchema: {
@@ -1451,7 +1447,6 @@ async function listRecursive(dir) {
 // src/tools/spec/presentPublishPlan.ts
 var presentPublishPlanTool = {
   definition: {
-    clearable: false,
     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.",
     inputSchema: {
@@ -1476,7 +1471,6 @@ import fs10 from "fs/promises";
 var PLAN_FILE = ".remy-plan.md";
 var writePlanTool = {
   definition: {
-    clearable: false,
     name: "writePlan",
     description: "Write 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. The plan is displayed standalone in the UI with approve/reject buttons attached. The plan body ends with its last substantive section \u2014 do not write any closing line addressed to the reader. No 'If this lands, I'll start building,' no 'Let me know what to adjust,' no 'Approve when ready,' no trailing horizontal rule with a sign-off. Wrap-up text belongs in your chat message alongside the plan, not in the plan file. If the user asks for revisions, call this tool again with updated content to overwrite the plan.",
     inputSchema: {
@@ -1507,7 +1501,6 @@ import fs11 from "fs/promises";
 var PLAN_FILE2 = ".remy-plan.md";
 var updatePlanStatusTool = {
   definition: {
-    clearable: false,
     name: "updatePlanStatus",
     description: 'Update the status of the current implementation plan. Use when the user approves or rejects the plan via chat (e.g. "looks good, go ahead" or "scrap it"). Approving sets the plan to active so you can begin implementation. Rejecting deletes the plan.',
     inputSchema: {
@@ -1549,7 +1542,6 @@ var updatePlanStatusTool = {
 // src/tools/common/setProjectOnboardingState.ts
 var setProjectOnboardingStateTool = {
   definition: {
-    clearable: false,
     name: "setProjectOnboardingState",
     description: "Advance the project onboarding state. Forward-only: building \u2192 buildComplete \u2192 onboardingFinished. Normally driven by automated actions \u2014 don't call this out of order during a normal build, or you'll skip stages the user hasn't experienced. Exception: if the project has been in `building` for a while, the build is clearly done (the user is iterating on a working app, deploying, etc.), and the user reports the editor seems stuck \u2014 disabled Preview/Spec/Code tabs, no reveal, etc. \u2014 call `setProjectOnboardingState({ state: 'buildComplete' })` to unstick them. `onboardingFinished` is always set by the frontend after the user dismisses the reveal; never call it yourself.",
     inputSchema: {
@@ -1572,7 +1564,6 @@ var setProjectOnboardingStateTool = {
 // src/tools/common/promptUser.ts
 var promptUserTool = {
   definition: {
-    clearable: false,
     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.',
     inputSchema: {
@@ -1704,7 +1695,6 @@ ${lines.join("\n")}`;
 // src/tools/common/confirmDestructiveAction.ts
 var confirmDestructiveActionTool = {
   definition: {
-    clearable: false,
     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 presentPublishPlan or writePlan (those already include approval). Do not use before onboarding state transitions.",
     inputSchema: {
@@ -1878,7 +1868,6 @@ function runCli(command, args, options) {
 // src/subagents/sdkConsultant/index.ts
 var askMindStudioSdkTool = {
   definition: {
-    clearable: false,
     name: "askMindStudioSdk",
     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: {
@@ -2019,7 +2008,6 @@ function stripDollarKeys(envelope) {
 // src/tools/common/searchGoogle.ts
 var searchGoogleTool = {
   definition: {
-    clearable: false,
     name: "searchGoogle",
     description: "Search Google and return results. Use for research, finding documentation, looking up APIs, or any task where web search would help.",
     inputSchema: {
@@ -2050,7 +2038,6 @@ var searchGoogleTool = {
 // src/tools/common/setProjectMetadata.ts
 var setProjectMetadataTool = {
   definition: {
-    clearable: false,
     name: "setProjectMetadata",
     description: "Set project metadata. Can update any combination of: display name, short description, app icon, and Open Graph share image. Provide only the fields you want to change.",
     inputSchema: {
@@ -2089,7 +2076,6 @@ var compactConversationTool = {
   // call (cleanMessagesForApi).
   backgroundNotify: "silent",
   definition: {
-    clearable: false,
     name: "compactConversation",
     description: "Compact the conversation history by summarizing older messages into a checkpoint. The summary preserves key decisions, what was built, and the current state of the project, but drops the verbose tool results, diffs, and intermediate steps that are no longer useful. Runs in the background.",
     inputSchema: {
@@ -2135,7 +2121,6 @@ var compactConversationTool = {
 // src/tools/common/loadSkill.ts
 var loadSkillTool = {
   definition: {
-    clearable: true,
     name: "loadSkill",
     description: "Load the full reference for a platform capability that isn't in your system prompt \u2014 task agents, agent interfaces, voice interfaces, MCP interfaces, data sources. The available skills and the trigger for each are listed in <available_skills>. Load one before writing code in its area, not after: these are APIs where a plausible-looking guess is usually wrong. Calling this is cheap and expected \u2014 if you're unsure whether you need it, load it. Only covers the capabilities listed in the catalog; for backend SDK actions and model IDs use askMindStudioSdk.",
     inputSchema: {
@@ -2186,7 +2171,6 @@ function isBinary(buffer) {
 }
 var readFileTool = {
   definition: {
-    clearable: true,
     name: "readFile",
     description: "Read a file's contents with line numbers. Always read a file before editing it \u2014 never guess at contents. By default returns the first 500 lines, and at most 64KB \u2014 a file with very wide lines (a CSV, a minified bundle) comes back short of 500 lines, so read a narrower range or grep rather than paging through it. To read a specific range, pass startLine and endLine (1-indexed, inclusive) \u2014 e.g. to read lines 253\u2013343, pass startLine: 253, endLine: 343. To read the end of a file or log, pass tail (the number of lines from the end). Line numbers in the output correspond to what editFile expects. For a large file, locate the relevant section first (symbols or grep), then read just that range.",
     inputSchema: {
@@ -2290,7 +2274,6 @@ import fs14 from "fs/promises";
 import path7 from "path";
 var writeFileTool = {
   definition: {
-    clearable: true,
     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.",
     inputSchema: {
@@ -2356,7 +2339,6 @@ ${unifiedDiff(input.path, oldContent ?? "", input.content)}`;
 import fs15 from "fs/promises";
 var editFileTool = {
   definition: {
-    clearable: true,
     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.",
     inputSchema: {
@@ -2449,7 +2431,6 @@ var DEFAULT_MAX_LINES2 = 500;
 var MAX_OUTPUT_BYTES = 3e4;
 var bashTool = {
   definition: {
-    clearable: true,
     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 or 30KB, whichever comes first. If a command would emit a lot of data, narrow it down (grep, head/tail, --short flags) rather than reading everything.",
     inputSchema: {
@@ -2571,7 +2552,6 @@ function formatResults(stdout, max, mode) {
 }
 var grepTool = {
   definition: {
-    clearable: true,
     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. Set outputMode to 'count' for per-file match counts (like grep -c) or 'filesWithMatches' for just the file paths (like grep -l). Add context (like grep -C), or contextBefore/contextAfter (like grep -B/-A), to include surrounding lines. Set caseInsensitive (like grep -i) for a case-insensitive search. For finding a symbol's definition precisely, prefer the definition tool if LSP is available. Automatically excludes node_modules and .git.",
     inputSchema: {
@@ -2683,7 +2663,6 @@ import fg from "fast-glob";
 var DEFAULT_MAX2 = 200;
 var globTool = {
   definition: {
-    clearable: true,
     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.',
     inputSchema: {
@@ -2781,7 +2760,6 @@ async function formatFile(dirPath, name, indent) {
 }
 var listDirTool = {
   definition: {
-    clearable: true,
     name: "listDir",
     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: {
@@ -2858,7 +2836,6 @@ var listDirTool = {
 // src/tools/code/editsFinished.ts
 var editsFinishedTool = {
   definition: {
-    clearable: false,
     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.",
     inputSchema: {
@@ -2925,7 +2902,6 @@ async function lspRequest(endpoint, body) {
 // src/tools/code/lspDiagnostics.ts
 var lspDiagnosticsTool = {
   definition: {
-    clearable: true,
     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.",
     inputSchema: {
@@ -2974,7 +2950,6 @@ var lspDiagnosticsTool = {
 // src/tools/code/restartProcess.ts
 var restartProcessTool = {
   definition: {
-    clearable: false,
     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.",
     inputSchema: {
@@ -3001,7 +2976,6 @@ var restartProcessTool = {
 // src/tools/code/runScenario.ts
 var runScenarioTool = {
   definition: {
-    clearable: true,
     name: "runScenario",
     description: "Run a scenario to seed the dev database with test data. By default truncates all tables first, then executes the seed function and impersonates the scenario roles. Use skipTruncate to run the seed function against existing data without resetting. 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.",
     inputSchema: {
@@ -3027,7 +3001,6 @@ var runScenarioTool = {
 // src/tools/code/runMethod.ts
 var runMethodTool = {
   definition: {
-    clearable: true,
     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. Returns synchronously \u2014 no need to sleep before checking results.\n\nBy default methods run unauthenticated. If the method is auth-gated (calls `auth.requireRole()`, filters on `auth.userId`, etc.), pass `userId: "testUser"` to run as the default test user \u2014 no scenario setup required, no userId lookup.',
     inputSchema: {
@@ -3062,7 +3035,6 @@ var runMethodTool = {
 // src/tools/code/queryDatabase.ts
 var queryDatabaseTool = {
   definition: {
-    clearable: true,
     name: "queryDatabase",
     description: "Execute a raw SQL query against the dev database and return the results. Use for inspecting data and debugging issues.",
     inputSchema: {
@@ -4134,7 +4106,6 @@ var COMMON_READ_TOOL_NAMES = new Set(
 // src/subagents/browserAutomation/tools.ts
 var BROWSER_TOOLS = [
   {
-    clearable: false,
     name: "setupBrowser",
     description: "Pre-authenticate the browser and optionally navigate to a starting page. Call this before interacting with authenticated content instead of manually logging in. Auth is optional \u2014 omit to just navigate without authenticating.",
     inputSchema: {
@@ -4167,7 +4138,6 @@ var 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. Batches that contain an interactive step (click, type, select) also return a `recording` object \u2014 one chunk of a continuous per-session rrweb recording that the viewer stitches into a single replay (not a standalone per-call clip). Timeout: 120s.",
     inputSchema: {
@@ -4584,7 +4554,6 @@ async function runBrowserAutomation(task, context, opts) {
 }
 var browserAutomationTool = {
   definition: {
-    clearable: true,
     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 to frontend code, to reproduce user-reported issues, or to test end-to-end flows. Never give it explicit values to use when filling out forms or creating accounts \u2014 it will use its own judgement (often it needs specific values to trigger dev-mode bypasses of things like login verification codes).",
     inputSchema: {
@@ -4614,7 +4583,6 @@ var browserAutomationTool = {
 
 // src/tools/code/screenshot.ts
 var screenshotDefinition = {
-  clearable: true,
   name: "screenshot",
   description: "Capture a screenshot of the app preview and get a description of what's on screen. Choose `fullPage`: `false` captures just the visible viewport (fast \u2014 for a specific section the page is scrolled to), `true` captures the entire page top-to-bottom (slower \u2014 for overall composition or content past the fold). Captures the settled page state \u2014 it cannot catch animations, transitions, or transient state. The analysis is not precise about every detail \u2014 for example it cannot reliably identify specific fonts by name, only describe what the letterforms look like. 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; `imageUrl` also accepts the disk path of an image file (a user upload, a saved asset) to analyze that instead of the preview. If the screenshot requires interaction first (logging in, clicking a tab, dismissing a modal, scrolling to a section), use the instructions param to describe the steps. To render a fixed-size image such as an Open Graph share card, set `width` and `height` (e.g. 1200 \xD7 630) and `format: 'png'`: the tool navigates to `path`, clips to exactly those pixel dimensions, and returns the image URL.",
   inputSchema: {
@@ -4720,7 +4688,6 @@ __export(searchGoogle_exports, {
   execute: () => execute
 });
 var 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: {
@@ -4753,7 +4720,6 @@ __export(scrapeWebUrl_exports, {
   execute: () => execute2
 });
 var 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: {
@@ -4811,7 +4777,6 @@ 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.
 `;
 var definition3 = {
-  clearable: false,
   name: "analyzeDesign",
   description: "Analyze the visual design of a website, an image URL, or an image file on disk. 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: {
@@ -4876,7 +4841,6 @@ __export(analyzeImage_exports, {
   execute: () => execute4
 });
 var definition4 = {
-  clearable: true,
   name: "analyzeImage",
   description: "Analyze an image 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: {
@@ -5110,7 +5074,6 @@ async function generateImageAssets(opts) {
 
 // src/subagents/designExpert/tools/images/generateImages.ts
 var definition5 = {
-  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: {
@@ -5178,7 +5141,6 @@ __export(editImages_exports, {
   execute: () => execute6
 });
 var definition6 = {
-  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: {
@@ -5256,7 +5218,6 @@ var COPY_EDITOR_TOOLS = [...COMMON_READ_TOOLS];
 var BASE_PROMPT2 = readAsset("subagents/copyEditor", "prompt.md");
 var copyEditorTool = {
   definition: {
-    clearable: false,
     name: "copyEditor",
     description: "Hand it user-facing copy and it hands back a sharper version \u2014 better structured for its audience and free of the overused words, telltale constructions, and rhythms that make text read as AI-generated. Think of it as a design expert for words: it elevates how the copy communicates and strips the AI fingerprints, but it never invents facts or claims you didn't give it. Use it on anything users will read: in-app strings, empty states, errors, the Build Overview, deck copy, launch posts, Slack announcements. Readonly.",
     inputSchema: {
@@ -5304,7 +5265,6 @@ var copyEditorTool = {
 
 // src/subagents/designExpert/tools/polishCopy.ts
 var definition7 = {
-  clearable: false,
   name: "polishCopy",
   description: "Hand off any user-facing copy you've written \u2014 headlines, captions, labels, body text \u2014 and get back a sharper version: better built for its audience and free of the fingerprints that make writing read as AI. It elevates how the copy communicates without inventing facts or claims you didn't give it. Give it the text plus what it's for (where it appears, the audience).",
   inputSchema: {
@@ -5656,7 +5616,6 @@ async function runDesignExpert(opts, context) {
 }
 var designExpertTool = {
   definition: {
-    clearable: false,
     name: "visualDesignExpert",
     description: DESCRIPTION,
     inputSchema: {
@@ -5864,7 +5823,6 @@ function getProductVisionPrompt() {
 // src/subagents/productVision/index.ts
 var productVisionTool = {
   definition: {
-    clearable: false,
     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.",
     inputSchema: {
@@ -5977,7 +5935,6 @@ var SANITY_CHECK_TOOLS = [
 var BASE_PROMPT4 = readAsset("subagents/codeSanityCheck", "prompt.md");
 var codeSanityCheckTool = {
   definition: {
-    clearable: false,
     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.',
     inputSchema: {
@@ -6112,7 +6069,6 @@ ${result.text}`;
 }
 var buildOverviewTool = {
   definition: {
-    clearable: false,
     name: "writeBuildOverview",
     description: "Generate or refresh the Build Overview \u2014 the project's home page in the Spec tab: a single-page, plain-language reference of everything the app actually contains, including the parts the user can't see (data stores, backend operations, access and roles, background jobs, seeded scenarios, the design system). You author the full copy: read the manifest and spec and state, plainly and exactly, what genuinely exists \u2014 real names and accurate counts \u2014 in calm, declarative, present-tense outcome language, with no persuasion or hype. Describe only what exists. Pass the complete copy as `content`; the design expert lays it out and skins it to the app's brand using your copy verbatim \u2014 it typesets your words, it does not rewrite them, so polish the copy before you pass it. Generate it at the end of a build; routine refreshes ride specSync's `refreshBuildOverview` flag instead, so call this directly only for the initial generation or when the user explicitly asks.",
     inputSchema: {
@@ -6173,7 +6129,6 @@ var specSyncTool = {
   // next real turn as a hidden background_results note instead.
   backgroundNotify: "passive",
   definition: {
-    clearable: false,
     name: "specSync",
     description: "Reconcile the spec to bring it in line with code changes you have made. Provide a brief, bulleted list of what changed and why; it finds the affected spec sections and updates them to match. Set `refreshBuildOverview` after a deploy or a large milestone to also re-author the Build Overview from the updated spec. Always runs in the background and completes silently \u2014 do not wait for it; its outcome appears as an automated note at the start of a later turn.",
     inputSchema: {
@@ -6260,7 +6215,6 @@ After reconciling the spec, refresh the Build Overview: author the complete upda
 // src/tools/common/scrapeWebUrl.ts
 var scrapeWebUrlTool = {
   definition: {
-    clearable: false,
     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",
     inputSchema: {

package/dist/index.js

@@ -403,7 +403,6 @@ var init_readSpec = __esm({
     DEFAULT_MAX_LINES = 500;
     readSpecTool = {
       definition: {
-        clearable: true,
         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).",
         inputSchema: {
@@ -536,7 +535,6 @@ var init_writeSpec = __esm({
     init_fileLock();
     writeSpecTool = {
       definition: {
-        clearable: true,
         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.",
         inputSchema: {
@@ -687,7 +685,6 @@ var init_editSpec = __esm({
     init_fileLock();
     editSpecTool = {
       definition: {
-        clearable: true,
         name: "editSpec",
         description: "Make a targeted find/replace edit to a spec file (src/*.md). old_string must appear exactly once (minor indentation differences are handled automatically); set replace_all to true to replace every occurrence. Read the file with readSpec first so you match the exact text, and include the full enclosing structure rather than an inner fragment. The file's YAML frontmatter (the leading --- \u2026 --- block, which holds required fields like name) is protected \u2014 an edit that would remove or malform it is refused. For a full rewrite, use writeSpec.",
         inputSchema: {
@@ -821,7 +818,6 @@ var init_listSpecFiles = __esm({
     "use strict";
     listSpecFilesTool = {
       definition: {
-        clearable: false,
         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.",
         inputSchema: {
@@ -855,7 +851,6 @@ var init_presentPublishPlan = __esm({
     "use strict";
     presentPublishPlanTool = {
       definition: {
-        clearable: false,
         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.",
         inputSchema: {
@@ -886,7 +881,6 @@ var init_writePlan = __esm({
     PLAN_FILE = ".remy-plan.md";
     writePlanTool = {
       definition: {
-        clearable: false,
         name: "writePlan",
         description: "Write 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. The plan is displayed standalone in the UI with approve/reject buttons attached. The plan body ends with its last substantive section \u2014 do not write any closing line addressed to the reader. No 'If this lands, I'll start building,' no 'Let me know what to adjust,' no 'Approve when ready,' no trailing horizontal rule with a sign-off. Wrap-up text belongs in your chat message alongside the plan, not in the plan file. If the user asks for revisions, call this tool again with updated content to overwrite the plan.",
         inputSchema: {
@@ -923,7 +917,6 @@ var init_updatePlanStatus = __esm({
     PLAN_FILE2 = ".remy-plan.md";
     updatePlanStatusTool = {
       definition: {
-        clearable: false,
         name: "updatePlanStatus",
         description: 'Update the status of the current implementation plan. Use when the user approves or rejects the plan via chat (e.g. "looks good, go ahead" or "scrap it"). Approving sets the plan to active so you can begin implementation. Rejecting deletes the plan.',
         inputSchema: {
@@ -971,7 +964,6 @@ var init_setProjectOnboardingState = __esm({
     "use strict";
     setProjectOnboardingStateTool = {
       definition: {
-        clearable: false,
         name: "setProjectOnboardingState",
         description: "Advance the project onboarding state. Forward-only: building \u2192 buildComplete \u2192 onboardingFinished. Normally driven by automated actions \u2014 don't call this out of order during a normal build, or you'll skip stages the user hasn't experienced. Exception: if the project has been in `building` for a while, the build is clearly done (the user is iterating on a working app, deploying, etc.), and the user reports the editor seems stuck \u2014 disabled Preview/Spec/Code tabs, no reveal, etc. \u2014 call `setProjectOnboardingState({ state: 'buildComplete' })` to unstick them. `onboardingFinished` is always set by the frontend after the user dismisses the reveal; never call it yourself.",
         inputSchema: {
@@ -1000,7 +992,6 @@ var init_promptUser = __esm({
     "use strict";
     promptUserTool = {
       definition: {
-        clearable: false,
         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.',
         inputSchema: {
@@ -1138,7 +1129,6 @@ var init_confirmDestructiveAction = __esm({
     "use strict";
     confirmDestructiveActionTool = {
       definition: {
-        clearable: false,
         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 presentPublishPlan or writePlan (those already include approval). Do not use before onboarding state transitions.",
         inputSchema: {
@@ -1325,7 +1315,6 @@ var init_sdkConsultant = __esm({
     init_runCli();
     askMindStudioSdkTool = {
       definition: {
-        clearable: false,
         name: "askMindStudioSdk",
         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: {
@@ -1487,7 +1476,6 @@ var init_searchGoogle = __esm({
     init_runCli();
     searchGoogleTool = {
       definition: {
-        clearable: false,
         name: "searchGoogle",
         description: "Search Google and return results. Use for research, finding documentation, looking up APIs, or any task where web search would help.",
         inputSchema: {
@@ -1524,7 +1512,6 @@ var init_setProjectMetadata = __esm({
     "use strict";
     setProjectMetadataTool = {
       definition: {
-        clearable: false,
         name: "setProjectMetadata",
         description: "Set project metadata. Can update any combination of: display name, short description, app icon, and Open Graph share image. Provide only the fields you want to change.",
         inputSchema: {
@@ -2878,7 +2865,6 @@ var init_compactConversation = __esm({
       // call (cleanMessagesForApi).
       backgroundNotify: "silent",
       definition: {
-        clearable: false,
         name: "compactConversation",
         description: "Compact the conversation history by summarizing older messages into a checkpoint. The summary preserves key decisions, what was built, and the current state of the project, but drops the verbose tool results, diffs, and intermediate steps that are no longer useful. Runs in the background.",
         inputSchema: {
@@ -3013,7 +2999,6 @@ var init_loadSkill = __esm({
     init_catalog();
     loadSkillTool = {
       definition: {
-        clearable: true,
         name: "loadSkill",
         description: "Load the full reference for a platform capability that isn't in your system prompt \u2014 task agents, agent interfaces, voice interfaces, MCP interfaces, data sources. The available skills and the trigger for each are listed in <available_skills>. Load one before writing code in its area, not after: these are APIs where a plausible-looking guess is usually wrong. Calling this is cheap and expected \u2014 if you're unsure whether you need it, load it. Only covers the capabilities listed in the catalog; for backend SDK actions and model IDs use askMindStudioSdk.",
         inputSchema: {
@@ -3070,7 +3055,6 @@ var init_readFile = __esm({
     MAX_BYTES = 64 * 1024;
     readFileTool = {
       definition: {
-        clearable: true,
         name: "readFile",
         description: "Read a file's contents with line numbers. Always read a file before editing it \u2014 never guess at contents. By default returns the first 500 lines, and at most 64KB \u2014 a file with very wide lines (a CSV, a minified bundle) comes back short of 500 lines, so read a narrower range or grep rather than paging through it. To read a specific range, pass startLine and endLine (1-indexed, inclusive) \u2014 e.g. to read lines 253\u2013343, pass startLine: 253, endLine: 343. To read the end of a file or log, pass tail (the number of lines from the end). Line numbers in the output correspond to what editFile expects. For a large file, locate the relevant section first (symbols or grep), then read just that range.",
         inputSchema: {
@@ -3182,7 +3166,6 @@ var init_writeFile = __esm({
     init_fileLock();
     writeFileTool = {
       definition: {
-        clearable: true,
         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.",
         inputSchema: {
@@ -3257,7 +3240,6 @@ var init_editFile = __esm({
     init_helpers2();
     editFileTool = {
       definition: {
-        clearable: true,
         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.",
         inputSchema: {
@@ -3366,7 +3348,6 @@ var init_bash = __esm({
     MAX_OUTPUT_BYTES = 3e4;
     bashTool = {
       definition: {
-        clearable: true,
         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 or 30KB, whichever comes first. If a command would emit a lot of data, narrow it down (grep, head/tail, --short flags) rather than reading everything.",
         inputSchema: {
@@ -3494,7 +3475,6 @@ var init_grep = __esm({
     DEFAULT_MAX = 50;
     grepTool = {
       definition: {
-        clearable: true,
         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. Set outputMode to 'count' for per-file match counts (like grep -c) or 'filesWithMatches' for just the file paths (like grep -l). Add context (like grep -C), or contextBefore/contextAfter (like grep -B/-A), to include surrounding lines. Set caseInsensitive (like grep -i) for a case-insensitive search. For finding a symbol's definition precisely, prefer the definition tool if LSP is available. Automatically excludes node_modules and .git.",
         inputSchema: {
@@ -3612,7 +3592,6 @@ var init_glob = __esm({
     DEFAULT_MAX2 = 200;
     globTool = {
       definition: {
-        clearable: true,
         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.',
         inputSchema: {
@@ -3716,7 +3695,6 @@ var init_listDir = __esm({
     MAX_CHILDREN = 15;
     listDirTool = {
       definition: {
-        clearable: true,
         name: "listDir",
         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: {
@@ -3799,7 +3777,6 @@ var init_editsFinished = __esm({
     "use strict";
     editsFinishedTool = {
       definition: {
-        clearable: false,
         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.",
         inputSchema: {
@@ -3887,7 +3864,6 @@ var init_lspDiagnostics = __esm({
     init_lsp();
     lspDiagnosticsTool = {
       definition: {
-        clearable: true,
         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.",
         inputSchema: {
@@ -3943,7 +3919,6 @@ var init_restartProcess = __esm({
     init_lsp();
     restartProcessTool = {
       definition: {
-        clearable: false,
         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.",
         inputSchema: {
@@ -3976,7 +3951,6 @@ var init_runScenario = __esm({
     "use strict";
     runScenarioTool = {
       definition: {
-        clearable: true,
         name: "runScenario",
         description: "Run a scenario to seed the dev database with test data. By default truncates all tables first, then executes the seed function and impersonates the scenario roles. Use skipTruncate to run the seed function against existing data without resetting. 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.",
         inputSchema: {
@@ -4008,7 +3982,6 @@ var init_runMethod = __esm({
     "use strict";
     runMethodTool = {
       definition: {
-        clearable: true,
         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. Returns synchronously \u2014 no need to sleep before checking results.\n\nBy default methods run unauthenticated. If the method is auth-gated (calls `auth.requireRole()`, filters on `auth.userId`, etc.), pass `userId: "testUser"` to run as the default test user \u2014 no scenario setup required, no userId lookup.',
         inputSchema: {
@@ -4049,7 +4022,6 @@ var init_queryDatabase = __esm({
     "use strict";
     queryDatabaseTool = {
       definition: {
-        clearable: true,
         name: "queryDatabase",
         description: "Execute a raw SQL query against the dev database and return the results. Use for inspecting data and debugging issues.",
         inputSchema: {
@@ -5026,7 +4998,6 @@ var init_tools2 = __esm({
     init_readSpec();
     BROWSER_TOOLS = [
       {
-        clearable: false,
         name: "setupBrowser",
         description: "Pre-authenticate the browser and optionally navigate to a starting page. Call this before interacting with authenticated content instead of manually logging in. Auth is optional \u2014 omit to just navigate without authenticating.",
         inputSchema: {
@@ -5059,7 +5030,6 @@ var init_tools2 = __esm({
         }
       },
       {
-        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. Batches that contain an interactive step (click, type, select) also return a `recording` object \u2014 one chunk of a continuous per-session rrweb recording that the viewer stitches into a single replay (not a standalone per-call clip). Timeout: 120s.",
         inputSchema: {
@@ -5507,7 +5477,6 @@ var init_browserAutomation = __esm({
     CAPTURE_COMMANDS = /* @__PURE__ */ new Set(["screenshotViewport", "screenshotFullPage"]);
     browserAutomationTool = {
       definition: {
-        clearable: true,
         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 to frontend code, to reproduce user-reported issues, or to test end-to-end flows. Never give it explicit values to use when filling out forms or creating accounts \u2014 it will use its own judgement (often it needs specific values to trigger dev-mode bypasses of things like login verification codes).",
         inputSchema: {
@@ -5598,7 +5567,6 @@ var init_screenshot2 = __esm({
     init_browserAutomation();
     init_surfaces();
     screenshotDefinition = {
-      clearable: true,
       name: "screenshot",
       description: "Capture a screenshot of the app preview and get a description of what's on screen. Choose `fullPage`: `false` captures just the visible viewport (fast \u2014 for a specific section the page is scrolled to), `true` captures the entire page top-to-bottom (slower \u2014 for overall composition or content past the fold). Captures the settled page state \u2014 it cannot catch animations, transitions, or transient state. The analysis is not precise about every detail \u2014 for example it cannot reliably identify specific fonts by name, only describe what the letterforms look like. 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; `imageUrl` also accepts the disk path of an image file (a user upload, a saved asset) to analyze that instead of the preview. If the screenshot requires interaction first (logging in, clicking a tab, dismissing a modal, scrolling to a section), use the instructions param to describe the steps. To render a fixed-size image such as an Open Graph share card, set `width` and `height` (e.g. 1200 \xD7 630) and `format: 'png'`: the tool navigates to `path`, clips to exactly those pixel dimensions, and returns the image URL.",
       inputSchema: {
@@ -5672,7 +5640,6 @@ var init_searchGoogle2 = __esm({
     init_runMindstudioCli();
     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: {
@@ -5715,7 +5682,6 @@ var init_scrapeWebUrl = __esm({
     init_runMindstudioCli();
     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: {
@@ -5808,7 +5774,6 @@ 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, an image URL, or an image file on disk. 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: {
@@ -5856,7 +5821,6 @@ var init_analyzeImage2 = __esm({
     init_screenshot();
     init_surfaces();
     definition4 = {
-      clearable: true,
       name: "analyzeImage",
       description: "Analyze an image 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: {
@@ -6128,7 +6092,6 @@ var init_generateImages = __esm({
     init_imageGenerator();
     init_surfaces();
     definition5 = {
-      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: {
@@ -6204,7 +6167,6 @@ var init_editImages = __esm({
     init_imageGenerator();
     init_surfaces();
     definition6 = {
-      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: {
@@ -6267,7 +6229,6 @@ var init_copyEditor = __esm({
     BASE_PROMPT2 = readAsset("subagents/copyEditor", "prompt.md");
     copyEditorTool = {
       definition: {
-        clearable: false,
         name: "copyEditor",
         description: "Hand it user-facing copy and it hands back a sharper version \u2014 better structured for its audience and free of the overused words, telltale constructions, and rhythms that make text read as AI-generated. Think of it as a design expert for words: it elevates how the copy communicates and strips the AI fingerprints, but it never invents facts or claims you didn't give it. Use it on anything users will read: in-app strings, empty states, errors, the Build Overview, deck copy, launch posts, Slack announcements. Readonly.",
         inputSchema: {
@@ -6330,7 +6291,6 @@ var init_polishCopy = __esm({
     "use strict";
     init_copyEditor();
     definition7 = {
-      clearable: false,
       name: "polishCopy",
       description: "Hand off any user-facing copy you've written \u2014 headlines, captions, labels, body text \u2014 and get back a sharper version: better built for its audience and free of the fingerprints that make writing read as AI. It elevates how the copy communicates without inventing facts or claims you didn't give it. Give it the text plus what it's for (where it appears, the audience).",
       inputSchema: {
@@ -6824,7 +6784,6 @@ Visual design expert. Describe the situation and what you need \u2014 the agent
     ];
     designExpertTool = {
       definition: {
-        clearable: false,
         name: "visualDesignExpert",
         description: DESCRIPTION,
         inputSchema: {
@@ -7067,7 +7026,6 @@ var init_productVision = __esm({
     init_surfaces();
     productVisionTool = {
       definition: {
-        clearable: false,
         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.",
         inputSchema: {
@@ -7199,7 +7157,6 @@ var init_codeSanityCheck = __esm({
     BASE_PROMPT4 = readAsset("subagents/codeSanityCheck", "prompt.md");
     codeSanityCheckTool = {
       definition: {
-        clearable: false,
         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.',
         inputSchema: {
@@ -7341,7 +7298,6 @@ The copy in <overview_copy> is final \u2014 it was authored and edited before it
 </html>`;
     buildOverviewTool = {
       definition: {
-        clearable: false,
         name: "writeBuildOverview",
         description: "Generate or refresh the Build Overview \u2014 the project's home page in the Spec tab: a single-page, plain-language reference of everything the app actually contains, including the parts the user can't see (data stores, backend operations, access and roles, background jobs, seeded scenarios, the design system). You author the full copy: read the manifest and spec and state, plainly and exactly, what genuinely exists \u2014 real names and accurate counts \u2014 in calm, declarative, present-tense outcome language, with no persuasion or hype. Describe only what exists. Pass the complete copy as `content`; the design expert lays it out and skins it to the app's brand using your copy verbatim \u2014 it typesets your words, it does not rewrite them, so polish the copy before you pass it. Generate it at the end of a build; routine refreshes ride specSync's `refreshBuildOverview` flag instead, so call this directly only for the initial generation or when the user explicitly asks.",
         inputSchema: {
@@ -7432,7 +7388,6 @@ ${readAsset(
       // next real turn as a hidden background_results note instead.
       backgroundNotify: "passive",
       definition: {
-        clearable: false,
         name: "specSync",
         description: "Reconcile the spec to bring it in line with code changes you have made. Provide a brief, bulleted list of what changed and why; it finds the affected spec sections and updates them to match. Set `refreshBuildOverview` after a deploy or a large milestone to also re-author the Build Overview from the updated spec. Always runs in the background and completes silently \u2014 do not wait for it; its outcome appears as an automated note at the start of a later turn.",
         inputSchema: {
@@ -7527,7 +7482,6 @@ var init_scrapeWebUrl2 = __esm({
     init_runCli();
     scrapeWebUrlTool = {
       definition: {
-        clearable: false,
         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",
         inputSchema: {

package/package.json

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