# Developer tools

Developer tools add technical context to recordings. They help engineers reproduce issues faster. They also reduce back-and-forth with customers.

Use these tools when you need more than “watch the video”. Use them for bugs, performance issues, and flaky flows.

### What gets captured

**System info**

Basic environment metadata, like:

* Browser and OS
* Screen and viewport size
* Locale and timezone
* Network indicators (when available)

**Console logs**

JavaScript console output during the session, like:

* Errors and stack traces
* Warnings and debug logs
* Client-side failures that don’t show in the UI

**Network logs**

HTTP request/response activity, like:

* Fetch/XHR calls
* Status codes (4xx/5xx)
* Payloads and response bodies (when available)

{% hint style="info" %}
Network logs are typically only available for Chrome-extension captures (and other replay-style captures). Regular customer-submitted recordings usually won’t include full network logs.
{% endhint %}

### Where to find it

Open any recording. Look for tabs like **System Info**, **Console**, or **Network** in the recording detail view.

### Setup (recommended order)

{% stepper %}
{% step %}

#### Install the Screendesk widget

This enables widget-based capture features and CSP configuration.

Go to [Installing Screendesk script](https://docs.screendesk.io/~/revisions/pAg2d5GCwbZlpJ20UTRh/request-screen-recording/developer-tools/installing-screendesk-script).
{% endstep %}

{% step %}

#### Enable console logging (if needed)

Turn on console capture in workspace settings.

Go to [Console logs and Network](https://docs.screendesk.io/~/revisions/pAg2d5GCwbZlpJ20UTRh/request-screen-recording/developer-tools/console-logs).
{% endstep %}

{% step %}

#### Use the Chrome extension for deeper traces

For full network timelines and richer dev tooling, use the extension capture flow.

Go to [Network Logs Captured](https://docs.screendesk.io/~/revisions/pAg2d5GCwbZlpJ20UTRh/request-screen-recording/developer-tools/network-logs).
{% endstep %}
{% endstepper %}

### Guides

<table data-view="cards"><thead><tr><th>Topic</th><th data-card-target data-type="content-ref">Guide</th></tr></thead><tbody><tr><td><strong>System Info</strong><br>What metadata is captured and where it appears.</td><td></td></tr><tr><td><strong>Console logs</strong><br>Enable and review JavaScript console output during sessions.</td><td></td></tr><tr><td><strong>Network logs</strong><br>Understand what network requests are captured and where.</td><td></td></tr><tr><td><strong>Install the widget</strong><br>Add the snippet and configure CSP for capture features.</td><td></td></tr></tbody></table>


---

# 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.screendesk.io/request-screen-recording/developer-tools.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.