Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

trusted_proxies

setting gone JSON

A Claude Code settings key, read out of the shipped bundle. It was in the build from v2.1.287 and was gone by v2.1.307.

Enterprise gateway gets a configurable database connect timeout and clearer rate-limit/proxy warnings

Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.274.

First seen v2.1.287 1 Oct 2026
Last seen v2.1.306 21 Oct 2026, gone by v2.1.307
Builds15 / 149on this box, as of v2.1.308
Written about v2.1.274 first named in a changelog, 16 Sep 2026
v2.1.287in the build not in the build never minedv2.1.308

In the changelogs

2

Releases whose published page names trusted_proxies.

  1. v2.1.274
    Enterprise gateway: configurable Postgres connect timeout, retried boot connection, and rate-limit / X-Forwarded-For diagnostics

    Enterprise gateway gets a configurable database connect timeout and clearer rate-limit/proxy warnings

    found in this entry's text

  2. v2.1.274
    OAuth gateway device-flow rate-limit errors get clearer network-attribution messaging and a metric

    Self-hosted gateway's OAuth device-login rate-limit errors now explain shared-network causes and point to specific settings

    found in this entry's text

First cited

2

The earliest release whose published evidence quoted trusted_proxies was v2.1.268, 10 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

ReleaseDateThe span that was quoted
v2.1.26810 Sep 2026client IPs: TCP peer address (listen.trusted_proxies empty)
v2.1.27416 Sep 2026Too many sign-in attempts came from your network address, which other people may share. If this keeps happening after a few minutes, a gateway setting needs changing for your network: listen.trusted_proxies or rate_limits.device_authorization. The gateway log says which.

Presence across releases

4
BuildsHow manyDatesReading
v2.1.287 – v2.1.30113 builds1 Oct 2026 → 15 Oct 2026 ◆in the build
v2.1.302 – v2.1.3043 builds16 Oct 2026 → 19 Oct 2026 ○not in the build
v2.1.305 – v2.1.3062 builds20 Oct 2026 → 21 Oct 2026 ◆in the build
v2.1.307 – v2.1.3082 builds21 Oct 2026 → 22 Oct 2026 ○not in the build

Build by build

20

One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.

BuildDateStateThe record behind it
v2.1.2871 Oct 2026·addedverdict: added
v2.1.2882 Oct 2026·presentverdict: present
v2.1.2893 Oct 2026·presentverdict: present
v2.1.2905 Oct 2026·presentverdict: present
v2.1.2916 Oct 2026·presentverdict: present
v2.1.2926 Oct 2026·presentverdict: present
v2.1.2937 Oct 2026·presentverdict: present
v2.1.2948 Oct 2026·presentverdict: present
v2.1.2958 Oct 2026·presentverdict: present
v2.1.2969 Oct 2026·presentverdict: present
v2.1.29914 Oct 2026·presentverdict: present
v2.1.30014 Oct 2026·presentverdict: present
v2.1.30115 Oct 2026·presentverdict: present
v2.1.30216 Oct 2026·removedverdict: removed
v2.1.30318 Oct 2026·absent—
v2.1.30419 Oct 2026·absent—
v2.1.30520 Oct 2026·addedverdict: added
v2.1.30621 Oct 2026·presentverdict: present
v2.1.30721 Oct 2026·removedverdict: removed
v2.1.30822 Oct 2026·absent—

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.

Feedback