A real browser it can drive
Chrome
bia runs Google Chrome with its own profile: cookies, logins, and tabs that belong to it. It can read pages, fill forms, and use passkeys from its vault.
The browser is installed and started as part of life on the machine, not a disposable sandbox. Remote debugging talks to the real Chrome so bia can snapshot a page, click, type, navigate, and check network activity.
When Meta or Google put up awkward dialogs, bia works through them the way a careful person would — including asking you for a captcha instead of guessing. File uploads can be fed straight into the page’s hidden inputs.
Passkeys are bridged through the secrets vault and a small Chrome helper, so sites that want a hardware-like key can still be signed into without pasting passwords into the chat.
In everyday life
- Keeps a dedicated Chrome profile across days and reboots.
- Opens sites, fills forms, and reads what is on the page.
- Notices tabs opening and closing without constant polling.
- Uses stored passkeys for sites that support them.
Unlike a normal chatbot
Many agents get a temporary browsing API with no memory of yesterday’s login. bia’s browser is its desk — the same desk tomorrow.