Changes to GitHub Copilot Individual Plans
Posted by zorrn 19 hours ago
Comments
Comment by K0IN 8 minutes ago
Comment by davepeck 18 hours ago
I get the impression that the intersection of HN posters and Copilot users is quite small in practice; that Claude Code and Codex suck up all the oxygen in this room. But it seems plausible we’ll see similar “true costs greatly exceed our current subscription pricing” from Anthropic and OpenAI someday soon…
Comment by sunaookami 2 minutes ago
Comment by firecall 1 hour ago
I just found out via other news sources, and was surprised I hadn't seen it on HN already.
Comment by andromaton 15 hours ago
I never understood the low visibility.
Expensive ram is annoying. I don't look forward to expensive ai.
Comment by alexaholic 7 hours ago
The change applies to existing subscriptions, some paid a year in advance.
Comment by wdroz 2 hours ago
> If you hit unexpected limits or these changes just don’t work for you, you can cancel your Pro or Pro+ subscription and you will not be charged for April usage. Please reach out to GitHub support between April 20 and May 20 for a refund.
Comment by alexaholic 7 hours ago
Opus 4.6 had a 3x multiplier in Pro. Now the new Opus 4.7 model has 7.5x in Pro+, which offers 5x more requests, but costs 4x more than Pro. So now Opus is essentially 2x the price it used to be.
It’s likely that Sonnet 4.7 will be the new 3x model in Pro — https://github.blog/news-insights/company-news/changes-to-gi...
This whole thing is a massive asshole move, and probably illegal in all countries with a minimum set of consumer protections.
Comment by everfrustrated 19 hours ago
I've been using the Pro+ with Opus 4.6 very successfully and being charged 3x rate was mostly acceptable.
But removing Opus 4.6 and replacing with Opus 4.7 with a 7x rate is just insane!
Comment by auguzanellato 7 hours ago
Comment by diath 19 hours ago
Comment by rectang 17 hours ago
Now it's going to cost me an upgrade to $39 Github Pro+ to keep using Opus, and even then it's with much higher multipliers. I don't fully understand the extent to which this reflects actual costs for Opus versus Microsoft leveraging network effects to discourage the usage of a competitor.
I didn't really want to wander outside of VSCode just yet because I was happy with VSCode/Copilot/Opus-4.5 and I don't want to spend all my time experimenting when stuff is changing so fast. But I guess my hand has been forced.
Comment by thecopy 7 hours ago
For what its worth, i have been paying for Pro+ and i still got locked out of Opus. I only have access to Opus 4.7 at 7.5x
Comment by diath 17 hours ago
This was my first thought too but apparently you can just use Claude Code within VSC: https://code.claude.com/docs/en/vs-code
Comment by rectang 13 hours ago
Comment by WhiteDawn 19 hours ago
Looks like I'm ending my subscription, good (likely too good, no way my account was even remotely within profitable range) access to opus-4.6 was the only reason I used this at all.
Comment by p1necone 12 hours ago
I had the exact same issues with the latter - randomly stops working, wipes chat history, just generally seems to be totally broken. But the former works totally fine and still lets you select sonnet/opus. My experience was before this recent 4.6 -> 4.7 change though.
Comment by benwills 13 hours ago
Opus 4.7 is available today for 7.5 credits per prompt.
They have also suspended new signups.
After testing all of the major IDEs/tools that integrate with LLMs over the last four weeks, I was happy to settle on Copilot. I, and others, seem to be a lot confident in that decision. Especially since there seems to be no refund path for people who prepaid for a year.
In my 30+ years online, I've never seen an industry change so much in terms of pricing, service levels, etc, as I have the last two months.
I'm really curious where all of this lands, and if AI coding tools will be something that only a small percentage can genuinely afford at a competitive level.
Comment by p1necone 12 hours ago
Warning: baseless speculation/theorizing ahead.
This is the consequence of LLM inference being really expensive to run, and LLM inference companies being really attractive to VCs. The VC silly money means their costs are totally decoupled from revenue for a while, but I guess eventually people look at incomings vs outgoings and start asking questions.
Previous big trends like SaaS apps, NFTs, blockchain etc were similarly attractive to VCs (for a period of time at least for the last two, the first one is still pretty attractive to VCs), but nowhere near as expensive to run so the behaviour of the companies running them wasn't quite the same.
Comment by theshrike79 8 hours ago
So:
- DO use AIs to build tools for yourself faster. If the AI goes away, the dashboard and scripts you made will still work.
- DO NOT build your business on top of 3rd party AI services with no way of swapping the backend easily. The question isn't whether there's going to be a "rug-pull", but when it happens. It might be sudden like this one or gradual where they just pump up the price like boiling a frog.
Comment by aleksiy123 18 hours ago
I guess overall probably was a good decision.
But 7.5x as well as quota limits is pretty hard to swallow.
The annoying thing about the quota limits is they make it really awkward to actually fully utilize the 1500 premium requests you are paying for.
Like if you don’t plan working around the daily and weekly quotas you may not actually be able to utilize your full request allocation.
Claude has the same issue. Single session blows through the quota.
Comment by hokkos 16 hours ago
Comment by fkarg 15 hours ago
From what I've been gathering, this split in success seems to depend a lot on the types of tasks, the domains / programming languages / frameworks used, and style of prompting.
I couldn't get 5.2 to follow instructions for the life of me, even when repeating multiple times to do / not do something. 5.3-codex was an improvement and 5.4 while _usually_ decent still regularly forgets, goes on unnecessary tangents, or otherwise repeatedly stops just to ask for continuation.
Sure, I'm paying 3x more per request, but I'm also doing 5x fewer requests.
Or well, used to. Still bummed about them dropping 4.6.
Comment by rectang 14 hours ago
As far as I can tell, the distinctive feature of my workflow is that I'm giving it small, contained single-commit-sized tasks and limited context. For instance: "For all controller `output()` functions under `Controller/Edit/` and `Controller/Report/`, ensure that they check `Auth::userCanManage`." Others seem to be taking bigger swings.
Comment by theanonymousone 5 hours ago
But seeing that they are stopping to get new subscriptions, and rumours/evidence that they plan to increase coefficients of remaining models, it seems they want us to see "the writing on the wall"
Comment by aleksiy123 15 hours ago
It felt like I constantly have to go back and either fix things or I just didn't like the results. Like the forward momentum/progress on my projects overally wasn't there over time. Even with tho its cheaper it just doesn't feel worth it, to the point I start to feel negative emotions.
I'm actually a bit worried that I've somehow become to feel more negative emotions with agentic coding. Quicker to feel frustrated somehow when things aren't working.
Comment by walthamstow 16 hours ago
Comment by thecopy 7 hours ago
Comment by alexaholic 7 hours ago
Comment by thecopy 7 hours ago
Comment by qaz_plm 16 hours ago
Comment by literallyroy 13 hours ago
The per-request model was pretty insane.
Comment by sovietmudkipz 13 hours ago
That's not how my creative energy works. I have time that I want to solve problems, and I want to solve them. I don't want a cooldown timer applied to solving a problem. Not to mention the anxiety of realizing that while I sleep I could have burned tokens in that time.
I'm incredibly disappointed when I sat down to my hobbyist programming time and realized copilot was suddenly and dramatically changed in a way that is incredibly disheartening.
Meter my token usage DON'T tell me when I can use them! ARGH.
Comment by p1necone 14 hours ago
Given that they've already silently had session + weekly rate limits for the past couple weeks already at least (I've hit them), I wonder if this change is just making them visible to the user, or if it's actually tightening them too.
If it's the former then I can say they're still significantly more generous than claude pro (on the pro+ plan), so this might be okay. If it's the latter, and the new limits are similar to claude pro then copilot is going to be significantly less useful to me.
Comment by alexandra_au 5 hours ago
They're all operating at a loss, enshittification is coming for us all.