gemini cli hangs indefinitely if .env is a named pipe (i.e. when using 1Password Environments) #19050
Description
What happened?
If you run gemini in a folder containing a .env populated by 1password Environments, the command will hang your terminal and never launch. More generically, 1password's environments work by replacing a .env file with a pipe named ".env" which, when read, will trigger 1password to pipe in the .env set up in the 1password application.
1Password is not necessary for this bug to replicate though. If you have a .env that's a named pipe, it will hang gemini, regardless of why it's there.
What did you expect to happen?
It should attempt to read the .env as per usual.
(this prompts 1password to get the user's consent to pipe in the .env, but that's somewhat tangental to the issue at hand)
Client information
- ** LI Version:** 0.28.2
- Git Commit: a212e5c
- Session ID: 92e34650-5f7-4613-a749-a3de15338881
- Operating System: linux v20.20.0
- Sandbox Envi onment: sandbox-0.28.2-0
- Model Version: auto-gemini-2.5
- *Auth Type: oauth-personal
- Memory Usage: 337.8 MB
- Terminal Name: Unknown
- Terminal Background: #1e1e1e
- Kitty Keyboard Protocol: Unsupported
- IDE Client: IDE
Login information
No response
Anything else we need to know?
No response