Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Hey everyone!
Everything had been working perfectly for the past two months, but yesterday, when I tried to launch the Claude Code extension, I started getting this error:
Error: Claude Code process terminated by signal SIGABRT.
I couldn’t find any fix for this issue online.
My system:
macOS Big Sur 11.7.10
Cursor version: 1.7.46
VSCode version: 1.99.3
I tried reinstalling both Cursor and the extension with a full cleanup, but the issue still persists.
The regular Claude Code CLI works fine.
Steps to Reproduce
Steps to reproduce:
Open Cursor
Enable the Claude Code extension
The error appears
Screenshots / Screen Recordings
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.7.46
VSCode Version: 1.99.3
Commit: b9e5948c1ad20443a5cecba6b84a3c9b99d62580
Date: 2025-10-14T01:21:46.830Z (8 hrs ago)
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin x64 20.6.0
Does this stop you from using Cursor
Yes - Cursor is unusable
deanrie
October 14, 2025, 11:57am
2
Hey, thanks for the report. It looks like the issue is with the Claude Code extension, not a Cursor bug.
Please try:
If MCP calls might be involved, try disabling them and run Claude Code again
Temporary workaround: use the Claude Code CLI directly while waiting for a fix
Or disable the extension so it doesn’t affect your Cursor workflow, Cursor’s built-in AI features will keep working
There’s a related GitHub issue, but no solution yet. I recommend tracking it:
opened 07:32PM - 16 Sep 25 UTC
bug
has repro
platform:linux
area:core
area:mcp
### Preflight Checklist
- [x] I have searched [existing issues](https://github.… com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
### What's Wrong?
Claude Code crashes with SIGABRT during shutdown when attempting to terminate MCP (Model Context Protocol) servers. The crash occurs during the cleanup phase when the application cannot properly shut down connected MCP servers, leading to a Node.js assertion failure during stdio cleanup.
### What Should Happen?
Claude Code should exit cleanly after properly terminating all MCP server processes and cleaning up resources.
### Error Messages/Logs
```shell
SIGINT failed, sending SIGTERM to MCP server process
Error sending SIGTERM:
SIGTERM failed, sending SIGKILL to MCP server process
Error sending SIGKILL:
Error terminating process:
Error closing client:
Cleanup timeout reached, stopping process monitoring
Process terminates with SIGABRT and generates core dump (261MB core file).
```
### Steps to Reproduce
1. Start Claude Code with MCP servers configured
2. Use Claude Code normally (any operations)
3. Exit Claude Code (Ctrl+C, quit command, or other exit method)
4. Application crashes during shutdown process with core dump
### Claude Model
Sonnet (default)
### Is this a regression?
I don't know
### Last Working Version
_No response_
### Claude Code Version
1.0.113
### Platform
Anthropic API
### Operating System
Ubuntu/Debian Linux
### Terminal/Shell
VS Code integrated terminal
### Additional Information
Stack trace analysis:
- Crash point: node::ResetStdio() during exit cleanup
- Signal: SIGABRT (assertion failure)
- Root cause: MCP servers failed to terminate (SIGINT → SIGTERM → SIGKILL all failed)
- Node.js cleanup assertion failed when trying to reset stdio during exit
Technical details:
- Executable: /usr/bin/node (Claude Code)
- Core dump shows uncaught exception during shutdown sequence
- MCP server termination timeout reached before clean exit
Since this isn’t a Cursor issue, it shouldn’t make Cursor itself unusable, only the Claude Code extension is affected.
Hi, dearnie!
Thank you so much for your help! I’ll be keeping an eye out for updates or a fix to the root issue.