VSCode Extension webview input field missing when using Remote SSH (requires clean reinstall to fix)

Status Fixed / completed
Reported on v2.1.78
Maintainer reply None cached
Activity 7 comments · opened Mar 25, 2026 · closed Apr 2, 2026

Root Cause

Shell environment resolution timeout. VS Code's Remote SSH extension host has a ~10s timeout to resolve the user's shell environment. A large/slow .bashrc or /etc/profile.d/ script caused this timeout, which prevented the Claude Code extension from completing its init sequence — resulting in a blank/empty webview panel.

Symptoms

  • Claude Code tab opens but panel is completely blank (no input field, no UI)
  • Extension activates successfully (logs show "Claude code extension is now active")
  • Webview sends init message but never receives a response
  • Tab cannot be reopened without full VS Code reload
  • VS Code remote agent log shows: Unable to resolve your shell environment in a reasonable time

Environment

  • VSCode: 1.113.0
  • Claude Code Extension: 2.1.78 through 2.1.90 (all affected)
  • Local machine: Ubuntu 24.04 (native)
  • Remote machine: Ubuntu 24.04 (via Remote SSH)

Actual Fix

Add an early return in .bashrc / shell profile when VS Code is resolving the environment:

# Skip heavy init when VS Code is resolving shell environment
if [[ "$VSCODE_RESOLVING_ENVIRONMENT" == "1" ]] || [[ "$ELECTRON_RUN_AS_NODE" == "1" ]]; then
    return 0
fi

What Did NOT Fix It

  • Removing npm global install of claude-code
  • Reinstalling claude CLI via official installer
  • Upgrading Node.js from 18 to 20
  • Clearing ~/.claude/ide/*.lock files
  • Resetting ~/.claude/settings.json to {}
  • Reinstalling the VS Code extension
  • Wiping ~/.vscode-server (appeared to work temporarily but was coincidental)

Note

The original report incorrectly identified the fix as "complete wipe of ~/.vscode-server". The actual root cause was a slow shell environment that exceeded VS Code's resolution timeout. This is not a bug in Claude Code — it affects any extension that spawns processes requiring the full user environment via Remote SSH.

View original on GitHub ↗

7 Comments

elfege · 5 months ago

Additional symptom: After closing the Claude Code tab, cannot reopen it without reloading VSCode window. The 'Open Claude Code' command does nothing until a full reload.

elfege · 5 months ago

Update: Issue also occurs when running VSCode locally on Ubuntu 24.04.2 (not via Remote SSH). The input field is missing in both local and remote scenarios. This appears to be a broader Linux/Ubuntu compatibility issue, not specific to Remote SSH.

elfege · 5 months ago

Correction: Claude Code works fine when running VSCode locally on Ubuntu 24.04.2. The issue only occurs when connected to a remote machine via Remote SSH. The problem is specifically with the Remote SSH scenario.

elfege · 5 months ago

Root cause identified: This is a regression. Version 2.1.76 works correctly via Remote SSH. The issue was introduced in a later version (tested broken on 2.1.83).

Workaround: Install version 2.1.76 and disable auto-update:

code --install-extension anthropic.claude-code@2.1.76

Then in VSCode settings, set extensions.autoUpdate to false or onlySelectedExtensions to prevent auto-updating to the broken version.

elfege · 5 months ago

Bisected: Regression introduced in version 2.1.78.

  • 2.1.76: ✅ Works
  • 2.1.77: ✅ Works
  • 2.1.78: ❌ Broken (no input field via Remote SSH)
  • 2.1.83: ❌ Broken

Recommended workaround: Pin to version 2.1.77

elfege · 5 months ago

Resolved: Root cause was shell environment resolution timeout. VS Code's extension host was timing out trying to source a large ~/.bashrc/profile, which prevented the Claude extension from completing initialization. Not a bug in Claude Code. Closing as user error.

github-actions[bot] · 4 months 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.