Your context, yours

openmemfs is the context of your personal agent: what it knows about you, your work and how you like things done, kept as files you can read and edit.

• It is yours. It runs on your server, in your database. You decide what goes in, how it is organised and who reaches it.
• It is the piece that stays. Agents and harnesses come and go: Claude Code today, another one tomorrow. Your context should not move with them. Connect any harness to openmemfs and it starts from what you already wrote.
• It is personal software. One person and their agents, not a product for many users. That is why it has no accounts and no login out of the box: you add what you need.
• It is code, and you own it. Fork it, change it and grow it with modules. With an agent at your side, extending it is a conversation: ask for a tab, a tool or a page and review the change.

You are responsible for keeping it, and free to make it whatever you need. Keep one thing true: whatever you add, openmemfs stays your context, plain files that you and your agents read and write.

The guides, in order

1. Your context, yours: this page.
2. Connect your agent: the MCP endpoint, in one command.
3. Your organisation file: the rules every harness reads first, in the Open Knowledge Format.
4. Extend openmemfs: modules, and what to add first.
5. Add authentication: before it leaves your machine.
6. Deploy it: Google Cloud Run and a free Supabase database.