> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wazoo.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# MemSearch

> Worlds vs MemSearch: a standalone memory library for coding assistants against a shared fact graph.

## At a glance

|                 | Worlds                        | [MemSearch](https://github.com/memsearch) |
| :-------------- | :---------------------------- | :---------------------------------------- |
| Data model      | RDF triples in a ledger       | Vector memory store                       |
| How facts enter | Import, patches, agent writes | Session capture                           |
| Retrieval       | Hybrid search + SPARQL        | Similarity search                         |
| Provenance      | Fact-level ledger             | None                                      |
| Deployment      | Hosted beta or embedded       | Library, self-managed                     |

## The philosophical difference

[MemSearch](https://github.com/memsearch) is a standalone, MIT-licensed memory
library extracted from the OpenClaw autonomous agent. You drop it into a project
and recall past sessions by similarity. Its plugin for Claude Code gives the
coding assistant persistent, human-readable memory across development sessions.

Worlds is a graph of curated facts. For coding assistants the difference is what
counts as memory. MemSearch recalls what you did before; Worlds asserts facts
about the codebase and organization that must be true, such as the service that
owns a pipeline or the person on call. Recall is similarity; assertion is state.

## When Worlds fits

* The fact must be checkable: which team owns this service must resolve exactly.
* You want relationships between facts, not just session history.
* State changes over time and you need to see the timeline.

## When Worlds does not fit

* You want memory today with a single library and no backend, tokens, or graph
  vocabulary to set up.
* Recalling past work by similarity is the whole job.
* You do not want to choose any vocabulary. Worlds reuses standard RDF and
  schema.org vocabularies ([items](/worlds/index)), but you still pick the
  domain predicates.

## Coexistence

Keep MemSearch inside the coding assistant for session recall, and point the
assistant at Worlds for authoritative project facts. The
[OpenClaw integration](/integrations/openclaw) and
[Claude Code integration](/integrations/claude-code) both describe how an
assistant reaches Worlds for verified context.