The memory desk

A shared context layer.
With a human point of view.

Agents read and write. You stay able to inspect, correct, and organize the context they use.

Open the memory desk

Files that make sense

Organize notes with paths and folders. Keep a store for each project, assistant, or body of knowledge.

#

Markdown, without ceremony

Edit the source, preview the result, and download a note whenever you need it elsewhere.

A trail of changes

Inspect retained versions and bring useful content back into a new draft. Version checks help prevent overlapping edits from silently overwriting each other.

A connection for your agent

Use the store-specific MCP interface or the public API. A URL selects the memory; authentication and permissions decide who can use it.

Sharing with boundaries

Invite teammates to a workspace, then grant content access to the stores they need. Workspace administration alone does not expose private notes.

An open foundation

The memory engine remains public and self-hostable. Hosted account management and the MarkdownMem interface live in a separate product.