Claude Code 2.1.270 restores read-only git in long Bash sessions

If long-running Claude Code sessions started stopping you for permission on read-only git in Bash, 2.1.270 is the pin. It is a one-line hotfix, not a feature release.

Anthropic published tag v2.1.270 on September 12, 2026. GitHub records the release at 2026-09-12T19:45:44Z. The notes list a single item:

Fixed read-only git commands in Bash unexpectedly asking for permission after a session had been running for a while (regression in 2.1.269)

The official changelog uses the same sentence and the same date. That page is generated from CHANGELOG.md on GitHub. The GitHub What's changed section and the 2.1.270 changelog heading carry only that fix. There is no second bullet. Nothing else shipped in this tag.

The regression showed up after a session had been running for a while, so short runs could look fine and long ones would not. Read-only git is how a session keeps its bearings. When those commands started asking again, the work waited on a prompt. 2.1.270 restores the prior behavior so those probes stay quiet.

If you never saw the extra ask, you can ignore the tag. If 2.1.269 left long Bash sessions nagging on read-only git, this is the version to pin. The changelog reminds you to run claude --version to check the installed version before you bump. Upgrade only if those permission prompts showed up in a long session.

Skip the 2.1.269 feature list. This release undoes one permission regression and adds nothing.

Next step: Run claude --version. If you are on 2.1.269 and long sessions re-prompted for read-only git in Bash, move to 2.1.270.

Sources