Out of curiosity, how many of you have had concerns regarding AI agents having access to your codebase and credentials in your codebase (eg. appsettings, API keys, etc.). How many of you realized it's a problem after it's saved to cloud and I imagine on a subscription, not API where your data is kept private...
Bump if you think we need a lightweight (eg. 100m param) draft model, that is trained explicitly to filter any sensitive data and scramble it, as a middleware service, to prevent data leaks to cloud. Either that, or a tiny model to run on a codebase to replace all sensitive data with references and an interaction layer for the agentic harness to call the reference, instead of directly calling the credentials from file?
What that would mean, is essentially, your SQL connection string stays safe, your API keys stay safe, your logins stay safe, if you expand, it can keep your banking details safe, while allowing you to use your AI to it's fullest, without slowing it down?
Idk, thought crossed my mind again and I thought I'd actually ask who else has thought of it?
Top comments (0)