peek

peek records your real browser session — DOM, console, and network — and exposes it to your local AI coding agent (Claude Code, Cursor, Cline, Windsurf, and any MCP client) through a Model Context Protocol (MCP) server. Instead of pasting screenshots or describing a bug from memory, your agent reads exactly what your browser saw. Everything stays on your machine. The extension ships captured sessions through a native-messaging stdio bridge to a local MCP server (peek-mcp) that writes to a local SQLite database. No cloud, no sign-up, no telemetry, no analytics, no third-party SDKs. The code is Apache-2.0 — you can verify the network surface yourself. How it works • Enable peek per site from the side panel. There is no "read and change all your data on all websites" — recording is per-origin opt-in, requested from a click. • peek records a masked rrweb session. Form values and password/email inputs are masked in the page before anything leaves it. • Point your AI agent at the peek-mcp server. It can list recent sessions, read console and network errors, find the user action that preceded an error, reconstruct the DOM at any moment, query DOM history, and generate a runnable Playwright reproduction. • A five-level, per-origin permission model controls what the agent may do — from read-only, to suggest, to act-with-confirmation. A destructive-action blocklist (delete, transfer, pay, …) always asks for confirmation, even at the most permissive level. peek is a free, open-source, self-hosted companion for AI-assisted debugging. It is pre-1.0 alpha and side-project–maintained; the extension also runs unpacked today for early testers. Source & docs: https://github.com/Cubenest/rrweb-stack · https://peek.cubenest.in