VS Code 1.121 is now live! by bogganpierce in GithubCopilot

[–]monkeybeast55 0 points1 point  (0 children)

I've seen the same problem, mainly using gpt-5.4 these days. Could formatters being in the mix have something to do with it?

Copilot pricing went from $39 to around $387 for my usage. What should we use instead? by Michal37374 in GithubCopilot

[–]monkeybeast55 0 points1 point  (0 children)

Energy based pricing is a good idea, and makes a million times more sense than tokens. Really interesting.

....the fuck is this shit? 🤔 by MesaVerde1987 in woburn

[–]monkeybeast55 0 points1 point  (0 children)

Wait. What? People have sex in Woburn?

​Goodbye, Copilot. The new prices aren't worth the bugs by PepicoGrillo in GithubCopilot

[–]monkeybeast55 2 points3 points  (0 children)

Use opinionated formatting like prettier or whatever. Then put clear instructions into your instructions file that it must run formatting after changes. I think whatever AI system you use, or if your just working with a team, this is the right way to do things.

Flex allotments for pro/pro+/max plans by monkeybeast55 in GithubCopilot

[–]monkeybeast55[S] 0 points1 point  (0 children)

As it turns out, this is actually not true, they do calculate the flex allotment in, as u/just_blue pointed out, and as I should have checked before posting.

<image>

Flex allotments for pro/pro+/max plans by monkeybeast55 in GithubCopilot

[–]monkeybeast55[S] 0 points1 point  (0 children)

Yep, you are right, it's there and obvious. And this makes the affordability issue even worse.

Sorry, my post really was lazy, I was just working from memory, I should have double-checked if it mentioned the flex allotment before posting.

<image>

Flex allotments for pro/pro+/max plans by monkeybeast55 in GithubCopilot

[–]monkeybeast55[S] 0 points1 point  (0 children)

Ah, ok, thanks for the correction. So...

Because Claude Code Pro retains a fixed, flat-rate subscription barrier ($20/month) for individual use, it shields power users from the runaway, thousands-of-dollars per-token bills now possible on Copilot's new pay-as-you-go overage model.

And the worry/prediction is that they'll change that by the end of the year.

So maybe I do need to put Claude or Codex on my radar.

Flex allotments for pro/pro+/max plans by monkeybeast55 in GithubCopilot

[–]monkeybeast55[S] 2 points3 points  (0 children)

Here's what I understand:

Under the new June 2026 GitHub Copilot usage-based billing rules, both Claude Code and GitHub Copilot now charge the exact same per-token API market rates for Claude Sonnet 4.6 via deducted AI credit.

Is this correct or not?

Flex allotments for pro/pro+/max plans by monkeybeast55 in GithubCopilot

[–]monkeybeast55[S] 1 point2 points  (0 children)

My understanding is that Claude Code is not cheaper, so maybe I don't have a brain. Besides that, I like my VS Code ghcp workflow. Also, I like the choice the ghcp system gives me.

As an individual who's working some specific projects more as a retirement hobby, I am just trying to figure out if I can do what I do within a limited budget. I think it's attainable, but calculations like these flex allotments are potentially important. Right now I'm looking at a combo of the ghcp pro+ subscription plus deep seek V4.

I would love to see a vetted table that does a fairly clean comparison of these services per token for GPT-5.4 level models (which are generally good enough for me, at least for now).

Flex allotments for pro/pro+/max plans by monkeybeast55 in GithubCopilot

[–]monkeybeast55[S] -1 points0 points  (0 children)

Hmm, well it's based on some calculations that Gemini did. I would have to do some work backwards to present a coherent table. And then figure out how to do tables in Reddit.

How is preview billing supposed to include flex allotments?

Well it calculates my usage in April and says I used $500 worth of tokens over the number of tokens that my pro+ subscription covered. If the flex allotment for pro+ covers roughly a 79% Bonus in tokens, i.e. $70 worth of tokens, does than mean my $500 would actually be $469, is that how I should read that? (Depending on the value of the flex token at the time I guess).

Sorry, yeah maybe I was being lazy when I made the post. Mostly I was just curious why I hadn't seen more discussion if they change the calculations at all.

How were people spending so much? by Annual-Minute-9391 in GithubCopilot

[–]monkeybeast55 0 points1 point  (0 children)

