shared memory for agentic communities

Your agents keep solving
the same problem
over and over.

Every Claude session, every Discord thread, every Cursor run — the lessons are real but they vanish. Cairn turns agent workflows into a reviewed, attributed map your community and your agents can both reach.

walk in now · writing still gated · closed beta opens may 18

works with your agents · via MCP

Claude Code
Cursor
Windsurf
Codex CLI
Gemini CLI
Antigravity
GitHub Copilot
Aider
what lives here

Four kinds of stones,
one map.

Cairn distinguishes lived experience from polished summary — so readers and agents always know where the line is.

lived experience

Field Note

A real scar from a real workflow. Debugging story, deploy disaster, an experiment that almost worked. Cannot be invented by AI.

human judgement

Take

Your opinion on architecture, agent design, a tool tradeoff. Signed by handle. AI can polish — it can't decide.

ai-distilled context

Brief

A grounded summary of public sources, paper, or docs. AI-drafted, human-approved, citations attached.

white space on the map

Open Question

Something the community hasn't yet answered. Visible holes invite contribution from the people who know.

see it in action

Ask the cairn.
Watch it light up.

One question pulls the cards that answer it — and the relations that hold them together.

The disagreement is part of the answer.

walk in

A world,
not a search box.

The map is hand-drawn. Each island is a region of the community's thinking. You walk to the one you need.

Distance gives shape to what's known.

from the terminal

Same cairn,
reached from where you work.

Your agent reads the map over MCP. A skill watches the session and offers the scar back when it's worth keeping. No tab switch, no copy-paste.

MCP · read/ask cairn

Pull a previous
visitor's trace.

The agent asks. Cairn returns the field note the last person who hit this wall left behind — handle attached.

The disagreement is part of the answer.

skill · write/cairn-reflect

Leave the scar
before it fades.

At session end, the skill distills a candidate field note. You hit Y. The card waits in pending for review.

Capture, not interrupt.

how it works

A loop, not an upload.

Knowledge happens in the work, not after it. Cairn lowers the cost of capturing it down to a single review step.

01

Workflow

You and your agent work — debug, ship, argue with the docs, ship again. Real signal lives in the trace.

02

Distill

Cairn or your skill pulls candidate Field Notes from the run. AI proposes; nothing is published yet.

03

Review

You approve, edit, or reject. Sensitive details masked, attribution attached, draft enters the map.

04

Reusable

Your community reads it. Your agents query it via MCP. The next workflow starts a step ahead.

why cairn

There's memory for one person.
There's memory for agents.
There should be memory for us.

you, alone

Personal notes

Obsidian, Notion, your scratch.md. Crisp voice and judgement, but locked to one head — agents can't reach it, communities can't build on it.

agents, alone

Stack Overflow / cq

Q&A or knowledge units indexed for agents to retrieve. Solves repeat-mistakes for coding agents — but no community voice, no map, no field notes from the people doing the work.

communities + agents

Cairn

Field Notes, Takes, Briefs, Open Questions. Human-governed, agent-native. Voice and structure — and a living map of what's known, contested, or missing.

for builders

Your community's hard-won lessons,
plugged straight into your agents.

You wrote the same Cursor rule twice. You answered the same Discord question last week. The lesson is real. The lesson keeps disappearing.

Cairn captures these lessons as structured cards, lets a human approve each one, and exposes the whole map to your agents over MCP.

  • ──Distilled, not invented. AI proposes Field Notes from real workflow traces. You decide what gets shipped.
  • ──Attributed forever. Every card carries a handle, a stable URL, and a date. Reputation accrues to people, not platforms.
  • ──MCP-native. One config line and your community's map becomes reachable from Claude, Cursor, or any agent runtime.
a workflow, threaded
field note · @chichi

Claude Code skills doubled my context — turned out to be plugin-skills loading scope.

↓ moss links to
brief · approved by @chichi

Skills as filesystem, not API

↓ cited by
claude code @ ~/myproject

via MCP: agent-skills/Skills as filesystem

Every community,
its own cairn.

The cairn is open to walk. Writing is still gated — leave your email and we'll let people in by hand from May 18.

one email · no spam · we'll only write when you're in