StackMap
Subscribe

hindsight vs spector

Agent memory that learns, not just recalls: retain/recall/reflect API over Postgres, SOTA on LongMemEval. Self-host via Docker with UI; Python/TS clients, any LLM provider. — versus — Java cognitive memory engine for agents: working, episodic, semantic and procedural tiers with decay, consolidation and association graphs, SIMD hybrid recall, served over MCP, REST/gRPC and SDKs.

The curated verdict

Both aim beyond recall to memory that learns and reflects; Hindsight leads on LongMemEval, Spector models forgetting and association explicitly.

hindsightspector
Stars62k28
Forks7.4k16
LanguagePythonJava
LicenseMITApache-2.0
Last activitytodayyesterday
Topicsmemory, agentsmemory
Curated connections153

hindsight — the curator's take

Pick it when you want a deployable memory *service* whose pitch is learning — agents that get better over time, not a transcript search. The LongMemEval lead was independently reproduced (Virginia Tech, Washington Post), which is more than most memory vendors offer, and the LLM side is pluggable down to Ollama/LM Studio for fully-local stacks. NOT an embedded library: you run a Docker service with Postgres and talk to it over HTTP — overkill for a single coding agent wanting session notes. The ™ and Hindsight Cloud signal a commercial trajectory; watch where the open/paid line lands.

spector — the curator's take

Consider it if you want memory that forgets and consolidates like a cognitive model rather than an ever-growing vector store, with an `npx` MCP server that embeds the kernel. Tiny project needing JDK 25 preview features — not something to bet production on yet; mature options like Hindsight or MemOS have far more evaluation behind them.