Martin Kühl

What's the output of `direnv status` in that case?

FWIW, that the `direnv: loading` etc. output doesn't appear is *correct and expected*. That output appears when direnv loads a custom environment, but in your case *direnv has already loaded...

@burdiyan did you read the earlier comments on this? What's happening is this: * direnv is setting up an environment *inside VSCode* * you're starting a terminal, which starts a...

I'm not sure where the issue is, could you explain what you're expecting and how what you're seeing is different?

> Personally I'd rather the extension just do the restart for me. Or perhaps that choice could be a config option? It is, you can enable `direnv.restartAutomatic`

I think that's a great idea :)

> I was having a problem where `direnv` failed loading the Nix shell due to an invalid `NODE_OPTIONS` flag, but _only_ in the VS Code integrated terminal. Outside of VS...

> If it's not a bug, how is this supposed to work? Like I said, if a variable needs to be unset then one should unset it. Also like I...

I don't know how this would affect WSL users. I *assume* those folks should be able to install and run direnv, right? Is there something we could do instead of...

FWIW it does work for me:  You'll have to give me a lot more to be able to help....