gemini-cli
npx @buildinternet/releases get gemini-cliConPTY process exit lifecycle is now synchronized and PTY output finalization hardened, with improved terminal buffer memory management and formatted Windows diagnostic paths. Also suppresses uncaught AbortError logs during request cancellation, preserves terminal focus when closing diff tabs in the VS Code companion, and fixes an auth error documentation link.
OAuth refresh tokens are now retained on refresh and credential deletion is idempotent. PTY file descriptor cleanup and execution lifecycle management improved, guard added against negative layout dimensions in border rendering, and flaky run_shell_command and file-system-interactive integration tests deflaked.
MCP tool call titles are now formatted as structured signatures with explanations segregated, and the A2A server's tasks metadata endpoint returns early for unsupported stores. AgentLoopContext properties are preserved across object spreads, plus changelog and version bump chores.
MCP OAuth now enforces RFC 9207 issuer identification, a hardcoded Google CrUX API key in chrome-devtools-mcp is removed, and the macOS Seatbelt sandbox isolates its temporary directory and settings. Also adds consent prompts on extension environment changes and boundary checks on workspace paths and system config.
Prevents indirect prompt injection via build file modifications and untrusted flags, and hardens sandbox filesystem boundaries and runtime state isolation. Also preserves explicit versioned Flash model IDs and AgentLoopContext properties across object spread.
Fixed an indirect prompt injection vector that could be triggered through build file modifications and untrusted flags, and hardened sandbox filesystem boundaries to isolate runtime state.
Fixed an issue where string values "true"/"false" in snapshots were incorrectly cast to booleans, causing data corruption. Also improved stdin bushing for small payloads and added labels so you can filter issues by component or priority.
Mitigated NTFS 8.3 short-name path issues, isolated the settings directory in sandbox containers, and enforced envelope metadata provenance for untrusted tool outputs. Explicit versioned Flash model IDs are also preserved.
Prevented server-side request forgery in MCP OAuth metadata discovery and authentication, and enforced fail-closed workspace trust with mcpServers filtered in restricted mode. Both are security fixes for MCP integrations.
This release enforces stricter security across the CLI: RFC 9207 issuer identification in the MCP OAuth flow, robust workspace path boundary checks with symlink resolution, strict permission checks on system-wide config paths, NTFS 8.3 short name mitigation, and isolation of temporary and settings directories in sandbox containers. It also sanitizes and removes a hardcoded Google CrUX API key in chrome-devtools-mcp and prompts for consent on environment changes.