browser-use

name	browser-use
description	Browser tasks through Warm Chrome; no Chrome for Testing.
role	tool-workflow

Browser Use

One public workflow for browser tasks through warm Agent Chrome. Code owns intent, authority, routing, runbooks, workflow recovery, and outcomes. The LLM drives the selected adapter through its native tool surface after verified attachment.

Start

• Code-owned task: browser-use guide — copy-paste core loop (task list → task run --intent <id> → run status).
• Open-ended task: read browser-connect dashboard --json, select a connectable adapter from its evidence, then run browser-connect connect <adapter> --json.
• Open-ended login wall: keep the verified handoff and run browser-use auth login --help only to discover the contract and required invocation. Then invoke the admitted browser-use auth login command and follow its typed continuation; never create a Runbook only to access auth.
• Read the selected adapter's native help or tool schema. Use that surface to perform and prove the requested outcome. Return only bounded outcome and artifact references through Browser Use.
• Never copy adapter commands, response parsing, tab or page mechanics, navigation, actions, snapshots, screenshots, findings, or retries into this skill or Browser Use runtime. Owner: docs/adr/0031-browser-use-delegates-browser-mechanics-to-adapters.md.
• browser-use --help — all command families; every leaf has --help.
• Connection attaches automatically on task run / runbook run. Open-ended native delegation uses browser-connect directly because it owns attachment. Envelopes and repair paths stay owned by runtime/browser-connect.
• For Runbook or Reviewed Action authoring and activation, read ../../docs/runbooks/authoring-runbooks.md before mutation.
• For browser-use project work, read references/coding-task-tracker.md before choosing or updating a tracker task.

Invocation

• From any CWD: browser-use resolves on PATH (setup sync installs and repairs the bin; setup status verifies).
• Repo-local: bun run browser-use <command> from skills/browser-use.

Safety

• Warm Chrome only: real Google Chrome, dedicated persistent profile, loopback CDP. Never Chrome for Testing, throwaway or everyday-default profiles, isolated Playwright/Puppeteer launch, AppleScript/open, or cold-browser fallback. Invariant detail: references/warm-chrome.md.
• No convention endpoints: never hardcode http://127.0.0.1:9222; verified endpoints travel inside envelopes.
• Never mass-kill by port; listener remediation is operator-owned (runtime/browser-connect/REPAIR.md#v1-inspect_listener).
• Never print tokens, cookies, passwords, or auth-bearing URLs; report secret checks by shape only (present/absent, length, status code).
• Never route a browser login through the generic one-password skill or an ambient op session. Follow the browser-use auth login continuation.

Owners

• Commands, flags, exit codes, diagnostic codes: skills/browser-use/src/command-contract.ts.
• Bundled guide content: skills/browser-use/src/browser-use-guide.ts.
• Connection, Verified Handoff Envelope, repair paths: runtime/browser-connect (src/command-contract.ts, REPAIR.md).
• Browser Authentication Transaction and its two entry modes: skills/browser-use/src/browser-use-runbook-auth.ts.
• Managed and user-present 1Password access leases: skills/browser-use/src/browser-use-auth-access.ts.
• Admitted native access-provider wiring: skills/browser-use/src/browser-use-runtime.ts and runtime/browser-use-security.

Next Safe Action

• Unsure where to start: run browser-use guide.
• Any failure envelope: read error.code, dispatch continuation.next_action_id verbatim, obey continuation.constraints. Exit 20 carries exactly one Repair Path anchor — follow it; never retry a convention port or fall back to a cold browser.
• Blocked or recovering: browser-use guide --topic recovery.
• Repeated terminal defect in browser-use, browser-connect, warm-chrome, a supported adapter CLI, or Browser Use Security; wrong or missing prose route; or prose-led outcome that does not satisfy the user's explicit request: hand off to ../browser-use-support-ticket/SKILL.md; file one redacted, deduplicated public support ticket. Do not file expected login, user, or target-site blockers.