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 of v2.1.238 Home All releases olderv2.1.237 v2.1.239newer
Claude Code v2.1.238

Remote bridge retries rejections that did not come from the origin server

You'll notice
Useful3 Signal3
Remote Control

Remote bridge retries 401/403/404s that came from a proxy rather than closing permanently.

Feature flag
tengu_ethereal_mist Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.238: off

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

What

When the remote connection is rejected with a 401, 403 or 404 that is reported as coming from something other than the origin server (a proxy, for example), the bridge now retries within a time window instead of closing permanently. Controlled by tengu_ethereal_mist, which falls back to on.

Details
  • Rejections are tracked as a streak; logs distinguish a permanent rejection from a retried non-origin one and include the attempt number.
  • A successful recovery is reported with the number of attempts and how long the streak lasted.
Evidence

nonOrigin403Retry

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

See this entry in the whole of v2.1.238 →