deepwiki-rs vs mex
Litho: a Rust, DeepWiki-style doc generator that turns any codebase into C4-model architecture docs - context, container, component and code-level pages with diagrams - via any LLM. — versus — A living wiki for your codebase, written by your coding agents: a Tree-sitter graph grounds structured Markdown notes, task-aware routing loads only what's needed, and drift checks catch stale claims.
Both generate a markdown wiki of a codebase; mex is written continuously by your coding agents on a Tree-sitter graph, Litho is a one-shot C4 generator you re-run.
| deepwiki-rs | mex | |
|---|---|---|
| Stars | 3.0k | 1.6k |
| Forks | 297 | 115 |
| Language | Rust | TypeScript |
| License | MIT | MIT |
| Last activity | 5 days ago | 2 days ago |
| Topics | code-intel, coding | code-intel, memory |
| Curated connections | 4 | 5 |
deepwiki-rs — the curator's take
Use Litho when you want a one-shot, opinionated architecture wiki (C4 layers, diagrams, multilingual) for a repo you inherited or need to onboard people onto - it is fast, single-binary, and the output reads like a human wrote it. Not a live code-intelligence layer: it regenerates rather than syncs, has no query API, and agents consume it as static markdown. The author has moved on to Terrain (which keeps the knowledge base in sync and serves it over ACP); Litho remains the focused generator. If you want the docs to stay current as agents edit code, mex or graft are the living-wiki alternatives; if you want a click-around dependency map instead of prose, codeflow.
mex — the curator's take
The answer to the instruction file that grew to 2,000 lines: knowledge lives in a routed `.mex/` wiki instead of one giant prompt, claims can be grounded to exact graph nodes by fingerprint, and `mex check` validates paths, commands, links, indexes and symbols spending zero tokens before `mex sync` sends the agent to repair only what drifted. Code stays the source of truth; the wiki is its maintained explanation. Limits worth knowing: the deterministic graph covers TypeScript/TSX, JavaScript/JSX, Python and Rust, so a polyglot monorepo outside that set gets a thinner spine — and the wiki is only as good as what your agents write into it, so it needs review like any other docs.