Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.eluu.ai/llms.txt

Use this file to discover all available pages before exploring further.

Some work lives in tools that don’t have APIs — old admin panels, niche SaaS products, sites with login walls and no developer access. Browser use solves this. Your colleague drives your own browser, on your laptop, signed in as you. You watch them work. They click buttons, fill forms, read pages, and take screenshots — all in your real browser session, with your real credentials, the way you’d do it yourself.

​
When to use it

Reach for browser use when an integration doesn’t exist for what you need:
  • A vendor portal that has no API.
  • An internal admin tool that no one ever wired up properly.
  • A research task that needs to sign in to a site and click around.
  • A workflow that depends on an exact UI flow (like submitting a form a particular way).
  • Filling out a long web form with data you’ve gathered elsewhere.
If a tool already has an Eluu integration (Salesforce, HubSpot, Linear, etc.), use that. Browser use is for the gaps.

​
How it works

Install the Eluu Chrome extension from the Chrome Web Store. Pair it to your account once. After that, when a colleague decides browser use is the right tool, the extension drives Chrome on your machine. You see what’s happening. The colleague describes each action — clicking the export button, filling in the date range. If something looks off, pause the session. Because it’s your browser, anything you’ve already signed in to works. The colleague doesn’t need credentials to your tools — they’re using yours, the same way a teammate watching over your shoulder would.

​
Asking for it

Tell the colleague to use the browser when it makes sense.
Use the browser to sign in to our vendor portal and download last month’s invoices.
Open the admin panel for our subscription product and pull the list of accounts in trial.
Go to this URL, fill out the contact form with these details, and confirm submission.
If the colleague guesses wrong and tries to use the browser when an integration would work better, just point at the integration:
Use Salesforce, not the browser, for this.

​
What it doesn’t do

The colleague isn’t signing in for you. If you’re not signed in to a site, they can’t sign in — they don’t have your password. They’ll prompt you, you sign in once, then they continue. They also can’t run while your laptop is closed. Browser use needs your browser open.

​
Where to next

Integrations

Where direct API integrations are the better tool.

Skills

Wrap a repeatable browser flow as a skill.