Desktop App

Native installers are available for macOS (Intel and Apple Silicon) and Windows.

Desktop uses native OS notifications, which still arrive even when the app is minimized or in the background. Clicking one brings the app forward and opens the relevant ticket directly. A persistent live connection to the server means notifications arrive instantly, not on the next refresh.

Desktop uses your OS’s native screen/window picker for screenshots and recordings, including system audio — see Attachments & Screen Recording.

The standalone Debug Tool opens an isolated Chrome window and captures its console output, network requests, exceptions, and every click, input, keypress, and page navigation — live, for ad hoc troubleshooting. Nothing here is saved or tied to a ticket; it’s a throwaway session for figuring something out in the moment.

A ticket’s Debug tab works the same way as the Debug Tool, but tied to that ticket specifically — start, stop, and save a session for other developers to review later, alongside any sessions saved before it.

The session viewer — shared by Desktop and the Dashboard — has Console, Network, Errors, and Interactions tabs. Console entries support free-text search plus a level filter (All/Errors/ Warnings/Logs), color-coded (errors red, warnings orange, ordinary logs the default text color) with a visible divider between entries; long entries clamp to 10 lines with a “Show more” toggle and a one-click copy button.

The Network tab lets you search captured requests by URL, filter by content type, and expand any request to see its URL, request/response headers, and request/response bodies, each with its own copy button — an image response renders as a clickable thumbnail that opens the original in your system browser.

You can also pick a captured request, edit its method, URL, headers, or body, and resend it live from Desktop to see a fresh response — JSON responses are auto-detected, pretty-printed, and syntax-highlighted.

Every recorded interaction (click, input, keypress, or navigation) is captured with a primary selector plus a structural fallback, so a saved session — from the Debug Tool or a ticket’s Debug tab — can be replayed step-by-step against a fresh Chrome window, with per-step progress and an automatic fallback if the original selector no longer matches.