Zplunge - Web Debugging & QA Tools

Zplunge helps frontend developers, QA engineers, and testers reproduce, document, and share bugs faster - without living in DevTools. Record what happened, see the network and console behind it, map a site's API as you click, and compare or inspect pages on the spot. ── SCREEN RECORDING WITH SYNCHRONIZED LOGS ── Record any browser session and replay it in the built-in Player — with console logs, network requests (XHR, Fetch, WebSocket), and user interactions locked to the video timeline. Trim recordings to the exact moment that matters, split large files into time-based or size-based parts, and export both video and logs as a matched pair (Zrec / Zlog). The Player supports playback speed control, log filtering, frame-accurate seeking, timestamped Comments pinned to the timeline, one-click "Copy Steps" as readable text for bug reports, and Copy as cURL / Copy as Fetch for any captured request. ── STEP REPLAY [BETA] ── Reproduce a recorded session automatically in a fresh tab — no re-clicking through the bug by hand. Zplunge finds each element the same way you interacted with it (stable selector, then a fallback scan), types and clicks in sequence, and pauses with a draggable on-page panel if a step can't be located, letting you retry, skip, or click by recorded coordinates instead. Edit the start URL before replaying to point the same steps at a different environment (staging vs. production). When it's done, get a git-diff-style report comparing console and network activity between the original recording and the replay. Best suited to straightforward, single-page flows for now. ── SHARE TO SHAREPOINT OR GOOGLE DRIVE [BETA] ── Send recordings straight from the Player to a shared link — SharePoint or Google Drive, your choice; only one is configured at a time. Sign in once (Microsoft or Google OAuth), and every recording after that uploads and shares as a link with one click, without leaving the browser. Google Drive access is scoped to files the extension itself creates, never your whole Drive. Chunked upload handles files of any size. Upload history is stored locally with date, filename, size, and direct link. Note: requires your own Azure App Registration (SharePoint) or Google Cloud OAuth Client ID (Google Drive), set up once in Settings; off by default. ── ISSUE TRACKER: CREATE FROM PLAYER OR PREVIEW [BETA] ── Create a bug straight from the Player or BBX Preview in Jira Cloud, Jira Server/Data Center, or Azure DevOps. Zplunge drafts the title and description for you and attaches the captured logs as a JSON file — plus the recording itself, when created from the Player. Oversized log attachments are split automatically to stay under a size limit you set. Sign-in uses the e-mail/API token or Personal Access Token you provide, and connections are HTTPS-only. Note: requires your own project/instance credentials, set up once in Settings; off by default. ── AI BUG SUMMARY [BETA] ── Turn a recording or BBX log into a written bug summary with one click, using the AI provider you choose: OpenAI, Anthropic, Google Gemini, or any self-hosted OpenAI-compatible endpoint (e.g. a local Ollama server). Only a focused subset of the capture is sent — console errors/warnings, failed requests, and poor Web Vitals, not a full raw log dump — with tokens, passwords, and URL parameters stripped before it leaves your browser. The request goes straight from your browser to the provider you pick, using your own account and API key; it never passes through infrastructure we operate. Note: off by default, requires your own API key, and is subject to your chosen provider's own privacy policy. ── BLACKBOX MONITORING ── Always-on passive monitoring that captures console errors, network requests, user interactions, and Web Performance Vitals (LCP, CLS, TTFB, FID, INP) in the background — no manual recording needed. Enable it per subdomain, set a global retention window (10 s – 1 h) in Settings, and open the Preview panel to browse a full event log. Repeated errors and warnings are automatically grouped (×47 style) so you instantly see signal vs. noise instead of an endless list. Filter by type — including a dedicated ⚡ Vitals filter. WebSocket connections are fully tracked. Analytics beacons, resources that fail to load, and anything blocked by a site's content security policy are captured too. When errors or network failures (4xx/5xx) are detected, the extension icon badge turns red with a count — click to open BBX Preview. Badge resets after you open Preview. ── APP WINDOWS ── Popup and PWA windows hide the extension toolbar, so monitoring could never be switched on from inside them — which is awkward, because that is often exactly where the failing requests are. Add the host once under Settings → App Windows and monitoring starts on its own in any window that site opens. Matching is by host, so it keeps working as the app moves between pages. Each host gets its own history window, up to 24 hours (12 by default), so you can still look up what happened earlier in the day. The toolbar badge shows both contexts at once — the left half is the tab you are on, the right half is your app windows, so "3|2" reads as three errors here and two over there. In the event log, a Tab / App filter and a marker on each row keep the two apart, and every entry has a Log button that opens its own history directly. Opening the log from the toolbar shows the current tab and every open app window together — each row labelled with its host, each site keeping its own history window — so you no longer have to guess which log to open. ── COOKIES & STORAGE LOG ── The Cookies popup tile is a full editor for the current tab's cookies — view, add, edit, and delete, with Secure, HttpOnly, SameSite and expiry all exposed. Independently, BlackBox Monitoring and recordings passively capture every cookie change (including expiry, shown as its own "Cookie expired" entry) and a Storage log for localStorage/sessionStorage changes — both get their …