Graphicle vs Hy Memory

Graphicle

One local program gives a coding agent a code graph and project memory through 25 typed, annotated MCP tools that return cited excerpts within a token budget, with agent-written memories held for human approval. It is one day old at version 0.1.0, its SDKs are not on any registry, and the licence and advisory check fails on main.

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.

Graphicle

1. Call recall_project with a max_tokens budget, then read_project_source with the cited id and byte offset to continue a cut excerpt
2. Use query_graph, get_neighbors and shortest_path for structure questions, and pass repo to reach another synced project
3. Treat proposed memories as drafts. They are not served until a person approves them in graphicle open under Memory
4. Ask the user before running graphicle setup, which edits agent settings, AGENTS.md and Git hooks, and use graphicle disconnect to undo it
5. Over HTTP send the key as Authorization: Bearer, never in the URL, and on 429 wait for the Retry-After reset

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