Skip to content

Cubenest/rrweb-stack

rrweb-stack

Two OSS products on one rrweb-based substrate. Both ship as npm packages today.

Product One line Install
tracelane The reporter for your WebdriverIO, Playwright, and Cypress tests. Self-contained HTML for every run — replay failures, audit successes, attach to any bug tracker. No SaaS, no dashboard, no signup. npx @tracelane/cli init
peek Your real browser, exposed to your AI coding agent over MCP — capture once, query forever, never leaves your machine. npm install -g @peekdev/cli && npx peek init

tracelane install — one command

Above: npx @tracelane/cli init in a real WebdriverIO project — detect runner, install, edit wdio.conf.ts, ignore reports dir.

peek query — sessions are structured data

Above: peek sessions list then peek sessions show ... --format markdown — a recorded browser session as queryable structured output, AI-ready.

CI OpenSSF Scorecard License

What's where

tracelane

Package Status What it does
@tracelane/wdio alpha WebdriverIO Service — capture + write HTML report
@tracelane/playwright planned (Q3 2026) Playwright Reporter implementing onTestEnd + onAttachment
@tracelane/cypress planned (Q4 2026) JSON-output adapter (no Test Replay overlap)
@tracelane/core alpha Framework-agnostic capture engine — depended on by the adapters
@tracelane/report alpha Self-contained HTML report builder

Docs: tracelane.cubenest.in (source under apps/tracelane-docs/). The tracelane-wdio README is the right starting point.

peek

Package Status What it does
@peekdev/cli alpha peek init installer + peek sessions query / export
@peekdev/mcp alpha stdio MCP server — exposes captured sessions to Claude Code, Cursor, Cline, Windsurf
peek-extension alpha (CWS submission pending) Chrome MV3 extension — the real browser, recorded

Docs: peek.cubenest.in (source under apps/peek-docs/).

Shared substrate

@cubenest/rrweb-core — vendored PostHog rrweb fork, PII masking primitives, large-DOM throttling, screenshot fallback, network/console capture abstractions, compression helpers. Used by both products. The fork is pinned by SHA + the substrate's NOTICE attributes both PostHog's plugin lineage and the upstream rrweb roots.

Why two products, one repo

Same recording engine, same trust model, two different consumer surfaces:

  • tracelane ships test-time captures into a self-contained HTML artifact your team and AI agents can read offline.
  • peek ships live-browser captures into an MCP server your AI coding agent can query.

Shared upstream means one fork to track, one masking surface to harden, one license + DCO + security policy.

Pre-launch state

Pre-1.0. Alpha packages live on npm. Branch protection is on main (PR + CI + DCO + linear history). All workflows use Trusted Publishing OIDC + SLSA provenance. Renovate runs with a 7-day cooldown (21 days for the @posthog/rrweb lineage) and config:best-practices. Public launch motion is in progress.

Contributing

Apache 2.0. DCO sign-off required on all contributions. See CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md.

Sponsor / support

About

Two OSS products on one rrweb substrate: tracelane (self-contained HTML test-failure replays for WDIO/Playwright/Cypress) + peek (browser companion for AI coding agents over MCP). No SaaS, no telemetry, local-first.

Topics

Resources

License

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Packages

 
 
 

Contributors