Codemble第一図·plate one
You built it with AI. Codemble reads your project on your own machine and draws it the way an Edo astronomer drew the sky — modules as star systems, functions as planets, your entrypoint as Home. Every star starts dark. You light it by proving you understand it.
uvx codembleNeeds uv — brew install uv · Python 3.11+ · opens your browser to pick a project
承 shō·plate two
The camera runs on rails, because wandering a 3D scene is not learning. Each level shows one thing well, and everything on it is something the parser proved.
Modules are star systems, imports are routes, your entrypoint is Home. Size is lines of code; brightness is how often something is called.
Zoom a system and its functions and classes orbit as planets, joined by call edges. Anything the parser could not prove is labelled possible call.
Open a planet for real source, a grounded explanation, and the language idiom it demonstrates — every claim linked to a real file:line.
One atlas, whichever language you shipped
Focus a language to dim the rest — the graph, the coordinates and your progress never change.How focus works
転 ten·plate three
Here is the turn. Codemble looks like a visualisation, and every visualisation lets you nod along without learning anything. This one asks you to prove it.
Short questions built from your code’s actual structure — which module imports this one, what Home reaches first. The answers come from the parsed graph, never from the model, so a confident wrong answer is not possible.
A region is one module. Pass its checks and it lights in kohaku amber and stays lit, saved locally in ~/.codemble/. Edit that file later and only that region goes dark again — nothing else you earned is taken away.
No XP, no streaks, no leaderboards. A fully lit atlas means you understand your project. The star chart beside it records every language concept you met on the way.
A region with no safe graph-derived check stays dark and tells you why. Lighting a star for showing up would be a lie about what you know.
結 ketsu·plate four
Codemble’s reader often cannot tell when a tool is wrong — that is exactly why they need it. A tool that teaches a beginner something false is worse than no tool, so these come first, including ahead of what we want to build.
Structure is never invented — nodes, edges and entrypoints come only from the parser.
Explanations are grounded, and say “unclear from the code” rather than guess.
Lens claims attach only to parser-detected constructs.
Every explanation links to a real file:line, so you can check it.
Check answers come from the graph, never the model.
Approximate call edges are labelled “possible call” — never stated as fact.
Install uv
Once per machine. It fetches Codemble on demand.
brew install uvChart your project
Every time. Nothing is left behind.
uvx codembleCodemble opens your browser — pick your project folder there, or skip the picker with codemble ./your-project. No Homebrew? Use theuv installer. Prefer a permanent install? pipx install codembleneeds no uv.
Your code is parsed locally. The only network calls are the LLM requests you configure, sent from your machine straight to your provider. Without a key you still get the atlas, the source, the lens and the checks — only the prose needs a model.