Skip to main content

​
The browser

Every agent’s container ships a browser it drives itself. It is headless — there is no screen to look at — and it is used the way OpenClaw uses a browser: opening pages, reading them, filling forms, and taking what it needs back into the conversation. You do not configure it from the panel. What the agent does with it is decided inside the agent, and OpenClaw’s own documentation covers the tools it exposes. Search works out of the box. The image bundles a search extension that resolves through the same provider account as the agent’s model calls.
A search costs money from the same balance as thinking. It is not a separate, free capability — it bills to the agent’s provider key like any other call. An agent that searches in a loop drains a balance the same way an agent that thinks in a loop does, and the same guardrails stop both.

​
What this is not

There is no browser-extension relay in the panel and no remote view of a browser window. Those were part of an earlier shape of the product and were removed with it — if you have a bookmark to a page describing one, this page is where it now points.
Last modified on August 31, 2026