[BUG] Claude Code for VS Code Extension SIGABRT on ARM64 with 64KB Page Size (Remote SSH)

Status Closed — not planned
Reported on v2.1.6
Maintainer reply None cached
Activity 13 comments · opened Jan 13, 2026 · closed May 24, 2026

Preflight Checklist

  • [x] I have searched existing issues 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?

The Claude Code VS Code extension (in remote SSH) crashes with SIGABRT (exit code 134) on ARM64 systems using 64KB kernel page size.

What Should Happen?

Claude Code vscode extension should run on remote ssh or tunnels but it does not. In other words, extension should work on ARM64 systems regardless of kernel page size.

Error Messages/Logs

$ ~/.vscode-server/extensions/anthropic.claude-code-2.1.6-linux-arm64/resources/native-binary/claude --version
Aborted (core dumped)
$ echo $?
134


Exit code 134 = 128 + 6 (SIGABRT)

Steps to Reproduce

  • Install Claude Code extension on VS Code Remote-SSH to an ARM64 server with 64KB page size
  • Extension fails to start with "Not connected" errors

Probable Cause

The native binary was compiled for standard 4KB page size:

$ file .../native-binary/claude
ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), dynamically linked, 
interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, ...

$ getconf PAGESIZE
65536

Binaries compiled with 4KB page alignment are incompatible with 64KB page kernels on ARM64.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.6

Platform

Anthropic API

Operating System

Other Linux

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

13 Comments

wael-mika · 7 months ago

The same issue

LorenzoTarricone · 7 months ago

I have the same issue!!

hmehrafarin · 7 months ago

Any stats on this?

wael-mika · 7 months ago

Is anyone working on it? Is there a way to bring attention to this issue?

hmehrafarin · 7 months ago

@chrislloyd @dougbarth I am not sure if I am tagging the right people but I'd appreciate any input on this!

Algomancer · 6 months ago

This is an annoying one in particular due to the npm depreciation.

hmehrafarin · 6 months ago

Do you know if there Is any workaround to get it fixed?

007 · 6 months ago

Most likely depends on https://github.com/oven-sh/bun/issues/17627 since claude is a bun-js binary.

highker · 5 months ago

Workaround

Verify you're affected

# Should return 65536 (64KB) — if it returns 4096, this isn't your issue
getconf PAGESIZE

# Should abort with exit code 134
~/.cursor-server/extensions/anthropic.claude-code-*/resources/native-binary/claude --version

Prerequisites

A working Node.js-based Claude Code CLI install. Verify with:

claude --version

If you don't have it, install via:

npm install -g @anthropic-ai/claude-code

Apply the workaround

# 1. Find the extension directory (Cursor or VS Code)
CLAUDE_EXT=$(ls -d ~/.cursor-server/extensions/anthropic.claude-code-*-linux-arm64 2>/dev/null \
          || ls -d ~/.vscode-server/extensions/anthropic.claude-code-*-linux-arm64 2>/dev/null)
echo "Extension dir: $CLAUDE_EXT"

# 2. Back up the broken native binary
mv "$CLAUDE_EXT/resources/native-binary/claude" \
   "$CLAUDE_EXT/resources/native-binary/claude.bak"

# 3. Create a wrapper that delegates to the Node.js CLI
cat > "$CLAUDE_EXT/resources/native-binary/claude" << 'WRAPPER'
#!/bin/bash
exec claude "$@"
WRAPPER
chmod +x "$CLAUDE_EXT/resources/native-binary/claude"

# 4. Verify it works
"$CLAUDE_EXT/resources/native-binary/claude" --version

Caveats

  • The wrapper uses whatever claude version is on your $PATH, which may differ from the extension version. You can pin it with:

``bash
npm install -g @anthropic-ai/claude-code@<version>
``

  • Extension auto-updates will overwrite the wrapper — you'll need to reapply after updates.
qiching · 5 months ago

We’re seeing the same issue on ARM64 machines with 64KB page size, and the workaround does help. Is there already a permanent fix available or planned, instead of relying on the wrapper?

007 · 4 months ago

Needs to be marked as evergreen, doesn't go stale just from ignoring it.

github-actions[bot] · 3 months ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

github-actions[bot] · 1 month ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.