runlens.

Your browser ran.
What went wrong?

Go from a failed automation to the step, selector and browser evidence behind it. RunLens brings the whole run into focus.

Start tracing Explore a trace
Local SQLite storage. Open source. Yours to inspect.
Run explorerIllustrative trace
A failed run, ready to inspect
checkout / playwright

Complete checkout

Failed
Execution trace0 ms 3.2 s
selector_missingFailed step

The checkout button could not be found.

[data-testid="place-order"]
DOM snapshot capturedat 00:03.200
Evidence stays with the runReplay, select a step or switch the evidence
Built for the browser stack you already use
PlaywrightPuppeteerTypeScriptCustom workflows

A failure is a moment.
The run is the context.

A timeout on its own tells you very little. Keep the steps before it, the page around it and the evidence at the breaking point together.

checkout-healthcheckFailed
NavigateClickInspect
STEPSubmit order
SELECTOR[data-testid="place-order"]
CLASSIFICATIONselector_missing
EVIDENCEScreenshot · DOM · events

Illustrative evidence summary

Capture the run.

Wrap meaningful steps and attach a browser adapter. Record timings, selectors, console errors and failed requests as your automation runs.

Find the breaking point.

Open the execution trace. Select a step to inspect its error, page context and captured artifacts in one place.

See what repeats.

Compare failure classes, selector issues and slow steps in the Reliability view. Export trace JSON when you need the whole record.

The browser evidence
stays on your machine.

RunLens stores traces in local SQLite. Its dashboard runs beside your automation. Inspect screenshots, DOM snapshots and events without a hosted tracing account.

Explore the SDK
Your automationPlaywright / Puppeteer / custom
Local trace store.runlens/runlens.db
RunLens dashboard127.0.0.1:5173

Give your next run
a little more context.

Build RunLens from source, try the bundled browser example and open your first trace.

Read the setup guide

Node 22.13+ or Node 24+ · pnpm · Chrome for the example

Start from source 
# Get a verified source snapshot
git clone https://github.com/AkhilTrivediX/runlens.git
cd runlens
git checkout f17f5de
pnpm install
pnpm build

# Capture a browser run, then inspect it
pnpm test:playwright
pnpm start:dashboard
Open http://127.0.0.1:5173 after the server starts.

A few things to know.

Does RunLens replace Playwright or Puppeteer?

No. RunLens instruments your existing workflow. Use the browser tools you already have and wrap the meaningful actions in RunLens steps.

Can I install it from npm?

The 0.1.0 package is being prepared for release. For now, build from the source using the quickstart above. The repository has instructions for packing and installing the SDK locally.

What gets captured?

Runs, steps, timing, selectors, browser events and classified failures. Browser adapters collect console and page errors plus failed requests. With debugger mode and a page context provider, RunLens can capture screenshots and DOM snapshots on failure.

Is this a hosted dashboard?

This website introduces the product. The RunLens dashboard runs locally and reads your SQLite trace store. Your local runs are not sent to this website.

Trace the fault.
Keep the whole picture.

Get started with RunLens