1
2 Comments

What happened in the first 48 hours after launching my Chrome extension

Two days ago I posted here about a small Chrome extension I built after almost leaking an API key into ChatGPT while sharing logs.

The idea is simple: when you paste text into AI chats (ChatGPT / Gemini / Claude), the extension scans it locally and detects things like API keys, emails, phone numbers, UUIDs, etc. If something sensitive is detected it can warn you or automatically mask the values before inserting the text.

I wanted to share what happened in the first ~48 hours after launching it.

Current numbers:

• ~40 Chrome Web Store page views
• 7 installs
• 1 review
• a few friends testing it and sending feedback

The most interesting part is that the extension already caught several things I didn’t notice while pasting logs during debugging.

Which confirmed the original problem: when you're moving fast with AI chats, it's very easy to accidentally paste sensitive data.

What surprised me most so far:

  1. The install conversion from page views seems pretty high (~15–20%).
  2. Most people who tried it immediately suggested adding more detection patterns.
  3. The hardest part right now isn’t building the extension — it's distribution.

I'm currently trying different places where developers hang out (Reddit, Hacker News, etc.) to see where this resonates.

Curious about two things:

  1. Do you manually clean logs before pasting them into AI chats?
  2. Where have you seen the best early traction for small developer tools?

Would love to hear how others approached early distribution.

on March 14, 2026
  1. 1

    Curious how others handle this — do you manually clean logs before pasting them into AI chats?

  2. 1

    If anyone is curious to try it:

    Chrome Web Store:
    https://chromewebstore.google.com/detail/pastesafe-—-ai-paste-sani/gpoiombmmaegnfijmcelgbkfbkelgdih

    Project page:
    pastsafe-ext.github.io/pastesafe/

    Would love feedback from people who use AI chats a lot.