Live data from Hacker News

GitHub Copilot is moving to usage-based billing

github.blog

41–50 of 583 posts

Re: GitHub Copilot is moving to usage-based billing

#43
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've used it quite a bit. There are a lot of AI terminal coding products and this is another one. It works well, handles sub-agents without issue and does a reasonable job operating in the Copilot ecosystem. It handles mid-task questions and such we well.

I’ve tried OpenCode, Claude Code and Codex CLI. But was just shocked that Microsoft has a version I hadn’t even heard of.

Personally I got CLI fatigue and am happy with Conductor for now, but things are moving fast in this space.

Re: GitHub Copilot is moving to usage-based billing

#44
post #30

Current multipliers vs from June Opus 4.6 3x -> 27x Opus 4.7 3x -> 27x GPT 5.4 1x -> 6x EDIT: only applies to annual plans

GPT 5.4mini is even worse, from 0.33x to 6x which is ~18 times more expensive now.

GPT-5.4 and GPT-5.4 mini are now the same price, which, why?

Re: GitHub Copilot is moving to usage-based billing

#47

Current multipliers vs from June Opus 4.6 3x -> 27x Opus 4.7 3x -> 27x GPT 5.4 1x -> 6x EDIT: only applies to annual plans

Not apples for apples.

Before:

- Opus 4.6 each premium request is 3 premium requests

After:

- Opus 4.6 each dollar spent is 27 dollars in copilot AI Credits.

Given that you'll receive 19 dollars of AI Credits in Business plan, that means you can probably say 1 "hi" to opus per month.

Post reply on HN