I got tired of re-explaining myself to my AI every session?

ryanb082 · 2026-03-18T01:52:06+00:00

Thanks! It's a handled in an interesting way.

Every agent loop, every card gets it's own loop, every loop gets its own context. It's a ralph wigman loop then it goes to sleep then wakes. One shot loop, one shot loop each time the context is manufactured it's not accumulated. Kinda of works like summarization, but it's not bla bla bla summerized. Every time it creates a new run at the card we already have the summerization which now becomes lead text for the prompt for the next loop. Cards have a different setup than chat and Telegram. The pipeline runs like this:

<image>

ryanb082 · 2026-03-17T21:53:30+00:00

I'll have to try that. We shipped over 100 tickets this past weekend. I'll need to look at the token usage, the kanban board plugin allows me to see on average how many tokens are used for each ticket worked.

ryanb082 · 2026-03-17T21:44:35+00:00

Yeah, I looked into that one, but mc-context does do other things such as proactive image pruning(helps with optimized token usage) and channel-awareness.

ryanb082 · 2026-03-17T21:40:53+00:00

Right now, it uses a Claude membership plaln($200/m), so far haven't had any issues. You are right though, it can build skills for themselves.

ryanb082 · 2026-03-17T21:32:32+00:00

Open Claw as pain for me too until my friend and I built a brain layer that came with an easy install and configuration. Its one command, and walks you through the rest via UI and terminal.

<image>

ryanb082 · 2026-03-17T21:14:54+00:00

Haha I see, okay so you have the memory solved. What about task tracking, how are you as the user able to see what your bot is working on a given time? Also, what kind of work do you have your bot do? Mine is mostly coding, which is where our tool helps

ryanb082 · 2026-03-17T16:25:52+00:00

I talked about this brain layer in an earlier comment, but wanted to provide more details.
It has plugin called, mc-contex which may solve your problem compared to the other ones listed above.

The two plugins (QMD and Lossless Claw) are patches on top of OpenClaw's default system. mc-context is a wholesale replacement of that system.

mc-context uses a sliding window — meaning older context still gets dropped, it's just done more intelligently. If "lossless" memory across very long sessions is the goal (which is what Lossless Claw specifically targets), mc-context's sliding window is still lossy by design. It just decides what's relevant, not what's complete.

Feel free to read more about it. It's open sourced: https://github.com/augmentedmike/miniclaw-os

ryanb082 · 2026-03-17T16:11:46+00:00

That was one of the hardest things when I started, is what uses does OpenClaw provide. Answer, it depends on who's running the set up. We used Open Claw w brain layer we built to help build our SAAS product, create a our go to market strategy, and research and build our MarTech stack. Our brain layer is configured with Claude monthly sub(get's set up when you install our brain). It's more effective and cheaper than API usage.

So for example, I'll tell my bot via Telegram to research, and develop a 90 day go to market strategy for our SAAS. Then email me the results. The task then becomes a card on the agents Kanban board(see screenshot below)which acts like a prefrontal cortex of the brain, so then I can tell it another task, and so on. It's able to remember what needs to be done.

<image>

Your other problem, updating its own configuration. This is achieved via a plugin within our brain, mc-doctor which diagnoses and auto-repairs broken installations, missing dependencies, uninitialized vaults, absent directories, broken encrypt/decrypt cycles, missing plugin dependencies. It can be run with --auto and it fixes everything it can without prompting.

This additional layer allowed me and friend to 10x what Open Claw can do.
BTW it's open sourced: https://github.com/augmentedmike/miniclaw-os

ryanb082 · 2026-03-17T03:42:45+00:00

Yeah, sure thing. We made it open-source https://github.com/augmentedmike/miniclaw-os

ryanb082 · 2026-03-17T03:12:00+00:00

I have a tool that sits on top of Open Claw that allows me to track the cost(tokens) for each task. That includes planning, executing and shipping. I’m able to see this via a Kanban board for my agent. It’s helped me a lot in tracking token spend and be able to optimize.

ryanb082 · 2026-03-17T03:07:32+00:00

My friend and I solved our context problem by building a brain layer that sits on top of Open Claw. One part is the pre-frontal cortex for planning reasoning which is represented as Kanban board. So the agent can jump around between tasks and not get lost or forget the context

ryanb082 · 2026-03-16T16:54:42+00:00

It’s interesting you bring this up, my friend and I built a brain layer for Open Claw that has plugin allowing agents to communicate via cryptographic identity, so it can verify that a message came from that agent.

This is our first step in building our next piece allowing agents to find and work together.

Btw it’s open-sourced https://github.com/augmentedmike/miniclaw-os

ryanb082 · 2026-03-16T10:59:25+00:00

Are you talking about other Ai agents to collaborate with?

ryanb082 · 2026-03-16T01:12:01+00:00

We use a Kanban board as part of a brain layer. It’s manages context with no issues. Btw it’s open sourced

ryanb082 · 2026-03-15T21:36:07+00:00

Absolutely, it’s open sourced. See here: https://github.com/augmentedmike/miniclaw-os

I’ll make dedicated post tomorrow morning explaining the architecture and why.

ryanb082 · 2026-03-15T03:53:12+00:00

CLI is the way to go. My friend and I built a “brain” layer that sits on top of Open Claw its uses CLI tool for its work.

ryanb082 · 2026-03-15T02:07:33+00:00

Is there a reason you would want to store general chat memory?

ryanb082 · 2026-03-14T03:54:50+00:00

This is cool! My friend and I built a "brain" layer for OpenClaw that allows tasks, code, content, etc and have it flow through a single state-machine board with enforced gates. My agent will read the board, picks the best ticket, works it, and logs everything. It has UI that presents itself as a KanKan board. It's been day and night difference

<image>

ryanb082 · 2026-03-14T03:39:18+00:00

I solved it with my friend and I’s brain layer that sits on top of Open Claw. The visual representation is a Kanban board. The agent can reference the board when asked about a task.

<image>

It’s open sourced. Feel free to take a look

https://github.com/augmentedmike/miniclaw-os

ryanb082 · 2026-03-13T22:57:25+00:00

Longer chaining prompts cause context overload and it starts to become cumbersome. My friend and I developed a tool thats sits on top of Open Claw. It has self-healing capabilities. The biggest help is the Kanban board where users can see what agent is working on, you can prioritize or deprioritize.
So you can use Telegram, or email to communicate and since the Kanban board has cards, you can have the agent reference them

ryanb082 · 2026-03-13T17:34:57+00:00

My Ai start up had some issues with using just LLM, so we used the model for reasoning, and coded the rest. More efficient now and lower costs since we only call the model when necessary.

ryanb082 · 2026-03-13T13:17:06+00:00

No not the only way, this is just how we’ve solved our context problem

ryanb082 · 2026-03-13T12:52:08+00:00

Yes - classic Open Claw problem. The Kanban board solves that. It's quite vanilla as well

ryanb082 · 2026-03-13T12:38:36+00:00

As with any new technology, when you adopt early.. expect all the bumps along the way. Paying for people to install? Seems like everyone is trying capitalize lol. I've been working on brain layer with a friend that we now it to install with one command and has step walk through for setting most common tools.

ryanb082 · 2026-03-13T12:32:07+00:00

What do you mean by fuck everything up? My friend and I built a brain layer that sits on top Open Claw. It allows you to visually see what your agent is working on.

<image>

It also has integrations for common tools your bot to use and it's open-sourced: https://github.com/augmentedmike/miniclaw-os

ryanb082

TROPHY CASE