@mindstudio-ai/remy 0.1.140 → 0.1.142

package/README.md

@@ -105,16 +105,13 @@ Available only when `onboardingState` is `onboardingFinished`.
 
 | Tool | Description |
 |------|-------------|
-| `clearSyncStatus` | Clear sync flags after syncing spec and code |
-| `presentSyncPlan` | Present a markdown sync plan to the user for approval (streams content) |
 | `presentPublishPlan` | Present a publish changelog for user approval (streams content) |
-| `presentPlan` | Present an implementation plan for user approval (streams content) |
 
 ### Tool Streaming
 
 Tools can opt into streaming via a `streaming` config on the tool definition:
 
-- **Content streaming** (writeSpec, writeFile, presentSyncPlan, presentPublishPlan, presentPlan): Streams `tool_input_delta` events with progressive content as the LLM generates tool arguments. Tools can provide a `transform` function to customize the streamed output (e.g., writeSpec/writeFile compute a progressive diff).
+- **Content streaming** (writeSpec, writeFile, presentPublishPlan): Streams `tool_input_delta` events with progressive content as the LLM generates tool arguments. Tools can provide a `transform` function to customize the streamed output (e.g., writeSpec/writeFile compute a progressive diff).
 - **Input streaming** (promptUser): Streams progressive `tool_start` events with `partial: true` as structured input (like a questions array) builds up.
 - **No streaming** (all other tools): `tool_start` fires once when the complete tool arguments are available.
 
@@ -157,10 +154,7 @@ Some tools are resolved by the sandbox rather than executed locally. Remy emits
 - `setProjectOnboardingState` — advances the onboarding flow
 - `setProjectName` — sets the project name
 - `confirmDestructiveAction` — renders a confirmation dialog
-- `clearSyncStatus` — clears sync dirty flags and updates git sync ref
-- `presentSyncPlan` — renders a full-screen markdown plan for user approval
 - `presentPublishPlan` — renders a full-screen changelog for user approval
-- `presentPlan` — renders a full-screen implementation plan for user approval
 
 ### Project Structure
 

package/dist/automatedActions/approvePlan.md

@@ -0,0 +1,5 @@
+---
+trigger: approvePlan
+---
+
+The user has approved the implementation plan in .remy-plan.md. Proceed with implementing the plan. Delete .remy-plan.md when all planned work is complete.

package/dist/automatedActions/buildFromRoadmap.md

@@ -8,7 +8,7 @@ First, review the specific item and think about how it fits with the existing sp
 
 Then, ask the user any clarifying questions about anything that is ambiguous or requires additional input. Consult the team for any design work, architecture review, or SDK guidance - even if they're just quick questions (that's what the team is there for - they want to help and feel valuable!). Additive feature work is the most fun to build, but make sure you take a step back first and consider any technical debt or organization implications - we need to keep the codebase clean, tidy, bug-free, and easy/intuitive to manage. When adding new features, this might mean extracting shared helpers to separate files, breaking apart components into multiple files, making new folders, etc. - Don't go overboard, but also don't keep adding to one giant file until it ends up unmanageable. Consider organization and structure when building the plan.
 
-Then, put together a plan to build out the feature. Present the plan to the user for their approval.
+Then, put together a plan to build out the feature. Write the plan with `writePlan` for the user's approval.
 
 When they've approved the plan, be sure to update the spec first - remember, the spec is the source of truth about the product. Then, build everything in one turn, using the spec as the master plan.
 

package/dist/automatedActions/codeCleanup.md

@@ -8,4 +8,4 @@ First, explore the project and get a sense of what has built.
 
 Read specific files and trace paths, don't just guess at how something works based on partial information. When you are finished exploring, identiy any high-impact areas for cleaning up the code. This can include things like directory organization, splitting things into separate files to make the project easier to scan, breaking up large components or screens, deduplicating copy-pasted code, removing dead code, and anything else that will leave the project more robust, reliable, and easier to scan/work on for developers. Do not optimize for the sake of optimizing, only focus on reducing real technical debt and leaving the product better and a more pleasant experience for other developers working on it.
 
