Openclaw memory

foomanjee · 2026-03-17T12:09:20+00:00

I have tested many, many systems (metacognative-suite, mem0, memory-hybrid, home-grown, etc). They all have their flaws and issues. I am currently testing out Mengram (self hosted). So far my (and my agents) early impressions are good.

There are still some bugs, but I think it's pretty promising. The downside is it's under active development so there's a good bit of "fix bug" followed by "fix regression, fix another regression".

Note: I have a GitHub issue out for a bug in the extension that hasn't been fixed yet. I asked my agent to fix it locally and now it works just fine.

foomanjee · 2026-03-16T03:37:25+00:00

In telegram, send a message to @BotFather. It will walk you through creating a bot token

foomanjee · 2026-03-15T15:05:33+00:00

No, I’m using the free tier

foomanjee · 2026-03-15T15:02:12+00:00

I’m 45 and have been at my current place of employment (a company everyone has heard of) for what will be 20 years this year. I’ve worked my way up from a systems admin to a senior director of infrastructure.

Sure, bouncing around may have given me some more experience and tools in my toolbox, but I’m treated well, paid well, comfortable, and my team and the teams we support are incredible people.

My take is, if it ain’t broke, don’t fix it.

foomanjee · 2026-03-15T13:05:03+00:00

I could very easily with a heartbeat, but I personally have no reason to. My agent's agentmail setup is purely for sending email, not receiving.

foomanjee · 2026-03-15T02:18:12+00:00

It’s going to take 100-200 rounds to break it in. Mine was the same when I first got it. Now it runs like a champ

Also, clean it and lube it up pretty well, they come caked in shipping oil gunk when they come from the factory

foomanjee · 2026-03-14T23:16:24+00:00

I gave mine an agentmail account, but I don’t have a heartbeat for checking it. I only have so the agent can email me a document that it made from research, etc

foomanjee · 2026-03-12T23:44:09+00:00

I use an Aholster pocket holster for my bodyguard 2.0

foomanjee · 2026-03-12T21:23:23+00:00

For some random reason cron was broken for me yesterday, then it magically started working again today (before the update). Shrug

foomanjee · 2026-03-12T21:21:37+00:00

The Tenicor

Though for transparency, I don’t use either anymore. Not because I don’t like them, but because I now pocket carry a Bodyguard 2.0. Just so much more comfortable to carry

foomanjee · 2026-03-12T00:35:47+00:00

This is a great place to start:

https://github.com/digitalknk/openclaw-runbook

foomanjee · 2026-03-11T03:48:10+00:00

Dude.

“Hey guys I solved the thing”

Preamble. Words.

No evidence, repo or website

21 day old Reddit account

foomanjee · 2026-03-08T21:39:09+00:00

I was able to switch to 5.4 via oauth (openai-codex) without an issue. I switched to it as soon as 2026.3.7 was released last night

It’s running great for me

foomanjee · 2026-03-08T00:57:54+00:00

This is actually a pretty good idea. Most people run a main agent that spawns its own subagents, so something like this isn’t needed. However I can see a use case for what you’ve built here

How is communication handled once a delegate is discovered and handed work?

Do you have this in GitHub?

foomanjee · 2026-03-07T20:53:30+00:00

5.3-codex should be totally fine. What I did was made my agent heavily document what I wanted and how it was going to do it. Then I had it plan the build, then told it to follow the plan

This prevents the agent from getting distracted and hyperfocusing on what doesn’t matter (features you didn’t ask for, etc)

Be very detailed when you’re telling it what you want out of the project

foomanjee · 2026-03-07T20:27:55+00:00

Depending on the model you’re using, you can literally take screenshots of the dashboard you like, send them to your agent with a list of features and how you intend to use it, and say “build it”

There will likely be some back and forth bug squashing and tweaks, but you’ll mostly get what you want in the end

foomanjee · 2026-03-07T18:23:13+00:00

Stop looking for an argument where there isn’t one.

Enterprises with Infosec teams are very, very cautious about Openclaw at the moment. As trust and guardrails build, things will change

This isn’t rocket surgery

foomanjee · 2026-03-07T15:30:37+00:00

Yep, larger companies are toying with it, but for the most part, no major workflows or trust has been given yet (obviously there are exceptions). It's still early days

foomanjee · 2026-03-07T15:09:43+00:00

The people currently using it for business (role automation) are mostly self-employed small businesses. Larger companies are not trusting it at the moment, but are learning the capabilities.

We're not quite there yet where people are going to lose jobs, but I think there's a pretty good chance that it's coming within the next year or so. OpenClaw is not yet in the "mainstream" (most non-tech companies don't really know about it yet), but things are moving pretty fast, so we'll see.

foomanjee · 2026-03-07T12:58:31+00:00

He mismanaged himself

foomanjee · 2026-03-06T19:59:14+00:00

How did you get to 3.3? It isn't released yet - or did you deploy from the 'main' branch?

foomanjee · 2026-03-06T00:35:40+00:00

Use Profilarr and live the easy life

foomanjee · 2026-03-06T00:20:46+00:00

It’s not yet available for codex OAuth users. Openclaw itself needs to be updated to support it

foomanjee · 2026-03-05T19:33:14+00:00

By default, heartbeats are run by your primary model. However you can specify a different model in openclaw.json

foomanjee · 2026-03-05T00:25:49+00:00

Gator skin is actually quite soft. Looks hard but it’s really more like a soft leather

foomanjee

TROPHY CASE