Input blocked when .env file exists in working directory (fish shell)
Input blocked when .env file exists in working directory
Environment
- Claude Code version: 2.0.55
- OS: Linux 6.14.0-116036-tuxedo
- Terminal emulators tested: xterm, wezterm, alacritty, TTY (text-only interface)
- Login Shell: fish (_not a problem with zsh as login shell_)
Description
When starting Claude Code in a directory containing a .env file, the input prompt becomes completely unresponsive. No text can be typed into the input field regardless of terminal emulator used.
Steps to Reproduce
- Create an empty
.envfile in any directory:
``bash``
mkdir test && cd test
touch .env
- Start Claude Code:
``bash``
claude
- Attempt to type anything in the input prompt
Expected Behavior
Claude Code should start normally and accept input.
Actual Behavior
The input prompt appears but entered text appears below the input box. Pressing enter moves the text into the input box, but there is now way to send a prompt.
Workaround
Move or rename the .env file before starting Claude Code:
mv .env .env.bak
claude
Or: Change the login shell to zsh (or probably to any other shell), then you can also enter a fish shell, it does not matter. Only when the login shell (changed with chsh) is set to fish, this is a problem
Troubleshooting Attempted
- Reinstalled Claude Code (native package)
- Reinstalled Claude Code via NPM
- Removed all configuration in
~/.claude - Removed Claude JSON config file in
$HOME - Tested multiple terminal emulators (xterm, wezterm, alacritty)
- Tested in TTY (text-only, no graphical environment)
- Toggled vim mode on/off
- Added content to
.envfile (placeholder comment) - Set
DOTENV_CONFIG_PATH=/dev/nullbefore launching - Finally, change the login shell to
zshand there you go.
None of the above resolved the issue.
Additional Notes
- Issue occurs with any
.envfile content (empty file, file with comments, file with valid variables) - Issue is not related to vim mode setting
- Issue occurs in all tested terminal emulators including bare TTY
This issue has 8 comments on GitHub. Read the full discussion on GitHub ↗