Keylock Bridge

About

Keylock Bridge is built for privacy-first, cost-efficient debugging with AI IDEs.

Many IDEs can already “see” a page—but sharing raw DevTools output can leak secrets and burn tokens. Keylock Bridge focuses on what’s usually missing: safe, compact, low-noise context your AI can use immediately.

== What’s new (v1.0.5) ==

■ Fixed Cursor deeplink install failing

== Features ==

✓ Automatic PII/secret redaction - Detects and removes common sensitive data (tokens, API keys, emails, auth headers) before anything is shared.
✓ Local compaction that saves tokens (and money) - Groups and summarizes noisy logs and network activity so you send the signal, not the spam—reducing context usage and egress.
✓ Designed for AI IDE workflows (MCP / JSON-RPC) - Exposes DevTools data as MCP/JSON-RPC tools so your IDE can request exactly what it needs, on demand.
✓ Fast setup - One-click/session-based provisioning so you can connect and start debugging without complicated manual configuration.

== Why it exists ==

Keylock Bridge’s mission is to make AI-assisted debugging safe by default and cheaper to run—by redacting sensitive data, compacting high-volume logs , and making setup frictionless.

== Privacy and data handling ==

Keylock Bridge is designed to minimize what leaves your machine. Redaction and compaction happen locally before any context is shared with your AI IDE or model.

Note: The extension may require permissions to access DevTools/page data in order to read console logs, network requests, and related debugging context. This access is used only to provide the requested debugging features.

== Enjoying Keylock Bridge? Please rate! ==

If Keylock Bridge saves you time (or tokens), a rating helps others find it.