HAIMIDB
One memory. Two ways to work.
You work in a table. Your AI works through tools. Both use the same Git-backed notebook, on your own computer.
A table for you
Browse models, search records and edit scalar or structured values in your browser. Changes stay in tab memory until you push them.
Tools for your AI
Eleven MCP tools run locally over stdio. Your AI can inspect models, find records, save changes and work with the same notebook you see.
Readable Git history
Each notebook is a deterministic memory.v2.jsonl file. Commits show what changed; Git history is the recovery source after hard deletion.
Models that explain themselves
Everything is a node. Models carry example values and descriptions; records and linked fields share the same structure.
Repository protection
Memory writes and notebook deletion require a valid .haimidb.json marker. An empty repository is initialized only with your confirmation; an existing project is not silently adopted.
Local-first processing
The browser or local engine processes notebook data and talks directly to GitHub. The small authentication service only exchanges and renews credentials, never notebook content.