Northwind support
AI Agents
Let your coding agent read the bug
The Screendesk MCP server and the sdesk CLI give Claude, ChatGPT, Cursor, and coding agents read access to reports, logs, network requests, transcripts, and frames.
Learn moreEngineering teams
Triage customer bugs with the full context attached
Issues from customers, support, and QA arrive with the recording, console logs, network requests, and an AI summary. Your agents can read them too.
Trusted by support teams from startups to enterprises
Spend less time reconstructing bugs. And more time fixing them.
Receive complete issues
Support and QA hand over the recording, logs, and device details in one report, instead of a thread of screenshots.
See the failing request
Network requests and console logs are captured while the customer records, with the status code and response.
Send to Linear
Checkout fails after clicking Pay
I’m trying to pay for the Pro plan but the payment never goes through.
Route work where you plan it
Reports land in Linear, Jira, or GitHub with an AI-drafted issue, the recording, and the logs attached.
Key metrics that matter. What teams see after adding video to support.
- customer satisfaction
- 17%
- first contact resolution
- 53%
- replies per resolution
- −26%
- saved per agent/day
- 1 hour
Built for the bugs that reach engineering. From the escalation to the fix.
Customer escalations
Support escalates with the customer’s recording and logs, not a paraphrase of the problem.
API and backend errors
See the failed request, its status code, and the response the customer’s browser received.
Environment-specific bugs
Every report carries the browser, device, locale, and timezone it was captured on.
Performance issues
Slow requests and their timing are on the report, so you can tell a slow page from a slow network.
Internal bug reports
Teammates report bugs from the Chrome extension, with instant replay and logs attached.
Unclear reproduction steps
AI writes the reproduction steps, expected and actual behavior from the recording.
Screen recordings
Bug reports with the technical context
Customers record from a link, with nothing to install. With the Screendesk snippet on your app, recordings include console logs and network requests.
Learn moreChrome extension
Internal reports in one click
Your team records a tab, takes a screenshot, or saves an instant replay of the last two minutes, with logs attached.
Learn morePart of the Screendesk platform. Recordings, live calls, and AI, connected to the tools you already use.
Questions from engineering teams
How are console logs and network requests captured?
Add the Screendesk snippet to your web app. Recordings made on your app then include console logs and network requests. The Chrome extension captures them for internal reports.
Can our AI agents read reports?
Yes. The Screendesk MCP server and the sdesk CLI give agents read access to reports, logs, network requests, transcripts, and frames.
Which issue trackers do you support?
Send reports to Linear, Jira, or GitHub with an AI-drafted issue. Folder automations can also create issues in Trello, post to Slack, or call a webhook.
Can engineers join a call with the customer?
Yes. Start a video call from the ticket. The customer shares their screen, an engineer can join, and the call is recorded and transcribed.
How is customer data protected?
Blur sensitive fields with CSS selectors, require privacy consent, and keep recordings in the US or Europe. SAML SSO, SCIM, and audit logs help you control access.
AI
Debugging context, powered by AI. From the recording to the root cause.
Report intelligence
Every recording gets a summary, reproduction steps, expected and actual behavior, and a severity.
AI-drafted issues
Send to Linear, Jira, or GitHub with the title and description drafted from the recording.
Agents that investigate
Claude, ChatGPT, Cursor, and coding agents read recordings, logs, and network requests through the Screendesk MCP and CLI.
