Integration with environment variables, powershell, terminal

[Dan]

I am having a blast using Rovodev to work on my passion projects. It's doing a great job and helping me with my productivity a lot. However, Rovodev keeps tripping up by using env variables and some powershell/bash commands which it has no access to.

I am on windows and running rovodev in a powershell terminal, but it keeps having issues by attempting to access env variables such as `dotnet` (which is set up correctly in %PATH% and works in a normal terminal, but Rovodev is lacking access to it). The same happens with attempting to use bash, or some powershell commands. 

Is there any sort of improvement that could be made so that Rovodev recognizes the context in which it is launched and does not keep attempting to use commands which are not available? Or better yet, can it get access to env variables, or force running inside a bash terminal by default?

[Dan]

I am also noticing very weird behavior in terms of integration with docker- whenever Rovodev runs docker compose build, the shell closes and opens immediately, leading Rovodev to believe the build succeeded, when there are in fact errors that prevent a successful compilation. Afterwards, he is not able to access docker compose logs to review the issue.