Features

Features

Everything Loupe does, at a glance.

Capture

• Element inspector — hover-highlight and click to select any element; comments anchor to the DOM, not to pixels.
• Screenshots — DOM-based capture in the SDK; pixel-perfect captureVisibleTab in the browser extension.
• Element context — every comment stores the target's outerHTML and a curated slice of computed styles.
• Privacy — mark elements data-loupe-redact to blur/exclude them from screenshots.

Durability

• Re-anchoring across redeploys — a multi-signal fingerprint re-resolves the element even after the markup changes. See Re-anchoring.
• Shadow-DOM isolation — the widget's CSS never leaks into the host page and the host CSS can't break the widget.
• URL normalization — utm_*, click ids, and dev params are stripped so comments don't fragment across query-string variants.

Storage & triage

• Postgres-backed — PGlite locally, hosted Postgres via DATABASE_URL.
• Object storage — screenshots stored as URLs (S3-ready), not base64.
• Kanban dashboard — open / in progress / done, page filter, screenshot thumbnails, live refresh.

Security

• Per-project secrets + HMAC identity — writes require a server-signed user HMAC; the dashboard/MCP use an admin key. See Authentication.

AI-native

• MCP server — comments become a task backlog for Claude Code, complete with element HTML, styles, and screenshot. See MCP Integration.
• llms.txt — machine-readable project facts for AI agents.

Delivery

• npm package and <script> tag for the SDK.
• MV3 browser extension for any site.
• Monorepo (npm workspaces), TypeScript throughout.