Live data from Hacker News

GitHub Copilot is moving to usage-based billing

github.blog

431–440 of 583 posts

Re: GitHub Copilot is moving to usage-based billing

#431
post #101

Earlier quoted context omitted.

Yeah, totally. The recent pricing changes have just made my Copilot subscription go from great deal to awful value over night. I've been wanting to get off MS more generally and this is good motivation. Will be playing round with OR this week.

Just be aware OpenRouter charges a 5.5% fee, I didn’t know until recently. I like the product, and I think the fee is fair, but if you want the absolute best pricing then go direct.

Or you could use gcp Vertex or aws Bedrock and still have access to a bunch of FMs without a markup.

Re: GitHub Copilot is moving to usage-based billing

#434
post #25

I was curious why a company would still use the VS Code + Copilot sidebar method for coding, rather than something like Claude Code. Turns out there’s a GitHub Copilot CLI! I thought I was pretty familiar with available options, but no one in my circles ever mentions this product. It doesn’t seem to have much mindshare. Has anyone used it? What’s your experience? https://github.com/features/copilot/cli

> I was curious why a company would still use the VS Code + Copilot sidebar method for coding, rather than something like Claude Code. I use Claude Code, but I kept my Copilot subscription around mostly for really cheap usage of other models when I need to try a different one (which appears to be ending, in a sense) and also the autocomplete in Visual Studio Code which was really great across a bunch of files, I coul…

Cursor (paid) and antigravity (free) come to mind.

Re: GitHub Copilot is moving to usage-based billing

#435

so what's everybody using to get autocompletions in vscode? i've been using copilot just because $10 is cheap, but i use opencode for everything other than completions. i tried the continue vscode extension, and it seemed kind of janky. are there better options?

Windsurf has free tab complete and has been good for me. Antigravity has free tab complete as well but no idea if its any good

I tried antigravity, it worked great for a couple weeks and then Google changed their rate limits and ruined it - I’d get about 3hrs of work before all the ai features just stopped working.

Re: GitHub Copilot is moving to usage-based billing

#436

Earlier quoted context omitted.

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.

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.

Re: GitHub Copilot is moving to usage-based billing

#437

Earlier quoted context omitted.

> 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.

Judging by the multiple providers selling it for around the same price (including non-VC funded competitors): no, it isn't subsidized.

Re: GitHub Copilot is moving to usage-based billing

#438

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…

As someone that is on the enterprise side in a non-tech F500 company, what I'm seeing is some FOMO and need to be part of the hype cycle. We're about to plonk a bunch of money on more Copilot licenses. Something got in the water where all the C-levels the past two months are pushing everyone to use AI but when they bring up examples of their uses its like "I use it to rewrite my emails" or prompt 'engineering' ideas…

I'm at an org, where every medium to large company meeting talks about AI in similar breathless non-specific terms, yet m365 copilot is the only approved AI chat, and GH copilot the only AI coding tool.

Re: GitHub Copilot is moving to usage-based billing

#439

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...

Is there a way to use the autocomplete feature with an api?

No but autocomplete is not part of this billing change

Re: GitHub Copilot is moving to usage-based billing

#440
post #25

I was curious why a company would still use the VS Code + Copilot sidebar method for coding, rather than something like Claude Code. Turns out there’s a GitHub Copilot CLI! I thought I was pretty familiar with available options, but no one in my circles ever mentions this product. It doesn’t seem to have much mindshare. Has anyone used it? What’s your experience? https://github.com/features/copilot/cli

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.

Bun in general I don't see the benefit either.

Post reply on HN