[BUG] SSH remote connection broken after Desktop app update to 1.8555.0 (worked in 1.8089.0)

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/48523
2. https://github.com/anthropics/claude-code/issues/39433
3. https://github.com/anthropics/claude-code/issues/52734

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

This issue is not a duplicate of the above.

Solution: claude-code #61498 — SSH Remote Connection Broken After Desktop Update

🔍 Root Cause

SSH remote connections worked in Desktop 1.8089.0 but broke in 1.8555.0 — a clear regression. Likely causes:

1. SSH connection handling refactoring between versions
2. Electron/Node.js version upgrade affecting SSH library behavior
3. Network/security policy change blocking SSH by default
4. SSH key/path resolution change in the remote context

🔧 Fix

1. Compare SSH connection code between versions

Identify the specific change that broke SSH. Focus on:

• SSH tunnel creation
• Port forwarding setup
• SSH key loading
• Connection timeout handling

2. Add SSH connection diagnostics

async function connectSSH(config: SSHConfig): Promise<SSHConnection> {
    try {
        logger.debug('SSH connecting', { host: config.host, port: config.port });
        const conn = await ssh2.connect(config);
        logger.debug('SSH connected successfully');
        return conn;
    } catch (err) {
        logger.error('SSH connection failed', { host: config.host, error: err.message, code: err.code });
        throw err;
    }
}

3. Add fallback connection methods

If primary SSH fails, try system ssh command as fallback.

🧪 Testing

• Verify SSH works with same config that worked in 1.8089.0
• Test on macOS, Linux, Windows
• Test with RSA, Ed25519, ECDSA keys
• Test with and without ~/.ssh/config

⚠️ Edge Cases

• Respect ~/.ssh/config (ProxyJump, ProxyCommand, custom ports)
• Support ssh-agent for key management

The above did not solve the issue.

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.