INTENT MAP
Understand why the code exists — not just what it does.
The Intent Map reads your code, its dependencies and its history to reconstruct purpose: what each file is for, the capabilities it implements, and the reasoning behind how it got this way. Every claim is marked measured or inferred.
Summaries at every level
Repository, file and function — a plain-English explanation at the altitude you need, generated from the actual code.
Measured vs inferred, always separated
An evidence block on every file card tells you which relationships were read from the graph and which the model reasoned about.
Relationship map with reasons
Real dependency edges, each one explained: why this file needs that one, not just that an import line exists.
Generate your Intent Map in under 2 minutes.
Analyze my codebase →No credit card required · Free tier available
Common questions
What does the Intent Map tell me?
Why each file and capability exists, not just what it imports — AI summaries at repository, file and function level, with an evidence block separating measured facts from inference.
How is the Intent Map different from the Code Map?
The Code Map shows how files connect. The Intent Map explains what each file is for. One is structure, the other is purpose.
Can I trust the AI summaries?
Each summary carries an evidence block that separates what was measured from the code from what the model inferred, so you can see which parts to check yourself.