Gemini CLI v0.63.0
Gemini CLI v0.63.0 caps memory in long agent runs
Each tool result is stored at 64 KB at most.
Gemini CLI v0.63.0 caps memory in long agent runs. Tool output used to go into session history in full. Now each stored result stops at 64 kilobytes, with a note on how much was cut.
01: Long agent runs
Long agent runs.
Chat compression starts at 512 KB of history
Chat compression used to wait until history filled a share of the model's context window. It now also kicks in once history passes 512 kilobytes or about 50,000 tokens, whichever comes first.
Older tool turns shrink to 2 KB summaries
Finished tool turns from earlier in a session now collapse to 2 kilobyte summaries, while the turn in progress keeps everything. Exited shell processes also release their output buffers.
02: Sign-in and retries
Sign-in and retries.
The endless sign-in loop on Windows, WSL and headless machines is fixed
On Windows, WSL and headless machines, Gemini CLI could ask you to sign in over and over. Credentials and settings are now written atomically, so the Gemini Code Assist extension for VS Code can't collide mid-write.
WSL and display-less Linux store tokens in an encrypted file
On WSL, or a Linux machine without a display, the system keyring can deadlock. Gemini CLI now detects that setup and keeps your tokens in an encrypted file in your Gemini folder.
The spinner shows retries during rate limits and outages
On a rate limit or an overloaded server, the spinner stayed on Thinking. With full error verbosity it now names the model and the attempt, like two of five. Low verbosity shows a shorter hint.
03: Headless runs
Headless runs.
Plan Mode carries out its plan in headless runs
In a headless run, Plan Mode used to stop and wait for your agreement, made zero tool calls, and ended. Now it picks a strategy, drafts the plan and carries it out.
Headless runs deny what they would have asked you about
In a headless run, a policy rule that would ask you now denies. MCP resources and web search results get the same untrusted wrapping as web fetch, and redirection rules match in every approval mode.
04: Tools and config
Tools and config.
git diff runs inside the sandbox again
Inside the execution sandbox, git diff failed with a cannot run error. An empty diff.external setting made git try to launch a program with no name. That override is gone, and diffs work again.
Disabled MCP servers stay off when their config file is broken
If the file listing your disabled MCP servers had a JSON error, those servers came back on. Now they stay disabled, Gemini CLI tells you the file is malformed, and it won't overwrite your entries.
Keys typed during startup reach the prompt
Keys you typed while Gemini CLI was starting could vanish while it probed your terminal. Standard input now pauses after that check and resumes as soon as the prompt starts listening.
The shell and tool output get three smaller fixes
Background shell commands now delete their temp folders on exit. A truncation limit of zero or less turns truncation off instead of inflating output. And extension update checks can't stop to ask for git credentials.
05: Editor sessions
Editor sessions.
Editors on ACP can reload a session started the same minute
Editors that drive Gemini CLI over ACP could fail to reload a session from the same minute. Session files now get unique names, and the session is located before setup runs.
Every fix, with its pull request, is in the v0.63.0 release notes
The Gemini CLI v0.63.0 release notes on GitHub list every fix with a link to its pull request.
