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

# Web & browser control

> How HQ specialists research the live web and drive a real browser — including the user's own browser — to finish work on sites with no API.

HQ specialists don't stop at static knowledge: they reach the **live web** and act on it. The browser is part of [qOS](/concepts/qos), and the broader picture lives in [How HQ works](/concepts/how-hq-works).

## Research on the live web

A specialist opens real pages, clicks, fills forms, and pulls out what it finds, the way a person would — from the region you choose, reaching sources, regions, and sites behind a login that an ordinary assistant gets blocked from. Answers come back with their sources, not a confident guess.

This matters because ordinary automation gets blocked on sight: most tools announce themselves, behave like a script, and render in ways a real machine never would. HQ's browser is built to look and behave like a real person on a real machine, so an agent can get legitimate work done on the sites your team already uses — including those with no API.

<CardGroup cols={2}>
  <Card title="A real browser, not a shell">
    A web browser built in Rust, driven from the platform — not a stripped-down automation shell.
  </Card>

  <Card title="Human-like behavior">
    Natural mouse curves, reading-pace pauses, and varied scrolling, so a session reads as genuine use rather than a script.
  </Card>

  <Card title="Real hardware rendering">
    Renders on genuine hardware, so pages render exactly as they would on a real computer.
  </Card>

  <Card title="Country-pinned egress">
    A proxy pool with rotation, plus leak prevention, so locale, timezone, and geo are pinned to the egress.
  </Card>
</CardGroup>

## Full browser control

An agent gets a full-featured browser it can read and act through: it sees the rendered page, fills forms, clicks, uploads files, and follows multi-step flows on sites with no API — all while looking like a genuine visitor. A clean command API covers navigation, clicking, typing, form-fill, file upload, screenshots, PDF export, cookies, and storage, so an agent can drive any website end to end.

## Driving the user's own browser

Beyond research on its own egress, an agent can also drive **the user's own browser** — useful for sites and sessions that live in front of the person, not on a server.

→ Connect and drive it through the [Browser control API](/api-reference/integrations/browser-connect).

<Note>
  Driving the machine itself — running turns and streaming the agent's work back — happens over [conversations and turns](/guides/streaming-chat). Web research and browser control are tools the agent reaches for inside that loop.
</Note>