v0.4.0 · early preview · MIT

Bring your code to light

Codiluce helps engineers understand their code and its architecture while agents keep changing it: every flow from the interface to the data, every commit, and every file an agent touches, you now get it.

npx codiluce@latest start .

Or tell Claude Code, Codex, or your coding agent:

Read the docsView on GitHub

Node.js 22.12 or newer. Run it in the repository you want to see.

Each Claude Code or Codex session is a character on the map: it hops to the files it reads and edits, and splits to read several at once.

A scripted replay of the map on a small made-up repository. Run it on yours to see the real thing.

Why now

The comprehension gap is widening.

More people and more agents are writing code, and every change is bigger than the last. Reading the diff no longer tells a team what the system does, which flows a change touches, or what it can break.

Codiluce keeps understanding in step with the code: every flow, dependency and change, linked to the source that proves it.

Illustration: from autocomplete to coding agents to agents working in parallel, the code agents write grows exponentially while human comprehension of it barely rises, so the gap between them keeps widening. With Codiluce on, comprehension rises to follow the output and the gap narrows.AutocompleteCoding agentsAgents in parallel
Agent outputComprehension gapHuman comprehensionLifted by Codiluce
An illustration of the trend, not measured data.

Goal

Agents keep changing the code. Humans should still understand it.

Codiluce exists so the people responsible for a system still understand it, whoever made the last commit. It answers the questions a review of the diff cannot.

agent/password-reset38 files+2,417−583

A diff says which lines changed. Not what they mean.

What the people responsible need to know

  1. Ask your agent. Its answer is saved beside the map, and every file, symbol and flow it names lights up.

  2. Each session’s reads, edits and searches mark the map as they happen, one color per agent.

  3. Pages, requests, commands and scheduled tasks are traced end to end, so every file says which flows reach it.

  4. Compare any two commits in place, then follow the blast radius of anything, hop by hop.

Agents

Work with your agents, not behind them.

Connect Claude Code, Codex, Cursor or any of twelve coding harnesses once. Your agent reads the index instead of guessing from file names, explains what it finds on your map, and you watch it walk through the files it touches.

Explain it with your agent

Ask in your own words. The agent follows flows, blast radius, history and source through Codiluce's MCP server, and publishes its answer to the map's Explain column. While it works, the map shows what it is explaining and each tool it calls.

  • Answers can be tours: scenes on the map, and diagrams that rise from it
  • Every link is checked against the index before the answer is saved
  • Answers are pinned to their commit and say when the code they link changes
  • No agent at hand? Ask in the map, with your own Anthropic or OpenAI key
claude mcp add codiluce -- npx -y codiluce mcp
Explanations →

Watch them work

Every session is a little character on the map. It hops to each file it reads or edits, labeled with what it does, splits into copies to read several at once, and waits in a queue beside the map to think, run the tests or wait for you. A colored square ties it to its session in Agents.

  • Open a session to keep only its characters; point at one to dim the others
  • Search past sessions by message or by the files they touched, and replay a finished one on the map, step by step
  • Only paths, searches and tool names are kept, in memory: never prompts, file contents or output
Agents →

And more

One map for every question about the code.

  • 3D or 2D

    See the code as blocks in 3D, or as a flat plan from above where names never overlap. Switching keeps the same place in the middle.

  • History

    Play the Git history of every file: additions, edits, moves and deletions in place, with diffs and who made them. Architecture snapshots on demand.

  • Impact

    Pick anything, or your uncommitted changes, and see what depends on it, hop by hop, grouped by application, feature and folder.

  • Pull requests

    Open pull requests and branches not merged yet light the files they change, with their commits, people and blast radius.

  • People

    Who changed which code, read from Git without a model. Coding agents and bots are marked as such.

  • Color by

    Color the map by the code no flow reaches, who changed it most, complexity, recent changes or hotspots.

  • Evidence

    Every link opens the file and line that proves it. What cannot be proven shows up as a finding, never as a guess.

  • Hide what you do not need

    Right-click a file or folder to hide it from the map, the history and its playback; Settings lists what is hidden. The analysis still covers it.

  • Private by design

    It runs on your machine, reads your code without running it, and never writes to your checkout. Nothing leaves unless you ask.

Stacks

Reads the stacks your team ships.

Codiluce maps any repository, and follows routes, handlers and calls through the languages and frameworks below. Every link carries its evidence; what it cannot prove stays visible.

Languages

  • TypeScript
  • JavaScript
  • Python
  • Java
  • C#
  • PHP
  • Go
  • Rust
  • Kotlin
  • Ruby

Also analyzed

  • Nuxt
  • Astro
  • Inertia
  • Echo
  • Fiber
  • Chi
  • Gorilla Mux
  • net/http
  • Axum
  • Actix Web
  • Rocket
  • Warp

Detected

Angular, Remix, Fastify, Koa, Hono, React Native, Expo, Electron, Tauri, Capacitor, Symfony, Drupal, CakePHP, Yii, Slim, Livewire, Celery, Sinatra, Hanami, Sidekiq, Jekyll, Quarkus, Micronaut, Ktor, Play, Akka HTTP, http4s, Android, Blazor, .NET MAUI, WPF, Windows Forms, Vapor, Shopify themes, and every other language: mapped with their files, lines and Git metrics.

What each stack supports →

Contribute

Shaped by the teams who use it.

Codiluce is open source and early. We would rather build what engineering teams need than guess it, so feedback counts as much as code: tell us how your team works, and what you still cannot see in your code.

01

Tell us what your team needs

Which questions about your code take the longest to answer? What is your stack, and how do agents work in it? Your answers shape what we build next.

Book a 30-minute call
02

Report what it gets wrong

Run it on your repository. What the analyzers cannot prove shows up as findings, and codiluce inspect diagnostics is the best start for an issue. Remove private paths first.

Open an issue →
03

Ask for your stack

Missing a language, a framework, or a question the map cannot answer yet? Open an issue with a public repository that shows it. Real code beats any description.

Request it →

Contribute code

  • Analyzers for more languages and frameworks. Each brings routes, entry points and calls with evidence, and fixtures that prove them.
  • The map itself: themes, interactions, performance on very large repositories.
  • Docs and examples from the way your team uses it.
Star on GitHubHow it works →

Develop locally

# get the source
$ git clone https://github.com/codiluce/codiluce.git
$ cd codiluce && npm ci

# map any repository from the checkout
$ npm start -- /path/to/repository

# before a pull request
$ npm test && npm run typecheck
$ npm run test:e2e

One rule for analyzers: name-only matching never creates an edge. Prove it, or report it.

See your repository in a minute.

npx codiluce@latest start .

Or tell Claude Code, Codex, or your coding agent:

Getting started →