> ## Documentation Index
> Fetch the complete documentation index at: https://docs.v3code.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# The browser

> A Playwright-backed browser the agent drives — navigate, fill forms, inspect network, save logins, and reconstruct pages pixel-perfect.

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

<ParamField path="open_browser / open_browser_page" type="url, mobile">
  Open a URL — with mobile emulation when you need it — in the built-in browser.
</ParamField>

<ParamField path="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.
</ParamField>

<ParamField path="handle_dialog" type="accept, prompt_text, select_files">
  Handle JavaScript dialogs and native file pickers — including selecting files for upload.
</ParamField>

<ParamField path="fill_form" type="fields">
  Fill a whole form in one call.
</ParamField>

### See and extract

<ParamField path="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.
</ParamField>

<ParamField path="get_computed_styles · watch_page">
  Inspect an element's computed CSS, or wait for the page to reach a condition before continuing.
</ParamField>

### Inspect like a developer

<ParamField path="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.
</ParamField>

<ParamField path="reconstruct_page_sources" type="script_url, output_dir, method">
  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.
</ParamField>

### Go beyond the built-ins

<ParamField path="run_playwright_code" type="code, timeout_ms">
  Run arbitrary Playwright code against the page for anything the named tools don't cover.
</ParamField>

<ParamField path="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.
</ParamField>

## 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.