VibeCodeMap

OpenAI Build Week · Developer tools

See the codebase
before it disappears
into code.

VibeCodeMap turns repository evidence and editable, source-linked models into a navigable 3D condition map—so humans can inspect the shape, interactions, side effects, and uncertainty of AI-built software.

Explore the live mapView the repository

Experimental investigation aid. Not proof that code is correct, secure, or complete.

Repository signalVCM / 0.1
D1 · CLID3 · ADAPTERSD4 · VIEWER
42 buildings7 roads6 districts

Live artifact · VibeCodeMap maps itself

Investigate the prototype from inside the prototype.

Open full-screen map ↗
Drag to orbit · scroll to zoom · WASD to move · click a buildingGenerated from the public VibeCodeMap repository
Visual grammar

Buildings

Components, interfaces, resources, actors, and expected-but-missing parts.

Condition bands

Complexity, coupling, mutating effects, coverage, and other named evidence. Unknown stays unknown.

Typed roads

Calls, events, state access, and static topology remain visually distinct instead of becoming one misleading graph.

From repository to reviewable form

Deterministic evidence where possible. Explicit inference where necessary.

The CLI does not pretend source parsing equals architecture. It gathers bounded evidence; the agent authors a reviewable model; the renderer preserves provenance, confidence, and missing information.

  1. 01vibecodemap inspect

    Bound the repository

    Inventory owned source, detect stacks, and keep generated or installed code out of the investigation.

  2. 02vibecodemap analyze

    Collect evidence

    Run implemented Go, Python, and JS/TS analyzers over one reviewed scope.

  3. 03vibecodemap model

    Describe the system

    An AI agent investigates the source and authors editable, source-linked architectural DSL.

  4. 04vibecodemap show

    Review the condition map

    Validate, compose, and open a navigable Three.js map with explicit evidence and unknowns.

Current analyzer coverage

Useful now, honest about depth.

StackCurrent supportMethod
GoAnalyzedGo parser / AST prototype
PythonAnalyzedPython AST subprocess
JavaScript / TypeScriptAnalyzed*Conservative lexical prototype
Dart · Kotlin/Java · Swift/Obj-CDetectedAgent investigation; no native analyzer yet

* JS/TS evidence is not compiler- or type-aware. Hosted viewing requires only a modern browser. Local analysis requires Go 1.24+; Python 3.10+ is needed only when Python source is analyzed.

Built with Codex + GPT-5.6

One continuous collaboration, from raw idea to runnable prototype.

Codex with GPT-5.6 in Sol Max mode was the primary engineering environment throughout ideation, architecture, implementation, visual critique, code review, testing, documentation, and submission.

Human direction

The core problem, visual-city metaphor, critique of misleading views, product boundaries, and every consequential direction change came from the builder.

Codex + GPT-5.6 execution

Translated the vision into Go contracts, DSL schemas, analyzers, tests, the Three.js renderer, agent guidance, and this public demo—then repeatedly audited its own work.

Key decisions

Unknown must stay unknown; static imports are topology, not runtime communication; AI architecture claims carry provenance; generated visual clutter must not masquerade as code complexity.

Map a repository

Clone, build, then ask the checked-in agent skill to investigate.

The live artifact above needs no installation. To analyze your own source, build the CLI and run the end-to-end skill from Codex.

git clone https://github.com/mmirolim/vibecodemap.git
cd vibecodemap
make build

./bin/vibecodemap show \
  examples/uzumtools/uzumtools.project.vcm.yaml