-When you have a plan, run it by the `codeSanityCheck` to get a second set of eyes. Then, present the plan to the user. The technical detail is important so the user has a sense of what the plan entails, but remember that the user is not very technical, so it is equally important to help them understand the why behind any refactors.
+When you have a plan, run it by the `codeSanityCheck` to get a second set of eyes. Then, write the plan with `writePlan` for the user to review. The technical detail is important so the user has a sense of what the plan entails, but remember that the user is not very technical, so it is equally important to help them understand the why behind any refactors.

package/dist/automatedActions/rejectPlan.md

@@ -0,0 +1,5 @@
+---
+trigger: rejectPlan
+---
+
+The user has rejected the implementation plan. Acknowledge and continue the conversation.

package/dist/automatedActions/sync.md

@@ -1,23 +1,12 @@
 ---
-  trigger: sync
+trigger: sync
 ---
 
 This is an automated action triggered by the user pressing "Sync" in the editor.
 
-The user has manually edited files since the last sync. The `refs/sync-point` git ref marks the last known-good sync state. It's created using a temporary git index that captures the full working tree (including unstaged changes) as a tree object — so it represents exactly what the files looked like at sync time, not just what was committed.
+Review the spec files in `src/` and the corresponding code in `dist/`. Identify any differences where one side has changes that the other doesn't reflect. Write a sync plan with `writePlan` describing what changed and what you intend to update. Write it for a human: describe changes in plain language ("renamed the greeting field", "added a note about error handling"), not as a list of file paths and code diffs.
 
-To see what the user changed, run: `git diff refs/sync-point -- src/ dist/`
-
-This compares the sync-point tree against the current working tree. Do not add `HEAD` or any other ref — the command as written diffs directly against the working tree, which is what you want.
-
-In the diff output: lines prefixed with `-` are what was in the file at last sync. Lines prefixed with `+` are the user's current edits. Sync should bring the other side in line with the `+` side.
-
-Analyze the changes and write a sync plan with `presentSyncPlan` — a clear markdown summary of what changed and what you intend to update. Write it for a human: describe changes in plain language ("renamed the greeting field", "added a note about error handling"), not as a list of file paths and code diffs. Reference specific code or file paths only when it helps clarity. The user will review and approve before you make changes.
-
-If approved:
+If the plan is approved:
 - If spec files (`src/`) changed, update the corresponding code in `dist/` to match
 - If code files (`dist/`) changed, update the corresponding spec in `src/` to match
 - If both changed, reconcile — spec is the source of truth for intent, but respect code changes that add implementation detail
-- When all files are synced, call `clearSyncStatus`
-
-If dismissed, acknowledge and do nothing.

package/dist/headless.js

@@ -6,7 +6,7 @@ var __export = (target, all) => {
 
 // src/headless.ts
 import { createInterface } from "readline";
-import { writeFileSync } from "fs";
+import { writeFileSync, readFileSync, unlinkSync } from "fs";
 
 // src/logger.ts
 import fs from "fs";
@@ -292,6 +292,28 @@ function parseFrontmatter(filePath) {
     return { name: "", description: "", type: "" };
   }
 }
