The codebase, made visible.
Point OpenVisio at any local repo. It builds the import graph, draws the map, and answers questions with citations — deterministically, on your machine.
Claude Code
Codex
Cursor
Zed
Windsurf
any MCP clientThe code-graph engine.
Set the direction. OpenVisio draws the territory — continuously and deterministically.
Deterministic indexing
Tree-sitter parses every file into symbols and resolved imports. No LLM in the pipeline — the same repo always yields the same graph.
How indexing worksThe import graph
Files and folders become nodes wired by their real imports — the structure your repo always had, finally drawn.
Explore the graphA city of code
Every file is a building: height is lines of code, color is language, folders form districts you can read at a glance.
Walk the cityRanked by what matters
PageRank surfaces the load-bearing files; churn × centrality flags the hotspots worth your attention first.
See hotspotsEvery codebase already has a shape. Files cluster, imports flow, hotspots burn. OpenVisio draws it — built from the source, never from guesses.
OpenVisio is the visual layer for a new generation of grounded engineering.
One graph.
Three projections.
The same deterministic layout rendered as a city, a galaxy, and a hierarchy — switch projections without losing your place.
→ Folders as nodes, wired by real imports. Click to recurse, level by level.
Your agent goes
codebase-native.
The same graph, exposed as an MCP server. Claude Code and Codex stop crawling files and start querying structure.
One call, ready-to-work context
A task description in; a ranked skeleton plus the relevant neighborhoods out — every line with an exact path:line anchor.
Read the docs$ resolve_context "add oauth login" # task-ranked skeleton + neighborhoods auth/oauth.ts:1 beginLogin() auth/session.ts:14 verifyToken() api/middleware.ts:8 requireAuth() # 92K tokens of crawling → 2.4K of structure
Context is a bill
your agent pays.
OpenVisio breaks each task down to the structure it actually needs — so the tokens that never mattered never get spent.
| Task | Raw crawl | With OpenVisio | Margin |
|---|---|---|---|
Understand the architecture new repo · first hour | 84K | 2.1K | 40× leaner |
Find where auth happens cross-service trace | 31K | 0.9K | 34× leaner |
Trace a call chain entry point → handler | 47K | 1.3K | 36× leaner |
Plan a refactor impact analysis first | 92K | 2.4K | 38× leaner |
Read every file the old way | 240K | — | window exceeded |
Engineers stop reading.
They start seeing.
I pointed it at a repo I had been dreading for weeks. Twenty minutes later I was explaining the architecture to my team — with the map on screen.
The MCP server is the unlock. Claude Code stopped grepping around and started asking the graph — our agent runs got dramatically cheaper.
The city view sold me instantly: you can see the hotspot before you read a single line.
Citations changed how much I trust AI answers about our code. Every claim is a path:line I can click and verify.
Onboarding juniors with the narrator almost feels unfair. They ask, it answers, the map lights up.
Local-first and read-only meant security signed off the same day. That never happens.
Free to map. Pro to converse.
The map, all four views, and local indexing are free forever. Pro adds the AI that reads alongside you — grounded answers and a hands-free agent.
Free
Map any codebase, locally.
- Unlimited local repositories
- All four views — City, Graph, Architecture, Atlas
- Filter, drill, and trace imports
- Export & import graph bundles
Pro
Add the AI that reads with you.
- Everything in Free
- Grounded narrator chat — answers cite real code
- Hands-free coding agent + spotlight
- Narrate any view on demand
- Priority support
Secure checkout via Stripe. Cancel any time — no questions, no lock-in. Your code stays on your machine on every plan.
See your codebase.
It runs locally and reads only — open a repo and the map builds in seconds.
$ npm i -g openvisio