Claude CLI core dumps (SIGSEGV/SIGABRT) during active sessions

Description

Claude CLI (claude-code) intermittently core dumps during active coding sessions, killing the process mid-conversation. This happens frequently enough to be a serious workflow disruption — multiple crashes per day during normal usage.

Environment

• OS: Ubuntu 25.10 (Linux 6.18.0)
• Hardware: Lenovo Legion (desktop-class workstation)
• Claude CLI: latest (installed via npm)
• Node.js: system default
• Usage pattern: Large codebase work (~4,500+ line files), multi-step tasks with file reads, edits, bash commands, and subagent spawning

Steps to Reproduce

1. Start a Claude Code session with a large codebase
2. Work on multi-step tasks involving file reads, edits, and bash commands
3. CLI crashes with core dump at unpredictable points — no specific trigger

Expected Behavior

CLI should not crash. If memory pressure is an issue, it should gracefully handle limits or warn before dying.

Actual Behavior

Process dies with core dump. --resume sometimes recovers the session, sometimes doesn't. No OOM or segfault in kernel dmesg — this is internal to the Claude CLI node process, not a system-level issue. /var/crash/ and coredumpctl show no system-level core dumps, confirming the crash is within the CLI's own process.

Impact

• Kills active work mid-task with no warning
• Forces re-establishing context from scratch (even --resume loses state)
• Multiple occurrences per day during normal coding sessions
• Significant productivity loss

Additional Context

This is on a machine with plenty of RAM and no system-level memory pressure. The crash appears to be a bug in the CLI's node process itself, not resource exhaustion.

---
GitHub: @alstergee