You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running Gemini CLI in PowerShell, I encounter severe input lag whenever I use the @ symbol to specify a file, with each character typed making the lag worse, as if it’s scanning the entire filesystem. This is most likely caused by PowerShell’s IntelliSense path completion trying to index everything after detecting @. A workaround is to temporarily disable path completion in the current session (Set-PSReadLineOption -CompletionQueryItems 0), run Gemini CLI from Command Prompt or WSL/Git Bash instead, or manually type the file path instead of using @ for autocomplete.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
When running Gemini CLI in PowerShell, I encounter severe input lag whenever I use the @ symbol to specify a file, with each character typed making the lag worse, as if it’s scanning the entire filesystem. This is most likely caused by PowerShell’s IntelliSense path completion trying to index everything after detecting @. A workaround is to temporarily disable path completion in the current session (Set-PSReadLineOption -CompletionQueryItems 0), run Gemini CLI from Command Prompt or WSL/Git Bash instead, or manually type the file path instead of using @ for autocomplete.
Beta Was this translation helpful? Give feedback.
All reactions