Skip to content
AIBRAINWORX / OpenSourceCoder.comLOCAL-FIRST. BUILT IN THE OPEN.
Open Source / Developer & Agent Tools

Gemini CLI 0.70 keeps approval prompts for unresolved Bash expansion

The November 19 release changes a default approval fallback and moves policy pattern matching to RE2. Explicit rules, shell differences and model-access terms remain important boundaries.

Listen to this articleBrowser Voice
Ready
Original explainer showing the Bash known-safe fallback retaining ASK_USER when arguments may expand, with explicit policies treated separately.
OpenSourceCoder.com original explainer based on Gemini CLI v0.70.0 source and linked changes. Not a terminal run, penetration test or certification of an agent sandbox. · Official publisher logo used for editorial identification; sources recorded in the artwork credits. No endorsement implied.
Event / context: 2026-11-19 UTC release. Source check: Nov 20, 2026.

Google's Gemini CLI 0.70.0 release, published November 19, changes how the client evaluates shell approval and custom policy patterns. It also includes session, worktree and interface repairs. The policy changes deserve attention because they affect the interpretation of a request before execution.

When the written command is not the final argument list

The Bash expansion change prevents a known-safe heuristic from upgrading a default ASK_USER decision when unresolved expansion may change the arguments. The tagged implementation checks for constructs such as unquoted globs, substitutions and variable expansion.

Its scope is important: this does not replace explicit allow rules or make the same helper operate on PowerShell. The change targets a fallback that would otherwise treat a command as known safe. We inspected that path in the versioned source; we did not run commands through the client or test an escape.

Our analysis: approval needs to describe the operation that will run

A familiar command name is not a complete account of an operation. The surrounding shell can change what its arguments refer to. An interface that evaluates only the text before those transformations can give a user an incomplete picture of the intended action.

That is why narrow changes to approval logic can matter even when the command itself looks ordinary. A meaningful assessment should separate the default heuristic from explicit operator policy, identify the shell involved and examine what happens when parsing cannot establish a confident result.

Policy patterns now have a different compatibility boundary

The policy-pattern update introduces a re2js-backed wrapper. RE2 syntax omits constructs including lookaround and backreferences; an invalid pattern produces a compilation error and its rule is skipped.

That makes custom policy compatibility an operational question, not merely a performance detail. A pattern that no longer loads cannot be assumed to enforce its former restriction. Administrators need to inspect the resulting policy and errors instead of treating an unchanged configuration file as proof of unchanged behavior.

The source license does not grant model access

The tagged README positions this client around enterprise Code Assist workflows and directs free and Google AI plan users to a different tool. It also warns against using this harness to benchmark Gemini 4 and later models.

Our repository profile records the Apache-2.0 client license. Service eligibility and model terms remain separate. We did not install the release, change approval settings or compare model scores; this is a source review of the release's documented behavior.

EXPLORE THE SOURCE

GitHub repositories

Primary-source reporting with original editorial analysis. No software installation, paid API call, local inference, deployment or independent performance/security test performed.

Follow your curiosity.

Pass the signal.