Skip to content
Proposals/Upgrade Gemini CLI to v0.55.1 for tool registry
proposalteamP5Worth a lookGCGemini CLI

Upgrade Gemini CLI to v0.55.1 for tool registry discovery and path security hardening

Move teams to Gemini CLI v0.55.1 to pick up tool registry discovery, case-insensitive sensitive-path blocklists, symlink escape fixes, read-only ~/.gitconfig in the macOS sandbox, and scrubbed-history thought-leakage fixes.

Why this loop

v0.55.1 ships concrete security and workflow changes that affect day-to-day CLI use: tool registry discovery, case-insensitive sensitive path blocklisting with VS Code HITL, defensive @-reference path resolution, symlink directory-escape protection in the memory import processor, read-only ~/.gitconfig in the macOS sandbox, exclusion of transient CI config from workspace context, preserved escape sequences in string literals, and stripping of thoughts from scrubbed history turns. Adopting the release reduces path-traversal and secret-leak risk and unlocks the new registry discovery path without waiting for a later minor.

Proposed actions

  1. npm install -g @google/gemini-cli@0.55.1 && gemini --version
  2. In your next Gemini CLI session, exercise tool registry discovery against your project’s configured tools/MCP servers and confirm newly discovered tools appear before relying on them in automation
  3. On macOS, restart Gemini CLI sandbox sessions so ~/.gitconfig is mounted read-only, then verify agents cannot rewrite global git identity or hooks via that file
  4. Re-test workflows that use @-file references and memory import on paths involving symlinks or mixed-case sensitive directories (e.g. .Env, .AWS) to confirm the new blocklist and defensive resolution hold
  5. After upgrade, start a fresh chat and confirm model ‘thoughts’ no longer persist in scrubbed/exported history turns used for logs or handoff

Agent prompt

Paste into your agent or query via MCP (`get_agent_prompt`) — free, no extra AI cost

Google Antigravity / agent task

# DevAgentRadar → Google Antigravity

Goal: turn this release signal into a safe pilot plan for my stack.

## Context
Assistant: Gemini CLI
Proposal: Upgrade Gemini CLI to v0.55.1 for tool registry discovery and path security hardening
Summary: Move teams to Gemini CLI v0.55.1 to pick up tool registry discovery, case-insensitive sensitive-path blocklists, symlink escape fixes, read-only ~/.gitconfig in the macOS sandbox, and scrubbed-history thought-leakage fixes.
Primary source: https://github.com/google-gemini/gemini-cli/releases/tag/v0.55.1

## Why it matters
v0.55.1 ships concrete security and workflow changes that affect day-to-day CLI use: tool registry discovery, case-insensitive sensitive path blocklisting with VS Code HITL, defensive @-reference path resolution, symlink directory-escape protection in the memory import processor, read-only ~/.gitconfig in the macOS sandbox, exclusion of transient CI config from workspace context, preserved escape sequences in string literals, and stripping of thoughts from scrubbed history turns. Adopting the release reduces path-traversal and secret-leak risk and unlocks the new registry discovery path without waiting for a later minor.

## Suggested actions
1. npm install -g @google/gemini-cli@0.55.1 && gemini --version
2. In your next Gemini CLI session, exercise tool registry discovery against your project’s configured tools/MCP servers and confirm newly discovered tools appear before relying on them in automation
3. On macOS, restart Gemini CLI sandbox sessions so ~/.gitconfig is mounted read-only, then verify agents cannot rewrite global git identity or hooks via that file
4. Re-test workflows that use @-file references and memory import on paths involving symlinks or mixed-case sensitive directories (e.g. .Env, .AWS) to confirm the new blocklist and defensive resolution hold
5. After upgrade, start a fresh chat and confirm model ‘thoughts’ no longer persist in scrubbed/exported history turns used for logs or handoff

## Config surfaces this release may change
- sandbox settings — check your repo before applying
- MCP servers — check your repo before applying


Please:
1. Map the change to concrete pilot steps
2. Flag security / permission implications
3. Keep the pilot reversible
agentmcpmodelsecurityideRelease source ↗

Your loop

This browser · no sign-in · not shared as “you”

Your decision stays on this device. A public tally appears after a few votes.

Originating release signal

GCGemini CLIv0.55.1Aug 11, 2026

v0.55.1 Release v0.55.1

fix/verify release npm ci ignore scripts · fix(ci): prevent workspace binary shadowing in release verification · Feat/tool registry discovery · fix(ci): prevent bad NPM releases and promote job crashes · Changelog for v0.50.0-preview.1 · Fix no_proxy test · chore(release): bump version to 0.51.0-nightly.20260625.g3fbf93e26 · Vertex base url update · fix(security): enforce case-insensitive sensitive path blocklist and vscode hitl · fix(core-tools): resolve defensive path resolution for at-reference files and fix macOS tests · feat(caretaker): implement Cloud Run webhook ingestion service · +73 more changes

Verified excerpt — the source's own words
## What's Changed
* fix/verify release npm ci ignore scripts by @rmedranollamas in https://github.com/google-gemini/gemini-cli/pull/28116
* fix(ci): prevent workspace binary shadowing in release verification by @galdawave in https://github.com/google-gemini/gemini-cli/pull/28132
* Feat/tool registry discovery by @ved015 in https://github.com/google-gemini/gemini-cli/pull/28113
* fix(ci): prevent bad NPM releases and promote job crashes by @galdawave in https://github.com/google-gemini/gemini-cli/pull/28147
* Changelog for v0.50.0-preview.1 by @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/28150
* Fix no_proxy test by @jerrylin3321 in https://github.com/google-gemini/gemini-cli/pull/28131
* chore(release): bump version to 0.51.0-nightly.20260625.g3fbf93e26 by @gemini-cli-robot in https://github.com/google-gemini/gemini-cli/pull/28151
* Vertex base url update by @DavidAPierce in https://github.com/google-gemini/gemini-cli/pull/28145
* fix(security): enforce case-insensitive sensitive path blocklist and vscode hitl by @luisfelipe-alt in https://github.com/google-gemini/gemini-cli/pull/27966

Excerpt ends here — this release continues at the source ↗.

Primary source ↗