HAIMIDB

Human Artificial Intelligence Memory Interface Database

Shared memory for a person and their AI. A table in your browser and MCP tools on your computer work with the same GitHub notebook.

Open the static app: https://olerhan.github.io/haimidb/ Source: https://github.com/olerhan/haimidb

Choose Connect with GitHub, authorize HAIMIDB and select your notebook repositories. No manual token is required. Data is processed in browser RAM and stored directly in GitHub. The authentication-only service exchanges and renews GitHub credentials; it does not process or store notebooks. No hosted engine or shared MCP endpoint exists. Fine-grained tokens remain an advanced option. Create repositories on GitHub, grant the App access, then refresh the repo list. Create them empty (no README, license or gitignore), select one in HAIMIDB and confirm Initialize memory repository. This commits a .haimidb.json purpose marker. Unmarked or foreign repositories cannot receive memory writes or deletions. Refresh does not grant access: add newly created repositories to the GitHub App installation's selected repositories first.

Install the local engine from the GitHub Release archive:

npm install --global https://github.com/olerhan/haimidb/releases/latest/download/haimidb-engine.tgz
haimidb login
haimidb init /path/to/empty-memory-folder
haimidb memory --clone /path/to/repository --notebook work
haimidb mcp

Set HAIMIDB_MEMORY to the generated haimidb2. string in your desktop MCP client's environment. The app also supplies a complete stdio configuration. Start haimidb to use local folders at http://127.0.0.1:7373.

For GitHub App connections, run haimidb login on the AI's computer with the same GitHub account. Browser and local sessions renew independently; no token is copied into MCP configuration. haimidb logout forgets this computer's session. Revoke the App in GitHub settings to remove access across devices.

Existing Format 2 notebook files remain valid. Reconnect in the renamed app; old connection credentials are not imported. Hard delete removes current nodes; Git history is the recovery source. Browser RAM must be pushed before closing.

Existing unmarked memory repositories require owner review and an explicit marker commit; HAIMIDB never silently adopts an existing project. See repository signatures, docs/spec/README.md and docs/adr/0004-github-app-authentication.md.