Default
Built-in
One action per step, reading each page as text. Predictable and easy to follow.
- Opens, reads, clicks and types on any page
- Each step shows up in the dashboard chat
- Works on both OpenClaw and Hermes
A real browser, included with every assistant
Every assistant has its own private Chromium, hosted in the EU. It opens pages, fills in forms and can stay signed in to the sites you choose. You decide how it browses and where it may go.
How it browses
Choose how your assistant drives the browser
Three ways to operate the same private browser. Switch in the assistant's Browser tab at any time; it restarts once to apply the change.
For long, multi-step jobs
Browser Use
On Hermes, the assistant writes short scripts that run against the browser, so long jobs take fewer round trips. On OpenClaw you get Browser Use's tool set, one action per step.
- Each script appears in chat as a Browser code row you can open
- You confirm once before a Hermes assistant starts writing code
- A fixed, reviewed version installed with the assistant
For existing Playwright prompts
Playwright MCP
Microsoft's standard browser tool set. Pick it if your prompts or skills were written for Playwright.
- The same private browser with a different set of tools
- Works on both OpenClaw and Hermes
- Turn page scripting off and its scripting tools are hidden too
Sign-ins
Let it browse signed in as you
Export your cookies with an extension such as Cookie-Editor and paste them into the Browser tab. You review every site before anything is applied.
Export
Cookie-Editor JSON, a Playwright storage state or a Netscape cookies.txt file.
Review
See each site and how many cookies it holds. Untick what you don't want; known ad trackers start unticked.
Apply
Applied to the running browser straight away, with no restart. Normal remember-me sign-ins survive restarts.
Diali doesn't keep them
The export goes straight to your assistant's browser. Diali keeps only the list of sites, the count and the expiry date.
Every cookie expires
Cookies with no expiry get the lifetime you choose, 7 days by default, and no imported cookie lasts longer than 30 days.
Up to 150 per site
The same limit Chromium keeps for itself. Anything over it is listed before you apply, with sign-in cookies kept first.
Private assistants only
Import is refused on an assistant other people can message, such as one in a group chat.
Your assistant can read them
Cookies are sign-in tokens. The assistant, and the AI model it uses, can read them, so only import accounts you're happy for it to use.
Reset in one click
Sign the browser out of everything and clear stored site data. The assistant's files and settings stay.
Your limits
Limits you set, per assistant
Every setting lives in the assistant's Browser tab and applies to that assistant only.
Private and in the EU
Each assistant has its own browser and its own profile, hosted in Belgium. Nothing is shared between assistants.
Blocked sites
Name the sites the browser should never open.
Only these sites
Or turn it around and allow a short list of sites only.
Page scripting switch
Choose whether the assistant may run its own JavaScript on pages. On by default, since most automation needs it.
Ad blocking and cookie banners
Optional uBlock Origin Lite and a cookie banner dismisser, both off by default.
A clean slate
Reset the browser's data at any time without touching anything else the assistant knows.
FAQ
Browser questions, answered
The same answers you'll find in our help centre.
Yes. Every assistant, on every plan, has its own private Chromium browser hosted in the EU, at no extra cost. It keeps its own profile, so sign-ins and site data survive restarts. You manage it from the assistant's Browser tab.
Built-in suits most people: one action per step, easy to follow. Browser Use suits long, repetitive jobs; on Hermes it writes short scripts, and on OpenClaw it offers Browser Use's tool set. Playwright MCP is for prompts and skills already written for Playwright. You can switch at any time, and the assistant restarts once.
Install a cookie export extension such as Cookie-Editor and export the cookies for the site. Then open the assistant's Browser tab, choose Log the assistant in as me, paste the export, review the sites and confirm. It applies straight away, with no restart.
Diali doesn't keep the cookies: they go straight to your assistant's private browser and expire within 30 days at most. Diali keeps only the list of sites, the count and the expiry date. The assistant, and the AI model behind it, can read them, so import only accounts you're comfortable letting it use. Import is refused on assistants other people can message.
Some sites tie a sign-in to your device or network and end it when it's used from somewhere else. Imported cookies also expire after the period you chose, 30 days at most. Sign in again with a fresh export. If a site keeps signing the assistant out, it probably doesn't allow automated access.
Yes. In the Browser tab you can list sites the browser should never open, or allow only a short list. You can also turn on uBlock Origin Lite and a cookie banner dismisser; both are off by default. Site lists are a convenience, not a security boundary: an assistant that can run commands can still reach the web in other ways.
With the Computer add-on, the assistant browses in its desktop's browser, the one you can watch live. Blocked sites, the page scripting switch and the drivers work there too. Sign-in import, allowed-only lists and extensions need the private browser, so they aren't available on an assistant with a Computer.
Not yet. Routing the browser through your own proxy, and cloud browsers run on your own Browser Use account, aren't available to customers today. We'll announce them on this page when they are.
Browser
Put a real browser to work
Every plan includes a private browser for your assistant.