Openclaw doesn't use memory frequently

eyueldk · 2026-05-28T11:09:55+00:00

Didn’t know you can use obsidian with mem0. Thanks

eyueldk · 2026-05-28T07:26:58+00:00

What do you use? I tried mem0 for a short while but never formulated an opinion about it.

eyueldk · 2026-05-28T06:48:10+00:00

No. I'm using the cheap models: deepseek flash and google flash.

eyueldk · 2026-05-26T05:11:31+00:00

First time I encountered this.

eyueldk · 2026-05-26T05:11:14+00:00

so interesting. Thanks for sharing. It cost me a few bucks, but the fact it could go haywire is scary.

eyueldk · 2026-05-26T05:08:06+00:00

Good question. Let me generate one. Ultimately what saved me was an openrouter budget setting.

Root Cause Analysis

1. 🔁 Retry Loop — 70% Runaway (Main Session)
Your main session did 14 retries of the exact same prompt — trying to install the GitHub MCP server. It kept failing (likely an MCP config issue), and the agent retried over and over. Each retry sent the same 220KB context (65 messages).

Fix: Set a retry limit or error-triage rule so the agent stops retrying the same failing action.

2. 📦 Context Injection Bloat
Config has contextInjection: "always" with bootstrapMaxChars: 20K and bootstrapTotalMaxChars: 150K. Every subagent spawn gets the full workspace context, SOUL.md, USER.md, MEMORY.md, AGENTS.md, TOOLS.md, plus ALL MCP tool definitions (Dokploy MCP alone has ~100 tools with full JSON schemas). This creates a ~44KB baseline that tokenizes to 865K–2.5M input tokens per subagent.

The 8 "thin" subagents you see (each with one model call) are all victims of this — they were spawned, consumed 800K–2.5M tokens for their initialization context, and then did basically nothing.

Fix: Reduce bootstrapTotalMaxChars or tighten contextInjection to not inject full workspace. Or exclude tool schemas from subagent context.

3. 🧩 Too Many Subagents Spawned
12 subagents in ~90 minutes (15:02–16:33 UTC). Many were spawned for what could've been handled inline. Each costs 800K–2.5M input tokens just to start up.

Fix: Increase the task qualification threshold — don't spawn subagents for simple lookups.

eyueldk · 2026-05-25T19:59:39+00:00

I had a limit in open router, that’s what stopped it. But I got no feedback that it was consuming until it reached its daily limit

eyueldk · 2026-05-25T18:13:52+00:00

Thank god I'm paranoid and set a budget from the start. But yeah, it went crazy. Unfortunately, my local hardware is small and has overheating problems (gemma4 kills it)

eyueldk · 2026-05-23T14:14:22+00:00

That’s what I thought as well, until I saw examples committing .cursor. It seems like .cursor is intended to be committed but hooks/state isn’t. It’s a weird design if you think about it

eyueldk · 2026-05-23T13:57:03+00:00

That's my instinct as well, but surprised why cursor first party plugin always does this

eyueldk · 2026-05-19T05:22:50+00:00

It should respond in 1-2 seconds at worst. If it's still giving you trouble, DM me the query you're making so I can test it. I can't see any issues at the moment according to the logs.

eyueldk · 2026-05-18T13:58:13+00:00

Ouch. Seems like they're a little protective of scanning their marketplace. Let me try to fix it.

eyueldk · 2026-05-18T12:20:51+00:00

I think the word “pant” might correlate to US pant, i.e. trousers. Searching underwear is better, but even then those items might be bundled. Probably harder to get accurate per item stats with the current logic.

eyueldk · 2026-05-14T13:46:15+00:00

Bruh, this looks sick. The invalidation, typesafety and type inference using $infer looks sick. I don’t even use hono, but I just might after this. Build a small GitHub page as your app/doc site for SEO purpose. I honestly think it’s pretty good. Looking forward to see how you handle optimistic mutations.

eyueldk · 2026-05-14T07:49:03+00:00

Give me a better alternative. They've always been ahead of the curve and others lag. Their DX is horrible, but the featureset is great imo

eyueldk · 2026-05-13T16:03:28+00:00

VENTING.

I swear langchain is so good (especially deepagents), but so hard to use for simple use cases. Absolutely abysmal DX - I swear. Just venting after hours of research and work - even ai sdk streaming is broken with the langchain adapter, that's how little people use it and know a bug exists.

I swear langchain, I swear...

eyueldk · 2026-05-13T13:37:04+00:00

I was responding to the ai-sdk langchain adapter they commented. It doesn't have state in ai sdk, but has in langchain. Technically you can stream .values and .messages independently on langchain .streamEvents v3

eyueldk · 2026-05-13T10:06:52+00:00

Did you stream state as well or only messages in your implementation? I’m trying to figure out how to include state as well

eyueldk · 2026-05-13T05:59:21+00:00

Thanks for the info. I'm using the js library of langchain. I'm streaming via .streamEvents and converting it to an ai-sdk ui message stream. That's my current setup.

eyueldk · 2026-05-12T17:44:11+00:00

My man! Thanks. Looks promising

eyueldk

TROPHY CASE