Cairn.ink Memory vs Supermemory for Claude Code

Both Cairn.ink Memory and Supermemory offer automatic Claude Code capture and recall. Choose Cairn.ink Memory for private Memories with Source Receipts and one Claude Code/Codex installer, including a no-account Local option. Choose Supermemory for its repository-container workflow, codebase indexing and deeper multi-container searches through its documented Claude Code plugin.

Which integrations are being compared?

Supermemory's official Claude Code plugin, accessed 2026-11-12, installs lifecycle hooks and connects to the Supermemory service. Its hosted MCP reference, accessed the same day, separately describes tools for memory, documents and spaces. These are related layers: the plugin handles automatic events, while MCP exposes operations an assistant can call.

Cairn.ink Memory's Cloud installer likewise supplies automatic integration and hosted memory tools. Its Local installer uses a SQLite database and explicit tools. Compare the actual mode you intend to operate rather than treating every connection as an identical form of memory.

Start by choosing the job. Do you want personal context to follow you between assistants, or want repository history and indexed architecture organized through a project's containers? Both can be useful, and their storage and access controls deserve equal attention.

How do the same dimensions compare?

Supermemory details below follow the plugin README, MCP reference, managed MCP page and pricing page, all accessed 2026-11-12. Cairn.ink Memory details follow its released installer guide and release README.

When should I choose Supermemory?

Choose Supermemory when its repository-container and codebase workflow fits how you work. The plugin README documents /supermemory:index for architecture, conventions and how to run the project. It also provides a context-gatherer agent for deeper searches across containers. Those are concrete reasons to evaluate it when finding old project work matters as much as remembering individual preferences.

The same README documents matching default repository containers across Claude Code, Codex and OpenCode. Identity is derived from a normalized Git remote, with a local-path fallback. This is useful for people deliberately adopting that ecosystem and its project organization. The managed service also documents spaces and client access, including collaboration within granted spaces.

Install its Claude Code plugin using the official in-session commands:

/plugin marketplace add supermemoryai/claude-supermemory
/plugin install supermemory

The plugin requires Node 18 or later and supports browser sign-in or an API key. Its hooks load profile context, search substantive prompts and save new conversation content in the background at Stop. A project configuration can override the container. Inspect the active identity through /supermemory:status before testing across clients.

For Cursor, use the separate managed MCP connection documented on Supermemory's MCP page. That page supplies an endpoint and browser OAuth flow. Match the intended space and account when comparing a record saved in Claude Code with one read in another assistant.

When should I choose Cairn.ink Memory?

Choose Cairn.ink Memory when private context should follow you between Claude Code and Codex and you want a visible source excerpt for saved Memories. Start with:

npx @cairn-ink/memory setup

Choose Cloud for automatic capture and prompt recall. Setup requires Node 22.16 or later and the selected CLIs on your path. Approve both tools, fully close them and wait for background work before confirming sharing. One browser sign-in connects a first paired installation, with a memory ID linking the same project across tools. Reopen them and review the four entries in Codex /hooks.

Choose Local for free, no-account explicit tools on one computer. Supported clients share a database and owner. The installer guide documents both modes, while manual hosted MCP is an alternative for explicit tools. Cursor uses a separate hosted MCP configuration.

Cloud saves conversation text after best-effort local masking and sends a masked, length-limited prompt copy for recall. The privacy controls explain the processing path and pause controls. Choose it when that data flow suits the work you want remembered.

How can I inspect and retire remembered context?

Supermemory's current MCP reference lists document browsing, exact document reads, and memory entries with source document IDs. It exposes forget_memory to forget a memory matching supplied content. Use those source links to examine what produced a remembered fact and inspect the result of a forgetting request.

Cairn.ink Memory's hosted recall_memory returns matching Memories with IDs and Source Receipts. A receipt contains a source excerpt and client metadata. Hosted forget_memory takes the exact Memory ID; Local additionally provides inspect_memory and revision-guarded correction and forgetting. Use the tool surface for your chosen mode.

These inspection paths offer different evidence. Test them with a deliberately fictional preference, read the returned record and source, then use the documented retirement operation. In a fresh conversation, check the old record alongside another harmless record you kept. This helps separate a successful retirement from an account or connection problem.

How should I think about sharing, cost and limits?

Cairn.ink Memory keeps personal and project-scoped Memory private to its owner. Shared Knowledge Cards have their own review and human-authorized publication process. Supermemory's managed MCP page describes team collaboration in authorized spaces; its plugin's shared repository identity describes continuity across coding agents. Decide which audience should receive each kind of context before capture begins.

As of 2026-11-12, Supermemory's pricing page describes managed plans with included credits, usage charges and plugin access on paid plans. The plugin README states MIT, with a separate Apache-2.0 notice for its bundled SDK. Match the service plan and expected processing to your use.

Cairn.ink Memory's current plans are on its pricing page, and Local mode is free. Its Local mode is a developer preview, and configured semantic recall sends selected text to the model provider. Supermemory documents capture filtering as best effort and says its capture-only protection excludes explicit MCP calls and recall queries.

Compare a harmless save, fresh-session retrieval, source inspection and retirement in the workflow you will actually use. For Cairn.ink Memory, start with the connection guide.