🚨 𝗜 𝗝𝗨𝗦𝗧 𝗦𝗛𝗥𝗨𝗡𝗞 𝗢𝗥𝗡𝗜𝗧𝗛 𝟭.𝟱 𝟭𝟮𝟮𝗕 𝗙𝗢𝗥 𝗧𝗛𝗘 𝟰𝟴𝗚𝗕 𝗩𝗥𝗔𝗠 𝗖𝗢𝗠𝗠𝗨𝗡𝗜𝗧𝗬! 🧪🔥 @ornith_ JUST released their new Ornith-1.5-122B, and naturally, I HAD to see how far I could push it with SAGE-EXL3! And the results surprised even ME! 🤯 Introducing... 🟢 𝗢𝗿𝗻𝗶𝘁𝗵-𝟭.𝟱-𝟭𝟮𝟮𝗕-𝗘𝗫𝗟𝟯-𝗦𝗔𝗚𝗘-𝟮.𝟱𝟴𝗯𝗽𝘄 📦 ~39.6 GiB GPU-resident LM weights 🧠 122B-class Mixture-of-Experts model ⚡ 2.58 bpw routed experts 💻 Targeting 48GB VRAM GPUs and above! 🚀 vLLM + EXL3 inference 𝗕𝗨𝗧 𝗛𝗘𝗥𝗘'𝗦 𝗪𝗛𝗘𝗥𝗘 𝗜𝗧 𝗚𝗘𝗧𝗦 𝗜𝗡𝗧𝗘𝗥𝗘𝗦𝗧𝗜𝗡𝗚... 👀 ━━━━━━━━━━━━━━━━━━━━ 🏆 𝗦𝗔𝗚𝗘 𝟮.𝟱𝟴 𝗕𝗣𝗪 𝘃𝘀 𝗠𝗜𝗔-𝗔𝗜𝗟𝗔𝗕 𝗘𝗔𝗤𝘃𝟭 𝟰.𝟬 𝗕𝗣𝗪! I compared my release against Mia-AiLab's Ornith-1.5-122B-EXL3-EAQv1-4-bpw quantization. Same model family. Same DGX Spark. 353 matched benchmark questions. 9 evaluation suites. Strict pass@1 scoring. 🟢 𝗠𝗬 𝗦𝗔𝗚𝗘-𝗘𝗫𝗟𝟯 𝟮.𝟱𝟴 𝗕𝗣𝗪 📦 41.00 GiB LM weights 🏆 𝟵𝟭.𝟳𝟴% — 𝟯𝟮𝟰/𝟯𝟱𝟯 🟣 𝗠𝗜𝗔-𝗔𝗜𝗟𝗔𝗕 𝗘𝗔𝗤𝘃𝟭 𝟰.𝟬 𝗕𝗣𝗪 📦 59.00 GiB LM weights 📊 𝟵𝟭.𝟱𝟬% — 𝟯𝟮𝟯/𝟯𝟱𝟯 𝗔𝗣𝗣𝗥𝗢𝗫𝗜𝗠𝗔𝗧𝗘𝗟𝗬 𝟯𝟬.𝟱% 𝗦𝗠𝗔𝗟𝗟𝗘𝗥 𝗟𝗠 𝗪𝗘𝗜𝗚𝗛𝗧 𝗙𝗢𝗢𝗧𝗣𝗥𝗜𝗡𝗧... 𝗔𝗡𝗗 𝗘𝗦𝗦𝗘𝗡𝗧𝗜𝗔𝗟𝗟𝗬 𝗧𝗛𝗘 𝗦𝗔𝗠𝗘 𝗢𝗩𝗘𝗥𝗔𝗟𝗟 𝗤𝗨𝗔𝗟𝗜𝗧𝗬! 🤯 Mine finished one question ahead overall. That's effectively a tie at this sample size, but the coding breakdown is particularly interesting! ━━━━━━━━━━━━━━━━━━━━ 💻 𝗖𝗢𝗗𝗜𝗡𝗚 𝗜𝗦 𝗪𝗛𝗘𝗥𝗘 𝗦𝗔𝗚𝗘 𝗣𝗨𝗟𝗟𝗦 𝗔𝗛𝗘𝗔𝗗! Scores shown as SAGE → Mia: ✅ HumanEval+: 39/40 → 39/40 🏆 MBPP+: 53/60 → 51/60 🏆 LiveCodeBench: 15/20 → 14/20 🏆 SciCode: 5/10 → 4/10 𝗖𝗢𝗗𝗜𝗡𝗚 𝗦𝗨𝗕𝗧𝗢𝗧𝗔𝗟: 🟢 SAGE: 112/130 — 86.15% 🟣 Mia: 108/130 — 83.08% 𝗙𝗢𝗨𝗥 𝗠𝗢𝗥𝗘 𝗖𝗢𝗗𝗜𝗡𝗚 𝗤𝗨𝗘𝗦𝗧𝗜𝗢𝗡𝗦 𝗣𝗔𝗦𝗦𝗘𝗗 𝗪𝗜𝗧𝗛 𝟯𝟬.𝟱% 𝗟𝗘𝗦𝗦 𝗠𝗢𝗗𝗘𝗟-𝗪𝗘𝗜𝗚𝗛𝗧 𝗠𝗘𝗠𝗢𝗥𝗬! 🔥 For transparency, Mia scored higher on MMLU-Pro STEM (96 vs 94) and MATH-500 (39 vs 38). Both tied on HumanEval+, MGSM, BFCL and multi-step tool chains. This isn't about claiming one quant wins everything. 𝗜𝗧'𝗦 𝗔𝗕𝗢𝗨𝗧 𝗚𝗘𝗧𝗧𝗜𝗡𝗚 𝗠𝗢𝗥𝗘 𝗤𝗨𝗔𝗟𝗜𝗧𝗬 𝗣𝗘𝗥 𝗚𝗕. ━━━━━━━━━━━━━━━━━━━━ ⚡ 𝗔𝗡𝗗 𝗬𝗘𝗦, 𝗜𝗧 𝗥𝗨𝗡𝗦 𝗢𝗡 𝘃𝗟𝗟𝗠! My measured vLLM 0.32.0 + vllm-exl3 performance on ONE DGX Spark: ⚡ 30.51 tok/s single-stream decode 🚀 32.60 tok/s with MTP-1 (greedy code test) 🔥 89.21 tok/s aggregate decode @ C8 📥 1,119 tok/s cold prefill (2K prompt) 🧠 Native 262K context support The public recipe is being streamlined around vLLM, with the older alternative serving instructions being retired. My goal is to make this practical for people who want an OpenAI-compatible local endpoint without needing an 80GB+ GPU just to load the model. The 48GB tier is the intended target; these published performance measurements were performed on my DGX Spark. Actual available context and batching capacity will depend on the GPU. ━━━━━━━━━━━━━━━━━━━━ 👀 𝗕𝗨𝗧 𝗛𝗘𝗥𝗘'𝗦 𝗪𝗛𝗔𝗧 𝗜'𝗠 𝗥𝗘𝗔𝗟𝗟𝗬 𝗘𝗫𝗖𝗜𝗧𝗘𝗗 𝗔𝗕𝗢𝗨𝗧... ⚡ 𝗧𝗪𝗢 𝗠𝗢𝗗𝗘𝗟𝗦. 𝗢𝗡𝗘 𝗦𝗣𝗔𝗥𝗞. 𝗜𝗦 𝗖𝗢𝗠𝗜𝗡𝗚 𝗕𝗔𝗖𝗞! If you've followed my previous experiments, you know I LOVE finding ways to run multiple powerful models on a SINGLE DGX Spark. And this ~41 GiB Ornith quant opens up some VERY interesting possibilities! Imagine... 🧠 𝗤𝗪𝗘𝗡𝟯.𝟴-𝗙𝗟𝗔𝗦𝗛-𝗡𝗘𝗫𝗧 — 𝗠𝗔𝗦𝗧𝗘𝗥 𝗔𝗚𝗘𝗡𝗧 A larger lead model handling complex reasoning, planning, orchestration and long-context tasks. ⚡ 𝗢𝗥𝗡𝗜𝗧𝗛 𝟭.𝟱 𝟭𝟮𝟮𝗕 — 𝗦𝗨𝗕-𝗔𝗚𝗘𝗡𝗧 My compact SAGE-EXL3 handling delegated coding, tool use and specialized agentic workloads! 𝗧𝗪𝗢 𝟭𝟮𝟬𝗕+ 𝗖𝗟𝗔𝗦𝗦 𝗠𝗢𝗗𝗘𝗟𝗦. 𝗢𝗡𝗘 𝟭𝟮𝟴𝗚𝗕 𝗗𝗚𝗫 𝗦𝗣𝗔𝗥𝗞. 𝗙𝗨𝗟𝗟𝗬 𝗟𝗢𝗖𝗔𝗟! 🤯 That's the direction I'm exploring for my NEXT Two Models. One Spark. experiment! Of course, simultaneous residency, runtime overhead, KV-cache allocation and actual master-worker performance still need validation with the selected Qwen quantization. But the smaller we can make these models without sacrificing useful quality, the MORE possibilities we unlock! 𝗧𝗛𝗜𝗦 𝗜𝗦 𝗪𝗛𝗬 𝗜 𝗗𝗢 𝗪𝗛𝗔𝗧 𝗜 𝗗𝗢! 💚 ━━━━━━━━━━━━━━━━━━━━ 🔬 𝗢𝗡𝗘 𝗟𝗜𝗧𝗧𝗟𝗘 𝗥𝗘𝗫𝗟𝟯 𝗧𝗘𝗔𝗦𝗘𝗥... In separate development testing, REXL3 has also reached: ⚡ 90.82 tok/s aggregate @ C8 🚀 ~2,150 tok/s prefill More on that another time. 😏 ━━━━━━━━━━━━━━━━━━━━ 💚 𝗠𝗔𝗞𝗜𝗡𝗚 𝗙𝗥𝗢𝗡𝗧𝗜𝗘𝗥 𝗔𝗜 𝗔𝗖𝗖𝗘𝗦𝗦𝗜𝗕𝗟𝗘! Not everyone has a DGX Spark or an 80GB GPU. But a LOT of enthusiasts, developers and independent researchers have access to 48GB-class hardware. I want powerful open-weight models to be accessible to MORE of those people. And beyond just fitting one model, I want to show what's possible when we start combining them on the SAME hardware! Huge thanks to @ornith_ for releasing Ornith-1.5-122B under an open-weight license and continuing to push efficient AI models forward! ━━━━━━━━━━━━━━━━━━━━ 🔗 𝗗𝗢𝗪𝗡𝗟𝗢𝗔𝗗 𝗠𝗬 𝗘𝗫𝗟𝟯 huggingface.co/vcruz305/Orni… 🛠️ 𝗩𝗟𝗟𝗠 𝗗𝗚𝗫 𝗦𝗣𝗔𝗥𝗞 𝗥𝗘𝗖𝗜𝗣𝗘 github.com/vcruz305/Ornith-1… 𝗦𝗠𝗔𝗟𝗟𝗘𝗥 𝗪𝗘𝗜𝗚𝗛𝗧𝗦. 𝗕𝗜𝗚𝗚𝗘𝗥 𝗣𝗢𝗦𝗦𝗜𝗕𝗜𝗟𝗜𝗧𝗜𝗘𝗦. 𝗧𝗪𝗢 𝗠𝗢𝗗𝗘𝗟𝗦. 𝗢𝗡𝗘 𝗦𝗣𝗔𝗥𝗞. ⚡ 𝗟𝗘𝗧'𝗦 𝗞𝗘𝗘𝗣 𝗣𝗨𝗦𝗛𝗜𝗡𝗚 𝗟𝗢𝗖𝗔𝗟 𝗔𝗜 𝗙𝗢𝗥𝗪𝗔𝗥𝗗! 🚀🔥

