Twinny installs itself on ssh host & not locally

[disarticulate]

Describe the bug
See potential related issues: #242
Twinny installs itself on remote ssh project vscode server and may not have access to "localhost" on client machine. Many plugins have the option between installing locally and on remote.

To Reproduce
Connect to a VSCode ssh project & install twinny. If there's no path to the ollama server, it gives error

Expected behavior
Twinny should be selective about where it installs when presented with a ssh project folder, since it's a typical work flow and Ollama on the client machine may not be available to the project folder.

Logging
See: See potential related issues: #242

API Provider
Ollama

Chat or Auto Complete?
All model inputs

Desktop (please complete the following information):
Assume it's a bug everywhere.

[rjmacarthy]

Thanks for reporting, any ideas what needs to change to fix it? By the way I did not investigate it yet. Many thanks!

[disarticulate]

(I've never developed a VScode extension)
There's probably two options:

1. Forward the necessary ports for ollama. Not sure if this is a two way street, but I know VSCode can open ports for development servers; but you'd need to reverse the polarity
2. https://stackoverflow.com/questions/58236172/visual-studio-code-how-to-run-extension-locally-on-my-laptop-when-connected-to

#2 is probably the correct work around for now. There also needs to be documentation in the settings clarifying ensuring access, and probably a check that has an error clearer than #242