Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Comfy Router is live One API for frontier image, video, 3D, and audio models. Same model string. Same arguments. No new SDK, no new key, no redeploy. What Comfy Router gives you: → Explicit routing. You name the provider, we call that provider. It's down? The request fails there....

7,420,417 görüntüleme • 3 gün önce •via X (Twitter)

34 Yorum

ComfyUI profil fotoğrafı
ComfyUI3 gün önce

Get Your API Key today:

ComfyUI profil fotoğrafı
ComfyUI3 gün önce

Learn more with the blog:

Robin Huang profil fotoğrafı
Robin Huang3 gün önce

Great work team!!

Yoland Yan profil fotoğrafı
Yoland Yan3 gün önce

LFG!

Maximus profil fotoğrafı
Maximus3 gün önce

Finally

Tara Ding profil fotoğrafı
Tara Ding3 gün önce

Congratulations!!!

Bohan profil fotoğrafı
Bohan3 gün önce

Sick!

TongTong C profil fotoğrafı
TongTong C3 gün önce

🔥🔥🔥

Atul Kumar profil fotoğrafı
Atul Kumar3 gün önce

The biggest win here is consistency. One workflow across image, video, 3D, and audio means teams can focus on building products instead of maintaining integrations.

Ethan Kurzweil profil fotoğrafı
Ethan Kurzweil3 gün önce

Sweet! 🎡

mathurah profil fotoğrafı
mathurah3 gün önce

ahh this is going to be such a game changer! congrats to the team on the launch :)

Carl Wheatley profil fotoğrafı
Carl Wheatley3 gün önce

Great launch!!!

Will Phillips profil fotoğrafı
Will Phillips3 gün önce

Epic! Feel like Router is the word of the quarter 🚀

TongTong C profil fotoğrafı
TongTong C3 gün önce

finally

Shun Ito profil fotoğrafı
Shun Ito3 gün önce

congrats for the launch!!

Grace profil fotoğrafı
Grace3 gün önce

This is a major upgrade LFG!

Sponko profil fotoğrafı
Sponko3 gün önce

😮‍💨

Aaliya profil fotoğrafı
Aaliya3 gün önce

The “finding out who did it” line fits nicely with the Beast Mode theme while keeping the CX message clear.

Olivia Li profil fotoğrafı
Olivia Li3 gün önce

Let’s go!!

Orestis Lykos profil fotoğrafı
Orestis Lykos3 gün önce

fal all the way down!

Rob Muresan profil fotoğrafı
Rob Muresan3 gün önce

DAMN!

rob - comfyui profil fotoğrafı
rob - comfyui3 gün önce

Very important things happening

Hasanuzzaman Khan profil fotoğrafı
Hasanuzzaman Khan3 gün önce

Batch workflows are going to save teams a surprising amount of time.

Ian Lim profil fotoğrafı
Ian Lim3 gün önce

Huge 🔥

Annette Sung profil fotoğrafı
Annette Sung3 gün önce

lit

Ashley Nicole profil fotoğrafı
Ashley Nicole3 gün önce

AI tooling is maturing—observability is finally becoming part of the conversation.

Arish Ai profil fotoğrafı
Arish Ai3 gün önce

The multimodal ecosystem is getting crowded—having one workflow across providers makes a lot of sense.

David Kwon profil fotoğrafı
David Kwon3 gün önce

Let's go! Great job @yoland_yan and team

David Marco💡 profil fotoğrafı
David Marco💡3 gün önce

Less glue code. More building. That's the kind of tradeoff every engineering team wants.

Tiger profil fotoğrafı
Tiger3 gün önce

Hyped!

AlphaEcho profil fotoğrafı
AlphaEcho3 gün önce

This is the kind of infrastructure launch developers actually appreciate less integration work, more shipping.

joao fig profil fotoğrafı
joao fig3 gün önce

@yoland_yan killing it 🔥

Arnez Ai profil fotoğrafı
Arnez Ai3 gün önce

Production-ready details like request IDs and retries are what make platforms stick.

Alishba profil fotoğrafı
Alishba3 gün önce

This feels like infrastructure built for builders, not just demos.

Benzer Videolar

HERMES AGENT VS OPENCLAW. a local ai onboarding flow test. a 3.9gb bonsai served on localhost, both agents upstream and latest, i point each one at the endpoint and watch which one even finds it. > hermes opens a provider menu, thirty plus options, local servers sitting right there next to the cloud ones, i hand it 127.0.0.1:8899, it verifies the endpoint, one model visible, auto-detects the model by name, bonsai-27b-q1_0, reads the context length straight off the server, saves it, and starts reasoning and firing real tool calls on my local model. no key. no friction. > openclaw has no menu. it goes hunting for a codex login, an openai key, finds none because there are none, prints no models available three times, defaults to openai/gpt-5.5, a cloud model it cannot reach, and dead ends on run auth login --provider openai. read that back. it asked me for an openai key. to run a model already running on my own machine. it never once looked at localhost. to be fair, openclaw can run local if you hand wire endpoint yourself. what it will not do is find the model already sitting on your box. hermes agent found it in one line. now the part i owe you. the auto-detect that just won, the model name read, the .gguf strip, the context length probe off the server, that is my code, it is in hermes agent main right now, authorship preserved, #2051 and #4218. the wizard fix that stops an agent from silently routing you to someone else's creds, the exact trap openclaw still falls into, mine too, #4210. i contribute to hermes agent, i told you that going in. one agent is built to talk to whatever you are running, the other is built to talk to a cloud api, so one found my model and ran it and the other asked me to log into openai. onboarding flow of both, mapped, below.

Sudo su

23,816 görüntüleme • 2 ay önce

Production traffic is not uniform. You get a few requests that need your best model, but most are simple questions and lookups you can solve with cheaper, faster models. The most expensive mistake you can make today is sending every request to your strongest model. You need routing. Period. This is the simplest trick to improve the architecture of whatever you are building. Please, don't implement routing yourself. You don't have to. I'm currently working with TrueFoundry's Auto Routing. It reads each request, classifies it as simple, medium, or complex, and sends it to the model assigned to that tier. You have two choices: 1. Send every request to the free heuristic classifier to score signals such as technical vocabulary, code, prompt length, and multi-step reasoning. 2. Send the request to an LLM classifier when its difficulty requires a more nuanced judgment. The beauty of using routing is that nothing changes in your code. You still call a single endpoint model, but routing works behind the scenes to pair every request with the best possible model. TrueFoundry ran several experiments with two different setups: 1. Send every request to Claude Opus 2. Send every request to a router with Haiku, Sonnet, and Opus The first experiment ran 550 deterministically graded academic prompts through every setup. Auto Routing was 69% cheaper while retaining 98% of the baseline quality. The second experiment ran three production-shaped workloads through every setup, using user chats, developer chats, and long agent tasks. Auto Routing was 80% cheaper. Thanks to the TrueFoundry team for partnering with me on this post.

Santiago

15,543 görüntüleme • 15 gün önce