Execute Commands in Windows

[Chris]

Hello, is there already a solution for running Node or Python commands in PowerShell on Windows?

ROVO keeps saying it can't execute tools like npm or npx because it can't find them. As a result, it's also unable to connect to MPC servers. I haven't found a solution so far. Whether PowerShell is started as administrator or not doesn't make a difference — it still doesn't work.

Without the use of ROVO, the commands run in PowerShell without any issues.

[Dr Valeri Colon _Connect Centric_]

Hi @Chris and welcome to the community. This can happen if Rovo’s CLI runs in a different environment than your normal PowerShell. Try launching PowerShell via Windows Terminal and ensure Node.js is added to your system PATH. Also, run where npm or where python inside Rovo to confirm visibility. Let me know if you're using WSL or a custom shell—it can affect resolution.

For more tips view the Dev Cli Community: https://community.atlassian.com/forums/Rovo-for-Software-Teams-Beta/Introducing-Rovo-Dev-CLI-AI-Powered-Development-in-your-terminal/ba-p/3043623

[Jaysef Lo]

i have tried your suggestions, but i still have the same error. I have node installed locally, i can run node --version, both in powershell and windows terminal. But once i start rovodev with "acli rovodev run", and i tell him to run node --version command.  This is what it does :

> can you run node version

╭─ Response ───────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ I'll check the Node.js version for you by running the command. │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
└── Calling powershell: {"command": "node --version"}

node : The term 'node' is not recognized as the name of a cmdlet, function, script file, or operable program. Che.
the spelling of the name, or if a path was included, verify that the path is correct and try again.
At D:\workspace\codeTyper\tmp_code_3313497c6720969a3633cdb6a2175cfa22475fd513760c003dff40751c23c3c7.ps1:1 char:1
+ node --version
+ ~~~~
+ CategoryInfo : ObjectNotFound: (node:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

╭─ Response ───────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ It looks like Node.js is not installed or not in the PATH on this system. Let me check if there are any other │
│ JavaScript runtimes available, like Bun (since I see a bun.lock file in the workspace):

When i tell him to echo path, it actually see the value of my path environment

> can you echo $path

╭─ Response ───────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ I'll check the PATH environment variable for you: │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
└── Calling powershell: {"command": "echo $env:PATH"}

"value_of_my_path"

╭─ Response ───────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ I can see that Node.js is actually installed! Looking at the PATH, I can see C:\Program Files\nodejs\ is included. │
│ Let me try running the node command again, but this time with the full path: