Errlekh Capture for Chrome and Edge
Records the active tab and captures editable screenshots. Recordings include console and network context, errors, clicks, and navigations. Sensitive patterns in diagnostic text are redacted before upload. The video shows what was visible on your screen. Nothing uploads until you publish the report.
The name behind the capture
Err
the error or failure
लेख(lekh)
a written record or account
Errlekh
the written record of an error
Say err-lekh. Capture writes the screen, console, network, and errors into one report.
Download
errlekh-capture-extension-v0.5.1.zip
ZIP · 69 KB · Chrome 116 or newer, current Edge
This is a developer build installed from a folder. A store listing is not available yet. If sign-in is needed or the network fails, the report stays inside the extension for retry or local download.
Try it on the demo checkout
A checkout that breaks on purpose. Record it, press a few buttons, and see every console message and request in your report.
Install
Load it unpacked in a minute.
Five steps, no build tools. Tick each one off as you go. This page remembers where you left off.
Save errlekh-capture-extension-v0.5.1.zip (69 KB). Clicking the button ticks this step for you.
Download ZIPDouble-click it on macOS, use Extract All on Windows, or run unzip in a terminal. You get a folder with manifest.json directly inside. Keep that folder somewhere permanent: the browser loads the extension from it every time it starts.
Paste the address into a new tab, then switch on Developer mode on the extensions page. Websites are not allowed to link to chrome:// pages, so copy the address instead of clicking it. In Edge, use edge://extensions.
chrome://extensionsedge://extensionsChoose Load unpacked and select the folder that contains manifest.json. Errlekh Capture shows up in the list. Pin it from the puzzle-piece menu so the toolbar button is one click away.
Open this workspace in the same browser and enter the team-test access details first. Then open Errlekh Capture Settings (the gear), save the prefilled workspace URL below, and record.
Filled in from the page you are on. The extension accepts https:// addresses, or http://localhost and http://127.0.0.1 for a local workspace.
Upgrading from v0.2.0 or earlier? Remove the old extension on the extensions page first, then load the new folder.
Privacy
What it captures. What it never reads.
The page hook runs in the main world and starts buffering when the page loads, so the boundaries are worth spelling out.
What it captures
- Visible-tab screenshots with drawing, rectangle, blur, and black-redaction tools
- Console messages (log, info, warn, error, debug) with available stack traces during recordings
- Every fetch and XHR request with method, status, timing, size, and safe headers such as content-type and request IDs
- Page resources (scripts, styles, images, fonts) with status and timing
- Uncaught errors and unhandled promise rejections
- Clicks and navigations
- The last 300 console and network entries from page load, before you press record
- The tab recording as WebM, with every entry aligned to its timeline
What it never reads
- Cookies and authorization headers
- Request bodies and typed input values
- Query-string values. Parameter names are kept, values are removed
- Response bodies, unless you turn on “Capture response bodies of failed requests” (off by default, failed requests only, redacted, 4,000 characters max)
Only allowlisted response headers are kept. Bearer and Basic credentials, JWTs, passwords, tokens, API keys, session IDs, and email addresses are redacted in console text, headers, and bodies, in the page and again on the server. Log entries stay in the extension until you stop and publish the recording.