AmbitGraph

You don't understand your own product!

You can't keep up with the amount of code!

One command, and you do. Deterministic. No tokens.

AmbitGraph draws your whole repo as a visual interactive map & library and gives them to you. It needs Python on your machine, never in your project. Free, offline, no account, no API key.

Python 3.11 or newer.

Install and run

pip install ambitgraph
python -m ambitgraph map <folder>

ambit map <folder> does the same when your Python scripts folder is on your PATH.

The command gives your terminal back and the map keeps serving. Stop it with python -m ambitgraph map <folder> --stop.

Your codebase is displayed in your browser as local webpages.

It does not make any changes to your codebase.

Update

pip install --upgrade ambitgraph

python -m ambitgraph --version (or ambit --version) prints the version you have.

Updating the tool is not the same as refreshing a map: after your code changes, just run python -m ambitgraph map <folder> again.

The cockpit

ambit cockpit --runs <dir> builds the UrCode screen — the Graph, the Library, and the whole map on one dark dashboard — as a static page over a folder of scan runs.

A GRAPH

Modules, Classes, Imports, Calls, DB Tables, anything in your code mapped on its connections.

An Indexed and Searchable LIBRARY

Understand what you have, what it does, and what it means.

Understand your own codebase in a way you never have. Simple, visual, and if you want more you can ask your agent what the hell it just did. A vibe coder can finally see how their code works. A senior can see at a glance when something has got too complicated.

Your machine

The map is served to your own machine, stays on your machine. It and your code belong to you

No AI

No AI is required. The map is plain reading of your code.

No model runs, no tokens burn, no key exists. If you want more than the map, your own assistant can work on top of it, on your own subscription, with whatever model you already pay for. Optional, always, and the map is finished without it.

In this version

Search finds functions and tables by name. The Library groups every file the scan read into families. The Graph draws one file and everything one hop from it, and every row in the Library opens it.

Search does not find routes or file names. Drawn connections do not carry their meaning beside them. There are no written explanation pages.