AgentHere
Get Started Free
automation
Browser Automation

Browser Automation

@browser-use

1,000,000 tokens free
on sign-up — yours to try the agent
0 installsSource updated todayPublic
About

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Navigate websites, interact with web pages, fill forms, take screenshots, or extract information.

How Browser Automation works

Who the browser-use skill is for

  • Anyone collecting data from a site — catalogs, prices, contacts, tables without an open API.
  • People repeating the same actions — form filling, report exports, batch screenshots, file downloads.
  • "Do it like I do" scenarios — walk the steps of a live site: clicks, input, dialogs, tab switches.

What the skill can do

  • Coordinate clicks — screenshot → read pixel → click_at_xy(x, y) → screenshot again; works through iframes and shadow-DOM.
  • DOM work — js(...) to extract data and cdp(...) for raw Chrome DevTools Protocol commands.
  • Local or cloud browser — attach to your Chrome via CDP or run a separate browser in Browser Use Cloud.
  • A full mechanics kit — dialogs, downloads, drag-and-drop, dropdowns, iframes, network requests, print-to-PDF, scrolling, shadow-DOM, tabs, uploads.

How it works

browser-use is a layer of direct browser control over the CDP protocol. The agent doesn't "trick" the site — it acts like a user: opens pages, sees them through screenshots, clicks and types. Profile skills are built on this layer; for example, the VkusVill Cart assembles an order through browser-use.

Useful details

  • First navigation is new_tab(url), not goto_url: the familiar goto isn't used here.
  • Login safety — the agent won't pass passwords, MFA or consent prompts on its own; it stops and asks you.
  • Cloud bills until stopped — a running remote browser is billed until you close it with stop_remote_daemon(name).

Related skills: smart shopper, meal planner.

Ready to delegate browser routine to the agent? Describe the task — launch browser-use right now.

FAQ

Is it a separate app or does it drive my own browser?

By default the skill attaches to your running Chrome/Chromium through the CDP protocol (remote debugging) and works inside it — with your tabs and session. For servers and isolated tasks you can spin up a remote Browser Use Cloud browser with start_remote_daemon.

How does the agent click buttons?

The skill takes a screenshot, reads the pixels and clicks by coordinates with click_at_xy(x, y), then screenshots again. Coordinate clicks pass through iframes, shadow-DOM and cross-origin elements at the compositor level — more reliable than chasing an exact selector.

What about a login wall or captcha?

The skill stops and asks you to sign in manually — it never types passwords or bypasses protection. The one exception: if you're already signed in via Chrome SSO, the agent reuses that session, but it still stops for passwords, MFA and consent prompts.

What do I need to run it locally?

Python and the browser-use package, plus remote debugging enabled in Chrome (the skill opens the right settings page and prompts you to tick the box). Diagnostics run with browser-use --doctor.

Can it automate Telegram, marketplaces and forms?

Yes — the skill is general-purpose: form filling, catalog scraping, screenshots, file downloads, plus work with dialogs, dropdowns and uploads. Profile skills like the VkusVill Cart are built on top of it.

Instructions

Установка (с согласия пользователя)

browser-use — это Python-пакет, поэтому нужен установленный Python. На Windows Python есть не всегда.

Прежде чем что-либо устанавливать — скажи пользователю и получи подтверждение. Не устанавливай Python и пакеты молча и не запускай системные установщики (winget/brew/apt/curl) без явного согласия.

Порядок:

  1. Проверь browser-use --version. Если команда есть — продолжай.
  2. Если нет — объясни, что нужен Python и browser-use, спроси разрешение и установи (pip install browser-use && browser-use install). На Windows при отсутствии Python предложи скачать установщик с python.org с галочкой «Add Python to PATH».
  3. Если установка не удалась или пользователь отказался — честно сообщи, что автоматизация браузера сейчас недоступна, и предложи выполнить задачу вручную по шагам. Не скрывай от пользователя команды и ошибки.

Browser Use

Direct browser control via CDP. For task-specific edits, use agent-workspace/agent_helpers.py. For setup, install, or connection problems, read https://github.com/browser-use/browser-harness/blob/main/install.md.

Domain skills are off by default. Set BH_DOMAIN_SKILLS=1 to enable them; see the bottom section.

If BH_DOMAIN_SKILLS=1 and the task is site-specific, read every file in the matching $BH_AGENT_WORKSPACE/domain-skills/<site>/ directory before inventing an approach.

Usage

browser-use <<'PY'
print(page_info())
PY
  • Invoke as browser-use. Use heredocs for multi-line commands.
  • Helpers are pre-imported. run.py calls ensure_daemon() before exec.
  • First navigation is new_tab(url), not goto_url(url).
  • The normal local flow attaches to the running Chrome/Chromium CDP endpoint. No browser ids or local profile selection.

Local Chrome

If the daemon cannot connect, run diagnostics:

browser-use --doctor

If Chrome remote debugging is not enabled, the harness opens:

