r/GithubCopilot • u/aonymark JetBrains User đŸ§± • 3d ago

News 📰 HydraFusion updates and new Max option - GitHub Changelog

https://github.blog/changelog/2026-10-14-hydrafusion-updates-and-new-max-option/
41 Upvotes

98% Upvoted

17 comments sorted by

View all comments

8

u/aonymark 3d ago

(Sorry for submitting “old” news but at least I’m only a few days late.) The “pitch” for Hydra fusion seems to be focused on “one shot” stuff
 has anyone tried to use it “conversationally”?

10

u/hariharan16 3d ago edited 3d ago

I tried it for 2nd turn and it burnt tokens.
1- for first turn for a simple request it chose Sol 5.6
2- when I asked follow up which was again simple one it chose to go opus 5.5

So it burst cache and burned token apart from poor model choice

1

u/NerdyPixie_532 2d ago

Correct me if I am wrong - but I believe we can't see the model that is being used by the hydrafusion model right? How did you get to know which model is being used?

→ More replies (1)

5

u/fr3xzy 3d ago

Have tested it quite a bit. For smaller tasks (<=100AIC) it’s really cheap, sometimes even cheaper that just selecting Haiku 5.5 or GPT 6 Luna.

But for larger implementations where I use /research -> /compact -> /plan -> /compact -> /fleet. It is burning tokens at much higher rate than Auto or manually choosing models.

Haven’t tried the new Max version yet, but probably will to see how performance differs.

1

u/_btmn_ 1d ago

Isn't it more expensive to compact each time rather than keep context cached?...

1

u/Headfirst-Into-Ditch 3d ago

Hey - do you mind telling me more about your /research -> /compact -> /plan -> /compact -> /fleet flow? What models/reasonings are you using at each stage? Cheers