Loading video...

Video Failed to Load

Go Home

Introducing SubQ Snap, the first long-context decision model for real enterprise work. Snap is the only decision model or LLM where compute per token stays constant as context grows. • 384K tokens of multimodal context, 12x larger than Jev. • 61.7 on Decision Index v0.2.1 vs Jev’s 57.9, outperforming...

4,033,804 views • 15 hours ago •via X (Twitter)

56 Comments

VCs Congratulating Themselves 👏👏👏's profile picture
VCs Congratulating Themselves 👏👏👏14 hours ago

big fan of your guys co-founder btw

Alexander Whedon's profile picture
Alexander Whedon14 hours ago

jian yang was ahead of his time.

Not Jerome Powell's profile picture
Not Jerome Powell15 hours ago

Using a frontier LLM for every decision is like driving a Ferrari to Walmart because you needed milk.

Mathew Chan's profile picture
Mathew Chan15 hours ago

What happened to your first model?

Alexander Whedon's profile picture
Alexander Whedon14 hours ago

It is in private beta with some of the world's largest enteprises, and we have released three generations since May. If you want to be considered for access, you can fill out the form here! Broader access will come, and this model release is a test run for us.

Linus ✦ Ekenstam's profile picture
Linus ✦ Ekenstam14 hours ago

I’d love to see a demo where this runs something very big, and finding very small pieces and at very high accuracy at speed. The launch video looks impressive though

Alexander Whedon's profile picture
Alexander Whedon14 hours ago

If you look around X, you will see quite a few! We gave a few hundred people access over the weekend, and dozens of folks built cool demos or thorough evaluations. One person even wrote a 70-page report. I'll try to highlight them as they start to show up on X.

Linus ✦ Ekenstam's profile picture
Linus ✦ Ekenstam14 hours ago

I’m looking forward, let me know if you have anything particular that really blows your mind, send it over, DM or just ping me, DM is way easier for me to spot than a ping tho 🙏🏼🫡

Ashmal Vayani's profile picture
Ashmal Vayani14 hours ago

Let's not stop at 384K 🚀

Alexander Whedon's profile picture
Alexander Whedon14 hours ago

You know we won't!

Ashmal Vayani's profile picture
Ashmal Vayani14 hours ago

On it, boss!

Carlos E. Perez's profile picture
Carlos E. Perez14 hours ago

I just signed up!

Alexander Whedon's profile picture
Alexander Whedon14 hours ago

Thank you! We would love to see what you build.

Chubby♨️'s profile picture
Chubby♨️14 hours ago

Yep, that looks super impressive! Good job! Love to see

Alexander Whedon's profile picture
Alexander Whedon14 hours ago

Thank you! We would love you to go build something awesome on top of it! Early access folks built a few dozen cool ideas, and we want to see more!

Toader Mihali's profile picture
Toader Mihali14 hours ago

Congrats on the launch! We ran subq-snap-preview through ~25k calls / 20 tasks in the closed beta (all zero-shot): • MMLU 86.8% · ARC-C 97.6% • 90–95% accuracy up to ~195k tokens • 9 languages + images • calibrated probs, ~0.55s p50 Full report 🧵👇

Alexander Whedon's profile picture
Alexander Whedon14 hours ago

Thanks for the thorough evaluation! There are so many nuggets here, I need more time to dig into this. I already flagged it in the discord!

Peter Banda's profile picture
Peter Banda14 hours ago

Welcome to the decision race 🔥 We just integrated and timed 8 hosts (24 models) - happy to add Snap as the 9th

Alexander Whedon's profile picture
Alexander Whedon14 hours ago

Thanks! Feel free to test us any way you want, the more evaluation the better!

The Rabbit Hole's profile picture
The Rabbit Hole14 hours ago

Big projects that felt like too much just got a lot more doable

Alexander Whedon's profile picture
Alexander Whedon14 hours ago

We can't wait to see your next project!

JeoCrypto's profile picture
JeoCrypto15 hours ago

Testing it right now

Nicole DeTommaso 🪄's profile picture
Nicole DeTommaso 🪄14 hours ago

Excited to see enterprises adopt specialized models like this. Congrats!

Alexander Whedon's profile picture
Alexander Whedon14 hours ago

Thanks!

Not Elon Musk's profile picture
Not Elon Musk14 hours ago

