Riven Memory Bridge

Durable memory across surfaces and sessions: the facts worth remembering about you and your work, readable and deletable.

A conversation ends and its context normally dies with it. Memory Bridge keeps the parts that were worth keeping and makes them available to the next conversation — in Chat, in Computer, and across devices.

What gets remembered#

• Durable preferences — how you want work done: format, tone, tooling, language.
• Stable facts — your role, your projects, the systems you work on.
• Project context — decisions and constraints that outlive the thread that produced them.

What is deliberately *not* remembered: transient task state, one-off details with no future use, and anything that reads as a judgment rather than a fact. Memory is meant to make the next session better, not to accumulate a dossier.

How recall works#

Memories are stored with embeddings and retrieved by relevance to the current turn, not loaded wholesale into every request. That bounds context cost and avoids the failure mode where old context crowds out the actual question.

Your control over it#

• Inspectable — memories are listed in settings in plain language, not as opaque vectors.
• Editable and deletable — correct or remove any entry; deletion removes the vector too, not just the label.
• Scoped — personal memory is yours; workspace memory is shared deliberately, never by accident. Memory never crosses tenants.
• Disableable — turn it off entirely and sessions become stateless again.

Staleness#

A remembered fact is a fact as of when it was recorded. Memory Bridge timestamps entries and prefers current evidence when the two conflict — a memory saying a file exists is not proof that it still does. Retention commitments are on Riven Trust.