Keylock Bridge door Keylock Bridge

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.

== 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 debugging context is shared with your AI IDE or model.

This add-on may request permissions to access page and developer tools data in order to collect console logs, network activity, and related debugging signals. This access is used only to provide the add-on’s functionality.

== Feedback and bug reports ==

If you encounter an issue or have a feature request, please contact us at contact@keylockbridge.dev

== Enjoying Keylock Bridge? ==

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

== Updates ==

See release notes and announcements where we post updates.