cocoindex vs tokensave
Rust-core incremental indexing engine: declare Target = F(Source) in Python and it keeps vector/graph/relational targets fresh forever, reprocessing only the delta — with per-row lineage. — versus — Code-intelligence MCP server for coding agents — a pre-indexed semantic graph (libSQL + FTS5) they query instead of grepping: symbols, callers, impact radius in one call. 100% local, 50+ languages.
Head-to-head on the code-index-for-agents job: tokensave ships a pre-indexed libSQL+FTS5 semantic graph agents query over MCP; CocoIndex's flagship cocoindex-code does the same over MCP but incrementally re-indexed on every commit via the Δ engine.
| cocoindex | tokensave | |
|---|---|---|
| Stars | 11k | 440 |
| Forks | 828 | 38 |
| Language | Rust | Rust |
| License | Apache-2.0 | MIT |
| Last activity | today | today |
| Topics | rag | coding, local |
| Curated connections | 2 | 6 |
cocoindex — the curator's take
The mental model sells it — 'React for data engineering': you declare what the index should contain, and the engine reconciles it against source changes forever, re-running only affected rows (cached by hash of input AND code, so editing your transform also invalidates precisely). That's the honest answer to stale agent context: sub-second freshness at a fraction of the re-embedding bill, with every vector traceable to its source byte. Sources span code, PDFs, Slack, audio; targets span pgvector, LanceDB, Neo4j, Kafka. The flagship application is cocoindex-code, an AST-aware incremental code-index MCP for coding agents. Use it when your corpus changes constantly and batch re-indexing is bleeding you; overkill for a static document pile — any one-shot RAG ingester handles that.
tokensave — the curator's take
Use it to stop agents burning tokens on grep/glob/read exploration: one MCP call returns the symbols, relationships and snippets a task needs, and it's local (libSQL, no cloud). Broad reach — 50+ languages, 12+ agent integrations. NOT worth it on small repos where a couple of greps suffice, and it's an index you must keep fresh (re-index on change) — a stale graph misleads the agent. 80+ tools is a lot of surface; most tasks touch a handful.