hn.today

Claude Code's "Don't Ask Again" exposes passwords in 1,122 public GitHub files

apiiro.com399 points273 comments
Screenshot of Claude Code's "Don't Ask Again" exposes passwords in 1,122 public GitHub files

The discussion centers on passwords found in committed Claude Code settings files. A Claude Code team representative says `.claude/settings.local.json` is intended to remain local, that users should enable secret scanning, and that auto mode is safer than maintaining permission rules. Commenters clarify that “Don’t Ask Again” does not expose credentials by itself: the risk arises when an approved command containing a secret is saved in a settings file and that file is committed. They also note that repository access matters: the files identified were in public repositories, while private repositories still expose credentials to anyone with access and can spread them through clones or forks.

Commenters divide over whether this is user error or a product failure. Some call committing settings files a basic security mistake and say secret leaks predate AI agents; others argue that writing secrets into project files is foreseeable behavior the company should prevent, and criticize the team’s emphasis on user responsibility. They also dispute the recommendation to use auto mode: supporters say fewer prompts reduce approval fatigue, while critics say it offers no defined security guarantee without sandboxing and can obstruct legitimate workflows. Suggested safeguards include secret scanning, isolated ephemeral machines, API proxies that require confirmation for sensitive actions, and password-manager access requiring biometric approval. Others object that agent access to credentials remains dangerous even with these controls.

Read on apiiro.com273 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Security

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.