Cannot run terminal commands

[avi12]

Describe the bug

When I ask the agent to run a command (e.g. eslint .), it tries to run the command but gets <exited with exit code MODULE_NOT_FOUND>

Affected version

0.0.338 Commit: 877e86a

Steps to reproduce the behavior

1. copilot --allow-all-tools

2. Prompt:

   run `pnpm lint:fix` and fix any errors
   

3. ● Now let me run pnpm lint:fix:
   
   ✗ Run linting with auto-fix
   $ pnpm lint:fix
   <exited with exit code MODULE_NOT_FOUND>
   

Expected behavior

Run the command successfully

Additional context

PowerShell 7.5.3
Windows 11 Pro Version 24H2 (0S Build 26.100.6725)

[SteveSandersonMS]

@avi12 Thanks for reporting this.

The MODULE_NOT_FOUND error sounds like an issue with your Node installation or NPM package cache. Searching the web for that error code brings back a lot of reports of people finding that random Node-related things stopped working (often after upgrading Node versions), and generally the solution is to npm cache clean --force, and possible reinstall Node entirely. This is unfortunately a bit outside Copilot CLI's control since we rely on a working Node environment.

Could you let us know if you can still reproduce the issue after ensuring Node and the packages are reinstalled? Thanks!

[avi12]

I typically use pnpm, not npm
also, this error occurs for any command that it tries to run, not just pnpm

[SteveSandersonMS]

@avi12 Yes, I understood you mean all shell commands don't work :)

What I mean is that copilot itself is running on Node, and it sounds like it's unable to load a module that we depend on for shell execution. So you may need to repair your Node installation or module cache in order for copilot to work correctly.

[RReverser]

I've had same issue with pnpm installation. Uninstalling copilot CLI from pnpm and reinstalling with npm has solved it.

Perhaps the CLI can't handle symlinks in node_modules?

[ygorduraes]

Same issue here, when installing the CLI through pnpm

[AjmalShajahan]

@avi12 @ygorduraes Try reinstalling pnpm https://pnpm.io/uninstall

[avi12]

I installed pnpm via WinGet

[AjmalShajahan]

I installed pnpm via WinGet

In that case you can do rm $env:PNPM_HOME; winget install -e --id pnpm.pnpm; pnpm setup
pnpm install -g @github/copilot; pnpm approve-builds -g

Did you also install node using pnpm by pnpm env use --global lts ?

[AjmalShajahan]

I installed pnpm via WinGet

@avi12 perhaps the build scripts have not run, could you share a log from ~.copilot\logs
You could also try pnpm install -g @github/copilot --force

[examon]

This appears to be addressed in current releases. We reworked how native modules are distributed, so prebuilds are now bundled directly in the package -- this should resolve the issue for supported install methods. Note that pnpm is not currently listed as a supported installation method; the recommended options are the official install script, Homebrew, WinGet, or npm. If you're still hitting this with a supported install method on the latest CLI version, please feel free to reopen.