Today we announce 1Password for Agents platform, building with companies @Muse, SpaceX Super Intelligence Grok @Bot, @AnthropicAI’s @Claudeai, @OpenAI, @TownAI, @Browserbase, @Browser_use, @heydana_ai, Instinct, @usekernel, @Perplexity_ai, @tryramp, @Tomo, and @wajo_ai, with more integrations on the way. 🎉 We've heard from so many of our customers who want to use these new personal AI agents to help them get more done, but want more control over what the agent can access with the same trust and ease of use they get when using 1Password directly. 1Password for Agents gives your agents access without giving up your passwords. When an agent reaches a sign-in form, it requests a credential from your vault. If you approve the request, 1Password directly auto-fills the credential in the destination site so the agent can’t see or take possession of the credentials. The agent gets the task done, but it doesn’t get your passwords.. You stay in control. 1Password for Agents free and optional for personal and family accounts. Unless you opt-in to an agent connector, agents cannot touch your vault. ➡️Learn more: bit.ly/487da6J

Introducing Ling-3.1-flash-1019 🚀 It scores 44 on the Artificial Analysis Intelligence Index, up from 41 for Ling-3.1-flash. Gains in agentic work: AA-Briefcase ~1400→1524 Elo and AutomationBench-AA 62%→68%. API access and open weights coming soon. Stay tuned.

Our latest model advances bring stronger capabilities for building and migrating software in low-resource programming languages such as COBOL, Fortran, and Visual Basic. These languages power software that banks, governments, and businesses depend on. Progress here means understanding decades of business logic and helping developers modernize those systems while preserving what works. We’re building these capabilities around the challenges developers and enterprise customers bring us. If your team is working on these systems, tell us which languages and workflows we should tackle next. openai.com/index/low-resourc…