rushdb-agent-memory

Store and link agent memories as structured records in RushDB.

320|25|Updated Dec 15, 2024
One-click install
npx skills add https://github.com/rush-db/rushdb --skill rushdb-agent-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rushdb-agent-memory
Source: https://github.com/rush-db/rushdb/tree/main/packages/skills/rushdb-agent-memory
Command: npx skills add https://github.com/rush-db/rushdb --skill rushdb-agent-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

RushDB Agent Memory provides a persistent, structured memory layer for AI agents, enabling durable storage of session data, decisions, and context. It unifies memory across conversations by constructing a connected graph of memories and relationships, replacing disparate vector stores and key-value caches with a single ACID-safe store.

Core Features & Use Cases

  • Store memories as typed records (e.g., SESSION, DECISION, ENTITY) and auto-link nested data into a graph.
  • Recall memories by meaning with semantic search, traverse related memories, and preserve context across sessions.
  • Replace fragmented memory tooling with a unified, graph-backed memory layer that supports ACID guarantees and complex queries.

Quick Start

Store a memory with a labeled data object and recall it later by semantic meaning.

Frequently Asked Questions about rushdb-agent-memory

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

FAQPage Schema
How do I add persistent memory to an AI agent across multiple sessions?

Persistent memory is achieved by storing session data and decisions as structured records in a graph database, enabling semantic recall and relationship traversal across multiple sessions. This approach replaces fragmented key-value caches with a unified ACID-safe store.

What is the best way to store and retrieve agent memories by semantic meaning?

Semantic recall is handled by storing labeled data objects as typed records and querying them by meaning. This allows agents to retrieve relevant context without relying on exact keyword matches.

Do I need an MCP server to use a graph database for agent memory?

Yes, an MCP server and specific client tooling are required to create records, bulk create data, query by meaning, and traverse relationships when using this graph-backed agent memory approach.

How does graph traversal improve AI agent context compared to vector stores?

Graph traversal improves context by auto-linking nested data into a connected graph of memories and relationships, replacing disparate vector stores with a single ACID-safe store that supports complex relationship queries.

Can I store different types of memories like decisions and entities in a single memory layer?

Yes, memories can be stored as typed records such as SESSION, DECISION, or ENTITY within a single unified memory layer. This allows diverse data types to be auto-linked and queried together.