Sessions end
A large context window can hold more of the current conversation. It does not automatically become durable knowledge for the next one.
FreeOpenClaw installer kit · v0.2.0
Your agent needs more than one memory blob.
The OpenClaw Memory Stack connects five distinct layers for automatic recall, session compaction, durable facts, daily execution notes, and optional cross-session retrieval.
Free email delivery. No checkout. Built for OpenClaw; compatibility with current Hermes is not verified.
Non-destructive installExisting files are backed up before managed blocks are applied.
Plain-file foundationDurable knowledge stays in Markdown you can inspect and correct.
Full source includedScripts, templates, examples, documentation, and tests ship together.
The failure mode
A context window is not a memory system.
Long context helps inside one conversation. Durable memory needs different jobs handled by different layers, with files remaining the source of truth.
Summaries flatten detail
Compaction helps the active thread, but important facts still need a durable place you can inspect, correct, and retrieve later.
One pile degrades
Daily execution logs, stable facts, current-session detail, and temporal history have different retrieval needs. Treating them as one blob creates noise.
Five layers
One job per layer. One system around them.
The kit does not pretend one database solves every kind of memory. It gives each layer a clear role and connects them through a portable installer.
Gigabrain · automatic recall
Surfaces relevant memories before a prompt and captures facts worth retaining.
LCM · session compaction
Compresses long conversations while preserving a path back to source messages.
OpenStinger · temporal retrieval
Adds optional cross-session recall and point-in-time history for multi-session work.
PARA · durable knowledge
Stores people, companies, projects, decisions, and stable facts in plain Markdown.
Daily notes · execution timeline
Records what happened today, what changed, and why a decision was made.
Before and after
Stop making every session start from zero.
BeforeThe agent starts a new conversation without the facts that shaped the last one.
→
AfterRelevant memory can be recalled before work begins.
BeforeLong threads collapse into summaries with no clean route back to detail.
→
AfterSession compaction preserves recoverable source material.
BeforeStable business facts live beside disposable daily chatter.
→
AfterDurable facts move into structured, inspectable Markdown.
BeforeWorkspace files grow until they consume the context they are meant to help.
→
AfterBootstrap files route retrieval instead of swallowing the whole knowledge base.
Installer flow
Preflight. Apply. Verify.
The scripts inspect the target workspace, create backups, add managed blocks, and keep repeat installs idempotent.
# 1. Check the target workspace bash scripts/preflight.sh /path/to/workspace # 2. Apply the core stack + guidance bash scripts/apply.sh /path/to/workspace \ --mode core-plus-guidance # 3. Run the installer contract checks python3 scripts/run_qa.py contract ✓ backups created ✓ managed blocks applied ✓ source files preserved
Complete archive
The full installer kit. Now free.
The recovered v0.2.0 archive is internally intact and includes the packaged installer plus its source, documentation, and QA harness.
Get the archive
Send the Memory Stack to your inbox.
Enter your details and we will email you an expiring download link. The ZIP is not published on this page.
FREE DOWNLOADDELIVERED BY EMAILNO SPAM. UNSUBSCRIBE ANYTIME
Compatibility
Read this before you install it.
Is this built for Hermes?
No. This is the original OpenClaw v0.2.0 installer kit. Its architecture remains useful, but current Hermes compatibility has not been verified.
Will it overwrite my workspace files?
The installer is designed to create backups and append managed blocks rather than replacing existing AGENTS.md and MEMORY.md content. Review the scripts before running them on a live workspace.
Do I need every layer?
No. The archive includes core, core-plus-guidance, and core-plus-openstinger modes. Start with the file foundation and add infrastructure only when the retrieval need justifies it.
Where is the source?
The complete source is included in the emailed archive alongside the packaged installer, documentation, templates, examples, and QA harness.
Need memory designed around a real operating loop?
Map the workflow first. Then decide what the operator must remember, where truth lives, and what gets reviewed by a human.