Most agent calls are structured decisions, not creative work.. I know this very well, first hand experience! Congrats on the launch. - Elon (p)

Avid's profile picture
Avid15 hours ago

this looks amazing a fresh take on decision models

Diego Alejandro's profile picture
Diego Alejandro14 hours ago

I don't trust you guys

Ryan Hart's profile picture
Ryan Hart14 hours ago

Still routing every decision through a full frontier model in 2026 is pure waste

Alexander Whedon's profile picture
Alexander Whedon14 hours ago

Agreed! This is why we will co-design our LLM and decision model to hand off work to each other.

• nanou •'s profile picture
• nanou •15 hours ago

The interesting part is how this changes the way we build AI agents. Let smaller models handle structured decisions and save the powerful LLMs for tasks that actually need them. Are we overcomplicating AI development by using one model for everything? 👀

ₕₐₘₚₜₒₙ's profile picture
ₕₐₘₚₜₒₙ14 hours ago

Exactly how things should be - powerful models solely focusing on the real challenges. Isolating problems like this is literally the most proactive way people will use Ai in the future, well done👏👏

Kevin Young's profile picture
Kevin Young15 hours ago

This is an exciting unlock for for decision model uses!

zaimiri's profile picture
zaimiri14 hours ago

what an insane context capability

Alexander Whedon's profile picture
Alexander Whedon14 hours ago

Thank you! More coming!

elvis's profile picture
elvis14 hours ago

Congrats on this launch. It's really key that decision models stay useful and efficient in longer contexts. Very cool stuff.

Alexander Whedon's profile picture
Alexander Whedon14 hours ago

Thank you!

Spencer Baggins's profile picture
Spencer Baggins14 hours ago

Most agents still choke on real context. Snap looks like it doesn’t

Alexander Whedon's profile picture
Alexander Whedon14 hours ago

It does not! We would love to see how you use Snap in your best agents.

kadd's profile picture
kadd15 hours ago

@Av1dlive This look solid

Sarah Adams Anderson's profile picture
Sarah Adams Anderson14 hours ago

Congratulations!

Alexander Whedon's profile picture
Alexander Whedon14 hours ago

Thanks, Sarah! We are excited to have you as part of our journey.

JeoCrypto's profile picture
JeoCrypto14 hours ago

Need access to SUBQ PREVIEW Early access ASAP Snap is beating all our internal benchmarks, but it's not enough

Shruti's profile picture
Shruti14 hours ago

feels like a new category

Alexander Whedon's profile picture
Alexander Whedon14 hours ago

It is!

Peter Mick's profile picture
Peter Mick14 hours ago

Bye bye Jev, hello SubQ Snap 👋

Alexander Whedon's profile picture
Alexander Whedon14 hours ago

We would love to see what you build!

Peter Mick's profile picture
Peter Mick14 hours ago

Can’t wait to take it for a spin, do you have a GitHub repo with sample / inspirational implementations we could look at Alexander?

Restructuring__'s profile picture
Restructuring__14 hours ago

Another software moat getting smaller

Aaliya's profile picture
Aaliya14 hours ago

awesome processing 100K tokens and returning a decision in under a second could be valuable for enterprise workflows that need fast answers from large datasets.

Rez Karim's profile picture
Rez Karim14 hours ago

This is the one. 384k in a single call with no chunking is exactly what long docs needed.

High Yield Harry's profile picture
High Yield Harry14 hours ago

All that context

AshutoshShrivastava's profile picture
AshutoshShrivastava14 hours ago

What baselines were used for the 13 benchmark wins? Would be good to see the evaluation setup on long-horizon compliance tasks.

Alexander Whedon's profile picture
Alexander Whedon14 hours ago

This was a comparison against Jev, on 16 benchmarks from the Decision Index. You can see the methodology here. We evaluated more than 50 benchmarks in total and created some of our own too.

AshutoshShrivastava's profile picture
AshutoshShrivastava14 hours ago

Thanks for sharing.. let me have a look .

Aleksandar Janca's profile picture
Aleksandar Janca14 hours ago

I let the model classify and an if/then makes the actual decision, that way I can explain every single one to the client

ɱҽԃι✨'s profile picture
ɱҽԃι✨14 hours ago

This is a remarkable advancement in AI capabilities, particularly the consistent compute cost across extended contexts.

