chromium-browser

原文涵盖的主题

• Chromium Browser
• Environment Contract
• Reference Routing
• Call Budget
• Page Ownership
• Interaction and Evidence
• Website Sign-In with 1Password
• Human Gates

Operate the configured Chrome DevTools MCP against the existing shared browser without disrupting unrelated tabs or authenticated state. Prefer this skill for rendered web pages in shared Chromium. When they fit, use search, fetch, APIs, CLIs, or connectors for retrieval. Use host computer-use/CUA tools for native apps, browser chrome, and browser-internal pages such as chrome://extensions. Also use native controls for a user-requested browser without a usable browser integration. Existing task authorization covers this controller choice without a separate permission request. Use one controller at a time for each browser. Preserve existing profiles, sessions, and unrelated tabs across controllers. Native controls do not relax privacy rules or approval requirements for the action itself. If the user selects another available browser integration, follow its tool contract. Treat the bundled scripts/chrome-devtools-mcp.sh wrapper and the tools exposed in the current session as authoritative. The wrapper runs the globally installed chrome-devtools-mcp executable and sets flags, logging, and browser attachment. Do not run the MCP package directly. The MCP attaches to an existing remote-d

这里只展示节选，请以完整原文和当前要求为准。