openmemfs
2026 · Open source · 4 of 5 parts in production
Agents change every few months; what they know about you should not change with them. I have been working for weeks with a memory of my own, text files in Postgres that my agents read and write, and I wanted anyone to be able to have theirs. openmemfs is that memory written from scratch for anyone to deploy: the context of your personal agent, kept as files you can read, edit and take with you. Its tagline says it in three words: own your context.
The decision that weighs most is what it leaves out. There are no users and no tokens: whoever reaches the server reads and writes everything. It is for one person, not a product for many, and each person adds the security they need where they deploy it. In return, the core reads in an afternoon and any agent can extend it with you.
It is built with TanStack Start, Hono, Postgres and TipTap, under the MIT license, with the code on GitHub.
Part by part
An editor for the person
Text files in Postgres with a Notion-style editor that reads and writes Markdown and saves as you type. Folders you create and move by dragging, tags on files and folders, categories and subcategories with their colour, search by name and by content, and a version history that says who changed what, you or an agent, and lets you go back to any of them. Light and dark.
The same hands for the agent
Anything a person does in the interface, an agent can do: every rule lives in a service layer with two doors, a REST API and an MCP server, which only read the request and call the service. If a model changes a file you have open, nothing is overwritten: you choose. And one file at the root, organisation.md, tells any harness how your memory is organised.
Small on purpose
One container and one Postgres, with no accounts, no login and no key: it is personal software, for one person and their agents. It grows by modules, each in its own folder with its tabs, pages, routes, tools and tables, and the guides show how to add authentication and deploy it to Cloud Run with a free Supabase database.
A website to start with
openmemfs.gonzaloverdugo.com explains on one page why your context should be yours and gathers the six guides, in order: connecting your agent, the organisation.md any harness reads, extending it, adding authentication and deploying it. The guides live once, in the openmemfs repository: the app reads them and the website fetches them on every deploy, so they never fall behind.
Community modules
5 · Ahead
Next, everyone extends it their own way. It is enough to open the repository in your harness and describe the module you want; the rules a module follows are written for an agent to follow. And the modules that serve more people can be shared.