Cairn-ink/cairn-memory

Keep important context between AI sessions. Change it when things change.
English · 繁體中文
See an example ·
Where to start ·
Local setup ·
Hosted setup ·
Limitations ·
Privacy
Starting a new AI session often means repeating your preferences and project
decisions. Cairn provides memory tools to save that context between sessions,
inspect the submitted text behind each memory, and update it when things change.
A preference changes
Suppose you save **“Keep my reports short.”** Later, you decide you need detailed
reports. You can inspect the old memory and its source text, correct the saved
preference, or forget it so it is no longer available for active recall.
This is an **illustrated explicit-tool example**, not a chat-client screenshot.
The local preview uses tools to save, inspect, correct and forget; it does not
automatically read your conversations.
- **Inspect the source.** Read the source text stored with a memory. A receipt
does not prove that the memory is true or correctly interpreted.
- **Correct what changed.** Update the memory at the revision you inspected.
- **Forget what should go.** Remove a memory from active recall.
Deletion and backup boundaries apply.
A **Source Receipt** is the submitted text attached to a memory. It helps you
check what was supplied when the memory was saved or corrected. It is not a
verified transcript of the whole conversation or proof of human intent.
Cairn Memory and Cairn
**Cairn Memory** is the open-source toolkit in this repository for saving,
inspecting and changing AI memory. **Cairn** is the hosted
shared memory map for people and AI, where people organize, review and share
knowledge.
This repository includes local memory tools and connectors to the hosted Cairn
service. Each path has its own setup and feature boundaries. Local use does not
require a Cairn account; hosted connections require a compatible service and
authentication.
Choose your starting point
| You want to… | Start here | What you need |
| --- | --- | --- |
| Understand the idea before installing | 繁體中文 or the recorded walkthrough | No installation or account |
| Try the open-source tools on your computer | Local preview setup or Windows guide | Terminal setup; Linux x64 and a bounded native Windows x64 check; no Cairn account |
| Use the documented hosted Claude Code or Codex connection | Hosted setup | A compatible hosted service and authentication; separate from local-preview client support |
| Build on the memory layer | Architecture and MCP tools | JavaScript or MCP integration work |
If you use Claude or Codex but do not usually install tools from a terminal,
start with the example and recorded walkthrough. This preview requires setup;
check the tested client paths before
connecting your AI tool.
Current preview
Cairn's open-source memory layer stores memories in your own SQLite file and
exposes them through MCP or JavaScript. No Cairn account is needed for local use.
**Developer preview.** Installed persistence and a narrow real-model memory loop
have retained evidence. Default extraction still fails
our source-support bar; see known limitations.
Save, inspect, correct and forget work without a model key. Semantic recall
requires your OpenAI key and sends selected context to that provider.
Watch the recorded walkthrough
Watch the 36-second model-free demo (MP4).
This records the memory tools running, rather than a conversation in Claude or
Codex. “Model-free” means no AI model is called during the walkthrough.
For long-conversation results, see the four-case real-model pilot.
It is an opt-in diagnostic with one failed Cairn answer, not a measurement of
long-term default-client recall reliability. Known limitations
Open the recorded tool walkthrough (GIF)
The demo below records the **model-free loop**: save, restart, inspect, correct
and forget. Its recall step reports model_not_configured.
Recorded responses and regeneration instructions ·
Verified capabilities and client support
Install
For **Claude Code and Codex automatic memory**, run the one-command installer:
This checkout prepares installer **0.5.3**; publication is a separate step.
Try it with node packages/setup/bin/memory.mjs setup. The plugin stays 0.3.2.
Requires Node ≥22.16 and at least one CLI on PATH. Setup asks about new tools,