TAG
#gemini cli
Stories connected through a shared idea, actor, technology or theme.
Gemini CLI nightly strengthens the latest agent runtime pathThe build was cut from the previous nightly release and distributed as a pre-release CLI package. Because it is a nightly build, the update signals ongoing agent-runtime development but is not a stable-channel guarantee.→Gemini CLI 0.60 hardens MCP OAuth, sandboxing and extension boundariesGemini CLI 0.60 enforces RFC 9207 issuer identification in MCP OAuth and improves web-fetch destination validation and connection routing. It also isolates macOS sandbox directories, validates extension paths and workspace boundaries, checks configuration ownership, sanitises environment changes and preserves provenance metadata for untrusted tool output.→Gemini CLI preview strengthens MCP OAuth, sandboxing and path boundariesThe preview adds destination validation for web-fetch utilities and enforces RFC 9207 issuer identification in MCP OAuth flows. It also isolates temporary directories, tightens extension and symlink boundary checks, requires consent for environment changes and removes a hard-coded CrUX API key.→Gemini CLI publishes a new 0.60 nightly buildThe build is tagged v0.60.0-nightly.20260907.g85aca163f and was published on 7 September. Its release page links the complete change set against the preceding nightly build but does not provide feature-level notes.→Gemini CLI nightly hardens macOS agent sandbox boundariesThe v0.56.0 nightly 20260822 build isolates Docker and container-runtime sockets and binaries in macOS Seatbelt. The change is a pre-release sandbox fix rather than a stable-channel feature.→