Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.319 ·

Bash edit diffs and kept output now need an extra check to pass

The Bash edit-diff feature, and keeping full Bash output in remote sessions, now also need an extra status check to pass

You'll notice Improvements
JSON All of v2.1.319
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
BashArea: what it touches
ImprovementsKind: in v2.1.319,
ImprovementsSection of the release

Unclear What the extra status check tests is not stated.

What

Two Bash features now need an extra status check to pass.

  • The Bash edit-diff feature already needed the server-controlled tengu_quiet_badger setting, which is off unless switched on remotely. When the extra check fails, it does not apply.
  • Keeping a command's full output in remote sessions, those with CLAUDE_CODE_REMOTE set, is now allowed only under extra conditions, one of which is that check.

When Claude Code cannot tell who will read a command's result, it logs that it is not keeping the full output.

The v2.1.318 build had tengu_quiet_badger off by default. The server returned it on for this site's account and off for an anonymous account, a change since the previous reading.

Why

Remote sessions that fail the check no longer keep full Bash output or get the edit diff.

Read from
Feature flag
tengu_quiet_badger Off by default, switched on for this account

The shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.

This account: on · anonymous baseline: off · compiled default in v2.1.319: off

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.319. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns off for tengu_quiet_badger, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_quiet_badger, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_quiet_badger, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_quiet_badger, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_quiet_badger, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_quiet_badger, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat the extra status check tests is not stated.

See this entry in the whole of v2.1.319 →

Feedback