Recipes
Memory Layer is built for coding agents, but the engine underneath — capture, curation, cited retrieval, honest refusals, self-maintaining activation — works for any project that accumulates durable knowledge. These recipes are short, copy-paste paths into six unconventional uses. Each needs only a running service (quickstart) and works keyless.
Obsidian / note vault
Make a Markdown vault queryable with cited answers, and keep it synced.
Research-paper corpus
Ingest reading notes, query across them, and share the corpus as a bundle.
Game NPC memory
Give NPCs durable, decaying memory of what the player did — over the HTTP API.
Skyrim playthrough chronicle
A tiny quest mod + bridge daemon chronicle your playthrough; ask "where did I leave off?".
Home automation
Record automation decisions as memories and ask "why did the heating turn on?".
Memory for your AI chats
Point any MCP client (Claude Desktop, Codex) at a chats project — pure configuration.
Two building blocks appear in every recipe:
memory ingest— turn a directory of documents into memories, no git required.- The HTTP API — the current v2 contract under
the
/v1route namespace (/v1/capture/task,/v1/query, …) for anything that is not a directory of files. Fetch/v1/openapi.yamlfrom the running service before upgrading a direct integration.