A 403 injected by your corporate proxy is retried as an outage instead of a hard refusal.
tengu_ethereal_mist Not enough to sayNothing 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's wrong with this entry?
Streaming connections and the bridge credential fetch now check whether a 403 came from Anthropic's own servers or was injected in front of them. A 403 from something else is treated as a temporary outage: the connection keeps retrying instead of giving up, and the bridge treats it as unreachable rather than as a real refusal, until it repeats past a threshold and is finally accepted as one.
- Repeated non-origin 403s are tracked as a streak with attempt count, window and gap, and recovery is logged as
cli_sse_nonorigin_403_recovered. - Disconnect reasons can now state how long the refusal lasted.
- The bridge side sits behind
tengu_ethereal_mist, whose compiled fallback is on; the effective value comes from remote config.
cli_sse_nonorigin_403_recovered
Strings lifted out of the shipped bundle, so the claim above can be checked against them.