Thanks for filing this report. To comply with OpenSSH, when coder-cli initially creates the coder_enterprise private key file, it removes its own write permissions. This makes subsequent executions of the command fail unless the user manually executes something like sudo rm ~/.ssh/coder_enterprise first, then runs coder config-ssh.

I think the best path forward is to improve the error message providing these instructions.

We could potentially make the command idempotent. If the key exists, we complete successfully, if it doesn't, we create it and complete successfully. Then we can have the error handling be for unexpected / extraneous cases.

@nathanpotter The trouble with making this idempotent is that the user can regenerate their key from the dashboard. So sometimes we do need them to manually delete it so we can rewrite to the file.

Kinda wonder how the gcloud CLI handles this because they seem to have figured it out.

Another issue for us is when we add a new environment and want to configure it locally via "coder config-ssh", it doesn't add quotes for the path to the key.
The behavior now: IdentityFile=C:\Users\User Name.ssh\coder_enterprise
The wanted behavior: IdentityFile="C:\Users\User Name.ssh\coder_enterprise"

Anyway I linked and created two pull requests that will solve this problem #139 #138.
it will be resolved when those two are merged.

@cmoog both of them go merged, I believe this will be fixed in the next build of the cli.
This issue is resolved.