this post was submitted on 22 Jun 2023
13 points (100.0% liked)

Programming

13368 readers
2 users here now

All things programming and coding related. Subcommunity of Technology.


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 1 year ago
MODERATORS
 

Copilot is great, but a hundred bucks for what is basically a smart autocomplete seems a bit much - mostly, I hate the fact that the code is constantly transmitted to github (my repos are mostly local) - are there any reasonably convenient options for doing this without github looking over my shoulder all the time? I'm using VSCode but not wedded to it.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] Saauan@beehaw.org 2 points 1 year ago (1 children)

For a research project, I'm currently looking into open-source GitHub Copilot alternatives and monitoring options. As someone else already said, you can use the FauxPilot self-hosted backend. It works pretty well, but you have to host it yourself. You can use this backend with a frontend extension, such as the official GitHub Copilot plugin (with telemetry disabled) or with the FauxPilot VSCode extension. However, I found that the FauxPilot extension is very lackluster in terms of features compared to the official extension (On top of my head, it does not have any caching mechanism, nor does it cancels the requests already made if you continue typing (they just pile up), and does not have any sort of filter for the completions. All of these lead to way too many generations being requested from the model.

TL;DR : If you want to use the GitHub Copilot extension, without GitHub looking over your shoulder, you can use the FauxPilot backend and opt-out of the telemetry from VSCode/Copilot (I don't know which one needs to be disabled) (or do as I did for research purposes, and change the telemetry url in the source code to a localhost one).

[โ€“] fuser@quex.cc 2 points 1 year ago

Thanks for taking the time to respond - it sounds like an interesting research project. This indeed looks like the ideal long-term solution, where the model is hosted locally and no code is sent to the internet while it's under development. I'll take a closer look at this - thanks again.