Joined April 2010
52 Photos and videos
Pinned Post
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
158
32,405
coming soon to lossless-claw: instant compaction chunks of context will be summarized in the background, building a "pending DAG" of summaries once /compact is run or threshold compaction kicks in, it's a simple swap of a precomputed summarization
2
9
749
was on the road today, got a notification that payment went through for some unused saas I'd forgotten about, and thought wait a minute... pulled out codex — "can you cancel this subscription for me?" it opened browser, navigated many menues, ignored discounts, cancelled boom
7
2
61
18,343
Josh Lehman reposted
Will be talking about the "app situation" and roadmap plans with @hrudolph live TODAY at 11:30 AM PST on the official OpenClaw podcast, live on Discord. discord.com/invite/clawd?eve…
19
15
171
77,352
Josh Lehman reposted
Just imagine launching an app after stuck in review for ages with a small team of maintainers and you hit #24 in productivity in the Apple App Store in <1 day. Just imagine!
imagine getting acquired by @OpenAI, get unlimited AI tokens and still drop this slop abomination
25
6
110
11,955
to update: openclaw plugins update @martian-engineering/lossless-claw openclaw gateway restart
5
320
lossless-claw 0.13.0 — the "four days of Fable" release 🧹 big refactor pass while we had Fable 5 🧠 transcript memory rebuilt on stable entry IDs 🧊 frozen/stalled conversations self-heal more often 📓 independent daily JSONL logs for easier debugging 🎚️ scoped context thresholds for different sessions/models
3
27
3,038
In hindsight the name “Fable” makes perfect sense. Once upon a time, we had this model…and then it vanished!
2
7
646
Josh Lehman reposted
Microsoft Build was one of those weeks I’ll be thinking about for a long time. I presented at Backstage at Build. Networked at GitHub Build on Tap. Two packed days in the Open-Source Zone. Eight straight hours talking with people about OpenClaw. A few "secret location" moments (more to come soon)! A couple of private dinners with very sharp people. Then closing it out with the amazing OpenClaw After Hours at GitHub event. I joked during the week that I was the dumbest person in the room, and I meant it as a compliment to the room. Huge thank you to @OpenClaw, @Microsoft, and @GitHub for making the week possible, and for giving this project and community such a strong place to show up. Special thanks to @ashleywolf, @KevinCrosby1, @GreggCochran, @OmarShahine, @shanselman, @steipete, @vincent_koc, @davemorin, @ArnoldCastro, @RegGroux, and the many others who made the week what it was. The best part wasn’t the schedule. It was the nearly 20 of my fellow OpenClaw maintainers, the people who stopped by, asked hard questions, shared ideas, challenged assumptions, and got excited about where OpenClaw is headed. GitHub Universe, anyone? #MicrosoftBuild #OpenClaw #GitHub #GitHubUniverse Thanks to all of my fellow maintainers: @BunsDev, @somalley108, @dallinfinite, Agustin Rivera, @pat_erichsen, @joshavant, @jlehman_, @_JacobTomlinson, @jesse_merhi, @thescottfan, Sarah Fortune, and @kevins8.
1
6
32
1,220
OpenClaw is a big deal, but the systems that OpenClaw is pioneering to build software like this at agentic scale are at least as significant. This is where software engineering is going — pay attention.
Here’s the video of my talk at MS Build: Build the thing that builds the thing. build.microsoft.com/en-US/se…
5
9
171
52,543
Josh Lehman reposted
Josh Lehman is one of the maintainers of OpenClaw, and he's shipping like a beast. In this episode he tells us how he built and shipped a paying SaaS product in 36 hours from a Costco parking lot, talking to his claw between family obligations. Episode 4 @jlehman_
1
1
7
843
to update: openclaw plugins update @martian-engineering/lossless-claw openclaw gateway restart
4
900
x.com/jlehman_/status/205649…
This release introduces a new feature called "focus mode" that lets you curate your context to what's most relevant to the task at hand. lossless-claw allows you to have a conversation of indefinite length in one session. It accomplishes this by compressing older information into summaries that can be “expanded” back to their original source material on-demand. If you’re context switching a lot in one session though, your session will still end up with a lot of material that’s probably not relevant to what you’re doing right now. /lossless focus <prompt> kicks off a subagent to build an in-depth summary of whatever you include in <prompt> by searching deeply through past context to put together a targeted summary with specific expansion cues. It replaces the normal DAG summaries in assembled context with this new “focus brief.” This lets you build an on-demand context that’s most relevant to the problem at hand. At any time you can run /lossless unfocus to remove it and restore the normal DAG-based summaries, or run a new /lossless focus <prompt> to shift focus to something else. While in focus mode, normal lossless summarization will still happen and accumulate as usual. You can run /lossless refocus to incorporate the newer material into the original prompt, producing a new focus brief that replaces the old one that incorporates relevant information since the original was generated. All three of these commands — focus, unfocus, refocus — trigger full compaction first since they mutate the prompt prefix. If we’re going to break the prompt cache, we might as well do it all at once. One caveat: if you use this with GPT 5.5 as your summary model and have a long-running session, be prepared to wait for a while. I’ve seen it take up to 10 minutes to complete. Being thorough has a cost! Using GPT 5.4-mini will make this much faster.
3
1,559
This release introduces a new feature called "focus mode" that lets you curate your context to what's most relevant to the task at hand. lossless-claw allows you to have a conversation of indefinite length in one session. It accomplishes this by compressing older information into summaries that can be “expanded” back to their original source material on-demand. If you’re context switching a lot in one session though, your session will still end up with a lot of material that’s probably not relevant to what you’re doing right now. /lossless focus <prompt> kicks off a subagent to build an in-depth summary of whatever you include in <prompt> by searching deeply through past context to put together a targeted summary with specific expansion cues. It replaces the normal DAG summaries in assembled context with this new “focus brief.” This lets you build an on-demand context that’s most relevant to the problem at hand. At any time you can run /lossless unfocus to remove it and restore the normal DAG-based summaries, or run a new /lossless focus <prompt> to shift focus to something else. While in focus mode, normal lossless summarization will still happen and accumulate as usual. You can run /lossless refocus to incorporate the newer material into the original prompt, producing a new focus brief that replaces the old one that incorporates relevant information since the original was generated. All three of these commands — focus, unfocus, refocus — trigger full compaction first since they mutate the prompt prefix. If we’re going to break the prompt cache, we might as well do it all at once. One caveat: if you use this with GPT 5.5 as your summary model and have a long-running session, be prepared to wait for a while. I’ve seen it take up to 10 minutes to complete. Being thorough has a cost! Using GPT 5.4-mini will make this much faster.
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
1
4
34
4,278
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,425
Josh Lehman reposted
@jlehman_ Lossless is the only external plugin I can’t do without! Great project!
2
10
997
Lots of the features in this one were focused on codex harness compatibility. When the next version of OC drops it’ll be much, much better.
lossless-claw 0.10.0 — the "long chats survive" release 🧵 recall spans rotated conversation segments 🧹 full-sweep compaction replaces cache-churning incrementals 🧊 hot prompt caches stay protected under normal pressure 🔁 bootstrap/restart transcript weirdness fixed 📦 fresh installs need fewer hacks
17
1,357
Peter was fond of telling me that lossless-claw trashed the cache. I tried to find creative ways around that, but ultimately he was right — incremental compaction is just bad for prompt caching. That's been removed and now it's much more cache-friendly.
Lossless is a really interesting concept for OpenClaw to have an "infinite" context window/memory. It compacts conversations in blocks that the model can refer to, building a tree to look up past messages.
4
32
2,430
to update: openclaw plugins update @martian-engineering/lossless-claw openclaw gateway restart
1
1
9
4,764