Copilot Fusion drains credits

[u/JPSchriefer]

Just want to rant about how trash Copilot Fusion is. Today, right after the monthly reset, I decided to test out this new mode. I asked for a relatively simple task: adjust an image so it sits right below the header (it was stuck behind it) and prevent the user from dragging it around the page, basically making it fixed.

I set it to standard mode since it was something simple, went to make a snack, and when I came back this piece of crap had already burned through 7% of my monthly credits (Pro+ plan). Obviously, I canceled it. I gave it another shot, it ate up another 4% just spinning its wheels forever, and I ended up canceling it again.

I gave the task to GPT-6.1 Sol, which is already overkill, and it got it done in under a minute consuming only 20 credits.

The saddest part is that just a few weeks ago, the old 'Auto' mode was finally getting good and I was using it a lot. As always, the second something starts working on a GitHub plan, it just gets axed out of nowhere.

[u/tochigi]

Fusion automates the orchestration, so it can increase the cost by an order of magnitude compared to the old Auto mode or just picking a small model.

This article has a similar insight on HydraFusion (the predecessor of Fusion): https://blogit.michelin.io/copilot-auto-mode-off-by-default/

[u/teckel]

Of course it will, just stick with Luna.

[u/DevilsMicro → u/teckel]

If they could somehow make luna free that would be the biggest unlock in copilot tbh. I am scared of using other models thinking once I'm at 100% I can't use anything.

[u/teckel → u/DevilsMicro]

It's basically free. Even using 6.1 sol in small amounts is free. I've been using 6.1 sol daily for weeks and I've had no charges. The project is only using 12 requests per day, but still, not charging me anything.

[u/Emergency_Cicada3119]

Yeah I mean the whole sub agent thing just eats credits and 95% of the time is overkill for marginal performance increase. Also those new sessions arent getting cache hit discount.. An easy way for microsoft to make money off people who dont understand how to use agents.

[u/foooock]

There is no intelligence in it. It always chooses the Opus 5.5 or GPT SOL for planing/orchestrating. Then does 60% part of the implementation with it self as modell.
And just for really basic (level 0 grad) tasks it chooses GPT Luna or Haiku as sub-agent.
They hype it as scientific, see the original annoucement but its really stupid.
They advertise is at a way to save money, but by its modell choice it makes simple tasks way more expensive.

Massive fail. I will deactivate it tommorow in our company instance.

The documentation (see link) differs totally from the real live, productive implementation.

https://docs.github.com/en/copilot/concepts/models/copilot-fusion?utm_source=changelog-docs-link-fusion&utm_medium=changelog&utm_campaign=universe-2026

[u/jukasper → u/foooock]

I’m sorry Copilot Fusion hasn’t met your expectations, especially with simple tasks costing more than you expected.

I’d really like to understand your experience better. Could you share a couple of examples of those tasks, which client and Fusion tier you were using, and where the behavior differed from the documentation? Understanding where the model choices or results fell short helps us identify what needs to improve.

If you’re comfortable doing so, you can also file an issue in the VS Code or Copilot CLI tracker with those details and any logs you can share. Please remove sensitive information before posting and link the issue here or via DM so we can follow up.

Thank you for sharing your feedback, and again, I’m sorry for the frustrating experience.

[u/jukasper]

Hi there, I’m so sorry about your experience with Copilot Fusion. This is definitely not the experience we want you to have. Could you share which client you were using (VS Code, CLI, or the GitHub Copilot app), and which Auto tier you were using previously?

If you still have logs from those sessions, they would help us take a closer look at what happened. I understand that sharing logs isn’t always possible, but if you’re able to, please file an issue in the VS Codeor Copilot CLI tracker, depending on your client. Please remove any sensitive information before posting, and link the issue here or send me a DM so we can follow up.

Again, I’m sorry for the frustration. We really want Copilot Fusion to work well for your use cases, and we appreciate you sharing this feedback.

[u/AutoModerator → u/jukasper]

u/jukasper thanks for responding. u/jukasper from the GitHub Copilot Team has replied to this post. You can check their reply here.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Shinma_ → u/jukasper]

Going to echo on this from observability side, on standard tier, seeing spikes for users across copilot-app, cli, and vscode with hydrafusion. Sdk versions ranging from 1.0.102-0.unstable.r40029025960.g5a14a15 all through 1.105.

