gortex vs graphicle
Code-intelligence engine in one static Go binary: tree-sitter graph over 257 languages, compiler-grade resolution for 17, multi-repo, 175 configurable MCP tools — up to 50x fewer tokens. 100% local. — versus — One Rust program giving coding agents a code graph plus memory of docs, decisions and past sessions, served over MCP to Claude Code, Codex, Cursor and VS Code.
Both are single-binary code-intelligence engines over a tree-sitter graph for agents.
| gortex | graphicle | |
|---|---|---|
| Stars | 2.0k | 509 |
| Forks | 194 | 36 |
| Language | Go | Rust |
| License | Apache-2.0 | Apache-2.0 |
| Last activity | yesterday | yesterday |
| Topics | code-intel, local | code-intel, memory |
| Curated connections | 8 | 5 |
gortex — the curator's take
The coverage play on this shelf: 257 grammars, cross-repo and cross-SERVICE edges (HTTP routes, contracts) with a provenance/confidence tier the single-repo tools don't attempt, and one install that configures 19 coding agents. When NOT: 175 MCP tools is a context bill of its own — prune the toolset or your agent pays the index's price in schema tokens; benchmarks are self-published; and if you want memory as plain files, this is the opposite philosophy.
graphicle — the curator's take
Use it when you want code intelligence and project memory from one local install instead of a code-graph MCP plus a separate memory server. Skip it if you already run a dedicated code graph you like, or need team-shared memory. Its memory comparison against seven systems is pre-release and self-reported.