Apiiro: Claude Code's "Don't Ask Again" setting leaks secrets
11/22/2026 — 11/22, 19:19·1 sources (all)·1 reports (all)
Key takeaways
- Agentic security firm Apiiro found that Claude Code stores its "Don't Ask Again" preferences in local files on the developer's machine, expo…
Background & analysis
On November 22, 2026, InfoQ reported that the agentic security firm Apiiro had found Claude Code exposing secrets in public repositories. According to the report, the problem stems from the way Claude Code implements its "Don't Ask Again" setting, which stores related data in a local file on the developer's machine. Apiiro identified 1,122 secrets in claude/settings.local.json files. It found another 1,160 secrets in git history, in the shared settings.json, and in agent chat transcripts stored inside repositories. The report was written by Sergio De Simone. The available material stops at Apiiro's findings and counts; it does not include any response from Anthropic or describe any remediation.
AI-generated from 1 reports · updated 27 minutes ago
Related AI tools
- Heat index
- 98
- All sources
- 1
- All reports
- 1
- First seen
- 48 minutes ago
Reports on this story headlines open the original
Agentic security firm Apiiro found that Claude Code has been exposing secrets in public repositories because of how it stores "Don't Ask Again" settings in local files, InfoQ reports. Apiiro identified 1,122 secrets in claude/settings.local.json files and another 1,160 in git history, shared settings.json and agent chat transcripts stored in repos.
InfoQ · AI/MLAI score 58
Other stories people are talking about
- Heat index 28Developer uses hooks to push Claude Code alerts to iPhone1 sources
- Heat index 49Developer benchmarks Claude Code Code Mode: 44% cheaper despite more requests1 sources
- Heat index 29Developer ports 908 VS Code themes to Claude Code1 sources
- Heat index 58Developer breaks a Claude Code mod five ways to test validation1 sources
- Heat index 52Developer shares five Claude Code hooks that block recurring mistakes1 sources
How is heat calculated?About the methodHide
Heat counts how many independent sources covered a story in the last 48 hours: one source counts once no matter how many posts it published, decaying with a 24-hour half-life. What ranks first is what many people are talking about.
This page aggregates public feeds. Headlines and summaries are machine-organized and remain the property of the original authors; verify important facts at the source. If you believe a headline or summary infringes your rights, email the contact address in the footer with the page URL and basis of your claim, and we will remove or replace it after review.
- Surge
- Discussion rising fast
- New
- First report within 6 hours
- Rising
- Still gathering discussion

