Browser Run now includes an Inspect panel inside its session recordings, giving engineers direct access to console logs, network traffic, and the final DOM snapshot for each recorded tab. This eliminates the need to replay a session to gather the same data, which speeds up debugging, performance tuning, and security audits.
Inspect Panel Overview
The panel is divided into three tabs:
- Logs – searchable console output with level filters, useful for tracing script errors or AI model inference messages.
- Network – a per‑request view showing method, status, headers, payload, response body, and a timing waterfall. Sessions can be exported as a HAR file.
- DOM – an expandable representation of the page’s HTML at the end of the recording, with a copy‑to‑clipboard option.
When a recording contains multiple browser tabs, the Inspect panel switches context to match the tab selected in the viewer.
Operational Impact
To capture the new data, recording must be enabled when launching a Browser Run session. After the session ends, the recording appears under the Browser Run → Runs view in the Cloudflare dashboard, marked by a recording icon.
Beyond the UI, the recorded network activity can be fetched via the provided API as raw JSON or a HAR file. This enables integration with existing CI/CD pipelines, automated log‑analysis tools, or custom security scanners. Practitioners should consider adding a step that pulls the HAR after a test run and feeds it into performance regression checks.
Security and Compliance Considerations
The Inspect panel surfaces data that may include sensitive request headers, payloads, or DOM content generated by the application. Teams need to treat stored recordings as potentially confidential and enforce appropriate access controls in the Cloudflare dashboard and any downstream storage used for API‑retrieved artifacts.
Because the source mentions “current limits” for session recording, operators should monitor usage against those limits to avoid unexpected truncation of logs or network data, which could affect forensic completeness.
Related CloudNinjas coverage: hands-on guides.
What This Means For Practitioners
Adopt the following actions:
- Enable session recording on all test and production‑like runs where post‑mortem analysis is valuable.
- Integrate the network‑activity API into debugging or security tooling to automate extraction of logs, HAR files, or JSON payloads.
- Review and tighten IAM policies around the Browser Run → Runs UI and API endpoints to limit exposure of captured data.
- Track the platform‑defined recording limits and adjust test durations or data volumes accordingly.
By incorporating the Inspect panel into routine workflows, engineers can reduce turnaround time for issue resolution and gain richer visibility into client‑side behavior without recreating the environment.
