> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/request-screen-recording/developer-tools.md).

# Logs & blur

Console logs, network requests and system details from your customer's browser, attached to each recording.

When a customer records with Screendesk, the recording can carry what their browser was doing: console logs, network requests and system details. Engineers can reproduce the issue without asking the customer to open developer tools.

{% embed url="<https://app.screendesk.io/recordings/bb0fe094-449d-492e-a153-036ec34aec68>" %}

Console logs, network requests and system details are available on every plan. Auto blur is available on Pro and Enterprise.

Console and network capture needs the Screendesk snippet on your website: see [Install the snippet](/request-screen-recording/developer-tools/installing-screendesk-script.md). To hide sensitive content in recordings, see [Auto blur](/request-screen-recording/developer-tools/auto-blur.md).

## What gets captured

Open a recording and click **Insights**.

<figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2Fo0KAaHLQXxnvaIKdIj92%2Fdocs-window-devtools.png?alt=media" alt="A recording&#x27;s Dev Tools console in Insights"><figcaption></figcaption></figure>

* **Dev Tools → Console**: console messages with their level, uncaught errors with their stack traces, failed requests and the customer's clicks, along the video's timeline. Filter by log level.
* **Dev Tools → Network**: the page's requests (Fetch/XHR, documents, scripts, styles, fonts, media) and WebSocket connections, with status, timing, headers and response body. Filter by type, or show **Errors only**.
* **System Info**: OS, browser, device, screen and window size, locale, timezone, IP address, ISP, VPN detection and connection speed. The recorder collects these, so they need no snippet. Videos recorded with the Chrome extension or uploaded have none.

The website snippet redacts data in the browser before anything is sent: passwords, tokens, cookies, authorization headers and API keys, and personal data such as email addresses, phone numbers and card numbers.

{% hint style="info" %}
Logs and errors from scripts that run before the snippet aren't captured. Requests made before it still show in **Network**.
{% endhint %}

## Customer context

Attach details from your app to every recording, such as the user ID, plan or feature flags. They show in **System Info**, next to the console logs.

Register them once, in your app's root:

{% tabs %}
{% tab title="App root" %}

```bash
npm install @screendesk/sdk
```

```javascript
import { screendesk } from "@screendesk/sdk";

// Read when a recording starts and when it stops.
screendesk.metadata(() => ({
  userId: currentUser.id,
  plan: currentUser.plan,
  flags: featureFlags.enabledKeys(),
}));
```

{% endtab %}

{% tab title="Plain HTML" %}

```html
<script>
  window.__screendesk__ ||= {};
  window.__screendesk__.exports ||= {};
  window.__screendesk__.exports.metadata =
    () => ({ userId: 42, plan: "pro" });
</script>
```

{% endtab %}
{% endtabs %}

The callback must be synchronous and return a JSON object of 10 KB or less. Values are sent as you return them, so leave out credentials and other private data. **Settings → Logs & blur → Logs → Customer context** shows when details last arrived.


---

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