chromeflow 0.1.1 → 0.1.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CLAUDE.md +1 -0
- package/dist/index.js +1 -1
- package/dist/tools/browser.js +1 -1
- package/package.json +1 -1
package/CLAUDE.md
CHANGED
|
@@ -97,5 +97,6 @@ Use the absolute path for `envPath` — it's the Claude Code working directory +
|
|
|
97
97
|
- After any action → `get_page_text()` to check for errors (not `take_screenshot`)
|
|
98
98
|
- `click_element` not found → `scroll_page("down")` then retry
|
|
99
99
|
- Still not found → `take_screenshot()` then `highlight_region(x,y,w,h,msg)`
|
|
100
|
+
- `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,"Type: [value]")` — do NOT ask the user to type unless all automated attempts have failed
|
|
100
101
|
- Waiting for async result (build, save, deploy) → `wait_for_selector(selector, timeout)`
|
|
101
102
|
- Never use Bash to work around a stuck browser interaction
|
package/dist/index.js
CHANGED
package/dist/tools/browser.js
CHANGED
|
@@ -13,7 +13,7 @@ function registerBrowserTools(server, bridge) {
|
|
|
13
13
|
);
|
|
14
14
|
server.tool(
|
|
15
15
|
"take_screenshot",
|
|
16
|
-
"Capture a screenshot
|
|
16
|
+
"Capture a screenshot ONLY when click_element or fill_input has failed and you need pixel coordinates to call highlight_region. DO NOT use this to check page state, confirm actions, or see what loaded \u2014 use get_page_text for all of that.",
|
|
17
17
|
{},
|
|
18
18
|
async () => {
|
|
19
19
|
const response = await bridge.request({ type: "screenshot" });
|
package/package.json
CHANGED