recall is memory for a person and their agents: it captures what you decide and why, keeps it as a graph you can read, and hands the right part of it to whatever AI you are working with. This page is the ten-minute path.
Sign up in the app. A workspace is a company or a household; you can belong to several. Every workspace gets a shared space and a personal space for each member. Spaces are the unit of sharing (the API calls them buckets).
Add a connector with the address https://<your host>/mcp. The tool sends you to recall to sign in; you choose the workspace and what the tool may do (read only, read and write, or everything you can do). It never sees your password, and you can disconnect it under Settings → Connected apps.
One plugin brings the memory server, the skill, the hooks and the backfill command. Inside Claude Code, or in a terminal:
claude plugin marketplace add mvmkrac/recall-plugins claude plugin install recall@recall
Before the first command: the plugin lives in a private repository today, so that machine needs GitHub access to mvmkrac/recall-plugins: a token in a credential helper or an SSH key on the account. If it fails over SSH, name the https address yourself: claude plugin marketplace add https://github.com/mvmkrac/recall-plugins.git.
Then, in a new session, type /mcp, choose recall-memory and sign in with your recall account, picking the workspace and what the tool may do. That signs in the session. The backfill below pairs the machine as well, with a key of yours that you approve with a six-character code.
Last, run /recall:backfill once in each project. A new workspace knows nothing, so the first brief would say nothing; this reads the sessions Claude Code already kept for that directory into memory. It skips what recall already has, so running it again is safe, and extraction happens in the background — the brief fills over the next few minutes.
After that nothing is typed again: the project brief arrives with the first prompt of a session (there is no session-start hook — it is the answer to that first prompt), the records that match arrive on every later prompt, and each session is captured as it goes. No memory lives on your machine. Codex is the same plugin: codex plugin marketplace add mvmkrac/recall-plugins, install it from /plugins, then type /hooks once to trust its hooks — Codex runs no plugin’s hooks until you have.
Script install (legacy). Developers → Connect also offers a one-line curl … | bash installer that writes hooks and a config file into your home directory. It still works and machines already on it keep working, but it is superseded by the plugin and gets no new features; put a new machine on the plugin.
Ship text with the generic script, upload a document on a space page, or call the REST API with a key from Developers → Keys (a key can be read-only). Try every call first in Developers → Playground.
The first time an AI connects, the brief says setup is needed and the AI runs a short interview: who you are here, which parts of the work exist, what is shared and what stays personal. It writes your role profile and a charter per space. You can run the same interview in the app (Home → Run the interview here) or fill it in by hand under Set up; Set up leaves the menu once both exist. Charters are what route memory: "recruiting facts go here, my own habits stay personal".
Home shows what memory learned in the last day, what needs you (proposals, contradictions, failed slices, unanswered questions), recent sessions and your brief. Memory is the wiki: domains and topics on the left, filters by type, origin and horizon, and a page for every record with its reason, the quotes it rests on, its history and chain, and what it is filed under. Graph is the map. Chains puts decisions, lessons and conflicts on a time axis you can zoom. Chat answers only from records and quotes what was said; it opens as a drawer on any page and remembers the conversation per space. Sessions shows every conversation shipped and what it yielded. Dreams is the review inbox for what the nightly pass proposes, with a Conflicts view to settle contradictions. Analytics shows what is used, what it costs in tokens, and what people ask that memory cannot answer. ⌘K searches everything.
Create a department space, write its charter, add a group, grant people or agents on the space's access tab. Every person and agent has a page: what they reach, what they taught, what they asked. Export a space as Markdown or JSON at any time. An agent gets a key with a ceiling; it can never delete or govern. Use <private>…</private> around anything that must never be stored.
Accounts and permissions in Postgres; memory in ArcadeDB, one database per workspace; models wherever you point Settings. Details on the privacy page.