Enable terminal/shell command execution in Gemini (VS Code) — yarn/git commands failing

[Feeh03114]

Hi everyone,
I’m using Gemini inside VS Code and it currently fails whenever it tries to run shell/terminal commands (examples: yarn, git, etc.). It looks like shell execution is blocked/disabled, or not properly configured.

What I’m trying to do

Enable Gemini to execute terminal commands from within VS Code (or at least let it trigger them reliably), so it can run things like:

• yarn install
• yarn lint
• yarn tsc --noEmit
• git status, git diff, etc.

Current behavior

• Any command execution attempt results in an error.
• (If relevant) It happens even for basic commands like git status.

Questions

1. Is there an official way to enable/allow shell execution for Gemini in VS Code?
2. Is this controlled by a setting, permission, policy, or workspace trust in VS Code?
3. Are there known limitations (e.g., Gemini can’t execute shell commands at all), and what’s the recommended workflow instead?

Environment

• OS: macOS 26.1 (25B78)
• VS Code: 1.107.1 (Universal)
• Confirmar: 994fd12f8d3a5aa16f17d42c041e5809167e845a
• Data: 2025-12-17T14:15:14.850Z
• Electron: 39.2.3
• ElectronBuildId: 12895514
• Chromium: 142.0.7444.175
• Node.js: 22.21.1
• V8: 14.2.231.21-electron.0
• SO: Darwin x64 25.2.0
• Gemini extension/plugin: 2.64.0
• Node/Yarn: v22.14.0

Error message / logs

Command "npx eslint --cache ." is not in the list of allowed tools for non-interactive mode.

If this is “by design”, fair enough — but then what’s the best workaround? Because right now Gemini is basically on a “no terminal, no party” diet 😅