Copilot CLI segmentation fault

[PrithviKaushik]

Select Topic Area

Question

Copilot Feature Area

General

Body

I can't run Copilot CLI after installing it. I'm on Fedora, node and npm versions are proper.

[haroonmaqbool]

Hey @PrithviKaushik! A segmentation fault in the Copilot CLI usually means the install got corrupted or there’s a Node.js mismatch. Try removing and reinstalling it cleanly:
sudo npm uninstall -g @githubnext/github-copilot-cli
sudo npm install -g @githubnext/github-copilot-cli
Also make sure Node is version 18+. On Fedora old cached binaries can also cause this you can clear them with:
sudo rm -rf ~/.npm
Then reinstall again. That should fix the segmentation fault.

[haroonmaqbool]

Since it’s still segfaulting even after a clean reinstall, it’s most likely an issue with the binary build for your Fedora version or a Node ABI mismatch.

Try this next:

# Remove existing global cache and rebuild binaries
npm cache clean --force
sudo rm -rf ~/.cache ~/.npm

# Then reinstall with a fresh build
sudo npm install -g @githubnext/github-copilot-cli --unsafe-perm

# And check Node version
node -v

[PrithviKaushik]

Node is v22.20.0.
Did the rest too, still doesn't work sadly.

[schrew-pfizer]

Same here, it works for small questions but once it needs to do some actual work it crashes with segfault:

 Welcome to GitHub Copilot CLI
 Version 0.0.354 · Commit 076bd172b

 Copilot can write, test and debug code right from your terminal. Describe a task to get started or
 enter ? for help. Copilot uses AI, check for mistakes.

 ● Logged in as user: schrew-pfizer

 ● Connected to GitHub MCP Server

 > write a test using nightwatch.js to test the /drivers and edit driver form much like we did for
   tests/e2e/002_device_page.test.js

 ● I'll examine the existing test file and create a similar test for the drivers
   page and edit driver form.

 ✓ List directory tests/e2e (9 files)

 ✓ Read tests/e2e/002_device_page.test.js (140 lines)

 ● Now let me check the drivers page structure in the source code to understand the
   form better:

 ◎ Examining existing test structure (Esc to cancel · 528 B)

 /app                                                                          claude-sonnet-4.5 (1x)
 ─────────────────────────────────────────────────────────────────────────────────────────────────────
 >  Enter @ to mention files or / for commands
 ─────────────────────────────────────────────────────────────────────────────────────────────────────
 Ctrl+c Exit · Ctrl+r Expand recent                                          Remaining requests: 98.4%
‍
Segmentation fault (core dumped

/app # node --version
v22.21.1

[schrew-pfizer]

Adding memory to my laptop improved it (makes it happen less). But it still happens on latest version checked out today:

/app # copilot
 Welcome to GitHub Copilot CLI
 Version 0.0.367 · Commit 9b421b4

 Copilot can write, test and debug code right from your terminal. Describe a task to get started or
 enter ? for help. Copilot uses AI, check for mistakes.

 ● Logged in as user: schrew-pfizer

 ● Connected to GitHub MCP Server
 Can you write tests with vitest for src/views/devices/Devices.vue and put them in
      tests/components/views/devices/Devices.test.js

 ● I'll help you write tests for the Devices.vue component. Let me first examine the component to
   understand its structure and functionality.

 ✔ List directory src/views/devices
   └ 11 files found

 ✔ List directory tests/components/views
   └ 12 files found

 ✔ Read src/views/devices/Devices.vue
   └ 257 lines read

 ✔ List directory tests/components/views/devices
   └ 6 files found

 ✔ Read vitest.config.js
   └ 19 lines read

 ● Now let me check existing test examples to understand the testing patterns used in this project:

 ✔ Glob "tests/**/*.test.js"
   └ 41 files found

 ● Let me look at some similar test files to understand the testing patterns:

 ◎ Examining component structure (Esc to cancel)

 /app                                                                            claude-sonnet-4.5 (1x)
 ───────────────────────────────────────────────────────────────────────────────────────────────────────
 >  Enter @ to mention files or / for commands
 ───────────────────────────────────────────────────────────────────────────────────────────────────────
 Ctrl+c Exit · Ctrl+r Expand recent                                            Remaining requests: 83.4%
‌
Segmentation fault (core dumped)

And indeed it works as long as it doesn't have to reason or think too much. As soon as there's a more challenging question it just crashes....

[rob-p]

I'm getting this same behavior on a MacBook Pro M1 Max (64GB). Any update on the situation here? I can't even launch the application.

[TomaszGrzmilas]

Got the same error on ubuntu:24.04 container.
node --version
v22.23.4

Installed by:
curl --retry 3 -fsSL https://gh.io/copilot-install -o "$WORK_DIR/copilot-install.sh"