Github copilot agent pricing is different between kilo and copilot extension

[SeanBannister]

The only reason I don't use Kilo over Copilot is when you use agent mode in copilot every request the agent makes is counted as a single request. You're billed when you enter the prompt and hit enter.

But in Kilo every agent request is a seperate request to the github copilot API.

With Copilot Chat now being open source (https://github.com/microsoft/vscode-copilot-chat/) is it possible to reverse engineer the API that copilot uses so we can get the same pricing model when using GitHub copilot in Kilo.

[janpaul123]

Interesting idea! Let's see how that shakes out when others do this first; in situations like this companies are often initially not very clear on what's acceptable uses of their APIs.

[adamhill]

According to this video the one-vs-many calculation / decisions are done on the backend of Copilot. They are discussing a premium requests and how it counts them when you set some setting in Experimental.

https://www.youtube.com/live/QcaQVnznugA?si=br7L8iMgoTGtJhXF&t=4617

[druellan]

Zed uses the Language Server Protocol instead of the Language Model API to connect directly to Github, I wonder if that might be a better solution:
https://github.com/zed-industries/copilot
https://github.com/github/copilot-language-server-release