Open source · CLI · VS Code · Desktop

Your software is a world.
Go explore.

Code.Voyage turns a codebase into an explorable software world — services become buildings, APIs become roads, events ride the railway. See the whole map, follow a request on its journey, and ask the world where things happen.

  • Evidence first — every route leads back to source
  • Static analysis — no production access needed
  • Deterministic — AI never invents architecture
Create Payment
  1. Gateway POST /payments
  2. createPayment() + paymentId
  3. Risk Engine score ● ok
  4. Ledger payment.created
● confirmed◐ likely

Explore

Fly over the World Map or walk the streets in first person. Districts, buildings, floors, rooms — down to the source line.

Follow

Pick a business flow and follow the journey: a cargo travels the routes, stopping at every function, door, shipment and storage.

Ask

Ask the World in plain language — Where is paymentId created? — and get teleported to the answer, with evidence.

Teleport

Press / and jump to any service, endpoint, table, topic, class, function or document in the world.

World grammar

Every shape means something.

Code.Voyage is not a pretty picture of your repo. Every element in the world is a real, detected fact about your software — and you can always ask Why is this here?

Read the World Grammar →
Follow the journey

Don't read the flow.
Ride it.

Start a Voyage from any entry point. The world dims, a glowing cargo travels the routes, and the camera follows — pausing at every stop with what came in, what changed, what was stored, and the exact source line.

  • Suggested Voyages named from your endpoints — Create Payment, Capture Payment, On payment.created → Ledger
  • Journey Passport for every field: origin, changes, storage, travel
  • Fan-out ghost cargos when a flow branches; trains for Kafka, trucks for RabbitMQ
  • Ends with ✓ Voyage complete — stops, routes, objects changed, DB writes
Follow the journey
Ask the World

Ask a question.
We'll take you there.

Answers are grounded in your software graph and shown spatially: the world teleports, highlights the buildings involved and opens the evidence. Deterministic rules first; an optional Claude fallback only ever sees a secret‑free world summary — never your code.

PaymentService.createPayment()

paymentId is generated here, before the risk check. Stored in payments.id, then travels on payment.created to Ledger Service.

● confirmedpayment.service.ts:42Teleporting to Payment Service…
Demo world

Land on a familiar shore.

Spring PetClinic Microservices is the reference world: a gateway, four services, config, discovery and databases. Explore it read‑only, follow Add Visit, or ask where owners are stored — no repository of your own required.

Code.Voyage Benchmark · PetClinic suite 100% node & route recall on B01–B03

PetClinic World · World Map ⛵ Add Visit
Open source · install your way

One world. Three ways in.

Map a repository from the terminal, explore without leaving VS Code, or open the desktop app for long journeys through large codebases. Everything runs locally — your code never leaves your machine.

VS Code

Stay in your editor

Open the world beside your code, teleport from a symbol to its building, and start Voyages from any handler.

ext install code-voyage.code-voyage

Or download the .vsix and install it via Extensions → Install from VSIX…

View on the Marketplace →
npm code.voyage PyPI code.voyage publisher code-voyage license Apache‑2.0 hi@code.voyage
Why Code.Voyage

Don't read the map.
Step inside it.

  1. 01

    Evidence first

    Every route, stop and answer carries its evidence and a confidence — confirmed, likely, inferred. Nothing is drawn that cannot lead back to source.

  2. 02

    Static before live

    The world is built from the repository alone: no agents, no production access. Live Voyage — runtime traffic — comes later, on the same map.

  3. 03

    Deterministic, then AI

    Analyzers and rules build the graph. AI may name and describe, but it never invents architecture.

  4. 04

    Open by default

    Open‑source engine, viewer and benchmark. Inspect it, extend it, own it.

Your codebase is already a world.
You just haven't seen it yet.