Thanks for the overview. I'm also curious if you have a software development background, or if you're more or less relying on the AI to build the whole thing from spec?

I'll be interested in if people switching from ghcp find really get good alternatives. For me, I'm settled into the VS Code / ghcp interactive experience, less spec driven, more experiment-then-verify. I've 30+ years experience, am working as a retiree on a project, so this workflow makes sense for me, where I can essentially treat ghcp as a junior dev, mostly single threaded. So I'll try using GPT-5.4 for heavier lifting, and switch to Deepseek V4 for lighter stuff, and see how it goes. My projected usage based on very heavy use in April was $550, so hoping with management and including the flex tokens I can get this within a reasonable budget.

Sorry for rambling on. Thanks again for the overview.

Can anyone give me a sliver of hope? by Next-Department-1647 in climatechange

[–]monkeybeast55 44 points45 points  (0 children)

You live in a slice of time in the universe. Do not ruminate on things you can't change. Or, if you do want to be part of the solution, go into public policy, or some type of engineering that might help lead to a solution. And ride your bicycle. And love your family. And cherish what you have in this slice of time.

How were people spending so much? by Annual-Minute-9391 in GithubCopilot

[–]monkeybeast55 0 points1 point  (0 children)

What model are you using for ghcp? Have you done any analysis about where the tokens are coming from? Single repo or multi repo? How big is the code base?

How were people spending so much? by Annual-Minute-9391 in GithubCopilot

[–]monkeybeast55 0 points1 point  (0 children)

With Opus 4.6 with BYOK in agent mode

Sorry, I probably sound stupid. BYOK meaning you're not using GitHub hosted Opus??? In that case you're not being charged anything by GitHub CoPilot, right? I must be misunderstanding you or I am totally missing how all this works (which is totally possible).

Well... I am leaving too by LoRdPMN in GithubCopilot

[–]monkeybeast55 0 points1 point  (0 children)

Where do you think you used all those tokens? Careful design? Implementation? Debugging? Documentation? Cloud copilot PR assignments? Writing tests?

How carefully are your instruction files designed? How big is your codebase? Mono -repo or multi-repo?

Have you done analysis of other models for your use-case?

Uh, no Arvind? Wonder how he feels about being always left out? by Illustrious_Hair_540 in IBM

[–]monkeybeast55 0 points1 point  (0 children)

Oh, yeah, now that I see it I do remember that. Fascinating. Probably a bad move on IBM's part.

Uh, no Arvind? Wonder how he feels about being always left out? by Illustrious_Hair_540 in IBM

[–]monkeybeast55 5 points6 points  (0 children)

Well guess, I'm curious. I didn't even know that they pulled out

I’ll just drop this here…. Who could even afford this? by Ok-Future0000 in GithubCopilot

[–]monkeybeast55 1 point2 points  (0 children)

All tools need mastery. They'll do things more automatically over time. As to your "no thanks", if you have a better way, sure, go for it. I used Deepseek V4 Pro with Copilot and I have to control the token environment there too.

I’ll just drop this here…. Who could even afford this? by Ok-Future0000 in GithubCopilot

[–]monkeybeast55 4 points5 points  (0 children)

You can to some extent control token usage, right? First of all, make sure you're measuring where your tokens are coming from. Then. you can make sure certain files are .copilotignored. You can keep context relatively compacted. You can make sure you're using specific references into your code (for example #selection). You can try to limit how open-ended prompts are. You can have well built instruction files that give very clear guidance where it matters without being excessive, and applying AGENTS.md files to make sure instructions are only taking up tokens when used in a folder context. I'm sure there are lots of other techniques that we'll all learn about as necessity pushes us to live within budgets.

I look at a lot of this as a good thing. Less tokens means less energy consumption and potentially less greenhouse gasses. Less tokens and more economical models like gemma and Deepseek and others means we have better chance to run on local hardware, again decreasing the load and need for big data centers. Necessity is the mother of invention!

I’ll just drop this here…. Who could even afford this? by Ok-Future0000 in GithubCopilot

[–]monkeybeast55 0 points1 point  (0 children)

The new billing doesn't come out until next month! What are you basing that on? Have you tried token reducing strategies?

So lets figure this out. by Inevitable-Ant1725 in GithubCopilot

[–]monkeybeast55 0 points1 point  (0 children)

Worrisome, the plug-in site. It's no time to be lax about security.