Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.268 ·

Gateway login can recognize and display internal network paths

Device-code gateway login now checks whether the connection stays inside a declared internal network and shows the path in the trust prompt.

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaGatewaywhat it touches
KindInternal Changesin v2.1.268,
Group of 2 Under the hood No documentation found

Device-code gateway login now checks whether the connection stays inside a declared internal network and shows the path in the trust prompt.

What

  • The interactive gateway login flow (the device-code OAuth sign-in) now accepts a list of declared internal networks (internalNetworks) and resolves the gateway's host against that list before contacting the OAuth endpoint.
  • If the connection matches a declared network, the trust prompt shown to you now displays the actual network path, e.g. "Connecting from to , both inside declared ".
  • The gateway setup screen component was updated to accept this internalNetworks list as a new prop alongside the existing initialUrl and screenLocked props, so the wizard can be told about or restricted to these internal addresses.

Why Seeing the concrete network path in the trust prompt makes it easier to verify a gateway connection is staying inside your organization's declared network rather than silently trusting an unfamiliar route.

Read from
Names in the bundleinternalNetworks
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 doubtWhat internalNetworks controls in the gateway setup flow is not specified by the finding.

See this entry in the whole of v2.1.268 →