claude-code - 💡(How to fix) Fix SSH Code: "Ambiguous output redirect" on remote servers with csh/tcsh default shell [1 comments, 2 participants]

Claude Desktop SSH Code fails to probe remote machines that use csh/tcsh as the default shell. The error occurs during the probe phase, before any CLI deployment. Error message in UI: Failed to probe remote machine: Ambiguous output redirect. Try again This worked correctly in the previous version. After updating Claude Desktop, all new sessions fail with this error. Existing sessions from before the update still work fine.

TL;DR

Wrap the probe command with bash -c '...' to ensure compatibility with the remote server's default shell.

Guidance

• Verify that the SSH connection is successful by checking the ssh.log for a successful connection message, such as [SSH2Connection] Connected to server:4543.
• Check the probe command sent by Claude Desktop to identify any bash-specific syntax that may be causing the incompatibility with csh.
• Consider detecting the remote shell before probing to determine the best approach for executing the probe command.
• As a temporary workaround, use existing sessions that were created before the update, as they are not affected by this issue.

Example

# Example of wrapping the probe command with bash -c '...'
probe_command="bash -c 'your_probe_command_here'"

Notes

This solution assumes that the remote server has bash installed and available for use. If bash is not available, an alternative approach may be needed.

Recommendation

Apply workaround: Wrap the probe command with bash -c '...' to ensure compatibility with the remote server's default shell, as changing the default shell to bash is not feasible in the given enterprise environment.