Gemini CLI v0.65.0 keeps resumed sessions intact
2 days ago
Gemini CLI 0.65.0 is a release of fixes, and the ones most people will feel are about resuming sessions. Exiting quickly after a resume could delete the session's history, and pressing Control C rapidly could poison the session. Both are fixed. So are a hang on Enter, sign-in retry loops and slow ignore filtering.
Ask about this presentation
Chapters
Show transcriptHide transcript
Gemini CLI 0.65.0 is a release of fixes, and the ones most people will feel are about resuming sessions. Exiting quickly after a resume could delete the session's history, and pressing Control C rapidly could poison the session. Both are fixed. So are a hang on Enter, sign-in retry loops and slow ignore filtering.
Slide text
Gemini CLI v0.65.0
Gemini CLI v0.65.0 keeps resumed sessions intact
Plus fixes for a hang on Enter, sign-in retry loops and slow ignore filtering
Resume a session and exit quickly, and the CLI could delete that session's history. Now the history is kept. Interrupting with Control C in rapid succession could poison the session. That's fixed too. And a resumed session no longer repeats tool responses.
Pressing Enter in interactive mode could hang the CLI. That's fixed. Verification and OAuth retries no longer loop forever. Choosing Google login again now clears the cached credentials. And the OAuth callback's issuer check now lines up with RFC ninety-two oh seven.
Two changes help in bigger projects. Ignore filtering is faster, and it can now skip an ignored directory whole instead of walking through it. And an @folder reference no longer reads every file inside that folder up front.
One fix tightens workspace trust. When you work in a folder you haven't trusted, its workspace settings are now read-only. And the untrusted-command check got quieter: it no longer misfires on command flags and compound loops.
The one new feature is for teams that export telemetry. The telemetry configuration now accepts custom OTLP headers, so the CLI can send your collector the headers it expects.
Expanding output with Control O could clear the terminal and reset your scroll position. Now it doesn't. And when one extension failed the allowlist check, the others stopped loading. Now they keep loading. Reverse search, terminal resizing and the VS Code companion got fixes too.
The release notes flag no breaking changes, but two behaviors are different. An @folder reference no longer reads every file inside it up front, and workspace settings are read-only in untrusted folders. To upgrade, install version 0.65.0 from npm. If a workflow relies on @folder reading a whole directory up front, test it first. Version 0.65.0 keeps resumed sessions intact.
