Problem Statement

coder ssh is a separate path from coder config-ssh && ssh <coder.workspace>. There are unpredictable behaviors.

1. For starters, you cannot use coder ssh to just run "one shot command" and get it in stdout

    # works
    ssh coder.fresh ls
    # does not work 
    coder ssh fresh ls

2. More importantly, it does not respect what you have set in .ssh/config, for example if you have special options around GPG forwarding, etc. This is the root of the customer issue

Proposal

• When running coder ssh, first attempt to use ssh and read the hosts, then gracefully fall back to the current behavior.
• Add a flag to prevent coder ssh from reading .ssh/config
• Add support to for running commands in workspace via coder ssh workspace [command] #2154

Related Slack Thread