claude-code icon indicating copy to clipboard operation
claude-code copied to clipboard

Input blocked when .env file exists in working directory (fish shell)

Open Dronakurl opened this issue 2 months ago • 3 comments

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

  1. Create an empty .env file in any directory:
    mkdir test && cd test
    touch .env
    
  2. Start Claude Code:
    claude
    
  3. 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 .env file (placeholder comment)
  • Set DOTENV_CONFIG_PATH=/dev/null before launching
  • Finally, change the login shell to zsh and there you go.

None of the above resolved the issue.

Additional Notes

  • Issue occurs with any .env file 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

Dronakurl avatar Nov 30 '25 22:11 Dronakurl

Found 1 possible duplicate issue:

  1. https://github.com/anthropics/claude-code/issues/4391

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

github-actions[bot] avatar Nov 30 '25 22:11 github-actions[bot]

No, this is something different. Even when the .env file is completely empty, I get this behaviour.

Found 1 possible duplicate issue:

1. [[BUG] APP_NAME in .env file breaks Claude Code terminal input #4391](https://github.com/anthropics/claude-code/issues/4391)

This issue will be automatically closed as a duplicate in 3 days.

* If your issue is a duplicate, please close it and 👍 the existing issue instead

* To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

Dronakurl avatar Nov 30 '25 22:11 Dronakurl

This is wild, it only is a problem in fish shell. So I am going back to zsh for a while

Dronakurl avatar Dec 01 '25 19:12 Dronakurl