A frontier AI lab specializing in long context. Makers of Vast-10M.

Pinned Tweet
Introducing Vast-10M from Voltropy: - The first frontier LLM with a ten million token context window - Beats Anthropic's Fable 5.1 at long-context reasoning - Early access opens TODAY
52
62
444
289,751
At ten million tokens, Vast-10M-Flash exceeds the performance of its base model at 1M tokens. It matches the performance of GLM 5.2 at 500k tokens. In other words, the models perform the same when Vast-10M-Flash has to process 20x more context.
1
4
497
Vast-10M-Flash is our strongest model, but our experiments validated VSA in all three models. VSA's scaling properties boost performance at shorter contexts and retain it all the way to 10M tokens.
1
5
468
We aren't yet ready to publicly share the details of how VSA works. But we invite you to try it for yourself in early access at voltropy.com. Our blog post there goes into more detail about why we created this technology and how it can make AI smarter and safer.
13
444
Vast-10M-Flash doesn't just beat its base model, DeepSeek v4.0 Flash. It beats its base model's replacement. We unexpectedly unlocked more capability by adding VSA than DeepSeek did by training a new model.
1
8
550
EXPLAINER: How Voltropy built Vast-10M, the best long-context LLM in the world. We invented a new form of scalable attention (VSA) and retrofitted it to legacy DeepSeek weights. Suddenly the old weights could compete head-to-head with OpenAI and Anthropic's strongest models.
6
6
114
9,201
We tested VSA on three model sizes spanning two model families. Every VSA-equipped model beat every DeepSeek and GLM baseline at every context length. It was a 9-0 victory for VSA.
3
12
857
Introducing Vast-10M from Voltropy: - The first frontier LLM with a ten million token context window - Beats Anthropic's Fable 5.1 at long-context reasoning - Early access opens TODAY
52
62
444
289,751
Early access to Vast-10M is now open at voltropy.com The technical paper is also live. Come read how Vast-10M measures up to Fable 5.1 and GPT-6 Astra.
2
22
2,433
Voltropy retweeted
Some founders are fighting for b2b saas. And others are fighting to win it all. This conversation is the moment I knew Ted and @ClintEhrlich were taking on Dario.
5 of 10 teams at demo day broke $10M annualized HF0 is not just for early stage companies Interviews started yesterday.
4
27
8,914
Voltropy retweeted
5 of 10 teams at demo day broke $10M annualized HF0 is not just for early stage companies Interviews started yesterday.
36
44
540
278,793
Voltropy retweeted
lossless-claw 0.11.1 — the focus mode release 🎯 /lossless focus curates your context ↩️ /lossless unfocus brings the normal context view back 🖼️ image externalization now works across roles 📦 installs stop pulling a second OpenClaw
13
6
112
31,528
"LCM: Lossless Context Management" (Ehrlich and Blackman, 2026) is now available on arXiv. This is the paper that caused @openclaw to modify its architecture to support context management. It's a must-read for anyone interested in RLMs vs LCM. arxiv.org/abs/2605.04050
1
1
12
1,836
Voltropy retweeted
lossless-claw 0.9.3 — the "please just keep working" release 🧠 cache-aware compaction fires before overflow 🔁 fewer repeated old instructions 🧰 lcm tools load on OpenClaw 2026.5.2+ 🔌 Codex, DeepSeek, Bedrock fixes 🛡️ safer migrations, payloads, and replay
12
15
215
39,570
🚀 hermes-lcm v0.7.1 is live! 🧠 Compression rollover continuity 🔌 Provider-prefixed model routing 🧼 Thinking-tag cleanup Update: git -C ~/.hermes/plugins/hermes-lcm pull --ff-only Bounded context, unbounded memory. Nothing is ever lost. @Voscko @Teknium @NousResearch github.com/stephenschoettler…
6
8
120
11,090
Voltropy retweeted
Recursive self-improving AI is here. I had heard people talking about self-improving AIs at some of the frontier labs but wasn't sure how real it was. One of the neo labs in the current @hf0 batch had a breakthrough and now it’s running in our basement. It’s real.
28
18
240
26,197
Lossless Context in OpenClaw feat. Josh Lehman x.lingyaoai.com/i/broadcasts/1AKEmONzY…
4
9
632
Voltropy retweeted
Fun fact about lossless-claw: in addition to solving agent amnesia and enabling infinite-length sessions, it's also very token efficient. Lossless summaries are great for prompt caching. I at about a 90-94% cache hit rate. Thanks to incremental compaction, your context rarely grows beyond 80k tokens before truncating back to 30-40k or less. This means that your model is almost always operating faster, smarter and cheaper since it has less overall context to operate on.
9
6
159
10,991
Voltropy retweeted
Why doesn't Anthropic just solve compaction by adding LCM to Claude? @Voltropy open-sourced LCM. It's in @OpenClaw. Every frontier lab should use it.
why is claude compaction so bad. codex compaction is basically instant. why can’t they just copy whatever oai did
1
1
6
2,748
Voltropy retweeted
A common line of questions I receive: what does lossless-claw do differently than memory systems? How do the two relate? Should I use both? Here’s the lowdown: Memory systems are good for letting you search for information that’s external to your context window, which are typically “memories” extracted from past/different conversations. This is necessary because: Compaction is lossy: when your conversation gets too big, your agent replaces the whole conversation with a summary. Do this a few times and details from the first conversation are no longer part of the summarized conversation. Your context is split across many sessions: you have conversations with different agents over time and want to be able to reference all of that in your current conversation. Memory systems work okay in the first case and pretty well in the second case. lossless-claw works phenomenally well in the first case and only indirectly addresses the second one. Let’s expand that. Lossless context makes frequent summaries of smaller pieces of context in the background. It keeps your most recent messages around verbatim (the “fresh tail”). As the summaries accumulate, they get combined into summaries of summaries. This lets your agent stay focused: older content is still there, but becomes more “vague” over time — kind of like your own recollection of events. Current messages are always there and never suddenly disappear to be replaced by a summary. This effectively solves the “post-compaction amnesia” problem where your agent seems to suddenly forget important recent details about what you were doing. The reason lossless-claw is called “lossless” though is because your older messages never get truly removed. The incremental summaries replace the messages, but act as “pointers” to them that can be used to expand the source messages back into context. Because the summaries stick around, your agent doesn’t forget about what it can expand should it need to. By contrast, memory systems don’t offer the agent any ideas about what can they can be used to remember. This is why you have to frequently tell your agent to “search its memories” explicitly for something. This feels unnatural and is certainly inefficient. Using lossless-claw means that you can keep one conversation going indefinitely without ever needing to reset. This assesses point (2) from above indirectly: if you don’t need to start new sessions all the time, you don’t need a way to recall information from past sessions! If you work across multiple agents and want to share memories between them, or want to be able to recall information that happened outside of the scope of a conversation (eg meeting notes), you’ll want a memory system. Much of what memory systems are used for is a poor fit for them stemming from overly naive approaches to managing context, which unfortunately are industry-standard. Don’t get me wrong: they’re still useful — I still use one — but they’re not the only tool that agents need to become effective personal assistants. Lossless-claw is among the first production-grade implementations of an alternative context management strategy, and certainly the most effective, and it’s only available on @openclaw. None of this would be possible without the excellent research into Lossless Context Management pioneered by @ClintEhrlich and @rovnys at @Voltropy, so make sure to give them a follow if you’re looking for some real alpha.
There's a lot of cool stuff being built around openclaw. If the stock memory feature isn't great for you, check out the qmd memory plugin! If you are annoyed that your crustacean is forgetful after compaction, give github.com/martian-engineeri… a try!
16
11
161
34,795
Voltropy retweeted
Voltropy (W26)
Six weeks ago, we were testing LCM in the basement of @HF0 at 2AM. Today it's endorsed by @steipete as the long-context solution for @OpenClaw. Welcome to the year of Voltropy. It's only March.
1
3
18
7,047