Aden v0.2.0 releases offline graph GUI and git-history replay

• Aden v0.2.0 added aden view, an interactive code graph that opens as a self-contained HTML file, with force-directed layout, subsystem coloring, search, edge filters, and click-through links back into an editor, according to RioPlay's release post.
• The same release added git-history replay, so the graph can rebuild a repo commit by commit, a feature that RioPlay's release post surfaced visually and The Graph That Audited Itself explains in more detail.
• Aden also shipped self-reported retrieval benchmarks where hybrid graph-plus-embedding retrieval matched or beat BM25 across five repos, with the biggest jump in the TanStack/query test cited in RioPlay's benchmark table.
• The most interesting part is the dogfooding: after pointing the viewer at Aden itself, RioPlay's release post said the graph exposed a vendored minified dependency cluster and 706 redundant edges, findings expanded in The Graph That Audited Itself.

You can browse the repo, read the launch post for the viewer, and back up the graph model with Six Live Edges. The useful weird bit is that the nicest-looking feature, the graph UI, doubled as a debugging tool that found structural mistakes in Aden's own edge model.

Aden positions itself as a local context compiler for codebases: it turns code, docs, and plans into a typed knowledge graph that humans and agents can query, per the GitHub repo and the earlier Introducing Aden post.

In v0.2.0, that graph got a browser front end. The blog says aden view writes a single offline HTML file, no server or CDN, then layers on force-directed layout, subsystem coloring, search, edge-type filters, containment expansion, and click-to-open source locations inside an editor.

That UI angle lands because there is still a live split between terminal-first agent tooling and people who want a friendlier surface. In Mattieboy2011's vibecoding post, a Codex user explicitly says they prefer a UI over a terminal while comparing coding tools.

The headline benchmark claim is simple: hybrid retrieval, described in the Reddit launch as graph-aware retrieval plus dense embeddings, beat or matched plain BM25 on every listed repo.

The table in RioPlay's benchmark table breaks out like this:

• getkin/kin-openapi: BM25 R@1 0.273, hybrid R@1 0.409, hybrid R@20 0.591
• rust-lang/rustfmt: BM25 R@1 0.095, hybrid R@1 0.095, hybrid R@20 0.238
• unoplatform/uno: BM25 R@1 0.150, hybrid R@1 0.150, hybrid R@20 0.300
• pallets/flask: BM25 R@1 0.176, hybrid R@1 0.176, hybrid R@20 0.294
• TanStack/query: BM25 R@1 0.091, hybrid R@1 0.182, hybrid R@20 0.364

The strongest result is TanStack/query, where top-1 recall doubled from 0.091 to 0.182. The weaker story is that three repos only matched BM25 at R@1, so the current evidence supports breadth and recall gains more clearly than a across-the-board top-hit jump.

The release post says Aden's own graph immediately surfaced a massive vendored mod-unknown hub and 706 redundant Documents edges. The deeper write-up adds that the first issue came from indexing a minified force-graph JavaScript bundle, and the fix was a one-line ignore rule for minified files.

The second issue was stranger. According to The Graph That Audited Itself, Documents edges were just the inverse of PartOf, which buried roughly 374 real prose-to-code links under redundant structure, so v0.2.0 introduced Contains as a separate edge type instead of just deleting the bad edges.

That is the sharpest part of this release. The graph viewer was shipped as visualization, then turned into an audit tool for the graph schema itself. Six Live Edges pushes that cleanup further, arguing an edge type only counts if it has an emitter, a consumer, and a test proving it changes answers.