Hypabase Memory

Persistent memory for agents. Stores preferences, decisions, facts, and events as a connected knowledge graph. Recalled by who, what, when, or why.

MIT-0 · Free to use, modify, and redistribute. No attribution required.
0 · 269 · 1 current installs · 1 all-time installs
MIT-0
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (persistent agent memory) align with what the skill asks for: a database path (HYPABASE_DB_PATH) and the uvx runner to launch a Hypabase MCP server. Requiring uvx to run the Hypabase adapter is coherent.
Instruction Scope
SKILL.md instructs adding an MCP server entry to ~/.openclaw/openclaw.json (expected for enabling the memory tool). It also documents memory APIs (remember, recall, consolidate, forget). The file references optional embedder-related env vars (e.g., HYPABASE_EMBEDDER and an OpenAI embedder) — these are not required for basic operation but are mentioned and may imply networked calls if chosen.
Install Mechanism
Instruction-only skill with no install spec or code files; low-risk from install point of view. It relies on the external 'uvx' binary which the user must install separately (SKILL.md references uv project docs).
Credentials
Declared primary credential HYPABASE_DB_PATH (SQLite path) is proportionate. The SKILL.md also documents optional env vars for embedders (including an OpenAI option that would require an API key). Those optional external credentials are not listed as required in the metadata — this is reasonable but worth noting because selecting an external embedder can introduce networked credential use.
Persistence & Privilege
always:false (normal). The setup instructs editing the user's OpenClaw config (~/.openclaw/openclaw.json) to add an MCP server entry — this is expected for enabling the tool but does modify agent configuration and causes a local background server (uvx) to be invoked when used.
Assessment
This skill appears to do what it says: run a local Hypabase memory server and store memories in a SQLite DB. Before installing: verify the source of the 'uvx' runner (trustworthy upstream), pick a safe HYPABASE_DB_PATH (it's a local SQLite file that will hold stored memories), and be aware that choosing an external embedder (e.g., OpenAI) will require supplying API credentials and will send text to that provider for embeddings. If you prefer purely local operation, use the local embedder option (fastembed/ONNX) and avoid supplying cloud API keys. Also note the setup edits your OpenClaw config to add an MCP server — review that change and the uvx command/args before enabling it.

Like a lobster shell, security has layers — review code before you run it.

Current versionv0.2.4
Download zip
latestvk977v3eppddf1yxw64h28jyyq581yh7s

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🧠 Clawdis
Binsuvx
Primary envHYPABASE_DB_PATH

SKILL.md

Hypabase Memory

Persistent memory for agents. Stores preferences, decisions, facts, and events as a connected knowledge graph. Recalled by who, what, when, or why.

Setup

Add the MCP server to your OpenClaw config (~/.openclaw/openclaw.json):

{
  "mcpServers": {
    "hypabase-memory": {
      "command": "uvx",
      "args": ["--from", "hypabase", "hypabase-memory"],
      "env": { "HYPABASE_DB_PATH": "hypabase.db" }
    }
  }
}

uvx handles all Python dependencies automatically. Requires uv.

Quick start

Store a memory — one verb, roles for the participants:

remember(penman='(prefers :subject Alice :object Python :memory_type semantic)')

Recall it:

recall(entity="Alice")                              # everything about Alice
recall(entity="Alice", action="assign", role="subject")  # what Alice assigned
recall(entity=["Alice", "Bob"])                     # memories involving both
recall(mood="planned")                              # all plans

When to Remember

Store a memory when the user:

  • Makes a decision or states a preference
  • Shares a fact about themselves, their team, or a project
  • Assigns a task or delegates work
  • Describes an event, meeting, or outcome
  • Explains a procedure or workflow

PENMAN Notation

Every memory is a verb with participants in role slots:

(verb :role "entity" :role "entity" ...)

Examples:

(prefers :subject Alice :object Python :memory_type semantic)

(assigned :subject Alice :object "billing task" :recipient Bob
 :instrument Jira :locus Monday :tense past :memory_type episodic)

(has :subject "quick sort" :attribute "time complexity"
 :value "O(n log n)" :memory_type semantic)

Multiple atoms in a single call:

(deployed :subject Alice :object API :locus Monday :tense past)
(reviewed :subject Bob :object API :locus Tuesday :tense past)

One action per memory. When a sentence contains multiple actions, decompose into separate atoms. Shared entities link them in the graph.

"Alice told Bob to migrate the database":

(told :subject Alice :recipient Bob :object "database migration" :tense past)
(migrate :subject Bob :object database :mood planned)

Any role slot can hold a nested atom:

(believes :subject Alice :object (is :subject deadline :value Friday))

Entity Naming

Same string after lowercasing = same entity. Different strings = different entities until consolidate() merges them.

  • Pick one canonical name per entity and reuse it.
  • Use full descriptive names: "machine learning" not "ML", "JavaScript" not "JS".
  • Call consolidate() periodically to merge similar names via semantic similarity.

Tools

remember(penman, source?, confidence?)

Store memories as PENMAN atoms.

  • penman (required): One or more PENMAN atoms.
  • source (optional): Provenance source. Default: "memory".
  • confidence (optional): 0.0–1.0. Default: 1.0.

recall(entity?, action?, role?, memory_type?, mood?, negated?, since?, before?, limit?, min_strength?)

Query memories. At least one parameter required.

  • entity: Name or list of names.
  • action: Filter by verb.
  • role: Filter by role (subject/object/instrument/recipient/source/locus/attribute/value).
  • memory_type: episodic / semantic / procedural.
  • mood: actual / planned / uncertain / normative / conditional.
  • negated: true = only negated, false = only positive.
  • since / before: ISO date strings.
  • limit: Max results (default: 10).
  • min_strength: Minimum memory strength threshold.

consolidate(entity?)

Merge similar entities and compress repeated memories.

forget(older_than_days?, min_strength?, entity?)

Expire old or low-strength memories (soft delete).

Reference

Roles

Eight roles. Fill in what applies, skip what doesn't.

PENMAN roleRecall roleMeaningExample
:subjectsubjectWho or what it's aboutAlice
:objectobjectWhat is acted onthe proposal
:instrumentinstrumentTool, method, or meansSlack
:recipientrecipientWho receives or benefitsBob
:originsourceWhere it came fromthe old system
:locuslocusWhere, when, or contextsprint review
:attributeattributeA named propertytime complexity
:valuevalueThe specific valueO(n log n)

Memory types

TypeUse forDecay rate
episodicEvents, meetings, conversationsFast
semanticFacts, preferences, definitionsSlow
proceduralHow-to, workflows, processesSlowest

Moods

MoodWhen to use
actualSomething that happened or is true (default)
plannedSomething intended to happen
uncertainSomething that might be true
normativeSomething that should or shouldn't be
conditionalSomething that depends on a condition

Modifiers

ModifierValuesDefault
:tensepast, present, future--
:negatedtrue, falsefalse
:importance0.0 to 1.0--
:causeNested atom: why it happened--
:purposeNested atom: what for--
:conditionNested atom: if/when/unless--

Environment variables

  • HYPABASE_DB_PATH -- SQLite database path (default: hypabase.db)
  • HYPABASE_EMBEDDER -- Embedder for semantic search:
    • fastembed (default) -- BAAI/bge-small-en-v1.5 via ONNX
    • openai -- text-embedding-3-small (requires OPENAI_API_KEY)
    • sentence-transformers -- all-MiniLM-L6-v2
    • none -- disable embeddings

Files

2 total
Select a file
Select a file to preview.

Comments

Loading comments…