Vibe Coding
Gemini CLI now demands confirmation before running a build command after a build file changed
Two security fixes landed in the 2026-09-12 nightly (PRs #29250 and #29214). The first tracks tokens extracted from `<untrusted_context>` blocks in conversation history, requires explicit confirmation to modify `package.json`, `Makefile`, `pyproject.toml` or `BUILD.bazel`, and before running `npm run`, `make`, `cargo` or `blaze` checks for both a modified build file and untrusted flags, downgrading to `ASK_USER` and suppressing persistent approvals. The second hardens sandbox filesystem boundaries and isolates runtime state.
Source
↳ Follow the thread