Environment
- OS: macOS Darwin arm64 (Apple Silicon)
- Node.js: v24.14.1
- Package: @github/copilot@1.0.31
- Shell: zsh
Behavior
Running copilot or copilot --yolo produces no output and exits with code 1.
Running copilot auth status also produces no output.
Root Cause (diagnosed)
The binary wrapper (npm-loader.js) resolves @github/copilot-darwin-arm64 and runs it via spawnSync. The native binary crashes immediately with SIGSEGV (exit code 139). The wrapper catches the null status as ?? 1 and exits silently - no error message is printed.
Verified by running the native binary directly:
$ /path/to/node_modules/@github/copilot-darwin-arm64/copilot --version
[no output, exit: 139]
Steps to Reproduce
npm i -g @github/copilot@1.0.31 on macOS arm64 with Node.js v24
- Run
copilot or copilot --yolo
- No output, exits with code 1
Workaround
Downgrade to 1.0.25 (JS-only, no native binary):
npm i -g @github/copilot@1.0.25
Or run the JS fallback directly:
node $(npm root -g)/@github/copilot/app.js
Suggestion
The wrapper's empty catch {} silently swallows the native binary failure. A fallback to the JS implementation when the native binary crashes (non-zero exit), or at minimum a visible error message, would help users diagnose this.
Environment
Behavior
Running
copilotorcopilot --yoloproduces no output and exits with code 1.Running
copilot auth statusalso produces no output.Root Cause (diagnosed)
The binary wrapper (
npm-loader.js) resolves@github/copilot-darwin-arm64and runs it viaspawnSync. The native binary crashes immediately with SIGSEGV (exit code 139). The wrapper catches the null status as?? 1and exits silently - no error message is printed.Verified by running the native binary directly:
Steps to Reproduce
npm i -g @github/copilot@1.0.31on macOS arm64 with Node.js v24copilotorcopilot --yoloWorkaround
Downgrade to 1.0.25 (JS-only, no native binary):
Or run the JS fallback directly:
Suggestion
The wrapper's empty
catch {}silently swallows the native binary failure. A fallback to the JS implementation when the native binary crashes (non-zero exit), or at minimum a visible error message, would help users diagnose this.