+function loadPlanStatus() {
+  try {
+    const content = fs4.readFileSync(".remy-plan.md", "utf-8");
+    const match = content.match(/^---\n([\s\S]*?)\n---/);
+    const status = match?.[1]?.match(/^status:\s*(.+)$/m)?.[1]?.trim();
+    if (status === "pending") {
+      return `
+<pending_plan>
+You have a pending implementation plan in .remy-plan.md awaiting user approval. Do NOT begin implementing the plan until the user approves it. You may continue chatting, answering questions, and revising the plan if asked. To revise, call writePlan again with updated content. When the user approves the plan (via chat or any other signal), call updatePlanStatus with status "approved" before beginning any implementation work.
+</pending_plan>`;
+    }
+    if (status === "approved") {
+      return `
+<approved_plan>
+The user has approved your implementation plan in .remy-plan.md. You may reference it during implementation. Delete the file when you have finished all planned work.
+</approved_plan>`;
+    }
+    return "";
+  } catch {
+    return "";
+  }
+}
 function loadProjectFileListing() {
   try {
     const entries = fs4.readdirSync(".", { withFileTypes: true });
@@ -421,7 +443,7 @@ ${isLspConfigured() ? `<typescript_lsp>
 </code_authoring_instructions>
 
 {{static/instructions.md}}
-
+${loadPlanStatus()}
 <conversation_summaries>
 Your conversation history may include <prior_conversation_summary> blocks in the user's messages. These are automated summaries of earlier messages that have been compacted to save context space. The user does not see this summary, they see the full conversation history in their UI. Treat the summary as ground truth for what happened before, but do not reference it directly to the user ("as mentioned in the summary..."). Just continue naturally as if you remember the prior work.
 
@@ -1301,34 +1323,18 @@ async function listRecursive(dir) {
   return results;
 }
 
-// src/tools/spec/clearSyncStatus.ts
-var clearSyncStatusTool = {
-  clearable: false,
-  definition: {
-    name: "clearSyncStatus",
-    description: "Clear the sync status flags after syncing spec and code. Call this after finishing a sync operation.",
-    inputSchema: {
-      type: "object",
-      properties: {}
-    }
-  },
-  async execute() {
-    return "ok";
-  }
-};
-
-// src/tools/spec/presentSyncPlan.ts
-var presentSyncPlanTool = {
+// src/tools/spec/presentPublishPlan.ts
+var presentPublishPlanTool = {
   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.",
+    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: {
       type: "object",
       properties: {
         content: {
           type: "string",
-          description: "Markdown plan describing what changed and what will be updated."
+          description: "Markdown changelog describing what changed and what will be deployed."
         }
       },
       required: ["content"]
@@ -1340,49 +1346,75 @@ var presentSyncPlanTool = {
   }
 };
 
-// src/tools/spec/presentPublishPlan.ts
-var presentPublishPlanTool = {
+// src/tools/spec/writePlan.ts
+import fs9 from "fs/promises";
+var PLAN_FILE = ".remy-plan.md";
+var writePlanTool = {
   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.",
+    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 saved to .remy-plan.md and the user can review, discuss, and approve or reject it. If the user asks for revisions, call this tool again with updated content to overwrite the plan.",
     inputSchema: {
       type: "object",
       properties: {
         content: {
           type: "string",
-          description: "Markdown changelog describing what changed and what will be deployed."
+          description: "Markdown plan describing what you intend to do."
         }
       },
       required: ["content"]
     }
   },
-  streaming: {},
-  async execute() {
-    return "approved";
+  async execute(input) {
+    const content = input.content;
+    const file = `---
+status: pending
+---
+
+${content}`;
+    await fs9.writeFile(PLAN_FILE, file, "utf-8");
+    return "Plan written to .remy-plan.md. Waiting for user approval.";
   }
 };
 
-// src/tools/spec/presentPlan.ts
-var presentPlanTool = {
+// src/tools/spec/updatePlanStatus.ts
+import fs10 from "fs/promises";
+var PLAN_FILE2 = ".remy-plan.md";
+var updatePlanStatusTool = {
   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.",
+    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: {
       type: "object",
       properties: {
-        content: {
+        status: {
           type: "string",
-          description: "Markdown plan describing what you intend to do."
+          enum: ["approved", "rejected"],
+          description: "The new plan status."
         }
       },
-      required: ["content"]
+      required: ["status"]
     }
   },
-  streaming: {},
-  async execute() {
-    return "approved";
+  async execute(input) {
+    const status = input.status;
+    let content;
+    try {
+      content = await fs10.readFile(PLAN_FILE2, "utf-8");
+    } catch {
+      return "No plan file found.";
+    }
+    if (status === "rejected") {
+      await fs10.unlink(PLAN_FILE2);
+      return "Plan rejected and removed.";
+    }
+    await fs10.writeFile(
+      PLAN_FILE2,
+      content.replace(/^status:\s*\w+/m, `status: ${status}`),
+      "utf-8"
+    );
+    return "Plan approved. Proceeding with implementation.";
   }
 };
 
@@ -1546,7 +1578,7 @@ var 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.",
+    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: {
       type: "object",
       properties: {
@@ -1763,7 +1795,7 @@ var compactConversationTool = {
 };
 
 // src/tools/code/readFile.ts
-import fs9 from "fs/promises";
+import fs11 from "fs/promises";
 var DEFAULT_MAX_LINES2 = 500;
 function isBinary(buffer) {
   const sample = buffer.subarray(0, 8192);
@@ -1800,7 +1832,7 @@ var readFileTool = {
   },
   async execute(input) {
     try {
-      const buffer = await fs9.readFile(input.path);
+      const buffer = await fs11.readFile(input.path);
       if (isBinary(buffer)) {
         const size = buffer.length;
         const unit = size > 1024 * 1024 ? `${(size / (1024 * 1024)).toFixed(1)}MB` : `${(size / 1024).toFixed(1)}KB`;
@@ -1834,7 +1866,7 @@ var readFileTool = {
 };
 
 // src/tools/code/writeFile.ts
-import fs10 from "fs/promises";
+import fs12 from "fs/promises";
 import path6 from "path";
 var writeFileTool = {
   clearable: true,
@@ -1872,7 +1904,7 @@ var writeFileTool = {
         lastNewlineCount = newlineCount;
         const lastNewline = partial.content.lastIndexOf("\n");
         const completeContent = partial.content.substring(0, lastNewline + 1);
-        const oldContent = await fs10.readFile(partial.path, "utf-8").catch(() => "");
+        const oldContent = await fs12.readFile(partial.path, "utf-8").catch(() => "");
         return `Writing ${partial.path} (${newlineCount} lines)
 ${unifiedDiff(partial.path, oldContent, completeContent)}`;
       }
@@ -1881,13 +1913,13 @@ ${unifiedDiff(partial.path, oldContent, completeContent)}`;
   async execute(input) {
     const release = await acquireFileLock(input.path);
     try {
-      await fs10.mkdir(path6.dirname(input.path), { recursive: true });
+      await fs12.mkdir(path6.dirname(input.path), { recursive: true });
       let oldContent = null;
       try {
-        oldContent = await fs10.readFile(input.path, "utf-8");
+        oldContent = await fs12.readFile(input.path, "utf-8");
       } catch {
       }
-      await fs10.writeFile(input.path, input.content, "utf-8");
+      await fs12.writeFile(input.path, input.content, "utf-8");
       const lineCount = input.content.split("\n").length;
       const label = oldContent !== null ? "Wrote" : "Created";
       return `${label} ${input.path} (${lineCount} lines)
@@ -1901,7 +1933,7 @@ ${unifiedDiff(input.path, oldContent ?? "", input.content)}`;
 };
 
 // src/tools/code/editFile/index.ts
-import fs11 from "fs/promises";
+import fs13 from "fs/promises";
 
 // src/tools/code/editFile/_helpers.ts
 function buildLineOffsets(content) {
@@ -2014,7 +2046,7 @@ var editFileTool = {
   async execute(input) {
     const release = await acquireFileLock(input.path);
     try {
-      const content = await fs11.readFile(input.path, "utf-8");
+      const content = await fs13.readFile(input.path, "utf-8");
       const { old_string, new_string, replace_all } = input;
       const occurrences = findOccurrences(content, old_string);
       if (replace_all) {
@@ -2030,7 +2062,7 @@ var editFileTool = {
             new_string
           );
         }
-        await fs11.writeFile(input.path, updated, "utf-8");
+        await fs13.writeFile(input.path, updated, "utf-8");
         return `Replaced ${occurrences.length} occurrence${occurrences.length > 1 ? "s" : ""} in ${input.path}
 ${unifiedDiff(input.path, content, updated)}`;
       }
@@ -2041,7 +2073,7 @@ ${unifiedDiff(input.path, content, updated)}`;
           old_string.length,
           new_string
         );
-        await fs11.writeFile(input.path, updated, "utf-8");
+        await fs13.writeFile(input.path, updated, "utf-8");
         return `Updated ${input.path}
 ${unifiedDiff(input.path, content, updated)}`;
       }
@@ -2057,7 +2089,7 @@ ${unifiedDiff(input.path, content, updated)}`;
           flex.matchedText.length,
           new_string
         );
-        await fs11.writeFile(input.path, updated, "utf-8");
+        await fs13.writeFile(input.path, updated, "utf-8");
         return `Updated ${input.path} (matched with flexible whitespace at line ${flex.line})
 ${unifiedDiff(input.path, content, updated)}`;
       }
@@ -2268,12 +2300,12 @@ var globTool = {
 };
 
 // src/tools/code/listDir.ts
-import fs12 from "fs/promises";
+import fs14 from "fs/promises";
 import path7 from "path";
 var EXCLUDE = /* @__PURE__ */ new Set([".git", "node_modules"]);
 var MAX_CHILDREN = 15;
 async function readAndSort(dirPath) {
-  const entries = await fs12.readdir(dirPath, { withFileTypes: true });
+  const entries = await fs14.readdir(dirPath, { withFileTypes: true });
   return entries.filter((e) => !EXCLUDE.has(e.name)).sort((a, b) => {
     if (a.isDirectory() && !b.isDirectory()) {
       return -1;
@@ -2314,7 +2346,7 @@ function formatSize(bytes) {
 }
 async function formatFile(dirPath, name, indent) {
   try {
-    const stat = await fs12.stat(path7.join(dirPath, name));
+    const stat = await fs14.stat(path7.join(dirPath, name));
     return `${indent}${name}${" ".repeat(Math.max(1, 30 - indent.length - name.length))}${formatSize(stat.size)}`;
   } catch {
     return `${indent}${name}`;
@@ -3381,11 +3413,11 @@ var BROWSER_TOOLS = [
 var BROWSER_EXTERNAL_TOOLS = /* @__PURE__ */ new Set(["browserCommand"]);
 
 // src/subagents/browserAutomation/prompt.ts
-import fs13 from "fs";
+import fs15 from "fs";
 var BASE_PROMPT = readAsset("subagents/browserAutomation", "prompt.md");
 function getBrowserAutomationPrompt() {
   try {
-    const appSpec = fs13.readFileSync("src/app.md", "utf-8").trim();
+    const appSpec = fs15.readFileSync("src/app.md", "utf-8").trim();
     return `${BASE_PROMPT}
 
 <!-- cache_breakpoint -->
@@ -4227,12 +4259,12 @@ async function executeDesignExpertTool(name, input, context, toolCallId, onLog)
 }
 
 // src/subagents/common/context.ts
-import fs14 from "fs";
+import fs16 from "fs";
 import path8 from "path";
 function walkMdFiles2(dir, skip) {
   const files = [];
   try {
-    for (const entry of fs14.readdirSync(dir, { withFileTypes: true })) {
+    for (const entry of fs16.readdirSync(dir, { withFileTypes: true })) {
       const full = path8.join(dir, entry.name);
       if (entry.isDirectory()) {
         if (!skip?.has(entry.name)) {
@@ -4248,7 +4280,7 @@ function walkMdFiles2(dir, skip) {
 }
 function parseFrontmatter2(filePath) {
   try {
-    const content = fs14.readFileSync(filePath, "utf-8");
+    const content = fs16.readFileSync(filePath, "utf-8");
     const match = content.match(/^---\n([\s\S]*?)\n---/);
     if (!match) {
       return {};
@@ -4294,7 +4326,7 @@ function loadRoadmapIndex() {
   const parts = [];
   try {
     const indexJson = JSON.parse(
-      fs14.readFileSync("src/roadmap/index.json", "utf-8")
+      fs16.readFileSync("src/roadmap/index.json", "utf-8")
     );
     if (indexJson.lanes?.length > 0) {
       const laneLines = indexJson.lanes.map(
@@ -4397,7 +4429,7 @@ The first-party SDK (@mindstudio-ai/agent) provides access to 200+ AI models (Op
 }
 
 // src/subagents/designExpert/data/sampleCache.ts
-import fs15 from "fs";
+import fs17 from "fs";
 var SAMPLE_FILE = ".remy-design-sample.json";
 var cached = null;
 function generateIndices(poolSize, sampleSize) {
@@ -4411,14 +4443,14 @@ function generateIndices(poolSize, sampleSize) {
 }
 function load() {
   try {
-    return JSON.parse(fs15.readFileSync(SAMPLE_FILE, "utf-8"));
+    return JSON.parse(fs17.readFileSync(SAMPLE_FILE, "utf-8"));
   } catch {
     return null;
   }
 }
 function save(indices) {
   try {
-    fs15.writeFileSync(SAMPLE_FILE, JSON.stringify(indices));
+    fs17.writeFileSync(SAMPLE_FILE, JSON.stringify(indices));
   } catch {
   }
 }
@@ -4747,7 +4779,7 @@ var VISION_TOOLS = [
 ];
 
 // src/subagents/productVision/executor.ts
-import fs16 from "fs";
+import fs18 from "fs";
 import path9 from "path";
 var ROADMAP_DIR = "src/roadmap";
 var PITCH_DECK_SHELL = readAsset(
@@ -4762,13 +4794,13 @@ async function executeVisionTool(name, input, context) {
     case "writeFile": {
       const filePath = resolve(input.path);
       try {
-        fs16.mkdirSync(ROADMAP_DIR, { recursive: true });
+        fs18.mkdirSync(ROADMAP_DIR, { recursive: true });
         let oldContent = null;
         try {
-          oldContent = fs16.readFileSync(filePath, "utf-8");
+          oldContent = fs18.readFileSync(filePath, "utf-8");
         } catch {
         }
-        fs16.writeFileSync(filePath, input.content, "utf-8");
+        fs18.writeFileSync(filePath, input.content, "utf-8");
         const lineCount = input.content.split("\n").length;
         const label = oldContent !== null ? "Wrote" : "Created";
         return `${label} ${filePath} (${lineCount} lines)
@@ -4780,11 +4812,11 @@ ${unifiedDiff(filePath, oldContent ?? "", input.content)}`;
     case "deleteFile": {
       const filePath = resolve(input.path);
       try {
-        if (!fs16.existsSync(filePath)) {
+        if (!fs18.existsSync(filePath)) {
           return `Error: ${filePath} does not exist`;
         }
-        const oldContent = fs16.readFileSync(filePath, "utf-8");
-        fs16.unlinkSync(filePath);
+        const oldContent = fs18.readFileSync(filePath, "utf-8");
+        fs18.unlinkSync(filePath);
         return `Deleted ${filePath}
 ${unifiedDiff(filePath, oldContent, "")}`;
       } catch (err) {
@@ -4797,8 +4829,8 @@ ${unifiedDiff(filePath, oldContent, "")}`;
       }
       const filePath = resolve("pitch.html");
       try {
-        fs16.mkdirSync(ROADMAP_DIR, { recursive: true });
-        const existing = fs16.existsSync(filePath) ? fs16.readFileSync(filePath, "utf-8").trim() : "";
+        fs18.mkdirSync(ROADMAP_DIR, { recursive: true });
+        const existing = fs18.existsSync(filePath) ? fs18.readFileSync(filePath, "utf-8").trim() : "";
         const currentDeck = existing || PITCH_DECK_SHELL;
         const task = `
 <pitch_content>${input.task}</pitch_content>
@@ -4823,7 +4855,7 @@ Respond only with the complete HTML file and absolutely no other text. Your resp
           /```(?:html|wireframe)\n([\s\S]*?)```/
         );
         const html = htmlMatch ? htmlMatch[1].trim() : result;
-        fs16.writeFileSync(filePath, html, "utf-8");
+        fs18.writeFileSync(filePath, html, "utf-8");
         return `Pitch deck written successfully.`;
       } catch (err) {
         return `Error generating pitch deck: ${err.message}`;
@@ -5065,10 +5097,9 @@ var ALL_TOOLS = [
   codeSanityCheckTool,
   compactConversationTool,
   // Post-onboarding
-  clearSyncStatusTool,
-  presentSyncPlanTool,
   presentPublishPlanTool,
-  presentPlanTool,
+  writePlanTool,
+  updatePlanStatusTool,
   // Spec
   readSpecTool,
   writeSpecTool,
@@ -5110,12 +5141,12 @@ function executeTool(name, input, context) {
 }
 
 // src/session.ts
-import fs17 from "fs";
+import fs19 from "fs";
 var log7 = createLogger("session");
 var SESSION_FILE = ".remy-session.json";
 function loadSession(state) {
   try {
-    const raw = fs17.readFileSync(SESSION_FILE, "utf-8");
+    const raw = fs19.readFileSync(SESSION_FILE, "utf-8");
     const data = JSON.parse(raw);
     if (Array.isArray(data.messages) && data.messages.length > 0) {
       state.messages = sanitizeMessages(data.messages);
@@ -5164,7 +5195,7 @@ function sanitizeMessages(messages) {
 }
 function saveSession(state) {
   try {
-    fs17.writeFileSync(
+    fs19.writeFileSync(
       SESSION_FILE,
       JSON.stringify({ messages: state.messages }, null, 2),
       "utf-8"
@@ -5177,7 +5208,7 @@ function saveSession(state) {
 function clearSession(state) {
   state.messages = [];
   try {
-    fs17.unlinkSync(SESSION_FILE);
+    fs19.unlinkSync(SESSION_FILE);
   } catch {
   }
 }
@@ -5402,10 +5433,7 @@ function getToolCalls(blocks) {
 var EXTERNAL_TOOLS = /* @__PURE__ */ new Set([
   "promptUser",
   "setProjectOnboardingState",
-  "clearSyncStatus",
-  "presentSyncPlan",
   "presentPublishPlan",
-  "presentPlan",
   "confirmDestructiveAction",
   "runScenario",
   "runMethod",
@@ -5467,7 +5495,6 @@ async function runTurn(params) {
   const STATUS_EXCLUDED_TOOLS = /* @__PURE__ */ new Set([
     "setProjectOnboardingState",
     "setProjectMetadata",
-    "clearSyncStatus",
     "editsFinished"
   ]);
   let lastCompletedTools = "";
@@ -6156,8 +6183,6 @@ ${xmlParts}
   const USER_FACING_TOOLS = /* @__PURE__ */ new Set([
     "promptUser",
     "confirmDestructiveAction",
-    "presentPlan",
-    "presentSyncPlan",
     "presentPublishPlan"
   ]);
   function resolveExternalTool(id, name, _input) {
@@ -6374,6 +6399,23 @@ ${xmlParts}
       userMessage = resolved;
     }
     const isHidden = resolved !== null || !!parsed.hidden;
+    const rawText = parsed.text ?? "";
+    if (rawText.startsWith("@@automated::approvePlan@@")) {
+      try {
+        const plan = readFileSync(".remy-plan.md", "utf-8");
+        writeFileSync(
+          ".remy-plan.md",
+          plan.replace(/^status:\s*pending/m, "status: approved"),
+          "utf-8"
+        );
+      } catch {
+      }
+    } else if (rawText.startsWith("@@automated::rejectPlan@@")) {
+      try {
+        unlinkSync(".remy-plan.md");
+      } catch {
+      }
+    }
     const onboardingState = parsed.onboardingState ?? "onboardingFinished";
     const system = buildSystemPrompt(
       onboardingState,