What exactly is stored?
Three kinds of thing: facts (a subject, a predicate and a value, with the sentence you said), notes (your words, whole, filed under the day they were saved) and, if you import them, Markdown notes. Nothing is stored unless an agent or you saves it. Renor does not record your chats.How are memories created and updated?
An agent callsremember, save_memory or remember_note. A fact is replaced only by saving a new value for the same subject, predicate and scope; the old value stays in history. A note is never replaced by a later note.
Does it use embeddings, a graph or summaries?
A ledger of facts with validity dates, plus search over notes by exact words and by meaning (embeddings; every hosted workspace has this on). A workspace without an embedding provider would match exact words only. Retrieval follows[[wikilinks]] between notes: a note linked from a match can be added as a further match (its reason is graph). Renor does not build a knowledge graph from your text. A write-time summary exists only where an optional digest is switched on; it is off by default.
What if two memories contradict each other?
If both are facts under the same subject, predicate and scope, the newer one is current and the older is history. If the contradiction is between two plain notes, or two spellings of a subject, Renor keeps both and cannot tell which is current. When facts disagree across scopes or under names one word apart,get_context lists the disagreement in a conflicts field instead of picking one.
How does retrieval decide what to inject?
Renor does not inject anything. Your agent callsget_context, and the host application decides whether and when. The reply holds the current facts, then the best-matching notes, cut to a token budget (800 by default, at most 4,000). When nothing closely matches, the reply says relevant: false.
Can several agents read and write the same memory?
Yes. Every MCP client you sign in belongs to one workspace and reads and writes the same memory. A named connection’s author is authenticated; only an unnamed fallback label is self-reported.Can I export everything?
Yes.export_memory returns everything the workspace holds in one documented format (renor-export/v1): the fact ledger with superseded values, every daily-log entry, every note in full, and everything retired, each with its metadata. A manifest counts each kind, and a large workspace is paged, never cut. See Export and your data.
Can I delete individual memories?
You can retire one: it leaves every read and search at once and can be restored. Retiring is not erasure: a retired note or log entry stays in your workspace until you delete it permanently on the dashboard’s Memories page. A retired note keeps counting toward storage until then; a retired log entry stops counting as soon as it is retired. Deleting permanently cannot be undone, and only you can do it there; agents cannot. A retired saved fact stays in the history record: to erase one, or to delete your whole account and memories, email privacy@renor.cloud.What happens if the service is unavailable?
Your agent’s call fails with an error and nothing is written. There is no local copy that catches up later. There is no uptime SLA.Is there an API? Can I self-host?
There is one MCP endpoint,https://mcp.renor.cloud/mcp, with 24 tools. Renor documents no REST API for memory. The memory engine is open source under AGPL-3.0 at https://github.com/patrickpassosb/renor-engine and can be self-hosted with its README. The hosted service adds the website, dashboard, sign-up and operations around the same engine.
How much latency does it add?
About half a second per hostedget_context call at the median, almost all of it network and account lookup rather than search. Renor publishes no latency guarantee.