Capture · Debug · Reproduce · Collaborate
DevPeek
A proxy-first debugger for frontend, backend, and QA: from HTTPS traffic and breakpoint scripts to injected page debugging and session recording, timeline replay, and LAN collaboration—closing the loop between “seeing the bug” and “showing it to someone else.”
Read the full documentationInstall, certificates, scripts & breakpoints, replay, and collaboration
Windows installer (.exe) only for now—macOS and Linux builds are coming soon. See install guide for setup and updates.
Highlights
Four areas cover traffic analysis, page debugging, replay, and team reproduction—mix and match as you need.
Capture
Proxied traffic, HTTPS, many clients—clear at a glance
- Record proxied traffic with HTTPS parsing; each client gets its own tab so sessions stay separated.
- Breakpoint rules and scripts (including auto-breakpoints) are easy to manage; switch rule presets in one click for frequent workflows.
- Global scripts hook every request phase—decrypt params, rewrite bodies, and turn custom logic into reusable pipelines.
Debug
Bring proxied pages into DevPeek
- Inject debugging for HTML served through the proxy and work inside DevPeek instead of juggling browser and capture tools.
- Elements, Console, and Network panels feel close to everyday frontend debugging.
- Record interactions to preserve repro steps; on desktop, pair with the DevPeek Chromium extension to record a tab and import into the app.
Reproduction
One timeline for actions, logs, and network
- Replay debugging sessions step by step along the user’s path.
- Align each step with console output, DOM changes, and network calls—see what happened right after what they did.
Collaborate
Find teammates on the LAN, share in one gesture
- Discover other DevPeek users on the LAN with less file shuffling and timestamp wrangling.
- Send captures or debug recordings so colleagues can reproduce the same scene quickly—great for joint debugging and escalations.
Quick start
- 1
Install and attach to the proxy
Download the Windows installer and set up local or system proxy per the guide; point phones and other devices at the same proxy to join capture.
- 2
Analyze traffic, inject debug, or use the extension
On the capture side, inspect HTTPS decryption, breakpoints, and scripts; for page issues use injected debugging and DevTools. To record a page in the desktop browser without full proxy capture, use the DevPeek extension and import into the app, then open it from History or replay.
- 3
Record, replay, and collaborate
Record sessions into History as you debug; replay on the timeline or open a replay window from Repro entries. To hand off, use LAN collaboration to send the session or recording.