Browser Use 1.0.0
WarnAudited by ClawScan on May 10, 2026.
Overview
The skill is a coherent Browser Use integration, but it gives autonomous cloud browsers access to persisted login sessions with limited scoping or approval guidance.
Install only if you are comfortable letting Clawdbot and Browser Use control a cloud browser that may be logged into your accounts. Use a separate browser profile, avoid syncing personal cookies, keep the API key scoped and revocable, approve sensitive actions manually, and stop/delete sessions and profiles when finished.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A cloud browser controlled through this skill could access or act inside accounts already logged into the selected browser profile.
The skill relies on both a provider API key and authenticated browser session state. Those privileges can let the agent create billable sessions and act as the user on sites where the profile is logged in.
API Key is read from clawdbot config at `skills.entries.browser-use.apiKey` ... Use profiles to persist logins and cookies.
Use a dedicated Browser Use API key and a dedicated low-privilege browser profile. Avoid syncing personal Chrome cookies unless you explicitly want the cloud browser to use those sessions.
An imprecise prompt or unsafe webpage could lead the browser task to take unintended actions in logged-in services.
The skill documents an autonomous task agent that can operate a browser using an authenticated profile, but it does not define approval gates, allowed actions, allowed sites, or safeguards for high-impact actions.
Run autonomous browser tasks - like a subagent that handles browser interactions for you. Give it a prompt and it completes the task. ... `profileId` | Use a profile for auth
Require explicit user approval before using authenticated profiles for purchases, account changes, messages, posts, deletions, or other irreversible actions. Prefer bounded prompts with `startUrl` and `maxSteps`.
If the browser control endpoint or configured profile is exposed or reused unexpectedly, other agent components may control the logged-in browser session.
The cloud browser control URL is passed into the gateway/browser tool configuration. The instructions do not specify how to protect, scope, rotate, or remove that control endpoint, which may control an authenticated browser session.
gateway config.patch '{"browser":{"profiles":{"browseruse":{"cdpUrl":"<cdpUrl-from-response>"}}}}' ... Now use the `browser` tool with `profile=browseruse` to control it.Treat CDP URLs as sensitive. Stop sessions when finished, remove stale gateway profiles, and avoid connecting profiles that contain sensitive logins unless necessary.