# Direnv, project environment and zsh

**URL:** <https://discourse.flox.dev/t/direnv-project-environment-and-zsh/707>\
**Category:** Help\
**Created:** [March 28, 2023, 7:16pm UTC](https://discourse.flox.dev/t/direnv-project-environment-and-zsh/707 "2023-03-28T19:16:37Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![aameen](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.flox.dev/aameen/32/564_2.png) [@aameen](https://discourse.flox.dev/u/aameen)\
**Post date:** [April 12, 2023, 8:09pm UTC](https://discourse.flox.dev/t/direnv-project-environment-and-zsh/707/12 "2023-04-12T20:09:48Z")

</div>

@etorreborre I think I found the cause of this when I was working on the other `direnv` response for you.

It looks like `flox` isn’t detecting non-interactive shells, so if you have multiple envs in a project ( the default + any package ) it will try to prompt you to select. You won’t see the prompt because it’s not an interactive shell, and it’ll just hang.

If you instead explicitly use `. <( flox activate -e '.#default'; );` it shouldn’t hang.  
I’ve filed a bug fix ticket for this so hopefully we can get it resolved soon.

---

_[View the full topic](https://discourse.flox.dev/t/direnv-project-environment-and-zsh/707)._