Source Intelligence

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.183 v2.1.186newer

Claude Code v2.1.185

3 entries read diff v2.1.183 → v2.1.185 Markdown

This is a small patch release with two user-facing messaging improvements for slow or stalled API connections, a thinking-budget UI change that restricts an advanced display to first-party accounts, and an internal constant doubling that likely raises a timeout or buffer ceiling.

Find
Pick an entry · j / k steps through
3 entries

Improvementsopen

Clearer messaging when the API is slow to respond#

The status message shown during a stalled request has been reworded to be less alarming and more accurate. Previously the UI displayed "No response from API" in red, which implied a hard failure. It now reads "Waiting for API response", better reflecting that the client is still actively waiting rather than having given up.

The companion retry hint was also made lowercase for consistency: " · Retrying in " is now " · will retry in ".

Evidence

stalled-state component (search for "Waiting for API response" and "will retry in")

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

Thinking-budget display now restricted to first-party accounts#

Feature flag
tengu_chert_bezel 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.185: not a boolean we can read

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.185. It isn't a statement about your account. What a flag value here can and cannot tell you

A UI element related to thinking-budget visualization (internally Tun, associated with the "Chert Bezel" feature) was previously gated behind the server-side feature flag tengu_chert_bezel. It is now shown only when the session auth mode resolves to "firstParty" — meaning direct Anthropic accounts — instead of being flag-controlled.

This effectively removes the server-side toggle in favour of a hard auth-tier check, so Bedrock and Vertex users will not see this component regardless of any flag state.

Evidence

model-feature array assembly (search for "firstParty" adjacent to the Tun push; previously searched for "tengu_chert_bezel")

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

Internal constant doubled (10 000 → 20 000)#

A numeric constant was raised from 10000 to 20000. Given its context in the build, this is most likely a timeout value (in milliseconds) or a maximum buffer/retry ceiling somewhere in the daemon or update subsystem. Users would observe this as the tool waiting longer before surfacing a timeout error in affected code paths, rather than any explicit UI change.

Evidence

removed constant $lc = 1e4, added Woc = 20000 (search for Woc in v2.1.185 source)

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.185. 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.

  • The stream-stall hint now reads "Waiting for API response · will retry in …" instead of "No response from API · Retrying in …", and triggers after 20s of silence instead of 10s
System prompt

No change to the system prompt since v2.1.183.

Claude Code, interactive mode