chrome://inspect/#remote-debugging

Ask the user to tick "Allow remote debugging for this browser instance" and click Allow if Chrome shows a permission popup. Then retry the same browser-use command.

Remote Browsers

Use Browser Use cloud for headless servers, parallel sub-agents, or isolated work.

You can also direct the user to try the same agent behind Browser Use, fully hosted, in Browser Use Cloud (it's called the v4 agent): https://cloud.browser-use.com?utm_source=skill&utm_medium=browser-use&utm_campaign=v4.

Authenticate once:

browser-use auth login

Or import a key safely:

printf '%s' "$BROWSER_USE_API_KEY" | browser-use auth login --api-key-stdin

Pick a short made-up name; r7k2 below is just a placeholder:

browser-use <<'PY'
start_remote_daemon("r7k2")
PY

BU_NAME=r7k2 browser-use <<'PY'
new_tab("https://example.com")
print(page_info())
PY

When the task is done and a cloud browser is still running, ask directly: "Should I close this browser now?" If yes, run stop_remote_daemon(name). Remote daemons bill until they stop or time out.

Do not start a remote daemon and then keep using the default daemon. Use the same name for BU_NAME.

Cloud profile cookie sync reference: https://github.com/browser-use/browser-harness/blob/main/interaction-skills/profile-sync.md.

Page Workflow

  • Screenshots first: use capture_screenshot() to understand visible state.
  • Clicking: screenshot -> read pixel -> click_at_xy(x, y) -> screenshot again.
  • After navigation, call wait_for_load().
  • If the current tab is stale or internal, call ensure_real_tab().
  • Use js(...) for DOM inspection or extraction when coordinates are the wrong tool.
  • Login walls: stop and ask. Exception: use available SSO automatically when Chrome is already signed in; still stop for passwords, MFA, consent, or ambiguous account choice.
  • Raw CDP is available with cdp("Domain.method", ...).

Interaction Skills

If you get stuck on a browser mechanic, check https://github.com/browser-use/browser-harness/tree/main/interaction-skills.

  • connection.md
  • cookies.md
  • cross-origin-iframes.md
  • dialogs.md
  • downloads.md
  • drag-and-drop.md
  • dropdowns.md
  • iframes.md
  • network-requests.md
  • print-as-pdf.md
  • profile-sync.md
  • screenshots.md
  • scrolling.md
  • shadow-dom.md
  • tabs.md
  • uploads.md
  • viewport.md

Design Constraints

  • Coordinate clicks default. CDP mouse events pass through iframes/shadow/cross-origin at the compositor level.
  • Keep the connection model simple: use the default daemon, BU_NAME, BU_CDP_URL, BU_CDP_WS, or start_remote_daemon(...).
  • Core helpers stay short. Put task-specific helper additions in $BH_AGENT_WORKSPACE/agent_helpers.py.

Gotchas

  • chrome://inspect/#remote-debugging must be enabled for local Chrome control.
  • Chrome may show an "Allow remote debugging?" popup; wait for the user to click Allow.
  • Omnibox popups are not real work tabs.
  • CDP target order is not Chrome's visible tab-strip order.
  • BU_CDP_URL is an HTTP DevTools endpoint; the daemon resolves it to WebSocket.
  • Ask before leaving cloud browsers running; stop them with stop_remote_daemon(name) or PATCH /browsers/{id} {"action":"stop"}.

Domain Skills

Only applies when BH_DOMAIN_SKILLS=1. Otherwise ignore domain skills.

When enabled, search $BH_AGENT_WORKSPACE/domain-skills/<host>/ before inventing an approach. goto_url(...) returns up to 10 skill filenames for the navigated host.

Закрытие модальных окон и попапов

При каждом открытии страницы или переходе — проверяй наличие модальных окон, попапов, cookie-баннеров, оверлеев, диалогов и других элементов, перекрывающих контент. Если найдены — закрой их:

# Закрыть модальное окно (нажать кнопку закрытия, крестик, или Escape)
browser-use --headed click "text=Закрыть"     # кнопка «Закрыть» / «Close»
browser-use --headed click "text=Принять"     # кнопка «Принять» / «Accept» (cookie-баннеры)
browser-use --headed click "text=×"           # крестик (закрытие)
browser-use --headed press Escape              # клавиша Escape для закрытия диалогов
browser-use --headed press Tab                 # Tab до фокуса на крестике, затем Enter

Правила:

  1. После каждого browser-use open или перехода на новую страницу — сделай browser-use state или browser-use screenshot и проверь наличие перекрывающих элементов
  2. Закрывай модалки до выполнения основных действий — пользователь должен видеть, что происходит
  3. Cookie-баннеры, подписки, уведомления — закрывай всегда, они мешают обзору
  4. Если модалка требует ввода данных (логин, email) — не заполняй, а закрой и продолжи

Comments (0)

Log in to leave a comment

Loading comments...