Follow Discord
Sweep 28 Sep 2026 · 18:16Z Build v2.1.284 505 read Stable v2.1.277 Latest v2.1.284 Next v2.1.284 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.284 ·

Gateway config now checks the login settings for telemetry forwarding

Gateway configuration now checks the auth settings on each telemetry.forward_to entry and reports problems with their Google login settings

You'll notice Improvements
JSON All of v2.1.284
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
GatewayArea: what it touches
ImprovementsKind: in v2.1.284,
ImprovementsSection of the release
What

In a self-hosted gateway's configuration, each telemetry.forward_to entry says where to send telemetry (usage and performance data). Entries that include auth login settings are now checked when the configuration is loaded, and any problems are reported against that entry's Google login settings.

Why

If you run your own gateway, mistakes in telemetry forwarding login settings show up when the configuration is checked, rather than later.

Read from
Names in the bundletelemetry.forward_to
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhich specific problems the check reports is not stated.
Anthropic's release notes agreeAdded auth: { google: {} } for Claude apps gateway telemetry.forward_to destinations, so telemetry can be exported straight to Google…

See this entry in the whole of v2.1.284 →

Feedback