copilot-language-server experience

[arunoruto]

Github dropped their copilot SDK with the copilot-language-server (LSP server, I guess?).
Has someone tried it out? Share your experience with everyone :)

EDIT the needed LSP feature to enable CLS to work with Helix is being tracked in this issue #13039

[adpande]

I am trying to configure it right now. No success yet

[arunoruto]

My PR to nixpkgs just came through, so I am also testing it, but to no avail :)
It seems like an initial sign-in is needed to authenticate, but Helix doesn't support this command/feature. I guess we have to wait until they enable login via token.

[RobbieMcKinstry]

I'm working on a plugin using Steel to get it to work. I've managed to authenticate using the method in the README -- you send a message to the LSP, and it echos back a URL the user opens to authorize this device. The authentication persists in between editor sessions (I'm not sure how) so at least for now it's a one-time setup.

However, that wasn't enough to get Copilot suggestions. I suspect @kirawi's right, and that the LSP message Copilot uses for e.g. in-lay hints isn't supported in Helix yet. I plan to work around it with some Steel code.

[arunoruto]

Seems like the Auth process got a bit simplified via the latest release: github/copilot-language-server-release#3 (comment)

You can use a token in your environment to authenticate via the LSP!

[kirawi]

The required iteration of the LSP specification is not yet stabilized, so we can't implement it yet, I think.