Add support for codebase Indexing when using a remote VSCode connection

[strikeoncmputrz]

First off, Kilo Code is outstanding. Thanks for the awesome capability!

I am assuming that codebase indexing doesn't work for remote vscode instances. I spent a few hours troubleshooting codebase indexing. I figured it was an issue with my Qdrant workload or the embedding server I was trying to use. Using tcpdump, I noticed that vscode-server on the remote host wasn't actually initiating any outbound connections to the embedding server or qdrant. I verified the same from my local host which is running the vscode UI for the remote session.

I opened a new vscode window to edit files on my local filesystem and codebase indexing began to work immediately.

[Juice10]

Interesting @strikeoncmputrz! Thanks for sharing this. I'm curious what Qdrant url you are using there, is it http://localhost:6333 and if so, do you also have qdrant running on the remote machine? Or do you have it setup to something on the network that both instances can access?

[strikeoncmputrz]

Hey @Juice10 thanks very much for replying.

My qdrant url is https://qdrant.lan:6333. It's a k8s workload and its IP resolves to a host on my servers /24 subnet.

When I launch vscode in the local context from my laptop in a different subnet, there are no issues connecting to qdrant. When I launch a vscode remote session from a server that's in the same subnet as qdrant, Kilo cannot connect. From an SSH session on the same "remote session" server I am able to curl qdrant.lan.