Memory for people and their agents

Every memory system remembers. This one learns your judgment.

recall stores why a decision was made, surfaces what conflicts before an agent acts, records how you resolved it, and checks itself against what actually happened — so a fleet of agents behaves like one operator: you.

Open the app Read the API

A typical memory

One sentence about a person

content: "alice prefers async standups"
embedding: [0.02, -0.41, …]

Retrieval is similarity. Nobody can say why, or what changed.

recall

A typed record, with its reason, wired to what it affects

Decision "Async standups for the sales team"
reason   "three time zones; live calls lost half the team"
validFrom 2026-07-18   author agent:writer-7
──DECIDED_FOR──→ Project: Sales onboarding
←──SUPERSEDES──  (history kept, with its reason)

What it does

Remembers why

Decisions carry reasons, lessons carry what failed, preferences carry how strongly. Correction never deletes — the old record keeps its reason and drops out of recall.

Stops the mistake before it ships

Before an agent acts, the plan is checked against live decisions and lessons. It answers with what conflicts and why it was decided — not a similarity score.

Knows who said what

Every record names the person or agent that wrote it. Filter to yours, to an agent's, and trace any record back to the session it came from.

Shares by bucket

Personal memory, company-wide memory, and department buckets like Sales, granted to people, groups, or agents — each with a capability tier and an explanation of why they reach it.

Gives agents a ceiling

An agent with nothing to teach is read-only. Writers may write; none may govern. A bucket's agent switch binds every key. Revoke one agent without touching a person.

Works everywhere

REST today, MCP for Claude Code, Cursor and any agent harness, and a skill that teaches an agent how to use memory well — not just where it is.

Who it's for

One person and their AI

An augmented brain that gets measurably more like you: what you decided, why, what you like, how that changed, and how you reason.

A team running agents

Social, support, sales, ops — agents that act on your behalf and keep doing the thing the team already decided against. Now they can't.

A company

Invite people, put them in groups, share the right buckets, give agents scoped keys, and keep an audit trail of every change — with personal memory staying personal.

Not memory for agents — that's a commodity. Why-memory for agents that act on your behalf.