Claude Code 2.1.270: Inline Diffs and Key Fixes

James Turner

Brought to you by Jellypod AI! You know, Lachlan, if you have ever asked an AI coding agent to run something like sed or prettier write in your terminal, you know there is this annoying blind spot.

Lachlan Reed

Oh, mate, absolutely. It is like firing a arrow into the dark, right? The tool runs, returns exit code zero, and Claude is sitting there thinking, well, I guess that worked! But it has no idea what actually changed on disk unless it goes and runs a separate git diff or a Read tool call.

James Turner

Exactly. It wastes an entire extra tool turn just to confirm what it did. But in Claude Code 2.1.269, and tweaked again in 2.1.270, Anthropic added a setting called bashEditDiffEnabled.

Lachlan Reed

Okay, so what does bashEditDiffEnabled actually do under the hood?

James Turner

When you toggle bashEditDiffEnabled in your configuration, the Bash tool runner intercepts file modifications on the fly. So if a shell command alters a file, it automatically appends an inline unified diff right into the tool result itself.

Lachlan Reed

Oh, that is clever! So Claude sees the exact lines that changed immediately, no extra git diff required.

James Turner

Right on the spot. Though, you do have to be a bit careful with context token usage, you know? If you run codegen or format fifty files at once, suddenly you are dumping huge diffs into your context window.

Lachlan Reed

Yeah, fair point. You gotta weigh the convenience against blowing out your prompt limits. But speaking of shell commands doing sneaky things, there was a really important security fix around this too, yeah?

James Turner

Yeah, the tee command fix. Previously, if you set path scoped deny rules for Edit calls, a Bash command using tee could sometimes bypass the check and overwrite files outside your working directories. Now, Edit deny rules explicitly cover tee commands in Bash too.

Lachlan Reed

Man, sandboxing AI agents is such a moving target. I love seeing those security holes patched up. And speaking of bugs, version 2.1.270 fixed that super annoying git prompt issue, right?

James Turner

Oh yeah! If you were in a long session, read only git commands like git log or git status would suddenly start asking for explicit user permissions out of nowhere.

Lachlan Reed

Like mate, why are you asking me for permission to read a log? You have been doing it for three hours!

James Turner

It was a regression in 2.1.269, but 2.1.270 completely fixed it so read only git commands stay smooth. Plus, the goal command now automatically handles exponential backoff retries if your API drops or hits rate limits, instead of silently stalling out.

Lachlan Reed

That is a huge quality of life step. Little friction fixes like that make working with terminal agents so much less frustrating.

James Turner

Definitely. Toggle bashEditDiffEnabled, update your CLI, and your refactoring loops will be way faster.