nodo

Nodo

Map any codebase in seconds. Nodo scans your project, draws an interactive dependency graph, flags code smells, and — crucially — emits clean, structured context your AI coding agent can actually use.

Zero dependencies. Pure Python standard library. One self-contained HTML file that works offline. No build step, no npm install, no account.

Built for solo "vibe coders" who lean on Claude Code / Cursor / Windsurf, and for senior engineers who want a fast architectural read on an unfamiliar repo.

Install as a Claude Code plugin

/marketplace
#  ↳ when prompted "Enter marketplace source:", type:  shivae372/nodo
/plugin install nodo@nodo

Don't see /marketplace (or a "path does not exist" error)? Your Claude Code is out of date — run claude update, then retry. Prefer no plugins? Nodo is clone-and-run — see Quick start.

Part of the claude-bootstrap ecosystem: claude-bootstrap (the capability/self-improvement layer) reads Nodo's architecture map automatically at session start.

---

Why

When you let an AI write whole features, two things get hard:

1. You lose the map. Where does this function reach? What breaks if I touch it?
2. The agent lacks context. It re-reads files, guesses at architecture, and sometimes breaks unrelated flows.

Nodo fixes both. The HTML viewer is for your eyes. The nodo-context.json / .md files are for your agent — point Claude Code at them and it understands your architecture and open issues without you explaining a thing.

---

Quick start

Nodo is clone-and-run — pure Python standard library, no install, no dependencies.

git clone https://github.com/shivae372/nodo
cd nodo
python -m nodo /path/to/your/project --open

To map a project from anywhere, point Python at the launcher in the cloned repo:

python /path/to/nodo/nodo.py /path/to/your/project

That's it. Open .nodo/nodo.html in any browser.

Recommended: the Claude Code skill

The repo ships a /nodo skill for Claude Code. Copy .claude/skills/nodo/ into any project's .claude/skills/, then just type /nodo — the skill rebuilds the map and the AI-agent context files in one step, and Claude reads them back automatically. This is the blessed, highest-trust way to run it.

---

Two modes: vibe-coder (default) vs advanced

Nodo runs at two depths — pick one:

	Vibe-coder (default)	Advanced (--deep)
Command	python nodo.py .	python nodo.py . --deep
Speed / deps	Instant, zero dependencies (pure stdlib, regex)	Heavier; install tree-sitter tree-sitter-language-pack markitdown
Graph	File + import dependency graph	+ tree-sitter symbols (~19 langs) + a function-level call graph
Semantics	Structure + issues + hubs + data flow	+ knowledge graph (concepts, topic communities, god-nodes) + multimodal (docs/PDFs/images)
Best for	Daily iteration, issue-spotting, blast radius — staying in flow	Onboarding, architecture review, big-picture understanding

What "semantic" means here. Syntactic is structure — files, imports, definitions (vibe mode). Semantic is meaning — concepts, how things relate, which functions call which (advanced mode). Nodo builds the semantic scaffold deterministically (no embeddings, no LLM, nothing leaves your machine) and lets your AI assistant be the reasoning layer on top. So you get semantic depth grounded in real evidence — never a hallucinated graph — plus everything vibe mode already gives you. Advanced mode also surfaces: