# The browser

V3Code ships its own browser, and the agent can **drive anything in it** — not a screenshot-and-click toy, but a **Playwright-backed automation surface** with dev-grade tools. The agent can navigate, read the DOM headless, take images, click through a page, work an authenticated flow, reverse-engineer a layout — it can even drive interactive pages and games. Real work on the web, not a demo.

It's **DOM-driven first** (the agent targets real elements by reference and selector) with **screenshots available** when it needs to see the page — so it's precise where a purely visual agent guesses.

The headline trick: it can **reconstruct a website pixel-perfect** — pull a live site's build back into source you can study, clone, or rebuild from.

## What the agent can do

### Drive the page

### open\_browser / open\_browser\_page

Open a URL — with mobile emulation when you need it — in the built-in browser.

### navigate\_page · click\_element · type\_in\_page · hover\_element · drag\_element

Full interaction: navigate/back/forward, click (including double-click and specific mouse buttons), type text and keys, hover, and drag between elements.

### handle\_dialog

Handle JavaScript dialogs and native file pickers — including selecting files for upload.

### fill\_form

Fill a whole form in one call.

### See and extract

### read\_page · extract\_page\_data · screenshot\_page

Read page content, pull structured data with a focus hint, or screenshot the page or a single element.

### get\_computed\_styles · watch\_page

Inspect an element's computed CSS, or wait for the page to reach a condition before continuing.

### Inspect like a developer

### get\_browser\_console\_logs · intercept\_network · get\_browser\_network\_log

Read the console, intercept requests by URL pattern (optionally with bodies), and pull the network log — the tools you'd use to understand or reverse-engineer how a site actually works.

### reconstruct\_page\_sources

Reconstruct a live page's sources into files — the basis for cloning a site pixel-perfect, bundling it out of the browser, or studying how it's built.

### Go beyond the built-ins

### run\_playwright\_code

Run arbitrary Playwright code against the page for anything the named tools don't cover.

### save\_browser\_session · restore\_browser\_session

Save and restore a browser session, so the agent can stay logged in across runs instead of re-authenticating every time.

## Why it's more capable than a basic browser agent

Most agent browsers can click, type, and screenshot. V3Code's adds the developer layer: **network interception, console access, computed styles, session persistence, page-source reconstruction, and raw Playwright** — which is what lets it reverse-engineer a page, clone a layout, drive an auth'd flow, or debug why a site behaves the way it does.