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.
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.
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.
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.