Related Videos

Qwen3.8-Flash-Next is still going strong at 364.7K tokens of context on an M5 Max. And this isn’t just a static long-context test. The model was reasoning about how to speed up its own workflow while using tools, and the tool calls kept working without misses. Setup: • Qwen3.8-Flash-Next • M5 Max • 128GB unified memory • MLX-Serve PR #363 • OpenCode 2 • 364.7K context The interesting part isn’t simply getting hundreds of thousands of tokens into memory. It’s what happens once the context gets this large. Long-context inference usually comes with a painful tradeoff. As the KV cache grows, memory pressure increases and generation can slow down. But this setup is still pushing through 364K tokens while maintaining a usable agent workflow. The model can reason, call tools, inspect results, continue working, and keep the session moving. And the tool calls reportedly haven’t missed so far. That’s important for agentic coding. A huge context window is only useful if the model can actually operate reliably inside it. A 400K-token context that constantly breaks tool calls isn’t very useful. A 364K session that can keep reasoning and executing tools is a different story. And the test isn’t finished yet. The current run is approaching 400K tokens, with the expectation that it can keep going. This is also another interesting example of why Apple Silicon keeps showing up in local LLM experiments. The M5 Max’s unified memory gives a large model and its growing KV cache access to one shared memory pool. With MLX-Serve continuing to improve, these machines are becoming surprisingly capable long-context inference boxes. The bigger takeaway: Context length is becoming a workload, not just a model specification. Running a model at 256K is one thing. Keeping an agent alive at 300K+ while it reasons and uses tools is much more interesting. And Qwen3.8-Flash-Next is showing that this can be pushed surprisingly far on a single 128GB Mac. 364.7K and counting. Next stop: 400K.

FHILY👑

39,982 views • 1 month ago

This is one of the craziest AI launches of 2026 and it came out of basically nowhere (Save this). A company called Subquadratic just shipped SubQ, and the benchmarks are almost hard to believe. To understand why this is such a big deal, you have to understand the fundamental problem that has defined AI for the last decade. Every large language model in existence is built on transformer architecture, and transformers use a mechanism called standard attention that checks every single word in a sequence against every other word. Double the context length and compute doesn't double, it quadruples, triple it and compute goes up nine times. This quadratic scaling is why frontier models have been stuck at roughly 1 million tokens, why running them at those lengths gets expensive fast, and why the AI labs have essentially been printing money charging you more the longer you need the model to think. The industry has known this problem existed since 2017 but they scaled it anyway. SubQ is built from the ground up to solve it. Instead of processing every possible token relationship, SubQ's sparse attention architecture identifies which relationships actually matter and ignores the rest meaning compute is used where it counts and wasted nowhere else. The result is that compute scales linearly with context length instead of exponentially, and the implications of that one architectural shift are enormous. At 12 million tokens, SubQ reduces attention compute by nearly 1,000x compared to standard frontier models and at 1 million tokens, it runs 52x faster than FlashAttention. And it does all of this while posting frontier level accuracy, scoring 95% on the RULER 128K long-context benchmark versus Claude Opus 4.6's 94.8%, and an 81.8 on SWE-Bench Verified coding tasks, besting Opus 4.6 (80.8) and DeepSeek 4.0 Pro. The cost comparison is where it gets genuinely insane. SubQ runs at under $1.50 per million tokens less than 5% of what Claude Opus charges. On the RULER benchmark, running the test with SubQ cost $8, running the same test with Claude Opus cost $2,600 and that's a 300x cost reduction at equivalent or better accuracy.. Subquadratic launched with $29 million in funding, SubQ is available today for early access via API, and SubQ Code, a coding agent built on the architecture ships alongside it. The transformer has been the unchallenged foundation of every major AI system since 2017. SubQ is the first serious evidence that something structurally better might have just arrived.

Milk Road AI

278,687 views • 5 months ago

