Devs accidentally committing secrets and forgetting to gitignore env files is nothing new, this is just a new surface. It’s why secret scanning is such an important part of a CI/CD pipeline.
a high entrop for any data going out from that blind CLI should be banned without exception. The user then needs to approve. its the responsibility of Anthropic.
I can only speak anecdotally, but from what I’ve seen firsthand the user does need to approve. In fact, the user needs to approve almost everything, unless they choose to put the CLI into “auto-mode” which should just be assumed is at one’s own risk.
In regard to
settings.local.jsonI’ve only ever seen it automatically created gitignored. I’m not saying it’s not possible for the user to prompt in some way to intentionally or accidentally bypass that, but still.At some point this honestly isn’t Anthropic’s problem. And a developer that takes the stance of “privacy and security is the responsibility of my toolkit” is one that is either very green, or reckless.
it’s a bit tedious in some ways but I really liked working with GitHubs secret system. As long as you ensure nothing changes in the GitHub run system you could use various key signing mechanisms or even uploads to service providers like AWS with out sharing via dot files or user configuration only files that end up being committed to the repo.
What the fuck is this website?
Are they ripping off HN and AI summarising their posts our what
This is what I thought people referenced for over a decade whenever they mentioned HN because no one pointed me to the actual HN.
y combinator was founded by sam altman and is really mostly AI schill and very boring nowadays
That explains why LLMs are so stochastic.
https://apiiro.com/blog/coding-agents-leaking-secrets-github-dont-ask-again
is this the original?
