> For the complete documentation index, see [llms.txt](https://developers.oxylabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.oxylabs.io/products/agent-browser/device-type.md).

# Device Type

Learn how to set Oxylabs Agent Browser device types for more accurate scraping of responsive layouts and device-specific content.

Instead of manually setting viewports, touch support, and User-Agent headers in your local library config (which can create fingerprint mismatches and trigger connection timeouts), the Agent Browser allows you to emulate specific device classes natively by adding the `p_device` query parameter to your connection string:

```bash
wss://username:password@hb.oxylabs.io?p_device=mobile
```

### Supported device profiles

You can configure the `p_device` parameter using three supported device profiles:

<table><thead><tr><th width="123">Parameter value</th><th width="620">Description</th></tr></thead><tbody><tr><td><code>desktop</code><br><em>(default)</em></td><td>Full-size viewport, desktop platform headers, standard mouse/keyboard input schemas, and a desktop User-Agent string.</td></tr><tr><td><code>mobile</code></td><td>Compact mobile viewport, touch event APIs enabled, mobile OS platform headers, and a mobile User-Agent.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.oxylabs.io/products/agent-browser/device-type.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.