... everyone , I've been building Prompt Armour a browser extension that detects and redacts sensitive data in real-time inside ChatGPT, Gemini, and Claude before you hit send. The problem: every time you paste code, emails, documents, or customer data into an AI chatbot, that data potentially gets stored, logged, or used for training. Most people don't think twice about it. How it works: - Scans your input in real-time as you type or paste - Detects names, emails, phone ... ... paint highlights without touching the DOM. Built with Plasmo, TypeScript, React. Available on Chrome Web Store now, Firefox version pending review. I'm trying to figure out what to build next. A few things on my radar: - Standalone redaction

... composing. * Scoped & read-only: Chips are TTL (time-to-live) bound, no auto write-back; your current project s memory stays clean. * Inline provenance: Replies show which chip informed which part. * Admin guardrails: Allow/deny lists, approvals, label-based redaction (PII/secrets), and audit logs. Why it helps * Cut repeat explanations across repos/teams. * Reuse proven auth/logging/CI/CD patterns instead of reinventing. * Faster onboarding by bridging Architecture + Conventions. * Safer incident response: pull the right runbook just for this thread. MVP flow 1. Compose ... ... project/label/item. 3. Attach 1 3 chips (e.g., Auth , Runbook ). 4. Send. Chips are used for this reply only and auto-expire. Privacy & compliance * Default-deny cross-project recall; everything is explicit & logged. * Sensitive labels can be auto-redacted