[BUG] Claude Code unresponsive over Remote-SSH on a Linux server under memory load (both VS Code extension and CLI)

Resolved 💬 0 comments Opened Jun 10, 2026 by quangvh88 Closed Jun 10, 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?

Environment:

  • Client: VS Code on Windows 10, connected via Remote-SSH
  • Remote: Linux server (Ubuntu), shared GPU node, ~125 GB RAM, conda base env
  • Claude Code CLI version: <output of claude --version>
  • VS Code extension version: <e.g. tried latest, also pinned 2.1.170>
  • A heavy GPU training job (PaddleOCR) is running on the same server during use

What Should Happen?

The Claude Code VS Code extension becomes unresponsive ("The window is not responding").
Switching to the Claude Code CLI in a terminal does NOT fix it — <describe exact CLI behavior:
hangs after sending a prompt / crashes on launch with <error> / freezes on startup>.
Pinning the extension to 2.1.170 did not help.

Expected: Claude Code responds normally.
Actual: <UI freeze / CLI hang / exact behavior>

Error Messages/Logs

Steps to Reproduce

  1. Connect to a remote Linux server via Remote-SSH from Windows VS Code
  2. While a GPU training job is consuming server resources
  3. Run claude in the terminal (or open the extension)
  4. <send a prompt / it hangs at ...>

<img width="1920" height="1040" alt="Image" src="https://github.com/user-attachments/assets/05500bc5-905c-4215-b115-5dada61c3bcd" />

Claude Model

Other

Is this a regression?

Yes, this worked in a previous version

Last Working Version

It's still working in other machine that isn't used Fable

Claude Code Version

2.1.170 (Claude Code)

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

VS Code integrated terminal

Additional Information

administrator@k8s-ai-worker01:/opt/setup$ claude doctor

───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Diagnostics
├ Currently running: native (2.1.170)
├ Commit: 1cda84def004
├ Platform: linux-x64
├ Path: /home/administrator/.local/share/claude/versions/2.1.170
├ Config install method: native
└ Search: OK (bundled)

Updates
├ Auto-updates: enabled
├ Auto-update channel: latest
├ Last update attempt: none recorded
├ Stable version: 2.1.153
└ Latest version: 2.1.170

Background server
└ Status: not running
└ Mode: ephemeral
└ See claude daemon status for details

Remote Control
└ Status: enabled
└ ✓ First-party provider (api.anthropic.com)
└ ✓ Not disabled by org policy (disableRemoteControl)
└ ✓ claude.ai OAuth token present
└ ✓ claude.ai subscriber auth active
└ ✓ OAuth token has user:profile scope
└ ✓ Organization UUID resolved
└ ✓ Feature-flag evaluation enabled
└ ✓ tengu_ccr_bridge gate (no server response this session)
└ isGrowthBookEnabled=true
└ telemetryDisabledBy=none
└ DISABLE_GROWTHBOOK=unset
└ hasFreshGrowthBookFeatures=false
└ growthBookFeaturesLoaded=311
└ growthBookLastFetched=2s ago
└ tengu_ccr_bridge=true

Still having issues? Run /feedback to report details.

Enter to continue

View original on GitHub ↗