DevPeek

Page debug & replay

The Debug tab mirrors proxied HTML with Elements / Console / Network and records sessions. On desktop Chromium-based browsers on your PC, the DevPeek extension can record without proxy preview and import into the app. Repro aligns recording, console, DOM, and network on a timeline—often in a separate window.

Entering debug

Switch to the Debug tab; if no client is chosen, you see eligible devices. You need at least one HTML document fetched through the proxy. If empty, confirm the proxy path and a trusted CA.

Click Debug on a row to mirror the page. Content Security Policy limits injectable resources—differences vs a normal browser tab are expected.

Tooling

  • Resize preview; see client IP and mirrored URL.
  • Throttling: built-in presets or the same custom numbers as global throttling.
  • Zoom the mirror; Leave debug returns to the picker.
  • Inspector-style panels for Elements / Console / Network.

Record a debug session

Use Record in the preview. Switching clients, leaving the route, or closing without saving may discard in-progress recordings with a warning. Saved sessions land in the History sidebar list.

Repro (replay)

In the main Debug view, open History for saved recordings. Export JSON, Delete, or Send to a LAN peer (see Collaboration); Repro usually opens a new window. Import JSON when the UI offers it.

Import recording JSON validates files; malformed payloads or missing mirror events may block playback.

The toolbar has Play / Pause and Preview / Edit; keyboard nudges depend on the build’s a11y hints.

Chromium extension capture

On Chrome, Edge, or other Chromium browsers, install the DevPeek extension (store listing title may vary by channel). It records in the active tab without forcing full proxy capture—handy for quick front-end captures.

  • Open the popup from the toolbar: Start recording this tab / Stop this tab; multiple tabs can record in parallel with a concurrency hint.
  • Talk to desktop DevPeek: after stopping, the extension POSTs to the desktop collaboration HTTP port (same path as importing recordings). Start DevPeek locally first.
  • Ports & offline: the extension auto-detects the collaboration port in a scan range; if you changed the collaboration listen port, set the port in the popup. While offline you can still record; data queues locally and auto-upload when DevPeek is up, or manage queued items in the popup.
  • Do not record on built-in pages like chrome://—extensions cannot run there.
  • After import, entries appear in History like any other recording (replay, export, send—per build).

Exports may contain secrets—avoid public channels.