[FEATURE] SSH Connector for Claude Code for Web

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

Claude Code CLI works beautifully over SSH on self-managed servers. As more features shift to dependence on web and now mobile apps and Slack interfaces, workflows that don't use GitHub are getting left behind.

Use case: I manage multiple production codebases via SSH on my own infrastructure. These aren't Git repos. Claude Code CLI has been transformative for this work. I'd like to trigger those same sessions (or work orders) remotely (via Slack, mobile, browser) without requiring GitHub as an intermediary.

Proposed solution: An SSH connector option alongside the GitHub connector — specify a host, authenticate via key, and run Claude Code against that remote environment.

Proposed Solution

Proposed Solution
I'd like to be able to run claude --workspace user@server:/path/to/project (or similar) to register a remote environment, then trigger sessions against it from Claude Code Web, Slack, or mobile.
There should be a command or setting that allows:

Registering SSH hosts with key-based auth (similar to how GitHub repos are connected today)
Specifying one or more working directories per host
Optionally defining setup commands (e.g., source ~/.bashrc, cd /var/www/myproject)

The interface should show:

Connected SSH environments alongside GitHub repos in the environment picker
The same session experience as GitHub-based sessions: progress updates, ability to review changes, async execution
Output delivered the same way (Slack thread updates, web UI, etc.) — just without the PR step since there's no Git

Essentially: treat a remote SSH directory the same way you currently treat a cloned GitHub repo in the VM, but let my server be the VM.

Alternative Solutions

I'd like to be able to run claude --workspace user@server:/path/to/project (or similar) to register a remote environment, then trigger sessions against it from Claude Code Web, Slack, or mobile.

There should be a command or setting that allows:

• Registering SSH hosts with key-based auth (similar to how GitHub repos are connected today)
• Optionally defining setup commands (e.g., source ~/.bashrc, cd /var/www/myproject)
• BONUS: Specifying multiple working directories per host, each instantiated as a separate project in the Code interface

The interface should show:

• Connected SSH environments alongside GitHub repos in the environment picker
• The same session experience as GitHub-based sessions: progress updates, ability to review changes, async execution
• Output delivered the same way (Slack thread updates, web UI, etc.) — just without the PR step since there's no Git

Essentially: treat a remote SSH directory the same way you currently treat a cloned GitHub repo in the VM, but let my server be the VM.

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_