Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All releases Home ←olderv2.1.240 v2.1.242newer→

Claude Code v2.1.241

5 entries read diff v2.1.240 → v2.1.241 Markdown
How it breaks down
Not switched on1Under the hood4

Claude Code now sends the VS Code extension a map of experiment flags at startup, and that map picks up an entry called tengu_sable_thrush, which tells the IDE whether narration summaries are enabled so it can branch on that. The flag is off by default in this build unless a server config switches it on. If you want to decide for yourself, CLAUDE_CODE_SABLE_THRUSH forces it on or off in either direction. Nothing about narration itself is reachable here; this is only the plumbing that reports its state.

The control-protocol schema an SDK client uses to set extended thinking now describes its null case more accurately: passing null for thinking_display clears the override so Claude Code's own default display handling takes over, rather than falling back to the API default. This is a wording change to the schema description alone. The fields, the "summarized" and "omitted" values, and the --thinking-display flag all behave exactly as they did before.

Find
Flag state
Pick an entry · j / k steps through
1 entry

What probably matters to you

Anything you can use today, anything that visibly changes, and anything worth poking at. One line each, open for detail.

Not switched on
Useful2 Signal4
IDE Integration Notable not in their notes

Narration gate state now reported to the VS Code extension#

A narration-summary feature can be forced on with an env var, but it's off by default here.

Narration summaries sit behind a flag that is off unless server config or CLAUDE_CODE_SABLE_THRUSH turns it on, and the VS Code extension is now told its state.

Feature flag
tengu_sable_thrush On for this account, and not off by default

The flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.

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

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

CLAUDE_CODE_SABLE_THRUSH
What

Claude Code sends the VS Code extension a map of experiment flags at startup, and that map gains one entry, tengu_sable_thrush, so the IDE side can branch on whether narration summaries are enabled. The flag is off by default in this build unless a server config turns it on. Set CLAUDE_CODE_SABLE_THRUSH to force it on or off in either direction.

Details
  • The value comes from the narration module's own check: the environment variable wins if set, otherwise the remote flag is consulted with an in-source fallback of false.
  • The result is read once and latched for the process; a test-only helper exists to clear that latch.
  • The flag itself is not new, it already drove narration-summary rendering in 2.1.240. What is new is that its state is shared with the extension.
  • What the extension does with the value lives outside this build.
Evidence

tengu_sable_thrush: (Cmr(), ln(uYr)).isSableThrushEnabled(),

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

Were these the right ones to put at the top? 2 answered
Below the fold

Everything else

Smaller changes and internals, grouped as the pipeline found them. Nothing is dropped, it is only further down.

1 entry

Improvementsopen

Under the hood
Useful1 Signal1
Elsewhere not in their notes

Clearer wording for clearing the thinking display override#

A schema description was reworded to explain that clearing the thinking display setting restores Claude Code's own default.

--thinking-display
What

The control-protocol schema that lets an SDK client set extended thinking now explains the null case differently: passing null for thinking_display clears the override so Claude Code's own default display handling applies, rather than reverting to the API default. Wording only; the fields, the "summarized" and "omitted" values, and --thinking-display all behave as before.

Details
  • Affects max_thinking_tokens and thinking_display on the extended-thinking control request.
  • No gate; visible to anyone reading the schema.
Evidence

null clears that override so Claude Code's default display handling applies again

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

3 entries

Internal Changesopen

Under the hood
Useful2 Signal1
Elsewhere

Version stamped to 2.1.241#

The version number moved from 2.1.240 to 2.1.241; nothing else changed.

What

The embedded build constants advance from 2.1.240 to 2.1.241, with a new build timestamp and commit hash. Nothing changes but the numbers.

Details
  • The version string is inlined at roughly 120 places, so it moves everything that reports a version: --version, the /status and /doctor panels, the claude-code/ and claude-cli/ User-Agent strings, the shr- prefixed environment-runner version header, the update and downgrade messages, the Remote Control minimum-version check, the daemon start log line, and telemetry group names built from the version.
  • Build time is 2026-08-22T22:46:48Z.
Evidence

GIT_SHA: "c87e2742fc9ad269ec8920460d00a091b1e410f0", BUILD_TIME: "2026-08-22T22:46:48Z"

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

Under the hood
Useful1 Signal0
Elsewhere

Code-review prompt rebuilt with the same text#

The code-review prompt was rebuilt with identical wording, so reviews work exactly as before.

What

The multi-angle code-review prompt was re-emitted in the bundle, but a line-by-line comparison against the previous build shows the same angles, phases and fallback text in the same order. Reviews behave exactly as before.

Details
  • Covers the Angles A through E block, the verify and sweep phases including the recall-biased variant, and the text used when subagents are unavailable.
  • The apparent change is the minifier reshuffling internal symbols.
Evidence

### Angle E \u2014 wrapper/proxy correctness

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Under the hood
Useful1 Signal0
Elsewhere

Module startup wiring shuffled#

Startup wiring was rearranged behind the scenes with no difference you can see.

What

One aggregate module initialiser no longer runs a dependency it previously did, and a single initialiser call was added elsewhere. Bookkeeping that follows the code motion in this release, with no effect anyone can observe.

Evidence

ia_();

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Verbatim
Official · Anthropic

Anthropic’s official release notes

Published verbatim by Anthropic for v2.1.241. Text is unmodified from the upstream changelog. Everything else on this page came out of the bundle instead, which is why the two lists don't match.

  • Bug fixes and reliability improvements
Read it on GitHub →
System prompt

No change to the system prompt since v2.1.240.

Claude Code, interactive mode

Read the prompts for this release →
Documentation

What the docs did around this release

117 documentation changes were recorded within 24 hours either side of this release, nearest first. The closest 12 are below. They're here because they happened near this release in time. That's not a claim that this release caused the edit, or that the page documents anything in it.

changelog Changed +4 -0 recorded here claude-code plugins-reference Changed +1 -1 recorded here claude-code claude-tag/users/when-claude-responds Changed +1 -1 recorded here claude-docs claude-tag/concepts/how-it-works Changed +5 -3 recorded here claude-docs claude-tag/concepts/agent-identity Changed +1 -1 recorded here claude-docs claude-tag/admins/setup-overview Changed +1 -0 recorded here claude-docs whats-new/index Changed +16 -0 recorded here claude-code whats-new/2026-w34 New page +101 -0 recorded here claude-code whats-new/2026-w33 New page +83 -0 recorded here claude-code quickstart Changed +5 -5 recorded here claude-code claude-apps-gateway Changed +26 -22 recorded here claude-code changelog Changed +4 -0 recorded here claude-code

Every time above is when this site's poller recorded the change, which is up to half an hour after the edit on an ordinary read and up to a day after it on a full sweep. Upstream's own edit time is used instead wherever a capture carries one. None of these do.

The documentation ledger →
Switches

Every name in this release

The 2 literal strings found in the bundle, with the number of entries that name each one. Picking one searches for it. A name is here because this build's code mentions it, which is not the same as it working or being finished.

CLI flags

Environment variables