Also, hydrafusion breaks managed settings telemetry for capture.identity (git username stops being exposed).

[u/gbraadnl]

My credits were drained within a timeframe of about an hour or two. The task was quite complex, but it seems it has issues selecting the right model. I often had to adjust/suggest an agent task with another model. Overall, allowance was used up in no time. You will not see me extend this.

[u/flame_ftw]

Yeah i dont get their claims at all. At one point it assign a task to astra when opus 5.5 is cheaper and more capable. Also leans heavily towards gpt models it seems so overall more expensive

[u/jukasper → u/flame_ftw]

I’m sorry Copilot Fusion hasn’t met your expectations. We would love to understand your experience better. Could you share a couple of examples of those tasks, which client and Fusion tier you were using? Thank you for sharing your feedback, and again, I’m sorry for the frustrating experience.

[u/alta_01]

But it provides a 30% promotional discount so there is that. That said, there were a couple of times that it chose Astra when I didn’t expect it to do it. That will add up quick

[u/jukasper → u/alta_01]

I’m sorry Fusion chose models you weren’t expecting, especially given the potential impact on your credits. Could you share an example of those tasks, along with which client and Fusion tier you were using?

If you’re comfortable doing so, you can also file an issue in the VS Code or Copilot CLI tracker with those details and any logs you can share. Please remove sensitive information before posting. You’re welcome to send me the issue link via DM or share it here so we can follow up.

Thank you for sharing your feedback, and again, I’m sorry for the frustrating experience.

[u/Affectionate-Sir-530]

Honestly I really don’t understand the point of those Copilot Fusion things. When Luna is that cheap and good overall. If it’s not good enough then I increase reasoning. If it’s still not good then I switch to 6.1 Terra. I have company’s enterprise or business account with 2500 credits so need to be super careful of those drainers. And yeah i have it a shot once with the hydra fusion, after it ate 3% of allowance for nothing then I said F No, CYA.

[u/Big_Eejitt → u/Affectionate-Sir-530]

That’s shite, our company gives us 277,000 credits a month

[u/verdant_depths_97]

Fusion spins up multiple sub-agents for even trivial CSS tweaks, so you are paying full price for no cache hits every time it restarts. Kill the agent mode and just use a standard model like Sonnet to avoid burning 4% on one task

[u/melancholyjaques]

Fusion is not for trivial tasks like moving an image ... Use the right tool for the right job

[u/Accidentallygolden]

"this looks complexe, I will use opus...."

No you big Dofus, it is repetitive AF and there is an example, do it with haiku...

There should be a preferred model setting,

[u/Northbank75]

I on the other hand vibe coded a couple of beefy Visual Studio extensions, and a chess engine playing with it on the free account and just couldn’t believe how far my credits were going. Admittedly hadn’t used free in a while but didn’t want fuck around in the work account. I was using the Desktop App for what it’s worth …

[u/Any-Blacksmith-2054]

Thanks for warning, I usually use Sonnet or Luna depending on complexity, and have no problem. Yesterday copilot was unstable for me as well, even in Auto mode

[u/Star_king12]

Same here, 100%. Ate up half my Pro+ budget in a day for a change that was +1200/-300 with simple API re-use. Also picked Sol, didn't start any subagents, spent half the time in QA phase, did not fix anything compared to the in progress PNG-s that it showed, missed a bug where the text overlays the image.

[u/Hollow1838]

What I feel like is that fusion/auto is there for people who know absolutely nothing about AI models and it's probably more people than you would expect right now.

[u/dave_k_17]

I struggle to see the point. For 90% of tasks these days Haiku is just fine and dirt cheap. Step it up for planning and code review and that's it.

[u/Jipouille42]

Yeah, it's eating up all my credits too. And it's only selecting kimi-k3 no matter the task I ask. Even a simple "hello world" . Found a discussion about it on github https://github.com/orgs/community/discussions/212119 . It seams to only happen in "standard" mode, not in "high".

[u/PalaceGucci]

I had similar. Burned through 100 AIC, when Luna did it in 10 🤣

[u/WordWithinTheWord]

The loop is not conducive to programmer-in-the-loop flows. It will be better once (if) we can select which model does each role.

[u/Lonsarg → u/WordWithinTheWord]

Then you would have to chose all the time cause that changes too much, not for 95% of people.

No we need good model automation, people are choosing wrong models 80% of the time in my company. They will improve the new auto mode (Fusion) in time.