yunti-browser-runtime 0.2.0 → 0.2.1

package/mcp/tools.js

@@ -1359,6 +1359,8 @@ export function toolUsageHints(args = {}) {
       "After yunti_new_page, use the returned browserSessionId for follow-up calls on the new tab.",
       "Sessions expire quickly when the extension stops polling; stale-session errors include the reason and recovery hint.",
       "If a tool call fails due to parameters, inspect this hint output and the tool schema before retrying.",
+      "In 0.2.1+, default observe-first page actions avoid automatic Chrome debugger attachment; prefer yunti_observe_page plus fresh-uid yunti_click/yunti_hover/yunti_fill/yunti_select/yunti_scroll/yunti_type_text/yunti_press_key on anti-debug-sensitive pages.",
+      "Chrome debugger banners may still appear for explicit low-level or advanced tools such as yunti_cdp_send_command, raw CDP diagnostics, performance tracing, screenshot fallback paths, drag, upload, emulation, resize, or legacy snapshot compatibility.",
       "Prefer sanitized diagnostics before raw CDP events; screenshots are visible pixels and are not DOM-redacted.",
     ],
     workflows: {
@@ -1397,6 +1399,7 @@ export function toolUsageHints(args = {}) {
         "Call yunti_get_tool_usage_hints when tool usage is uncertain.",
         "Call yunti_list_browser_targets and choose the intended browserSessionId.",
         "Call yunti_observe_page before page actions and use fresh uids whenever possible.",
+        "On anti-debug-sensitive pages, stay on the default observe-first action tools; do not switch to CDP unless explicitly needed.",
         "After every action, verify by observing again or using snapshot, evaluate, screenshot, network, or console tools.",
         "For async rendering, validation, navigation, option loading, or infinite scroll, call yunti_wait_for, then yunti_observe_page, then continue with a fresh uid.",
         "If a result has ok=false, code, recoveryHint, or nextStepHint, follow that guidance before retrying.",
@@ -1420,6 +1423,7 @@ export function toolUsageHints(args = {}) {
         "Ask me before submitting, deleting, approving, purchasing, publishing, uploading sensitive files, or changing production data.",
         "Do not expose raw cookies, passwords, auth headers, tokens, private keys, or other secrets.",
         "Prefer sanitized diagnostics; use raw CDP or screenshots only when needed, and summarize safe findings.",
+        "On anti-debug-sensitive pages, use observe-first page actions because 0.2.1+ avoids automatic Chrome debugger attachment on the default action path.",
       ],
       minimalUseCases: {
         clickByUid: [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "yunti-browser-runtime",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "type": "module",
   "description": "Local browser runtime and MCP tools for AI agents.",
   "license": "MIT",

package/scripts/doctor.js

@@ -120,7 +120,8 @@ function buildNextSteps(checks) {
     steps.push("Save the same token in the extension popup.")
   }
   if (checks.bridge.ok && !checks.bridge.extensionConnected) {
-    steps.push("Load the extension, open an http/https page, then refresh the target page.")
+    steps.push("Load or reload the extension and open an http/https page; Yunti will auto-register accessible tabs.")
+    steps.push("If no page appears after a few seconds, refresh the target page as a fallback.")
     steps.push(`Open the optional local console for live status: ${checks.bridge.consoleUrl}.`)
   }
   if (!checks.mcpServer.ok) {

package/skills/yunti-browser-runtime/SKILL.md

@@ -92,6 +92,8 @@ Ask the user before submitting, deleting, approving, purchasing, publishing, upl
 
 ## CDP Rules
 
+- In `0.2.1+`, default observe-first page actions avoid automatic Chrome debugger attachment. `yunti_observe_page`, fresh-uid `yunti_click`, `yunti_hover`, `yunti_fill`, `yunti_select`, `yunti_scroll`, `yunti_type_text`, and `yunti_press_key` should be the first choice on anti-debug or anti-bot-sensitive pages.
+- Chrome may still show its debugger banner when using explicit low-level or advanced tools, including `yunti_cdp_send_command`, raw CDP event diagnostics, performance tracing, screenshot fallback paths, drag, upload, emulation, resize, and legacy snapshot compatibility. Use those only when the task truly needs them.
 - Never run CDP method names in a terminal or shell.
 - Always call CDP through `yunti_cdp_send_command`.
 - `yunti_cdp_send_command` requires `method`; `params` is optional but must be an object when provided.
@@ -192,7 +194,7 @@ Ask the user before submitting, deleting, approving, purchasing, publishing, upl
 
 ## Recovery
 
-- No connected tab: ask the user to open a page, load the extension, or refresh the page.
+- No connected tab: call `yunti_list_browser_targets` or doctor first so Yunti can auto-register accessible tabs; ask the user to refresh only when the page remains invisible because of browser restrictions or a failed injection.
 - Stale session: call `yunti_list_browser_targets` and use the latest `browserSessionId`.
 - Stale or missing page uid: observe again once `yunti_observe_page` is available, or take a fresh snapshot for compatibility workflows.
 - Wrong tab: use `yunti_list_browser_targets` to find the intended tab, then route CDP with that tab's `tabId` or `targetId`.