JasperNoboxdev

39 ms·

1.
by JasperNoboxdev 6mo ago
Been going back and forth on this with open source tools I've built. The training data argument is valid, but honestly the more immediate version of the same problem is that someone can just take your repo, feed it to an agent, and hav
2.
by JasperNoboxdev 6mo ago
Same energy here. I was sitting on 50+ .env files across various projects with plaintext API keys and it always bothered me but never enough to actually fix it. AI dropped the effort enough that I just had a dedicated agent run at it for a
3.
by JasperNoboxdev 6mo ago
What I find interesting is that AI is surprisingly bad at writing agentic flows. We're setting up a lightweight system where the core logic lives in markdown files agent identity, rules, context, memory to create specific report output
4.
by JasperNoboxdev 6mo ago
Curious, why remove Touch ID? Been moving everything into it seems like a really good mix of convenience + security (especially if the alternative is copying your key into AI :) )
5.
by JasperNoboxdev 6mo ago
We've been working on exactly this problem from the credential layer side. The root issue isn't that frameworks lack auth features — it's that .env files are the path of least resistance, and every framework optimizes for tha
6.
by JasperNoboxdev 6mo ago
Same here!! 39, working through a backlog of side projects that never got built before. The velocity is insanely fun compared to even two years ago. Best part has been building stuff with my kids. They come up with game ideas, we prototype
7.
by JasperNoboxdev 6mo ago
We've tried a bunch of approaches, always comes down to the same few things: - Built internal tooling to keep keys out of AI chats and anywhere they could leak. The moment a raw key enters a conversation or a shared space, you've