cocoindex-code vs Graft
Graft is much bigger: 5.6k stars against 2.7k.
Neither one leads on the six capability axes, so the choice comes down to which of them fits the way you already work.
Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.
Where they stand today
AST-based semantic search that is extremely lightweight, agent-friendly (skill/MCP plugin), and can run fully locally with offline embeddings.
- Stars
- 2.7k
- Tracked growth
- +49.3%
- Maturity
- ●●●●●
- Last commit
- 3d ago
- Language
- Python
- License
- Apache-2.0
- Cost to run
- Local embeddings free with the 'full' variant; slim/latest uses cloud embeddings and your API key.
Writes a readable, linked markdown graph of your code (no embeddings or external index), letting agents use a local, regenerable map rather than re-exploring the repo each run.
- Stars
- 5.6k
- Tracked growth
- not tracked long enough
- Maturity
- ●●●●●
- Last commit
- 1d ago
- Language
- TypeScript
- License
- MIT
- Cost to run
- Your API key, per-use
Six axes, head to head
Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.
| Axis | cocoindex-code | Graft |
|---|---|---|
Context depth How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository. | ●●●●● Whole-repo analysis | ●●●●● Whole-repo analysis |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● Path/lang filters | ●●●●● Minimal filters |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Config file options | ●●●●● Config options |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Fully local run | ●●●●● Fully local possible |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● BYO key / local | ●●●●● Bring-your-own-model |
Setup ease What it takes to get a first useful run out of it. | ●●●●● One‑minute setup | ●●●●● Two-command setup |
Which one to pick
Pick cocoindex-code if…
Easy setup — install in ~1 minute with zero config and optional local embeddings for offline/private use.
Pick Graft if…
Efficiency-first — pick Graft when you want much faster and cheaper agent runs (often with equal or better correctness) by providing a repo-wide local node graph that agents can read directly.
What people want from each one
cocoindex-io/cocoindex-code
Hacker News: Show HN: CocoIndex-Code open source embedded AST-based code MCP drew 2 points and 1 comments.
trailhq/Graft
Questions people ask
Is cocoindex-code better than Graft?
Neither one leads on the six capability axes, so the choice comes down to which of them fits the way you already work. cocoindex-code is worth picking when easy setup — install in ~1 minute with zero config and optional local embeddings for offline/private use.
Which of cocoindex-code and Graft keeps my code private?
cocoindex-code: Fully local run (5/5). Graft: Fully local possible (5/5).
What does each one cost to run?
cocoindex-code: Local embeddings free with the 'full' variant; slim/latest uses cloud embeddings and your API key.. Graft: Your API key, per-use.
Full profiles: cocoindex-io/cocoindex-code and trailhq/Graft. Everything else in Codebase context.