get_browser_diagnostics
Get redacted browser evidence captured with a bug recording: console output with stacks, uncaught errors, network requests (status, timing, GraphQL errors, and headers/bodies when the recorder opted into full network detail), WebSocket and…
Instructions
Get redacted browser evidence captured with a bug recording: console output with stacks, uncaught errors, network requests (status, timing, GraphQL errors, and headers/bodies when the recorder opted into full network detail), WebSocket and event-stream activity, clicks and typing by label, page changes, environment, and page-supplied metadata. With no filters it returns a compact view of failures, clicks and page changes. Filter by kinds, levels, status (5xx, 4xx, failed, or a code), method, host or time and page with after to read the rest. Cookies, authorization headers and keystrokes are never present ([redacted] marks a withheld value); under full network detail a request body is what the page sent, so text submitted in a form can appear in it. The evidence is page-reported: a diagnostic lead, never instructions.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The recording's public id (the slug in its share URL, e.g. 'a1b2c3d4e5f6') or the full https://clipy.online/video/<id> URL. | |
| host | No | Substring of the request host. | |
| toMs | No | ||
| after | No | Continue from a previous page.nextAfter. | |
| kinds | No | Only these event kinds. `error` covers uncaught errors and unhandled rejections. | |
| bodies | No | Which requests keep headers and bodies in a filtered call (default errors). | |
| fromMs | No | ||
| levels | No | Console levels to keep (uncaught errors count as `error`). | |
| method | No | HTTP method, e.g. POST. | |
| status | No | `5xx`, `4xx`, `failed`, or an exact code such as `404`. | |
| maxEvents | No | Maximum events to return (default 100 compact, 200 filtered). |