How-to· 1 min
Letting AI drive a browser — useful and fragile
If an API exists, use the API. This is the last resort, used deliberately.
AI Tools Hub Editorial · published · updated
Suitable work
- Extracting data from internal systems with no API
- Entering the same information into several sites
- Periodic checks of stock, price or listing status
- Scheduled retrieval from pages behind a login
Why it breaks
- A button label changed
- A confirmation dialog was added
- Two-factor authentication was enabled
- The page got slower
- Automated access was blocked
Credentials
- Create a dedicated account with minimum privileges
- Never use a personal account — it dies with the employee and blurs accountability
- Keep secrets in a secret manager, not in the flow
- Do not build around circumventing two-factor authentication
Check the terms
Many sites prohibit automated access, and some restrict what you may do with retrieved data. Internal systems are a different matter; external sites need the terms read first.
Run it isolated
Browser automation touches pages you do not control, so do not run it on your own machine. Use an isolated service. And since page content reaches the model, it is a prompt-injection path: grant no authority to what was read.
FAQ
How is this different from RPA?
The model looks at the screen, so small layout changes break it less often. It also introduces the possibility of misjudgement, so reliability did not simply improve.