Your browser

Let an agent work in your browser#

Many sites you use have no Opser app or integration: a supplier portal, a carrier's booking site, an older system your team signs in to. With the Opser Chrome extension signed in to your workspace, an agent can work on those sites in your own Chrome, signed in as you.

Open the Northwind supplier portal, find order PO-20817 and tell me its delivery date.

The agent opens its own tab, reads the page, and clicks, types and chooses options the way you would. To have it work in a tab you already have open, say which one. It keeps going until the task is done, and asks you only when you have to act yourself: signing in, a two-factor code, a CAPTCHA, or a choice only you can make.

Chat beside the page#

Click the Opser icon in Chrome's toolbar to open your agents in Chrome's side panel. Choose an agent from the menu and ask about the page you're on: it finds your open tabs and works in the one you mean. Records an agent links to open in a normal tab. The extension is only for your agents: it doesn't record meetings or read pages on its own.

What you see while it works#

The tab an agent works in glows blue and says which agent is using it. Tabs it opens sit together in a blue Opser tab group. Chrome also shows its own bar saying the extension is debugging the browser. In the chat, each step shows as it happens, such as opening a page or clicking.

An agent never drives your Opser workspace itself in your browser; it uses its Opser tools for that. It closes only the tabs it opened.

Stop it at any time#

Press Stop on the glowing tab, or Cancel on Chrome's bar, and the agent lets go of your browser at once and ends that task. Your next request can use your browser again. In the side panel, Opser in Chrome (at the bottom of the menu) has the switch that turns agents off for this browser and back on, and shows who is working. When you've turned them off, an agent asks you before carrying on.

The cloud browser#

An agent can also use Opser's cloud browser, which works when your computer is off. It keeps the sign-ins you make in it for next time. When a site needs you, the chat shows you a button to take the cloud browser over: sign in or pass the check, tell the agent you're done, and it carries on. Only you can open it.

Automations#

A scheduled automation can use the browser of the person who set it up, while they're still a member of the agent, or the cloud browser. If their browser isn't connected, the run says so instead of trying again and again. Steps that change something, such as clicking, typing or going back to a submitted form, count as done, so a retried run doesn't repeat them.

Costs and limits#

Working in your own browser costs only the agent's usual model use. The cloud browser also bills the time it runs; check Usage. Read the form before letting an agent submit anything that sends, buys, books, pays or deletes; for now an agent doesn't ask for approval before it acts in a browser.