Changelog

February 2026

We've spent the last six months rebuilding how teams capture, organize, and act on bugs and recordings. Screendesk now does a lot more than record screens — it routes, triages, and automates your entire support workflow. Here's everything that's new.

Bug reports

Chrome extension

A new Chrome extension lets anyone on your team file bug reports directly from the browser. Click the icon, pick your capture mode, and submit — the report lands in Screendesk with full technical context attached. No copy-pasting URLs, no describing what happened in words. Just show the bug.

Three capture modes are available from the extension popup.

• Video recording captures your active tab or entire desktop.

• Screenshot supports area selection, visible viewport capture — with an optional 3 or 6-second delay so you can set up the state you need.

• Instant replay reconstructs the last few seconds from DOM snapshots, giving your engineers a deterministic playback they can step through.

Before submitting, pick a folder, assign a team member, and apply labels — all from the extension. Automation badges on each folder tell you what will fire when the report lands.

Rich bug context

Every bug report ships with the technical context your engineers actually need. Screendesk automatically collects browser name, version, and engine. OS name and version. Screen resolution, window size, and device type. Timezone and locale. Network download speed, latency, IP address, ISP, and VPN detection status.

On top of that, each report captures JavaScript console logs with full stack traces, a complete network request log with headers, payloads, and response bodies, all click events with element selectors and coordinates, page navigation history, Core Web Vitals, and — for instant replays — full DOM snapshots.

Assign reports to team members, tag them with custom labels, organize them into folders, and control sharing with workspace-only or public link access. It's everything your engineering team needs to reproduce a bug without a single back-and-forth message.

Powerful workflows

A recording lands in Screendesk. Triage rules route it to the right folder. The folder triggers an automation. Your AI assistant picks it up through MCP. This is the pipeline we built.

Recording triage

Incoming recordings now route themselves. Define triage rules based on source integration (Zendesk, Intercom, Freshdesk, HubSpot, and 15+ others), customer email, country, recording type, team member, or whether the recording has audio.

Rules evaluate in priority order — first match wins. All conditions in a rule must match, and non-matching recordings stay unfoldered until you decide. Enable or disable rules without deleting them, reorder with drag-and-drop, or start from quick templates for common setups like routing by source or geography.

Folders

Recordings and bug reports now live in folders. Create Bug Report Folders and Recording Folders for received recordings, sent recordings, live sessions, and your video library — each with its own content type.

Folders can be public or private. Private folders have explicit member lists so only the right people see sensitive reports. Pin folders to your sidebar for quick access, archive them when a project wraps up. Every folder can also trigger automations when new content arrives.

Automations

Folders now power automations. When a new bug report or recording lands in a folder, Screendesk can automatically send an email notification, post a message to a Slack channel with Block Kit formatting, fire a webhook to any HTTP endpoint, or create a ticket in Linear, Jira, GitHub, or Trello.

Each automation supports template variables like {{bug_report.title}}, {{bug_report.user.name}}, and {{folder.name}} so notifications carry the right context without manual work. Toggle automations on or off, track execution logs with success rates, and chain multiple automations on a single folder.

MCP

Screendesk now speaks the Model Context Protocol. Connect your AI assistant — Claude, Cursor, or any MCP-compatible client — and give it direct access to your recordings and bug reports.

Your AI assistant can list recordings, read transcripts, pull console logs and network requests from any bug report, and update titles and descriptions. It cannot delete anything or change permissions.

Collaboration

Comments

Recordings and bug reports now have threaded comments. Leave feedback directly on a recording, @mention a teammate to pull them in, or attach up to five images per comment to add visual context. Mentions use inline autocomplete — start typing a name and Screendesk suggests matching workspace members.

For video recordings and instant replays, comments can be pinned to a specific timestamp. Click a timestamp badge and the player seeks to that exact moment. It's the fastest way to point at a problem without describing where it happens.

Subscribe or unsubscribe from any thread with one click.

Assignments

Assign any recording or bug report to one or more team members. Assignees receive an email and an in-app notification the moment they're added.

Enterprise

Audit logs

Every meaningful action in Screendesk is now logged with a tamper-proof audit trail. Logins, recording views, bug report deletions, folder changes, integration connections, SSO updates — 30 event types across six categories: authentication, authorization, data access, data modification, admin actions, and security.

Export logs as CSV or JSON, configure retention from 30 days to 7 years, and stream events in real time to your SIEM via webhooks with HMAC-SHA256 signature verification and automatic retry with exponential backoff.

Improved