peek
rrweb-stack
Two OSS products on one rrweb-based substrate. Both ship as npm packages today.
Product | One line | Install |
The reporter for your WebdriverIO tests — Playwright and Cypress on the roadmap. Self-contained HTML for every run — replay failures, audit successes, attach to any bug tracker. No SaaS, no dashboard, no signup. |
| |
Your real browser, exposed to your AI coding agent over MCP — capture once, query forever, never leaves your machine. |
|
Above: npx @tracelane/cli init in a real WebdriverIO project — detect runner, install, edit wdio.conf.ts, ignore reports dir.
Above: peek sessions list then peek sessions show ... --format markdown — a recorded browser session as queryable structured output, AI-ready.
What's where
tracelane
Package | Status | What it does |
alpha | WebdriverIO Service — capture + write HTML report | |
planned (Q3 2026) | Playwright Reporter implementing | |
planned (Q4 2026) | JSON-output adapter (no Test Replay overlap) | |
alpha | Framework-agnostic capture engine — depended on by the adapters | |
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 |
alpha |
| |
alpha | stdio MCP server — exposes captured sessions to Claude Code, Cursor, Cline, Windsurf | |
alpha (CWS submission pending) | Chrome MV3 extension — the real browser, recorded |
Docs: peek.cubenest.in (source under apps/peek-docs/).
peek requires Node.js ≥ 22. Its native
better-sqlite3dependency only ships prebuilt binaries for Node 22+; on older Node (notably Windows, which has no C/C++ toolchain by default) the install falls back to compiling from source and fails.
Related MCP server: Local Lens
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
GitHub Sponsors — github.com/sponsors/harry-harish (opening for launch)
The work is open-source and sustainable; sponsorship keeps it that way. See
docs/SUSTAINABILITY.mdfor the maintenance cadence.
This server cannot be installed
Maintenance
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Cubenest/rrweb-stack'
If you have feedback or need assistance with the MCP directory API, please join our Discord server