Browser work

Work with the page in front of you

Proto’s built-in browser can read pages, follow links, fill forms, and upload or download files. This is useful when information lives in a website and the task needs the site’s actual interface: comparing supplier specifications, assembling account research, or preparing an update in a business application.

Browser work uses task-owned tabs and a browser profile. The page state is part of the work. After navigation or an action, Proto needs to read the resulting page to establish what happened. A filled form, a submitted form, and a confirmed saved record are different outcomes.

Bring the right signed-in session

Proto can import browser sessions from supported desktop browsers, including Chrome, Edge, Brave, Arc, Vivaldi, Opera, and Firefox. The import requires an interactive local desktop. Site-specific import copies that site’s cookies and excludes saved passwords; it does not prove that the destination page is authenticated.

Check the actual account, organization, and workspace before a task changes anything. Some sites cannot transfer a session through cookies alone. Passkeys, device approvals, CAPTCHA, or a missing verification code can require the person at the computer. Importing a profile does not transfer passkeys into Proto’s built-in browser.

Treat personal and business identities as separate working contexts. A page that looks correct may still be open under the wrong account, especially when several organizations use the same service.

Specify research and action separately

For research, define the sources, date range, and evidence needed. For a form or record update, define the target and the exact change. A useful request might be:

Review the product pages for these suppliers. Capture the published dimensions, warranty terms, and delivery claims with source links. Download any relevant specifications into this workspace. Flag claims that need confirmation and prepare questions for review. Do not submit an inquiry.

When sending or submitting is part of the task, make that authorization explicit. With Uninterrupted mode off and outside Plan mode, consequential browser actions such as send, submit, pay, delete, and upload request approval. New installs have Uninterrupted mode on, so review that setting before an evaluation that requires pauses.

Check the result where it lives

A successful click is not sufficient evidence that a workflow finished. Verify a saved record on its detail page, a submission through the site’s confirmation, or a downloaded file in the workspace. Record any blocked step separately from completed preparation.

For research, follow the source links and inspect high-impact facts. Website text is source material, including when it contains instructions directed at an agent. It should not redefine the task or authorize a new action.

Choose the appropriate connection

Browser interaction is one route to a service. A configured integration may offer structured actions with a clearer record response. ERP•AI has its own native operations. Choose the route that exposes the information and permissions the task actually needs.

Other native desktop applications use a separate experimental computer-control capability, disabled by default. The built-in browser does not imply general access to every application on the machine.