# Watch your browsers live

### Via dashboard <a href="#id-0-toc-title" id="id-0-toc-title"></a>

From the dashboard you can list the browsers you have launched, to identify them easily you can make use of tags when creating them.

Once you identify your browser you can start a remote desktop directly from the dashboard using a screen icon.

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

The remote desktop startup process may take a few seconds. And in case you have not specified a label for the browser, the field will be empty.

### Via HTTP API <a href="#id-1-toc-title" id="id-1-toc-title"></a>

#### 1. `/StartRemoteDesktop` – **Start Remote Desktop** <a href="#id-2-toc-title" id="id-2-toc-title"></a>

**Method:** `POST`

**Description:** This endpoint starts a remote desktop session for the browser. The request must include the address of the browser session that was provided when the browser was created.

**Request Body:**

```bash
curl -X POST https://production.cloudbrowser.ai/api/v1/Browser/StartRemoteDesktop \
-H "Authorization: Bearer <your-api-token>" \
-d '{
    "address": "browserprovider-worker-*.cloudbrowser.ai"
}'
```

**Response:**

```json
{
    "password": "remote_desktop_password",
    "success": true,
    "status": 200
}
```

* **password:** The password needed to access the remote desktop.
* **success:** `true` if the operation was successful, `false` otherwise.
* **status:** `200` for success, or another number for an error.

#### 2. `/StopRemoteDesktop` – **Stop Remote Desktop** <a href="#id-3-toc-title" id="id-3-toc-title"></a>

**Method:** `POST`

**Description:** This endpoint stops an active remote desktop session. The request must include the address of the browser session that was provided when the browser was created.

**Request Body:**

```bash
curl -X POST https://production.cloudbrowser.ai/api/v1/Browser/StopRemoteDesktop \
-H "Authorization: Bearer <your-api-token>" \
-d '{
    "address": "browserprovider-worker-*.cloudbrowser.ai"
}'
```

**Response:**

```json
{
    "success": true,
    "status": 200
}
```

* **success:** `true` if the operation was successful, `false` otherwise.
* **status:** `200` for success, or another number for an error.

### Other considerations <a href="#id-4-toc-title" id="id-4-toc-title"></a>

The appearance and functionality of the remote desktop is limited for security reasons, however this does not represent any limitation on how the browser behaves in the production environment.

Likewise, the possible latency experienced on the remote desktop does not represent the actual browser performance.


---

# 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://cloudbrowser.gitbook.io/docs/cloud-service/watch-your-browsers-live.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.