I already had some existing tools and automations written that used our manual ssh/config entries, so when we switched to Coder they all just worked seamlessly already.

By including them in the ssh config, any other tools that lists out your connections as options just work, and don't require an official Coder plugin built into everything.

I agree. Even with the wildcard entry in the config, most tools should be able to connect. So, the only issue I see here is getting a list of available workspaces, which you were parsing from the SSH config. Right?

Yeah, it just helped list them out in a bunch of tools like Tinkerwell, Tabby, our own automations, some database tools, etc. I frequently change between a lot of workspaces and having every workspace already show up in every tool as an option to connect to was very convenient. Now there is a lot more set up to just get started on any project sadly.

What was nice about the old method is it provided universal compatibility with a lot of tools that just assume your frequent ssh connections have been added to your ssh/config.

Seems like every since this was switched, our Windows users can't connect with Jetbrains Gateway.

On macOS I did finally get it to generate the# --- START CODER JETBRAINS section in the ~/.ssh/config, but on Windows we're getting "No such host is known" and that block never gets added on Windows for the ssh config.

On macOS I did finally get it to generate the # --- START CODER JETBRAINS section in the ~/.ssh/config, but on Windows we're getting "No such host is known" and that block never gets added on Windows for the ssh config.

Could you file a separate bug report for this? We will look into it.
Please also include the gateway version the Coder plugin version and make sure it's reproducible on the latest version of both.