Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub Copilot is moving to usage-based billing

github.blog

Post reply on HN
Print view View original

401–410 of 583 posts

Re: GitHub Copilot is moving to usage-based billing

#401

Post by NSPG911 »

hakunin wrote: post #157

Everybody 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…

exactly why i loved Github Copilot, you could pull of these shenanigans, and nothing would ever happen. That was the best part of it

but now, you get literally nothing

Re: GitHub Copilot is moving to usage-based billing

#402

Post by evilsnoopi3 »

cityofdelusion wrote: post #370
fooey wrote: post #360

Earlier quoted context omitted.

for my experience currently, I greatly prefer the VSCode Copilot extension experience over the Claude Extension I think VSCode only supports copilot for "autocomplete" too on top of that, you need GitHub Copilot for the PR reviewer functionality in GitHub

Huh, I find my copilot plugin to be so incredibly glitchy. My agents are always reporting that their shells are mangled that commands are truncated and all kinds of nonsense. Sometimes they spin up dev servers fine other times it just hangs waiting for a terminal response. So far I have found relying on the CLI from the model providers to be significantly more reliable. I do like the integrations with the IDE however…

I had this problem and it turns out it was my oh-my-posh command prompt customization. VS Code injects certain control characters into the output stream for agents to observe events and the theming runs after those mechanics are hooked up so it can interfere. Updating to the latest oh-my-posh fixed it for me.

Here's the oh-my-posh GH issue[0] in case your problem is similar but not solvable with a simple package update.

[0]: https://github.com/JanDeDobbeleer/oh-my-posh/issues/7029

Re: GitHub Copilot is moving to usage-based billing

#404

Post by mullingitover »

my002 wrote: post #4

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.

The point of this loss leading is to properly hoover up the money in the pockets of enterprise customers, get them locked into the idea that they need the latest and greatest cloud-based model, while simultaneously starving everyone of the memory they'd need in order to run competent models locally.

In not-too-distant future we're going to be running better models on our phones than we can buy access to today in the cloud. Skate where the puck is going: soak the customers until that day comes.

Re: GitHub Copilot is moving to usage-based billing

#405

Post by NSPG911 »

born_a_skeptic wrote: post #103

I wonder if GitHub (Microsoft) is implicitly betting that enterprise demand is sticky enough to absorb these rates, especially given that Opus 4.6 “fast” was being listed at a 27x multiplier. Maybe they saw enough usage at that price point to conclude the demand is real. Or maybe the strategy is to keep the enterprise customers who can justify it while shedding heavier individual and power-user usage. The interesting…

Opus 4.6 "Fast" was originally at 10x, literally the same cost as Opus 4.1. After promotion period, it was 30x.

Re: GitHub Copilot is moving to usage-based billing

#406

Post by quietsegfault »

everfrustrated wrote: post #193
theanonymousone wrote: post #162

Something is hilariously off here: Why should I pay $10 and be forced to use it by the end of the month, while I can pay $10 and have it last as long as I want? Their "API pricing" is exactly the same as that of providers: https://docs.github.com/en/copilot/reference/copilot-billing...

I'm thinking the same. Downgrade to Pro and use OpenRouter (same price) for overage. Seems a massive loss for Microsoft. Presumably there's a further rugpull to come.

OpenRouter charges a 5% (?) fee for buying credits.

Re: GitHub Copilot is moving to usage-based billing

#407

Post by tclancy »

ctoth wrote: post #255
hirako2000 wrote: post #198

Earlier quoted context omitted.

It does feel like the music is about to stop. It has been years now, of cash injections, investors can't keep feeding the beast forever.

It has been years now of reading this same comment... Surely people can't keep typing it forever.

I’m not willing too, but I can set up a cron job to Claude -p the task.

Re: GitHub Copilot is moving to usage-based billing

#408

Post by djeastm »

mkhalil wrote: post #326
my002 wrote: post #4

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.

Why would folks be better paying 5.5% fee to OpenRouter ("Open") if most people just use one or two providers? Just use the provider's API.

The routing automatically routes you to other inference providers (for the same model) if/when the original provider goes down.

It's a convenience cost, for sure, but it's not valueless in a fast-moving world. Certainly if you're comfortable with one provider and it's cheaper, do that.

Re: GitHub Copilot is moving to usage-based billing

#409

Post by sergiotapia »

giwook wrote: post #71
my002 wrote: post #4

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.

Lots of us have noticed that usage limits for Claude have been nerfed in recent weeks/months. If anything, these new multipliers are more transparent than anything OpenAI or Anthropic have communicated regarding actual costs and give us a more realistic understanding of what it's costing these providers. The fact that we were able to get such a substantial amount of usage for $20/$100/$200 a month was never meant to…

That is folly because there is very minimal cost to switching providers, let alone models.

Re: GitHub Copilot is moving to usage-based billing

#410

Post by Gigachad »

cheema33 wrote: post #392
Gigachad wrote: post #378

Earlier quoted context omitted.

The hardware to run deepseek is still incredibly expensive.

> The hardware to run deepseek is still incredibly expensive. Deepseek API pricing is very low compared to Anthropic/OpenAI API pricing. For many, the 300% difference in pricing may be difficult to justify, if the quality difference is very small. And there will be many tasks where the most expensive/the best model, is not needed. Currently many people end up using Opus 4.7/GPT 5.5 for many tasks without thinking abo…

Is deepseek still on subsidized pricing though.
Post reply on HN