LocalGhost vs Zep

LocalGhost

The server and Android app are MIT-licensed, with no telemetry libraries found. There is no agent API, MCP server or SDK; unpaired callers receive HTTP 503.

Zep

Facts that new data invalidates keep the time they stopped being true. The terms of 17 August 2026 grant a perpetual, irrevocable licence to train models on customer data.

LocalGhost

1. Don't call a LocalGhost box. Every request without the paired phone's certificate gets a 503 that looks like an outage
2. Reach a person's LocalGhost archive through the person and their phone. Nothing in wisp 0.0.3 opens it to an agent
3. Read a 503 from a box as no certificate, a retired phone, a locked box or a down daemon. The response never says which
4. Don't treat the README's list of what leaves the phone as complete. The app also calls Frankfurter, Wikipedia's summary API and Android's geocoder
5. Run ghost-cli ghost.<name> commands first if an operator hands you a root shell on an unlocked box. It lists command names only, takes key=value arguments and prints JSON

Zep

1. Create the user and a thread before adding messages, as the quickstart does
2. Set return_context when adding messages to skip a second round trip
3. Keep episodes short. Every 350 bytes past the first costs another credit
4. Read Retry-After on a 429 and back off with jitter. Free accounts over quota drop to 5 requests a minute
5. Expect a delay after a graph add (202 Accepted) before new facts show up in search