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

Re:Claude Code's "Don't Ask Again" exposes passwords in 1,12... by eviluncle on Sunday November 08, 2026 @01:55AM (#50411026)

Not OP, but if I understand their complaint correctly, they're saying that on auto mode claude does a lot of things in obscure ways with "clever" (i.e non human readable) bash commands that perform multiple operations and OP feels they are losing control over their codebase and so they opt for edit mode where they get to review what commands claude runs.

[ Parent | on HN ]

Re:Claude Code's "Don't Ask Again" exposes passwords in 1,12... by fmbb on Sunday November 08, 2026 @02:07AM (#50411075)

Editing local files is not where you control your source code I hope.

Just tell Claude to never commit or push.

You are in control of git, Claude is simply a tool to quickly apply changes to local files for something you want.

[ Parent | on HN ]

Re:Claude Code's "Don't Ask Again" exposes passwords in 1,12... by watwut on Sunday November 08, 2026 @02:41AM (#50411198)

Yes, why should we do the things in easier and more comfortabke way (review small changes) when we can force user into harder one (newest changes mixed with all previous ones).

[ Parent | on HN ]

Re:Claude Code's "Don't Ask Again" exposes passwords in 1,12... by number6 on Sunday November 08, 2026 @03:43AM (#50411482)

I just review the MR

[ Parent | on HN ]

Re:Claude Code's "Don't Ask Again" exposes passwords in 1,12... by imtringued on Sunday November 08, 2026 @03:49AM (#50411504)

So basically you gave up?

[ Parent | on HN ]

Re:Claude Code's "Don't Ask Again" exposes passwords in 1,12... by fmbb on Sunday November 08, 2026 @04:17AM (#50411626)

What does this mean?

A Merge Request or Pull Request is the only thing that makes sense to review, and always has been since before LLMs.

If some author tells me “you can review each commit to make it easy” I will ask them to make separate PRs.

[ Parent | on HN ]

Re:Claude Code's "Don't Ask Again" exposes passwords in 1,12... by watwut on Sunday November 08, 2026 @06:29AM (#50412343)

It means you gave up on getting claude to show you changes as it is doing them, in a comfortable form, so that you can steer it as it is doing them.

[ Parent | on HN ]

Re:Claude Code's "Don't Ask Again" exposes passwords in 1,12... by soon_to_be_sb on Sunday November 08, 2026 @06:55AM (#50412489)

>A Merge Request or Pull Request is the only thing that makes sense to review, and always has been since before LLMs.

Why doesn't it make sense to review smaller units of change within a big PR?

[ Parent | on HN ]

Re:Claude Code's "Don't Ask Again" exposes passwords in 1,12... by skydhash on Sunday November 08, 2026 @07:35AM (#50412722)

Not GP, but in my experience, those small changes are usually contrived to be small. Like saving snapshots instead of being atomic and self contained. And if they are the latter, they should have been separate PR.

That’s why I usually look at the diff of the whole PR and prefer to merge by squashing. Commits inside the PR are usually noise.

[ Parent | on HN ]

Re:Claude Code's "Don't Ask Again" exposes passwords in 1,12... by soon_to_be_sb on Sunday November 08, 2026 @09:01AM (#50413461)

What you are saying is true if created manually. It is a chore to create sensible commits messages when you are committing often.

But LLMs appear to be pretty good at making small commits with sensible commit messages, that greatly help to make sense of the whole PR.

Regarding large monolithic commits, how do you even know where to start reviewing in a large PR? Smaller commits at least give you some sense of ordering.

[ Parent | on HN ]

Re:Claude Code's "Don't Ask Again" exposes passwords in 1,12... by imtringued on Sunday November 08, 2026 @03:45AM (#50411496)

Nothing more comfortable than having to use git commits and branching just for telling the agent which lines it messed up instead of simply not writing the garbage in the first place.

[ Parent | on HN ]