We're looking for developers who use AI coding tools every day to test our upcoming Chrome extension before launch.
Whether you're a vibe coder, AI engineer, frontend, backend, or full-stack developer, we'd love your feedback on real-world usage. Early testers will get access to all Pro features after launch.
Everyone talks about AI making developers more productive.I'm more interested in the new problems it introduced.
-Not hallucinations.
-Not prompt engineering.
Actual day-to-day workflow problems that only appeared because AI became part of development. Have you noticed one?
Hi everyone!
I'm working on a small developer tool, and before I build more features, I'd rather understand how people actually use AI day to day. If you're using tools I'd love to hear about your experience. A few things I'm curious about:
- What's your typical AI workflow?
- Do you ever paste logs, stack traces, or config files into AI?
- Have you ever worried about accidentally sharing something sensitive?
Is there anything about your current workflow that feels annoying or risky?
I'm not looking to pitch anything I genuinely want to learn from people who use these tools every day. Every reply helps me understand the problem better.
Always interesting to see what people in this community are working on.
Share your SaaS in 1–2 lines and tell us what problem it solves.I'll go first.I'm building SecureIntent, a Chrome extension that helps developers avoid accidentally sharing API keys, tokens, passwords, and other sensitive data when using AI tools. It scans pasted content locally, warns you before anything sensitive is shared, and can automatically redact secrets.
Curious to see what everyone else is building!
Quick question for people who use AI tools every day.Do you actually review everything before you paste it?I realized I almost never do anymore, especially with long logs or stack traces. I'm usually focused on the bug, not on whether there's something sensitive buried in the middle.
Have you ever caught yourself about to share something you shouldn't have? Or do you have a workflow that prevents that from happening?
Over the last few months I've been building a Chrome extension for developers who use ChatGPT, Cursor, Claude, and Copilot.
The idea came from noticing how often I was copying logs, stack traces, config files, and API responses into AI while debugging. Most of the time it's fine, but every now and then there's an API key, access token, password, or other sensitive information hidden somewhere in the middle.
The extension checks pasted content before it's submitted, warns if it finds sensitive data, and can automatically redact secrets. Everything runs locally in the browser.
It's still in beta, and I'm mainly looking for honest feedback from developers who use AI as part of their daily workflow.
I'd love to hear what you think or what you'd add.
The more we used ChatGPT and Cursor, the more we relied on copy and paste.
Logs, stack traces, API responses, config files... everything went through our clipboard.
It wasn't until recently that we realized we almost never looked at what we were actually pasting anymore.
That small workflow change led us to build a side project around the problem. We didn't set out to build a security tool - we just wanted something that would catch the mistakes we realized we were making ourselves.
I didn't notice it at first, but AI completely changed how I debug. Instead of reading through logs or tracing issues myself, I started copying everything into ChatGPT or Cursor. Terminal output, stack traces, config files, API responses... basically whatever might help solve the problem faster. After a while, I realized I wasn't even looking at what I was pasting anymore. That habit ended up inspiring a Chrome extension I've been building over the last few months. It scans pasted content for API keys, tokens, passwords, and other sensitive information before anything gets shared. It's funny how the problem wasn't AI itself. It was how quickly it changed my workflow without me noticing.
I've been using AI tools heavily for coding over the last year, and I noticed something that made me a little uncomfortable. Almost everyone copies and pastes logs, stack traces, config files, API responses, and chunks of code into ai Most of the time it's harmless. But every now and then there's an API key, access token, JWT, password, or internal URL buried somewhere in hundreds of lines of text. The scary part is that most leaks aren't intentional. People are usually focused on fixing a bug, not reviewing every line before they hit paste. So I built a Chrome extension that warns developers before sensitive credentials get pasted into AI tools or other websites.
What it does:
- Detects API keys, tokens, and credentials
- Warns before they're pasted
- Can redact secrets automatically
- Runs locally in the browser
- Doesn't send your raw text anywhere
I'm still validating the problem and would love feedback from other developers.
I've been working on a tool focused on preventing accidental secret leaks when developers use AI. The idea came from something I've seen over and over again: people paste logs, stack traces, config files, API responses, and chunks of code into AI tools while debugging. Most of the time it's not a security issue. But sometimes there's an API key, access token, internal URL, or credential buried somewhere in hundreds of lines of text.
As AI becomes a normal part of development, I'm curious how people are dealing with this.
- Are you using AI for coding every day?
- Do you have rules around what can and can't be shared?
- Are you relying on developer awareness or actual security tooling?
- Have you ever caught a secret before sending a prompt?
Also curious what everyone here is building these days. Always interested in seeing what other founders and developers are working on.
I've noticed how common it is to paste logs, configs, or code into AI tools while debugging.
Most people aren't intentionally sharing sensitive data, but it's easy to miss an API key, token, or internal URL hidden in a large block of text.
How are teams handling this today? Are you relying on awareness, policies, or tools to catch sensitive information before it gets shared?