Gemini CLI v0.62.0: Gemini 3.8 Flash, 3.5 Flash Lite, OAuth and PTY fixes#

Published by

Part of the Gemini CLI Version Tracker series. | Gemini CLI on GitHub | Releases

Gemini CLI v0.62.0 follows v0.61.0. It adds the Gemini 3.8 Flash and 3.5 Flash Lite models, retains the stored OAuth refresh token when a refresh response comes back partial so you stay signed in, hardens shell execution and Windows ConPTY lifecycle handling, and stops the terminal-border renderer from breaking on negative or non-finite dimensions.[1]

New models#

v0.62.0 adds the Gemini 3.8 Flash and 3.5 Flash Lite models to the CLI, registering gemini-3.8-flash and gemini-3.5-flash-lite as selectable model targets in the default model configuration.[7]

Staying signed in#

The auth fix is the one most users will feel. When a token refresh returned a response that omitted fields, the stored credential could be overwritten with the gaps, which meant the stored credential could lose its refresh token and the next session would ask you to log in again. v0.62.0 falls back to the existing stored credential when the refresh response omits fields, and makes credential deletion idempotent so a repeated delete no longer errors.[2] The practical result is fewer surprise re-authentication prompts across long-running sessions.

Reliability fixes#

The rest of the release is cross-platform reliability work, weighted toward Windows shell handling and the terminal UI.

AreaWhat changed
Shell / PTYPTY file-descriptor cleanup and execution-lifecycle management improved; on Windows, ConPTY process-exit lifecycle is synchronized and PTY output finalization is hardened.[3]
Terminal buffersTerminal buffer memory management improved and Windows diagnostic paths are formatted correctly in output.[3]
Border renderingBorder widths are guarded against negative, NaN, fractional, and non-finite values, returning an empty string instead of throwing on a bad layout dimension.[4]
ACP / MCPIn ACP mode the tool_call update is emitted before request_permission, and MCP tool-call titles render as structured signatures with their explanations separated out.[5]
VS Code companionTerminal focus is preserved when a diff tab is closed.[6]
Proxyproxy-agent interop is normalized so environment proxy settings resolve through the bundled build.[6]

The border-rendering change adds a small guard that repeats a border character only for a finite, non-negative count and otherwise returns nothing, so a terminal that reports a negative or zero width during a resize renders an empty border rather than crashing the layout.[4] The ACP and MCP tweaks target editor integrations driving the CLI over the Agent Client Protocol: emitting the tool call before the permission request gives the host a chance to show what is about to run, and the structured tool-call titles make MCP calls readable in that surface.

What this tells us#

v0.62.0 adds the Gemini 3.8 Flash and 3.5 Flash Lite models and fixes several reliability issues: auth dropped on a partial refresh, PTY file descriptors leaked during shell execution, the TUI could miscompute a border width, and the editor integration stole terminal focus. The Windows-specific ConPTY and diagnostic-path work stands out, since terminal handling on Windows is where a cross-platform agent tends to accumulate the most rough edges.

For Gemini CLI specifically, the continued investment in ACP and the VS Code companion is the throughline worth watching, because that is the path by which the CLI becomes the engine behind an editor rather than only a standalone terminal tool. v0.62.0 adds Gemini 3.8 Flash and 3.5 Flash Lite and steadies daily use on Windows and through an editor.

Sources#

This analysis is based on publicly available open-source code and release metadata, conducted for educational and research purposes. All trademarks and software referenced belong to their respective owners.

Previous Gemini CLI analysis: v0.61.0 (September 26, 2026)

All 4 Gemini CLI analyses: Gemini CLI Version Tracker · Official Gemini CLI changelog