Tooling Independent signal for people building with AI In the edition of Wednesday, 16 September 2026
The Early Edition

The change, the consequence, the evidence. Before the churn.

Eleven fixes

Gemini CLI 0.60.0 stable carries eleven hardening fixes and one enforcement of RFC 9207

By the Newsroom

Google released Gemini CLI v0.60.0 on 15 September with eleven fixes and hardening changes in its notes.

Among them: RFC 9207 issuer identification in the MCP OAuth flow, “envelope metadata provenance for untrusted tool outputs”, strict permission and ownership checks on system-wide configuration paths, and a removed hard-coded Google CrUX API key. The nightly this paper printed yesterday for the build-file injection fix reached the preview channel the same day as v0.61.0-preview.0.

What it changes Upgrade to 0.60.0; the OAuth issuer check can break an MCP server whose authorization server misreports its issuer.

Primary source read

google-gemini/gemini-cli v0.60.0

Published in the edition of Wednesday, 16 September 2026 · Beat: Tooling

More from Tooling

  1. Wednesday, 16 September 2026 llama.cpp 0.4.1 removes three loading flags and keeps reasoning by default
  2. Wednesday, 16 September 2026 Flowise’s Custom MCP node took an npm package name from the user and ran it
  3. Wednesday, 16 September 2026 PraisonAI’s codeMode ran model-written JavaScript behind a regex, and the constructor chain walked round it
  4. Wednesday, 16 September 2026 IBM’s MCP Context Forge shipped a Python sandbox that checked for dunder names as strings
  5. Wednesday, 16 September 2026 Docker’s MCP Gateway let an image label write its own docker run flags
  6. Wednesday, 16 September 2026 Claude Code’s permission checker missed an rm inside a subshell; 2.1.273 closes it and reopens what 2.1.268 refused