Cubenest

Independent · Open source

Developer tools, built in the open — and used every day.

A nest for small, self-contained developer tools — open-source, independent, and built carefully, not fast.

The toolsGitHub ↗

The tools

open source · built in the open
01The tools

tracelane

ALPHA

Replay your test failures. No cloud, no account, one HTML file.

A test-run recorder for WebdriverIO, Playwright, and Cypress. On failure it captures the DOM, console, and network as an rrweb timeline and writes one self-contained HTML report you can open anywhere. Allure tells you a test failed — tracelane lets you watch it fail.

Not a SaaS. No cloud, no account, no signup wall.

surface
npm — WDIO · Playwright · Cypress
output
one self-contained HTML file
status
alpha — APIs may change
npx @tracelane/cli init
Docs →▸ watch demoGitHub ↗

peek

ALPHA

Give your AI agent the session you're actually in.

A browser companion — MV3 extension + MCP server + CLI — that hands your real, authenticated browser session to coding agents like Claude Code and Cursor, as a replayable rrweb timeline of DOM, console, and network. Others pipe logs and screenshots; peek gives the agent the session itself.

Not a cloud recorder. Local-only, no telemetry — nothing leaves your machine.

surface
Chrome MV3 · MCP server · CLI
feeds
Claude Code · Cursor · Cline · Windsurf · VS Code
status
alpha — APIs may change
npx @peekdev/cli init
Docs →▸ watch demoGitHub ↗

Both built on @cubenest/rrweb-core — one recording engine, maintained in one place.

What's shipping

02What's shipping

May 2026

  1. 01

    tracelane and peek are now on npm (alpha). One command wires either into your project: npx @tracelane/cli init and npx @peekdev/cli init.

  2. 02

    Every package publishes with SLSA build provenance via OIDC — a verifiable supply chain, no manual signing.

  3. 03

    peek shipped a Claude Code Skill (~/.claude/skills/peek) and a recorded demo this month.

03Origin

We started in hardware. It didn't ship.

Cubenest began in a college dorm as a smart-home project: an affordable switch you could control from your phone. We got it to a working prototype, never to market. The gap between "it works on my desk" and "it's something someone can actually use" turned out to be the whole game. So now we build tools that close that gap — and we ship them.

Principles

04Principles
  1. 01

    Open by default. Apache-2.0, public roadmaps, documented failures.

  2. 02

    We use what we build. If we don't run it ourselves, we don't ship it.

  3. 03

    Honest about scope. Small, self-funded, one maintainer — built carefully, not fast. We'd rather under-promise.

  4. 04

    Claims live on the tool. tracelane and peek keep your data on your machine. Any future tool states its own posture.

We also take on a few client builds a year — same discipline, by referral.

— Harish, who maintains this.

05What we're exploring

Security.

Our tools already live in sensitive places: your authenticated browser, your CI pipeline. Security feels like the natural next direction. It's early; we'll say more when there's something real to show. No product yet, no claims.