Bitter Frontier What coding agents just made possible, where the bottleneck moved, and what deserves attention.

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 signals and issues that cite it, below.

2026-09-21-gemini-cli-v0-57-0-promotes-every-preview-only-item-from-the-previous-brief

v0.57.0 (2026-08-25) contains all four items the previous brief left preview-only: retry and TTL work (fa2f27aee), git subprocess environment neutralization (getSafeGitEnv, c0d192452), the agent registry checking isAgentsEnabled before loading built-ins (753e4cb55), and the Cloud Workstations OAuth redirect (58ba19945). Each is an ancestor of v0.57.0 by compare (behind_by 0). Four stables cut in the window: v0.57.0 (08-25), v0.58.0 (09-01), v0.59.0 (09-08), v0.60.0 (09-15). npm latest at close is 0.60.0.

Channel: tagged-release (v0.57.0, 2026-08-25, and every later stable). Half: both.

Operator consequence: experimental.enableAgents false now suppresses built-in subagents on stable. Stable Gemini CLI is a weekly promotion of the previous week’s preview; plan upgrades on that cadence.

Receipt

Finding metadata

Confidence
high

Run: 2026-09-21-weekly-digest-2026-08-20_2026-09-21-frontier-v0

Finding ID: 2026-09-21-gemini-cli-v0-57-0-promotes-every-preview-only-item-from-the-previous-brief

Accepted signals

Profile citations

Source links

Primary links, including exact changelog lines when available.

  1. Gemini CLI
    github release2026-09-21-gemini-cli-v0-57-0-promotes-every-preview-only-item-from-the-previous-briefgoogle-gemini/gemini-cli / v0.57.0tagged commit file2026-09-21-gemini-cli-v0-57-0-promotes-every-preview-only-item-from-the-previous-briefgoogle-gemini/gemini-cli / packages/core/src/agents/registry.ts

Versioned source: run artifact