Developers using Claude Code can check their public repositories today to see if they have inadvertently leaked sensitive credentials. Agentic security firm Apiiro...
Developers need to check their local configurations and repository histories immediately following findings from agentic security firm Apiiro.
How the “Don’t Ask Again” Feature Left Credentials Exposed
Developers using Claude Code can check their public repositories today to see if they have inadvertently leaked sensitive credentials. Agentic security firm Apiiro revealed on November 22, 2026, that Claude Code has been exposing secrets in public repositories due to how it handles local file storage for its “Don’t Ask Again” functionality.
The security investigation uncovered 1,122 secrets stored directly within claude/settings.local.json files. An additional 1,160 secrets were discovered across git history, shared settings.json files, and agent chat transcripts stored inside repositories.
Confirmed Exposure Points Versus Open Variables
The security firm’s investigation provides specific verification of where these credentials accumulate during standard tool operation. Apiiro confirmed that secrets are being written to local developer machine files and subsequently pushed to public repositories through standard version control workflows.
Pricing and software version details remain unconfirmed in the reporting. Additional specifics regarding future security patches from the developers of Claude Code are not in the sources.
What Tech Consumers and Developers Should Monitor
Tech consumers, gadget buyers, and developers affected by the tool’s storage mechanism should audit their current repository files and commit histories. Developers must inspect claude/settings.local.json, shared settings.json files, git history logs, and agent chat transcripts for lingering credentials.
Frequently Asked Questions
Q1: What caused Claude Code to leak secrets into public repositories?
Claude Code exposes secrets because of how it stores information in local files on developer machines to implement its “Don’t Ask Again” feature.
Q2: How many secrets did Apiiro identify in local settings files and git histories?
The security firm identified 1,122 secrets in claude/settings.local.json files and another 1,160 secrets in git history, shared settings.json files, and agent chat transcripts stored in repositories.
