[FEATURE] Hope Claude Code for VSCode supports remote SSH

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

I regularly develop and train models on remote Linux servers through VS Code Remote - SSH. In this workflow, the codebase, Python environments, GPUs, datasets, experiment logs, and terminals all reside on the remote machine rather than on my local computer.

Without Remote - SSH support in the Claude Code VS Code extension, I need to switch to a separate terminal-based workflow or manually move context between local and remote environments. Claude Code cannot reliably access the same remote workspace, terminal output, virtual environments, running processes, or debugging context that I am using in VS Code.

This creates unnecessary friction during iterative development, especially when debugging remote training jobs, inspecting logs, modifying code, and running experiments. It also makes it harder to use Claude Code safely and efficiently without copying project files or sensitive data from the remote server to the local machine.

Proposed Solution

Claude Code for VS Code should support workspaces opened through the VS Code Remote - SSH extension.

When a user connects to a remote machine using Remote - SSH, the Claude Code extension should automatically recognize that the active workspace is remote and operate within that same remote environment. Claude Code should be able to:

Read, search, and edit files in the remote workspace.
Use the remote terminal and execute commands on the remote host.
Access the same Python interpreter, virtual environment, containers, and project dependencies configured in the remote VS Code session.
Inspect remote logs, running processes, and debugging output.
Apply the same permission and confirmation workflow used for local projects.
Clearly indicate in the interface which remote host and workspace Claude Code is operating on.

The experience should feel equivalent to using Claude Code in a local VS Code workspace, while ensuring that code execution and file access remain on the connected remote server.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

Configuration and settings

Use Case Example

_No response_

Additional Context

_No response_