Google’s Gemini CLI now asks before editing your build files
The New Stack Amanda Caswell
Google’s Gemini CLI 0.61.0 now requires explicit confirmation before an agent edits build configuration files, runs build or test commands after those edits, or executes shell commands with arguments that match untrusted external content. The release was made on Wednesday and the related changes merged on September 11. This adds human-in-the-loop approval prompts and strengthens the sandbox so host credentials and settings are not exposed to the code running inside it.
Why it matters
The appeal of an autonomous coding agent is that you hand it a task, give it access to your repository The post Google’s Gemini CLI now asks before editing your build files appeared first on The New Stack.
Related stories
You too Google! Google Confirms Gemini Breached 3 Companies in AI Security Tests
MarkTechPost · 4 days ago ·
43
Google’s Gemini is the latest AI model to hack other companies
TechCrunch · 5 days ago ·
33