[BUG] ENOENT: /home/<redacted> not found on local machine when using Claude Code extension in UI mode over SSH

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?

Description

When using the Claude Code VS Code extension (v2.1.76) with remote.extensionKind: ["ui"]
to force local execution while connected to an SSH remote, the panel fails to load with:

ENOENT: no such file or directory, lstat '/home/<redacted>'

The path /home/<redacted> is the home directory on the remote SSH host, which is leaking
into the local extension's path resolution.

Steps to reproduce

1. Connect to an SSH remote in VS Code where the remote home directory differs from the local one
2. Install Claude Code extension locally with remote.extensionKind set to ["ui"]
3. Open the Claude Code panel

Expected behavior

Panel loads using the local claude CLI (/usr/bin/claude)

Actual behavior

Panel fails with ENOENT on the remote home directory path

Environment

• OS: Arch Linux (local), Linux (remote)
• VS Code: latest
• Claude Code extension: 2.1.76
• Remote: SSH

What Should Happen?

Panel loads using the local claude CLI (/usr/bin/claude)

Error Messages/Logs

ENOENT: no such file or directory, lstat '/home/<redacted>'

Steps to Reproduce

1. Connect to an SSH remote in VS Code where the remote home directory differs from the local one
2. Install Claude Code extension locally with remote.extensionKind set to ["ui"]
3. Open the Claude Code panel

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.76 (Claude Code)

Platform

Anthropic API

Operating System

Other Linux

Terminal/Shell

Other

Additional Information

_No response_