Upgraded Deprecation Warning for `unsandboxed` Permissions Lists File Paths, Five Offending Rules, and `command` Migration Steps
Managing project security protections is now guided by clearer instructions. Startup warnings for deprecated legacy rules now pinpoint exactly where the issues lie.
In the past, leaving legacy unsandboxed permission rules in CLI global, shared, or individual project configuration files often resulted in confusing startup warnings. Now, the startup warning has been thoroughly improved to list the full path of each affected configuration file, explicitly display up to five offending rules, and provide step-by-step migration instructions to guide you through rewriting them into new command rules, making maintenance crystal clear.
PERF
`/resume` Startup Responsiveness Accelerated, Fast Loading for Long Conversations with Cold Caches and Stale Summaries
Resuming large, extended tasks from previous discussions is now significantly more responsive.
Previously, when running the /resume command in the terminal to open an exceptionally large conversation history, noticeable delays would occur whenever the summary cache (a mechanism that temporarily stores conversation content in advance to speed up reading) was cold or stale. This startup responsiveness has now been improved, allowing the system to quickly complete loading and resume conversations even with unready or expired caches over long conversation histories.
BUGFIX
Plugin-Bundled MCP Servers Automatically Namespaced to Prevent Name Collisions
When extending the terminal with various external tools, name collisions among plugin-bundled servers are now completely resolved. When using MCP (Model Context Protocol, a protocol for connecting AI to external tools), bundled servers across different plugins that happened to share the same name previously collided with each other or overwrote custom servers in your mcp_config.json. Such naming clashes would prevent one of the servers from working properly. The system now automatically namespaces plugin-bundled servers, registering them independently in the <plugin>_<server> format to eliminate overlapping naming conflicts.
When frequently opening conversation histories or switching between tasks, the terminal no longer silently accumulates excessive system memory.
Previously, whenever conversation histories were opened or scanned from the command line, background goroutines responsible for evicting step cache (an internal mechanism for temporarily caching execution step records) often lingered and ran throughout the rest of the session, causing unnecessary memory leaks. This memory leak has now been fixed, significantly reducing system memory usage after running /resume or switching between conversations, keeping long-running sessions nimble and responsive.
BUGFIX
`view_file` Rejects Non-UTF-8 Binary Files and 100 MB Oversized Files to Prevent Context Overflow
When handing files over for AI reading, the tool now actively intercepts unexpected inputs that would overflow the context window. Previously, when using view_file to inspect files, non-UTF-8 encoded binary files were often forcibly parsed as plain text, and files larger than 100 MB were directly loaded into the model's context window (the upper limit of text capacity that the model can ingest and hold in a single turn). Such overloading frequently led to conversation aborts or errors. This defect is now fixed; unsupported binary formats and oversized files are directly rejected with a clear error before loading, preventing context window overflows.
BUGFIX
Gemini API Sessions Retain Thinking Blocks from Prior Turns and Correctly Propagate Thought Signatures
When engaging in multi-turn in-depth conversations with models via API keys, the thinking context from prior turns is now cleanly preserved.
Previously, when launching Gemini API sessions via GEMINI_API_KEY, sending subsequent user messages often caused the system to drop model thinking blocks from previous conversation turns. Additionally, thought signatures (digital markers used to verify the integrity and identity of reasoning processes) on text and thought parts failed to propagate properly. Both defects have now been fixed, allowing model thinking records and signatures to be smoothly retained and correctly propagated across multiple conversation turns.
BUGFIX
Artifact Review Fixes Parent Path Matching; Conversation Forks and Snapshots Exclude Internal System Directories
When reviewing code artifacts or branching conversations, internal project directory management is now much cleaner. Previously, if a parent directory path above .gemini/ contained skipped path names such as scratch, artifact review (an inspection panel for reviewing generated code outputs) often failed to trigger. In addition, when executing conversation forks or snapshot reverts, internal .system_generated/subagents and .system_generated/worktrees directories were unnecessarily copied, and deleting conversations failed to clean up subagent metadata. These management issues have now been resolved: forks and reverts no longer include internal directories, and deleting a conversation cleanly purges subagent records.
BUGFIX
Fixes Deleted Conversations Recreated as Empty `SQLite` Databases on Background Reconnection
When manually clearing unwanted conversation histories, deleted history files will never resurface.
Previously, after a user deleted conversation histories, any background queries attempting to reconnect would recreate empty, schema-less SQLite database files underneath. These ghost files added clutter and could not be read properly. This ghost recreation bug has now been completely resolved; background queries reconnecting after deletion no longer generate empty databases, keeping conversation deletions truly clean.
BUGFIX
Workspaceless Conversations Maintain Strict Isolation, No Longer Inheriting Custom Paths from Other Sessions
When launching the terminal outside of any project directory, standalone conversation environments now maintain proper isolation boundaries. Previously, when starting a new conversation without a workspace folder, the session often inadvertently inherited project paths and customizations from other open sessions running concurrently. This cross-session leak caused ad-hoc conversations to mistakenly read irrelevant project rules or file directories. This isolation defect has now been fixed: conversations launched without a workspace folder remain purely standalone, no longer inheriting environment paths and custom settings from other sessions.
Original changelog
Original changelogUpgraded Deprecation Warning for `unsandboxed` Permissions Lists File Paths, Five Offending Rules, and `command` Migration Steps
Improved the startup warning for deprecated `unsandboxed` permission rules across CLI, shared, and project configuration files to list each affected file path, up to five offending rules, and step-by-step instructions for migrating them to `command` rules.
Original changelog`/resume` Startup Responsiveness Accelerated, Fast Loading for Long Conversations with Cold Caches and Stale Summaries
Improved `/resume` startup responsiveness when opening a large conversation history with a cold or stale summary cache.
Original changelogPlugin-Bundled MCP Servers Automatically Namespaced to Prevent Name Collisions
Fixed MCP servers bundled inside plugins colliding with each other or with user-configured servers in `mcp_config.json` when they shared the same server name by automatically namespacing plugin MCP servers as `<plugin>_<server>`.
Original changelogOpening or Switching Conversations Fixes Background Goroutine Leak, Significantly Reducing Memory Usage
Fixed a memory leak where opening or scanning conversations left background step-cache eviction goroutines running for the rest of the session, significantly reducing memory usage after opening `/resume` or switching conversations.
Original changelog`view_file` Rejects Non-UTF-8 Binary Files and 100 MB Oversized Files to Prevent Context Overflow
Fixed `view_file` attempting to parse non-UTF-8 binary files as text or loading files larger than 100 MB into the model context; unsupported binary formats and oversized files are now rejected with a clear error before overflowing the context window.
Original changelogGemini API Sessions Retain Thinking Blocks from Prior Turns and Correctly Propagate Thought Signatures
Fixed Gemini API (`GEMINI_API_KEY`) sessions dropping model thinking blocks from prior turns on subsequent user messages and failing to propagate thought signatures on text and thought parts.
Original changelogArtifact Review Fixes Parent Path Matching; Conversation Forks and Snapshots Exclude Internal System Directories
Fixed artifact review failing to trigger when a directory name above `.gemini/` matched a skipped path component such as `scratch`, prevented conversation forks and snapshot reverts from copying internal `.system_generated/subagents` and `.system_generated/worktrees` directories, and cleaned up subagent metadata records when deleting a conversation.
Original changelogFixes Deleted Conversations Recreated as Empty `SQLite` Databases on Background Reconnection
Fixed deleted conversations being recreated as empty, schema-less SQLite database files when background queries reconnected after deletion.
Original changelogWorkspaceless Conversations Maintain Strict Isolation, No Longer Inheriting Custom Paths from Other Sessions
Fixed conversations launched without a workspace folder inheriting workspace paths and customizations from other open sessions.