Hindsight vs Hy Memory

Hindsight

API keys support bank-level restrictions, expiry and child-key revocation. Retain ingestion costs $10 per million tokens.

Hy Memory

An Apache-2.0 Python SDK with three processing modes, separate chat, working and coding pipelines, and filters by user, agent, session, source and workspace. Deletion does not stick everywhere. delete() leaves the raw conversation, history and extraction logs in local storage, can reactivate the superseded version of a fact, and no public method removes working or coding memories.

Hindsight

1. Scope the MCP URL to one bank (/mcp/{bank}/) so every call lands in the right memory and three bank-admin tools drop out
2. Use recall for lookups and keep reflect ($0.05 a call) for questions that need reasoning
3. Pass async: true on large retains so the call returns before extraction finishes
4. Treat HTTP 402 as out of credit and 403 as a key that can't reach that bank

Hy Memory

1. Pass user_id on every add() and user_ids on every search(). Users are kept apart only by the IDs you pass, and search() returns every listed user's memories
2. Choose the mode before writing. lite makes no LLM calls and stores raw text. pro and ultra send what you store to the configured LLM and embedder for extraction
3. Don't rely on delete() to erase a fact. The raw conversation, history.db and cache.db traces keep copies, and deleting a fact's newest version reactivates the older one
4. Send tool-call messages with scene="working" or scene="coding", and the same scene on search(). Without tool messages a write falls back to chat memory
5. Keep python -m hy_memory.server on 127.0.0.1. It has no authentication and allows any web origin