Signal Collective
Hong Kong Book a call
Signal Collective The Library Operations
We find where your growth is · Then we build it

Operations · The plumbing: automations, inboxes, browsers for agents. · a tool

Hand a boring web task to your AI

The open-source project browser-use, by browser-use

“Agents that use the browser.” — the project's own words, on GitHub

What it does
You describe a task in plain English, fill in this form, pull product prices into a spreadsheet, and it drives a real browser to do it: clicking, typing, reading the page, the way you would by hand. It needs an AI model behind it to decide what to click, so you connect it to a model you already use. It's code, not a finished app, so someone, even your own AI, writes a short script per job. It's good at repetitive browser chores, filling forms, pulling data off a page, checking a site for change, and bad at anything needing a login it lacks or a CAPTCHA in the way.
Replaces
an afternoon of manual browser work, form-filling, price-checking, copying between tabs
For
A founder or operations person who wants repetitive browser chores done automatically and has someone, or their own AI, able to write a short script for each job.
Not for
Not for anyone without help writing the task script, and not for anything behind a login you can't give it or a site that blocks bots outright.
Setup
15 min · Claude Code, Kimi, Gemini CLI or Codex · python 3.11 or newer, an API key for the LLM it drives, its own key or your existing OpenAI, Anthropic or Google key
Two tools, not talking One switch Joined, read-only inbox sheet turn it on inbox sheet read-only

Get it running

Paste this into the AI that runs on your computer. It does the install, checks it works, and tells you what to type first. If anything fails, paste the error back to it.

Paste into Claude Code
Install browser-use (https://github.com/browser-use/browser-use) on this computer and get it working for me. I am not a developer; explain each step in one line as you go and never skip one. You are Claude Code, running on my machine.

1. Check what this machine already has (git, Python or Node as the project needs, Docker if the README says so). Tell me anything missing and install it, asking me before anything that needs my password.
2. Clone https://github.com/browser-use/browser-use into ~/tools/browser-use and follow the README's install exactly.
3. Configure it. If it needs an API key or a login, stop and ask me for it; never guess one and never store it anywhere except where the README says.
   Tool-specific notes: Install with uv add browser-use (or pip install browser-use); it needs Python 3.11 or newer.
Add an LLM API key to a .env file in the project, BROWSER_USE_API_KEY for Browser Use's own models, or your own ANTHROPIC_API_KEY or GOOGLE_API_KEY if you'd rather use a model you already pay for.
Run the example agent script from the README (build an Agent with a task and a ChatBrowserUse model, then call agent.run()) as your smoke test, and watch the browser window it opens to see exactly what it clicked.
If a task needs to stay logged in somewhere, point it at your existing browser profile rather than typing a password into the script, never store a password in the task text itself.
4. Run the smallest test the README gives, and show me the output.
5. When it works, tell me what to type first, in one line, for this job: Point it at one page you'd otherwise skim yourself.
If anything fails, show me the exact error and fix it before going on.

What to point it at first

1

Point it at one page you'd otherwise skim yourself

Give it a single, boring task, like pulling a list of prices off one page, and check every value against the real page before you trust the output.

2

Fill in one form with real information

Have it complete one job application or contact form with your own details, then read it back before you ever let it submit for real.

3

Try one multi-step task on public pages

Give it something needing a few clicks in sequence, like comparing three public product pages, and watch the run, that's how you learn what it gets wrong.

What it must never do unattended

  • Start read-only. Let it report for a week before it is allowed to act.
  • Never automate anything you cannot undo with a click.
  • Never past a login or a CAPTCHA. Public pages only; respect robots.txt and the site's terms.
  • Never let it submit a form or complete a checkout on your behalf without watching the run, a wrong click here is a real action, not a draft.

Who made it

browser-use/browser-use on GitHub, under the MIT licence. 113,626 stars, checked 9 September 2026. Last change 7 September 2026. We did not write it; we checked it, and wrote this page so you can use it.

Also in Operations

What's in the library is how we work.

If you're launching or growing a brand across Asia and the West, a call is where we work out whether it's a fit.