The era of subsidised inference is truly ending. The new model multipliers ( https://docs.github.com/en/copilot/reference/copilot-billing... ) seem like a huge leap, though. From 1x to 6x for new-ish GPT and Sonnet models. 27x for Opus... Seems like folks would be better off with OpenRouter instead.
Even Sonnet 4.6 is 9x multiplier (previously 1x)! The only model I even used on Copilot was Sonnet and now its got a ridiculous multiplier. At this point they might as well just charge per Million tokens like every other provider instead of having a subscription.
GitHub Copilot is moving to usage-based billing
481–490 of 583 posts
Re: GitHub Copilot is moving to usage-based billing
#482Everybody who says it's a 5-9-27x seems to not be aware of the obvious loophole. More like 50x increase. You were able to use over $500 worth of Opus on a $10/mo Github plan easily, no hacks. You could just prompt "plan this out for me, don't stop until fully planned, don't ask any questions", and you would get ~$5 worth of planning in one 3x request. At 100 requests/mo, each easily reaching $5, that's easy $500 wort…
I created a 4 subagents that polled for new tasks, and restart after ~5h.
It was a great run.
Re: GitHub Copilot is moving to usage-based billing
#483Earlier quoted context omitted.
I'm curious about the opposite: Why would anyone use the CLI when, at least with Copilot, the VSCode plugin is super tightly integrated with VSCode, meaning the agent can see everything I can see. There's no mismatch in linter calls where I can see a lint in the ide that the agent can't find for example. I've had this problem even using CC in their VSCode extension, so I can't imagine it's not an issue in the CLI as…
I use the Claude Code VSCode plugin for 80% of my work. I prefer it because I can look at the code (although not as often anymore) and config (very often!) easily. It also lets me jump to previous conversations easily. There are a few cases where the CLI makes sense. One big one is if you are running multiple simultaneous sessions on a remote server using Tmux to have them preconfigured when you reconnect is nice. Bu…
I do that when I want to, but for me using agents in IDE is like looking with one eye covered.
Re: GitHub Copilot is moving to usage-based billing
#484Re: GitHub Copilot is moving to usage-based billing
#485Earlier quoted context omitted.
Which in turn owns Twitter. SpaceX is now a social media company in addition to a rocket company. One theory I think Matt Levine posited, is that SpaceX will go public with dual-class stock that gives Elon control even with a minority ownership stake, and will subsequently buy Tesla, which doesn't have dual class stock, making SpaceX the singular "Elon Musk company", with him having operational control despite being…
That theory aligns with Elon's long-held dream of X as the "Everything Company".
Re: GitHub Copilot is moving to usage-based billing
#486Earlier 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…
Why on earth would that happen when everything else is moving into the cloud to tie it to ever-escalating subscription fees and prevent piracy?
Even with gaming, where running high-end 3D games in the cloud seems like madness and inevitably degrades the quality of the experience, they won't stop trying.
Re: GitHub Copilot is moving to usage-based billing
#487Earlier quoted context omitted.
I'm already on Pro. Why should I keep it?
Only reason to keep it is if you like their UX and auto-complete. Everything else is on pay per use and if you don't use all of it (good luck with the 5 hour and week caps) you have just paid more for the auto-complete The deal is really pretty much garbage now and I believe that is the intent.
$10 a month for auto-complete on a good UX is good value IMHO.
Re: GitHub Copilot is moving to usage-based billing
#488Re: GitHub Copilot is moving to usage-based billing
#489Earlier quoted context omitted.
Is deepseek still on subsidized pricing though.
Judging by the multiple providers selling it for around the same price (including non-VC funded competitors): no, it isn't subsidized.