You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've added Understand-Anything as a git submodule in our research repo and want to evaluate it as a tool for quickly understanding large/unfamiliar codebases via its knowledge-graph pipeline.
Goals of this investigation
Pipeline & graph quality — Understand how the multi-agent pipeline analyzes a project and how accurately the knowledge graph captures files, functions, classes, and dependencies.
Scale & cost — Evaluate behavior, runtime, and token/cost on a large repo (100k+ LOC), plus any incremental/re-analysis support.
Integration & dashboard — Assess the Claude Code plugin install flow, cross-tool support (Codex, Cursor, Copilot, Gemini CLI), and the interactive dashboard's usefulness for exploration and Q&A.
Questions to answer
How well does it handle our primary languages/frameworks?
What data leaves the machine, and what are the privacy/security implications?
How does graph accuracy degrade on very large or polyglot repos?
Deliverable
A short write-up summarizing findings and a go/no-go recommendation.
Context
We've added Understand-Anything as a git submodule in our research repo and want to evaluate it as a tool for quickly understanding large/unfamiliar codebases via its knowledge-graph pipeline.
Goals of this investigation
Questions to answer
Deliverable
A short write-up summarizing findings and a go/no-go recommendation.