Claude Code approval files leak 1,379 secrets on GitHub

The significance here is less about the count than about the persistence layer: approvals meant to smooth workflows are quietly becoming a credential store, and that design choice is what turns routine developer behavior into public exposure. It affects teams using Claude Code in shared or public repositories, where saved approvals can outlive the commands they were meant to authorize. The team's stated interest in built-in secret scanning would address detection, not the underlying retention. Whether safeguards target storage itself or only flag leaks afterward is the open question worth watching.