Skip to content

Coder Desktop Integration #21

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ThomasK33 opened this issue Mar 6, 2025 · 10 comments
Open

Coder Desktop Integration #21

ThomasK33 opened this issue Mar 6, 2025 · 10 comments
Assignees

Comments

@ThomasK33
Copy link
Member

Implement an enhancement making this extension aware of Coder Desktop. With Coder Desktop running, there is already an established tunnel to a workspace; thus, the extension does not need to create another tunnel.

The extension should prioritize the existing tunnel rather than creating a new one and should be able to display tunnel statistics related to the VPN within the editor.

@matifali
Copy link
Member

Hi @fioan89. Can you start looking into this? I think the initial launch should contain this functionality.

@matifali
Copy link
Member

@ThomasK33 and I can help with how Coder Desktop works here.

@fioan89
Copy link
Collaborator

fioan89 commented Mar 14, 2025

Sure. Right now I was working on integrating uri handling. It's slowly progressing as Toolbox API is not as flexilblle as Gateway's API. Should I put it on hold?

@matifali
Copy link
Member

No that's a higher priorty. This is something we can look into after that.

@fioan89
Copy link
Collaborator

fioan89 commented Mar 14, 2025

OK, so I'll continue with uri handling if my understanding is correct.

@matifali
Copy link
Member

matifali commented Apr 3, 2025

This depends on coder/coder#16828 otherwise it would be too complex to handle different URIs for Coder desktop and existing Coder CLI.

@Kira-Pilot Kira-Pilot assigned sreya and matifali and unassigned sreya and matifali Apr 10, 2025
@matifali
Copy link
Member

We have a reference VS Code implementation at coder/vscode-coder#482

@matifali matifali assigned fioan89 and unassigned matifali Apr 17, 2025
@ethanndickson
Copy link
Member

ethanndickson commented Apr 18, 2025

I'm not too familiar with the Jetbrains plugins, but I'd recommend actually not using the VSCode implementation as a reference, since it looks like you don't use wildcard SSH configs, you can probably just config something like (not exact, haven't tested):

Match host coder-jetbrains-toolbox-foo--test.coder.bar exec "/path/to/coder connect exists agent1.foo.owner.coder"
  HostName agent1.foo.owner.coder
Host coder-jetbrains-toolbox-foo--test.coder.bar
  ProxyCommand /path/to/coder ssh owner/foo.agent1
  ConnectTimeout 0
  StrictHostKeyChecking no
  UserKnownHostsFile /dev/null
  LogLevel ERROR
  SetEnv CODER_SSH_SESSION_TYPE=JetBrains

Where the ProxyCommand is only used if the agent wasn't available at agent1.foo.owner.coder (also keeping in mind that the .coder suffix is configurable deployment-wide)

For that reason, a better reference implementation would be coder/coder#17419

@fioan89
Copy link
Collaborator

fioan89 commented Apr 18, 2025

Thank you for the feedback @ethanndickson. Wildcard config support was added no too long ago.

@matifali
Copy link
Member

since it looks like you don't use wildcard SSH configs

@ethanndickson, we do have wildcard configs on by default with the option to opt out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants