fluid-memory

Manage conversational memory with decay-based semantic retention and ChromaDB archival.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/wjlmrzd/OpenClaw-Wren --skill fluid-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fluid-memory
Source: https://github.com/wjlmrzd/OpenClaw-Wren/tree/main/skills/fluid-memory
Command: npx skills add https://github.com/wjlmrzd/OpenClaw-Wren --skill fluid-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fluid Memory solves the problem of unbounded, noisy conversational context by converting transient chat history into a semantic, decay-aware memory store that strengthens frequently accessed facts and archives or deletes low-value information automatically.

Core Features & Use Cases

  • Semantic vector storage using ChromaDB for embedding-based recall instead of keyword matching.
  • Decay + reinforcement model that reduces the weight of stale memories while boosting items accessed repeatedly (Ebbinghaus-inspired).
  • Incremental summarization and buffering to aggregate recent dialog and commit compact summaries to the vector store upon OpenClaw memory flush events.
  • Maintenance daemon and archival that nightly consolidates and archives low-value memories and hard-deletes long-archived items.
  • Use case: Keep a user's preferences and decisions accessible across sessions while automatically forgetting ephemeral or obsolete details.

Quick Start

Ask the agent to remember that the user prefers cola so Fluid Memory will store that preference during the next OpenClaw memory flush.

Frequently Asked Questions about fluid-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does semantic memory with decay-based recall work for conversational agents?

Semantic memory with decay-based recall converts transient chat history into a vector store where frequently accessed facts are reinforced while stale or low-value information is automatically down-weighted, archived, or deleted over time.

How do I store user preferences across sessions using ChromaDB vector storage?

You can store user preferences across sessions by asking the agent to remember the preference, which Fluid Memory commits to local ChromaDB vector storage during an OpenClaw memory flush event using incremental summarization.

Can I automate archival and deletion of low-value conversational memories?

Yes, you can automate archival and deletion of low-value conversational memories using a maintenance daemon that nightly consolidates archived items and hard-deletes long-archived entries based on configurable decay and boost thresholds.

Does OpenClaw support incremental summarization for memory flush events?

OpenClaw supports incremental summarization for memory flush events by aggregating recent dialog into compact summaries and committing them to the semantic vector store, preventing unbounded and noisy conversational context.

What is the best way to manage unbounded conversational context in Python agents?

The best way to manage unbounded conversational context in Python agents is applying a decay-aware semantic retention model that strengthens frequently accessed facts and archives obsolete details automatically using local vector storage.