Evidence record / gemini-cli

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-24-gemini-cli-preview-allows-an-explicit-per-server-private-network-mcp-oauth-exception

Preview allows an explicit per-server private-network MCP OAuth exception. oauth.allowPrivateNetwork defaults off and can be enabled for a specific MCP server. It permits the documented private address ranges and internal/local hostnames in OAuth endpoint validation. HTTPS is still required for non-loopback endpoints; link-local addresses remain blocked, loopback has a separate control, and resolved addresses are checked. The exception is scoped to MCP OAuth, not arbitrary web-fetch access.

Channel: preview-or-beta. Half: both. Date: 2026-10-20.

Operator consequence: An enterprise MCP integration with an internal authorization server can now try the regular preview without a public-endpoint workaround. Review the specific endpoints and DNS resolution before enabling the option. The harness removes infrastructure scaffolding but moves the trust decision into a durable, visible per-server setting.

Receipt

Finding metadata

Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0

Finding ID: 2026-10-24-gemini-cli-preview-allows-an-explicit-per-server-private-network-mcp-oauth-exception

Profile citations

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact