What happened?
[ACTION REQUIRED] 📎 PLEASE ATTACH THE EXPORTED CHAT HISTORY JSON FILE TO THIS ISSUE IF YOU FEEL COMFORTABLE SHARING IT.
bug-report-history-1775073884165.json
What did you expect to happen?
Since today, gemini cli cannot run any shell commands. Running them with e.g. !git status also results in "File not found: │
│ (Command produced no output)"
But if I exit gemini, I can run it fine in the same pwsh session, so my path is fine.
Client information
- CLI Version: 0.35.3
- Git Commit: 52d1034
- Session ID: d6e0c0da-7a63-4600-b3f3-4543b88b2c17
- Operating System: win32 v25.2.1
- Sandbox Environment: no sandbox
- Model Version: auto-gemini-3
- Auth Type: oauth-personal
- Memory Usage: 392.1 MB
- Terminal Name: Unknown
- Terminal Background: #282c34
- Kitty Keyboard Protocol: Unsupported
Login information
Google Account
Anything else we need to know?
I changed nothing on my system, gemini updated itself and then broke.
What happened?
[ACTION REQUIRED] 📎 PLEASE ATTACH THE EXPORTED CHAT HISTORY JSON FILE TO THIS ISSUE IF YOU FEEL COMFORTABLE SHARING IT.
bug-report-history-1775073884165.json
What did you expect to happen?
Since today, gemini cli cannot run any shell commands. Running them with e.g. !git status also results in "File not found: │
│ (Command produced no output)"
But if I exit gemini, I can run it fine in the same pwsh session, so my path is fine.
Client information
Login information
Google Account
Anything else we need to know?
I changed nothing on my system, gemini updated itself and then broke.