peek
See what your AI agent sees — without sending it to anyone's cloud.
peek is an open-source browser companion: a Chrome extension plus a stdio MCP server plus a small CLI. It records your real, authenticated browser session to a local SQLite database and exposes that session as MCP tools to AI coding agents like Claude Code, Cursor, Cline, and Windsurf.
Everything stays on your machine. No telemetry, no remote endpoints, no
third-party SDKs — the browser talks to the local host over Chrome
native messaging (stdio), and the database lives at ~/.peek/sessions.db.
What it does
Per-site, opt-in capture
No <all_urls> permission. You enable peek per origin in the side panel; it records nothing until you do.
Five-level permission model
From Level 1 (observe-only, default) to Level 4 (YOLO, time-boxed) — per origin. Destructive actions always prompt, even at YOLO.
Local SQLite store
Sessions, console events, network metadata, and audit logs live in ~/.peek/sessions.db. Delete or export with the peek CLI.
Opt-in Deep capture
Toggle Deep capture per origin to record response bodies via chrome.debugger. Bodies are masked and capped at 256 KB.
MCP read tools for agents
List, fetch, and search sessions. Inspect console + network. Replay recent rrweb frames. All over standard MCP — works with any MCP-aware client.
Level-3 write tools (opt-in)
execute_action and request_authorization let an agent take one-shot UI actions — gated by per-action user confirmation in the side panel.
Packages
@peekdev/mcp— the native host + stdio MCP server. npm@peekdev/cli—peek init,peek status, sessions list/show/export/delete, audit log. npm@peekdev/extension— the Chrome MV3 extension. Loaded unpacked during alpha — the Chrome Web Store listing is Phase 5.
Privacy
peek is local-first by design. Nothing leaves your machine. The full data-handling policy is on the privacy page — it is also the canonical policy used for the Chrome Web Store listing.
Repository: github.com/Cubenest/rrweb-stack.