Good idea! It's a nice idea to be able to ssh -F, and that way it could be excluded from the global scope if desired.

Right less things to debug when your local config just polluted by conflicting settings.

I'm slotting this in next sprint, related to Coder config storage in the CLI so linking #13325.

We went down the path of using Include at one point which caused issues with certain tools. For the best compatibility, we should retain the current behavior IMO.

Personally I use something along the lines of this:

# ~/.ssh/config
Include coder-*

# ~/.zshrc
coder_deployment() {
    deployment=$1
    export CODER_CONFIG_DIR="$HOME/Library/Application Support/coderv2-${deployment}"
    export CODER_SSH_CONFIG_FILE="$HOME/.ssh/coder-${deployment}"
}

An important detail is also the placement of the Include, most likely it needs to be at the top of the file, and also moveable by the user. I'm not entirely opposed to adding an option to automatically add the Include, though, but it adds a bit of additional complexity we need to handle (granted, in a similar manner we already handle the config).