chromeflow 0.1.7 → 0.1.9

package/CLAUDE.md

@@ -98,8 +98,9 @@ Use the absolute path for `envPath` — it's the Claude Code working directory +
 
 ## Error handling
 - After any action → `get_page_text()` to check for errors (not `take_screenshot`)
+- After `click_element("Save")` / form submission → use `get_page_text()` or `wait_for_selector` to confirm. Never use `wait_for_navigation` — most form saves don't navigate.
 - `click_element` not found → `scroll_page("down")` then retry
 - Still not found → `take_screenshot()` then `highlight_region(x,y,w,h,msg)`
-- `fill_input` not found → `click_element(hint)` to focus the field, then retry `fill_input`. If still failing, `take_screenshot()` then `highlight_region(x,y,w,h, message: "Click here — I'll fill it in")` (NO `valueToType`) then `wait_for_click()` then retry `fill_input` — after the user focuses the field by clicking, the active-element fallback will fill it automatically. After `fill_input` succeeds, immediately call `clear_overlays()` to remove the highlight. Only use `valueToType` when the user genuinely must type the value themselves (e.g. password, personal data).
+- `fill_input` not found → `click_element(hint)` to focus the field, then retry `fill_input`. If still failing, use `find_and_highlight(hint, "Click here — I'll fill it in")` (NO `valueToType`) then `wait_for_click()` then retry `fill_input` — after the user focuses the field by clicking, the active-element fallback fills it automatically. `find_and_highlight` uses DOM positioning (pixel-perfect) — only fall back to `take_screenshot` + `highlight_region` if `find_and_highlight` returns false. After `fill_input` succeeds, immediately call `clear_overlays()` to remove the highlight. Only use `valueToType` when the user genuinely must type the value themselves (e.g. password, personal data).
 - Waiting for async result (build, save, deploy) → `wait_for_selector(selector, timeout)`
 - Never use Bash to work around a stuck browser interaction

package/dist/index.js

@@ -27,7 +27,7 @@ async function main() {
   const bridge = new WsBridge();
   const server = new McpServer({
     name: "chromeflow",
-    version: "0.1.7"
+    version: "0.1.9"
   });
   registerBrowserTools(server, bridge);
   registerHighlightTools(server, bridge);

package/dist/tools/flow.js

@@ -70,31 +70,6 @@ If the click causes page navigation, this resolves when the new page finishes lo
       };
     }
   );
-  server.tool(
-    "wait_for_navigation",
-    "Wait for the browser to navigate to a new page (without requiring a prior click watch). Useful after calling open_page or after a form submission.",
-    {
-      urlPattern: z.string().optional().describe("Substring to match in the new URL \u2014 waits for any navigation if omitted"),
-      timeout: z.number().optional().describe("Max seconds to wait (default 30)")
-    },
-    async ({ urlPattern, timeout = 30 }) => {
-      const response = await bridge.request({
-        type: "start_click_watch",
-        timeout: timeout * 1e3
-      });
-      const url = response.url ?? "";
-      if (urlPattern && !url.includes(urlPattern)) {
-        return {
-          content: [
-            { type: "text", text: `Navigation detected to ${url} (pattern "${urlPattern}" not matched \u2014 proceeding anyway).` }
-          ]
-        };
-      }
-      return {
-        content: [{ type: "text", text: `Page navigated to: ${url}` }]
-      };
-    }
-  );
   server.tool(
     "wait_for_selector",
     `Wait for a CSS selector to appear on the page. Use this instead of polling with take_screenshot.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chromeflow",
-  "version": "0.1.7",
+  "version": "0.1.9",
   "description": "Browser guidance MCP server for Claude Code — highlights, clicks, fills, and captures from the web so you don't have to.",
   "type": "module",
   "bin": {