跳过导航
Super excited about HydraFusion in GitHub Copilot, and what it shows about the shift from model…
0:00 / 1:34

Super excited about HydraFusion in GitHub Copilot, and what it shows about the shift from model…

Satya Nadella

@satyanadella957万 位关注者

在 X 上查看
1,430 个赞下载原帖

330,538 次观看

Super excited about HydraFusion in GitHub Copilot, and what it shows about the shift from model selection to model orchestration. By bringing together multiple models to plan, build, critique, and complete coding tasks, it can deliver outcomes at up to 67% lower cost. It’s a great example of the value of a heterogeneous model ecosystem, and how we’re continuing to advance the cost-to-outcome frontier.

32 条评论

评论来自 X (Twitter) 上的原帖

  • Satya Nadella 的头像

    @satyanadella

    Try it out:

    84 个赞

  • EV_Trapper 的头像

    @EV_Trapper

    @morfmod has been delivering that for 2+ months now, we just can't launch because we have no funding :(

    5 个赞

  • Musaab⚡️ 的头像

    @musaabHQ

    MSFT now:

    5 个赞

  • Marcus 的头像

    @MarcusSpillane

    So you invented a committee that plans, builds and critiques, except this one is 67% cheaper and nobody asks to circle back.

    4 个赞

  • Nazar Ponochevnyi 的头像

    @nazar_198

    I spent the first 10 seconds wondering why Satya was wearing a GitHub hoodie..

    4 个赞

  • Scott | Free Speech Dev 🇺🇲 的头像

    @scottdotnetdev

    After you destroyed what little trust people had in GitHub Copilot with your pricing rugpull, I doubt anyone is going to circle back for another look, me included.

    3 个赞

  • Sam Tilston 的头像

    @samtilston

    The cost pressure is becoming impossible to ignore as coding workloads get more complex Using the expensive model for every step is a luxury orchestration can increasingly eliminate

    2 个赞

  • Autobunnyhop 的头像

    @0xAutobunnyhop

    67% lower cost is a serious gain. The interesting part is how orchestration turns different model strengths into one workflow.

    2 个赞

  • Jason Stapleton ☕️ ✍🏼 🎙️ 的头像

    @Jason_Stapleton

    Serious question: does ANYONE use copilot?

    2 个赞

  • Sergio Mattei 的头像

    @matteing

    costing six seven percent less?

    2 个赞

  • Prayush Jain 的头像

    @jainprayush9

    @grok - What is he saying? Summaries everything for me.

    2 个赞

  • Webster | JARVIS 的头像

    @websterweby

    model orchestration is gonna be the big theme this year for sure. wild how fast we moved from picking one model to mixing a whole team of them.

    2 个赞

  • Rui Costa 的头像

    @RuiCost56242151

    Almost everything is 67% cheaper than SlOpus 5. Compare it against Luna or Sol :)

    1 个赞

  • money simplified 的头像

    @simplified1554

    The 67% matters less than who controls the routing layer. One model: selection Multiple models: orchestration Next: automatic routing If the best model changes by task, model selection becomes infrastructure rather than a user decision.

    1 个赞

  • EKOS _ AGI 🦊 🇮🇷 的头像

    @OMID_0909

    Model orchestration is a big efficiency gain, but coordinating models is only half the problem. When multiple agents build on the same context, how do we ensure that context is consistent, traceable, and grounded in evidence?

    1 个赞

  • Guru dev  的头像

    @iamgurudevv

    60% huge

    1 个赞

  • Ryan Hecht 的头像

    @Ryan_Hecht

    Can't just be me who did a double take of whether that was actually Satya or @mariorod1 in the video!

    1 个赞

  • Jonathan Sandhu 的头像

    @SandhuJonathan

    “67% lower cost” because you stopped sending every subtask to the same expensive model and added routing, critique and retries. Now show the baseline, pass rate, latency and retry budget before “cost-to-outcome frontier” becomes another dashboard noun.

    1 个赞

  • Phil Hie 的头像

    @philhie

    model picking quietly becoming a solved problem, wild to watch

    1 个赞

  • Stats Wire 的头像

    @StatsWire

    Right now copilot has Auto option that gives only 10% discount

    1 个赞