Project maps
See which files connect.
Code Map gives you Tree and Graph views of your project. Inspect where files live, follow imports and importers, and see cycles and unresolved imports with their reasons.
lib/auth.ts is below the minimum, and three files import it.
What it does
The file tree tells you where. The graph tells you what connects.
Code Map has two views of the same repository. Tree shows its folders and files. Graph follows source imports, showing which files a module imports and which files import it.
Cycles and unresolved imports remain visible, with reasons for connections Iris Code cannot resolve. This is a map of source-level imports, not a recording of what the application does at runtime.
- Follow the connections around the file you are working on.
- Inspect cycles and unresolved imports rather than guessing at dependencies.
- Export the current view as an image, diagram, table or JSON.
Why use it
Read the connections before changing the file.
A familiar filename does not tell you which other modules depend on it. The map gives that investigation a place to start.
- Get oriented in unfamiliar code
- Start with the repository structure, then focus on the file you are reading. Its import neighbourhood gives you concrete files to inspect next.
- Investigate a tangled dependency
- A marked cycle makes an import loop visible. Unresolved reasons help distinguish a missing connection from one the analyser could not follow.
- Take the evidence into a discussion
- Export the current Tree or Graph for a pull request, document or conversation. The exported view gives other people the same structure to discuss.
How to use it
Start with one file. Follow its connections.
Free includes project structure, the open file's import neighbourhood and exports. Open earned folder and workspace import evidence without another action. A fresh project inspection uses applicable project access.
Open Code Map
Open your repository in the editor, then run the Code Map command. Start in Tree to see where its folders and files sit.
Command palette Iris Code: Open Code MapResultThe project structure is visible in one navigable view.
Switch to Graph and focus a file
Select the file you want to understand. Follow its imports and importers, opening the connected source when you need more context.
ResultYou can inspect the open file's source-level neighbourhood.
Inspect gaps, then share the view
Read any marked cycles or unresolved-import reasons. Export the view as PNG, SVG, Mermaid, Markdown, CSV or JSON when you want to discuss what you found.
ResultThe discussion can refer to an explicit map, including the connections that remain unresolved.
The capabilities, in detail.
- Code MapFree
- See where repository health is concentrated. Free shows the structure and the open file's folder; Iris Code Pro colours the whole workspace after a full scan.
- Import graphFree / Pro scopes
- Switch the Code Map to Graph to see how files import each other, with cycles marked and unresolved imports listed with a reason. Reads TypeScript, JavaScript, Vue, Svelte, Go, Python, Java, C# and Rust. Free shows the open file's imports and importers; folder and workspace scope need Iris Code Pro.
- Code Map exportFree
- Export the Tree or the Graph as it appears on screen: PNG or SVG for slides, Mermaid that GitHub draws in a pull request, Markdown or CSV tables, or JSON. Exporting is free.
Choose your scope
What's included.
- Free
- Free shows project structure and the open file's import neighbourhood. Exports are Free.
- Pro and Teams
- Earned workspace scans supply the full Code Map. Fresh folder and workspace inspection uses project access; saved views remain available after exhaustion.
Know the boundary
What it doesn't promise.
An import graph shows source-level connections. It is not a runtime trace or a promise that every dependency is resolved.
Start here.
Open Code Map in the Iris Code panel. Switch between Tree and Graph, then focus a file to inspect its connections.