> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/faqs-and-common-issues/device-and-environment-requirements.md).

# Device & environment requirements

## Device specification

Minimum Intel Core i3 12th Gen, Intel Core i5 is better. The most important factor is RAM. Recommended RAM is 16Gb to 32Gb.

### Browser

Conducttr works with any HTML5 browser. Chrome is recommended but we also work with Edge and Safari.

## Connection specification

Bandwidth greater than 1Mb/s. Video streaming is best with higher bandwidths&#x20;

Latency under 100ms. Latency is more critical than bandwidth. Recommended bandwidth and latency is bandwidth 20Mb and latency less than 20ms but Conducttr will work with worse connections.&#x20;

## Whitelisting

There are domains that may need to be whitelisted if you operate in a very tightly controlled network environment. Please contact support[^1] for the details.

[^1]: <support@conducttr.com>


---

# 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 by asking a question.

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

```
GET https://helpdocs.conducttr.com/faqs-and-common-issues/device-and-environment-requirements.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 `automate deployments from our CI pipeline` 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.
