The changelog for 2.1.270 is one bullet long. Fixed: read-only git commands in Bash unexpectedly asking for permission after a session had been running for a while. A regression from 2.1.269.
Why that particular bug stings
git status, git diff, git log — these are the commands Claude Code fires every couple of minutes to work out where it stands. They change nothing, so most people have them allow-listed and never see them.
That’s what broke, and only after a while. Early in a session everything behaved, then at some point a dialog appeared mid-work that had no business being there. Bugs like this are miserable because you can’t reproduce them: two minutes after launch it’s fine, two hours in it isn’t. If you work in auto mode, or leave a run unattended, you find out when nothing moves anymore.
The regression arrived with 2.1.269 the day before — the release with claude plugin eval, the Bash diff, and the permission work around the exclamation mark. That something slipped there makes sense: touching permission rules means touching the exact logic that decides when to ask.
My take
Four releases in four days, and this one repairs damage that’s a day old. You could read that as flailing. I read it the other way: a one-line release carrying nothing but the fix is the more honest option, compared with “it’ll ride along with the next big update.”
If you’re still on 2.1.269 and wondered why git status suddenly started prompting: that wasn’t your config. claude --version tells you where you are, and an update clears it.
Sources: Claude Code changelog, Claude Code release v2.1.270