# Project settings

Project settings contain various global parameters and configurations for all your tests and suites.

**What can you do in the project settings?**

**General tab:**

* Change [project](/organizing-tests/projects.md) name&#x20;
* Change timezone
* Set the default [timeout](/preventing-failed-tests/timeout.md) for local and cloud runs - this can help you to solve a situation when [cloud tests are sometimes failing](/troubleshooting/cloud-tests-sometimes-failing.md)
* Decide if you want to close the window after a successful test run automatically

**Browser tab:**&#x20;

* Enable/disable incognito mode for testing sessions, cookies, or local storage &#x20;
* Set a custom user-agent or custom HTTP request headers (for example, you can use it to let BugBug access an environment behind a [VPN or a firewall](/troubleshooting/vpn-or-a-firewall.md))
* Set browser language&#x20;

#### Screen size tab:&#x20;

* Set window width and height for desktop or mobile screen size - this enables you to [test mobile resolutions](/workflow-tips/mobile-version-testing.md)

**Selectors tab:**&#x20;

* Set and define the priorities for the automatic smart [selectors](/preventing-failed-tests/selectors.md), and define your own custom attributes, input names, text content, id, href, class name, etc.&#x20;

**Waiting conditions tab:**&#x20;

* Set default behavior of [waiting conditions](/preventing-failed-tests/waiting-conditions.md)<br>

**Note:** If you're looking for an [API token](/running-tests/running-via-api.md) see the [integrations](/integrations/api.md) tab

<figure><img src="/files/KguXrqRrU5ROB6ZRkcz6" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/koQvBfDDDi6f2iQzyksu" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/Hb9yWltyxsDpBDJz1Fy5" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/Oo3h5IGMlsl4iZH1R7EN" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/fY6do5EoR31a2StC5YC3" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

```
GET https://docs.bugbug.io/preventing-failed-tests/project-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
