Developer tools

Capture system info, console logs, and network activity alongside recordings for faster debugging.

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)

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.

Where to find it

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

Setup (recommended order)

1

Install the Screendesk widget

This enables widget-based capture features and CSP configuration.

Go to Installing Screendesk script.

2

Enable console logging (if needed)

Turn on console capture in workspace settings.

Go to Console logs and Network.

3

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.

Guides

Topic

System Info What metadata is captured and where it appears.

Guide

Topic

Console logs Enable and review JavaScript console output during sessions.

Guide

Topic

Network logs Understand what network requests are captured and where.

Guide

Topic

Install the widget Add the snippet and configure CSP for capture features.

Guide