Gemini CLI’s stable channel moved to v0.61.0 on 2026-09-23 (npm `@google/[email protected]`), bringing indirect prompt-injection defenses, hardened sandbox filesystem boundaries and isolated runtime state, AgentLoopContext preservation across object spreads, and correct handling of explicit versioned Flash model IDs.
Key Takeaways
- ✓Install stable with `npm install -g @google/gemini-cli` (now 0.61.0); preview/nightly remain separate tags
- ✓Blocks indirect prompt injection via build-file edits and untrusted flags (#29250)
- ✓Hardens sandbox filesystem boundaries and isolates runtime state (#29214)
- ✓Preserves AgentLoopContext fields across object spreads (#29335)
- ✓Keeps explicit versioned Flash model IDs intact during routing (#29252)
Project Links & Resources
Direct AccessIn-Depth Technical Analysis
Core Background & Industry Pain Points
CLI coding agents that can edit build files amplify indirect prompt-injection risk. After consumer traffic moved to Antigravity CLI, enterprise/API users still ride Gemini CLI’s stable channel—now v0.61.0 (2026-09-23).
Architecture Highlights & Internals
Stable absorbs defenses against build-file/untrusted-flag injection, harder sandbox FS boundaries with isolated runtime state, AgentLoopContext preservation across spreads, and intact versioned Flash model IDs. Diff: v0.60.0…v0.61.0.
Benchmarks & Measured Numbers
No new public coding-bench scores in the stable notes. Verified: GitHub v0.61.0 at 2026-09-23T23:59:15Z; npm latest = 0.61.0; docs title “Latest stable release: v0.61.0”.
Developer Getting Started
npm install -g @google/gemini-cli for stable; use @preview/nightly for experiments. Re-test sandbox write scope and versioned Flash routing after upgrade. Sources: changelog and GitHub release.
Discussion & Comments
0Sign in to join the discussion
Connect with AI developers to exchange benchmark insights.