Gemini-1.5 Pro has its spotlight stolen today, and people are poking fun at Sora vs Google memes. Well, I think it's the biggest boost in LLM capability so far in 2024. v1.5's 10M token context (1) excels at retrieval; (2) generalizes zero-shot to extremely long instructions like full tutorials and codebases; and (3) works across modalities such as text, audio, and video. Here's a stunning example: v1.5 learns to translate from English to Kalamang purely in context, following a full linguistic manual at inference time. Kalamang is a language spoken by fewer than 200 speakers in western New Guinea. Gemini has never seen this language during training and is only provided with 500 pages of linguistic documentation, a dictionary, and ~400 parallel sentences in context. It basically acquires a sophisticated new skill in the neural activations, instead of gradient finetuning. I talked about the Myth of Context Length many times before: don't get too excited by claims of 1M or even 1B context tokens. LSTMs already achieved literally infinite context length 25 yrs ago! What truly matters is how well the model actually uses the context to solve real-world problems, and Gemini-1.5 has surpassed the SOTA with flying colors. The paper is also well-written with lots of solid quantitative analysis on in-context memorization and generalization. Paper: “Gemini 1.5: Unlocking multimodal understanding across millions of tokens of context” Congrats to Jeff Dean Oriol Vinyals Sundar Pichai and team!

Jim Fan

278,557 views • 2 years ago

New short course: LLMs as Operating Systems: Agent Memory, created with Letta, and taught by its founders Charles Packer and Sarah Wooders. An LLM's input context window has limited space. Using a longer input context also costs more and results in slower processing. So, managing what's stored in this context window is important. In the innovative paper MemGPT: Towards LLMs as Operating Systems, its authors (which include the instructors) proposed using an LLM agent to manage this context window. Their system uses a large persistent memory that stores everything that could be included in the input context, and an agent decides what is actually included. Take the example of building a chatbot that needs to remember what's been said earlier in a conversation (perhaps over many days of interaction with a user). As the conversation's length grows, the memory management agent will move information from the input context to a persistent searchable database; summarize information to keep relevant facts in the input context; and restore relevant conversation elements from further back in time. This allows a chatbot to keep what's currently most relevant in its input context memory to generate the next response. When I read the original MemGPT paper, I thought it was an innovative technique for handling memory for LLMs. The open-source Letta framework, which we'll use in this course, makes MemGPT easy to implement. It adds memory to your LLM agents and gives them transparent long-term memory. In detail, you’ll learn: - How to build an agent that can edit its own limited input context memory, using tools and multi-step reasoning - What is a memory hierarchy (an idea from computer operating systems, which use a cache to speed up memory access), and how these ideas apply to managing the LLM input context (where the input context window is a "cache" storing the most relevant information; and an agent decides what to move in and out of this to/from a larger persistent storage system) - How to implement multi-agent collaboration by letting different agents share blocks of memory This course will give you a sophisticated understanding of memory management for LLMs, which is important for chatbots having long conversations, and for complex agentic workflows. Please sign up here!

Andrew Ng

201,127 views • 1 year ago

Qwen3.8-27B running at full BF16 on a free Kaggle TPU is kind of ridiculous. No quantization. No tiny context window. No expensive GPU instance. Just Qwen3.8-27B running on a Kaggle TPU v5e-8. The reported numbers: ~130 tok/s decode ~10,000 tok/s prefill 262K context That prefill number is especially wild. You can throw a huge amount of code or context at the model and ingest it extremely quickly, while still getting around 130 tokens per second during generation. And because it’s running in full BF16, you’re not relying on an aggressive quant just to make the model fit. But the really interesting part isn’t even the raw throughput. You can expose it as an OpenAI-compatible endpoint. That means you can plug the model into tools that already understand OpenAI-style APIs. Claude Code. Codex. OpenCode. And other compatible clients. So the workflow becomes pretty simple: Spin up the Qwen3.8-27B endpoint on Kaggle. Point your coding tool at the API. And suddenly you have a 27B coding model sitting behind the same interface you’d normally use for hosted models. The 262K context is also a huge deal for agentic coding. Large repositories can fit into a single context. Long conversations don’t need to be constantly trimmed. And tools can feed much more information back to the model without hitting a tiny context ceiling. The fact that this can be built around a free TPU environment is what makes this especially interesting. We’re getting to a point where experimenting with serious open models doesn’t always require owning a $2,000 GPU or paying for a large cloud instance. Free compute + open weights + an OpenAI-compatible API + existing coding agents. That’s a pretty powerful combination. Qwen3.8-27B is already an interesting model. Running the full BF16 version at ~130 tok/s with 262K context on free Kaggle TPU compute makes it a lot more interesting.

FHILY👑

35,910 views • 1 month ago