Understanding the API with GitHub

[omrisarig13]

Hello,

First, thank you for an awesome plugin - it is working extremely well for me, helping bringing much needed functionality of GitHub Copilot to nvim.

My company currently have a policy, where it's not allowed to use any non-official GitHub Copilot plugins. I'm trying to understand the communication between the plugin and GitHub, to prove that it is essentially not different than using the official plugin for different IDEs that do the same (such as the VS code plugin).

I've looked in the code, and tried to search online, but I couldn't find a definite answer regarding the API of Copilot.

I've seen that the code accesses GitHub through api.githubcopilot.com for example, but I couldn't find any documentation of this API from GitHub's side.
I've also tried looking for GitHub's own API for Copilot, but couldn't find anything that's officially documented. I did find this discussion, writing that there is no official API, and linking an unofficial, reversed-engineered protocol.

So my question is: Where does the API toward GitHub coming from? How was it developed for this plugin?
I'd be extremely happy for any information - and also information such as "it was copied from XXX" can really help me.

Thank you!

[deathbeam]

It was reverse engineered with mitmproxy mostly. But zed editor if i remember correctly is also using the exact same api, and recently microsoft actually open sourced their vscode chat plugin, which also uses the same apis (as this was mostly discovered through mitmproxy in vscode in first place): https://github.com/microsoft/vscode-copilot-chat

[omrisarig13]

Thanks for the fast and informative response!