This reminds me, I have to cancel co-pilot...
GitHub Copilot is moving to usage-based billing
291–300 of 583 posts
Re: GitHub Copilot is moving to usage-based billing
#292Earlier quoted context omitted.
> At this point they might as well just charge per Million tokens like every other provider instead of having a subscription. Pretty sure that's what they will eventually do
... that is exactly what they will do. Just click the link in this thread, or read the headline.
Why the multipliers then at all?
Re: GitHub Copilot is moving to usage-based billing
#293Earlier quoted context omitted.
Yeah it was crazy. Nowadays I use pi with OpenAI GPT 5.4/5.5, which to me seems both better and more generous than Claude. I supplement it with OpenCode Zen to get access to a bunch of models at token cost, and OpenCode Go ($10/mo) to get subscription-style access to Kimi, GLM and friends.
What is pi?
The minimalistic harness famous for having a tiny system prompt (avoids context pollution), and being what underlies openclaw. (https://pi.dev)
Re: GitHub Copilot is moving to usage-based billing
#294Re: GitHub Copilot is moving to usage-based billing
#295Re: GitHub Copilot is moving to usage-based billing
#296I'd be fine with it if they can make Sonnet 4.5 unlimited. I haven't personally seen any major differences between 4.6 or any of the other newer models. Claude 4.5 seems to be the right balance and works great for me.
Re: GitHub Copilot is moving to usage-based billing
#297What's the current situation for coding with Local LLM's on decent hardware? I have an M3 Max with 64 gb of ram and am thinking I should start looking at Ollama and Opencode? Is this a useful stack for smaller personal projects?
It’s getting there. You could give a try with qwen 3.6. It’s worth paying for better models in the cloud, but local models are now better than nothing.
Re: GitHub Copilot is moving to usage-based billing
#298What's the residual value of Copilot after the changes? For Enterprise plans, even copilot code reviews will be charged at token price + github action minutes for the execution of the review. One can roll one's own reviewer and have it spend the API tokens as well. At least one will be able to select the subset of files for the change set, if needed.
The background agents will also depreciate in value because of their harness that's a black box that's not optimized for token usage at all. Rolling one's own will be a better choice here.
Re: GitHub Copilot is moving to usage-based billing
#299Earlier quoted context omitted.
Did anyone really expect AI to be cheap? If/when it gets to the point where it can replace a skilled worker, the service can be sold for close to the same price as that skilled labour. But the AI can run 24/7, reliably, and scale up/down at a moments notice. There's not going to be much competition to drive prices down, the barriers to entry are already huge. There'll likely to be one clear winner, becoming a near-mo…
I do. "Commoditize your complement". Want to sell lots of silicon? Give away good local models to run on that silicon. Even if SOTA models in the cloud are a few percentage points better, most work can be routed to local models most of the time. That leaves the cloud providers fighting over the most computationally intensive tasks. In the long term, I think models are going to be local-first. (Unless providers can fi…
> In the long term, I think models are going to be local-first.
Why? There's an inherent efficiency advantage to scale, while the only real advantage for local models (privacy/secrecy) hasn't proven convincing for broader IT either.