KodaCode
Coming soon
The code graph

See how your code connects.

Your agents can understand your codebase without reading all of it.

KodaCode keeps a map of your project: every file, every function and what calls what. The map changes when your files change. An agent asks the map who calls a function and gets the callers and their signatures, not whole files.

More focus, fewer tokens.

Context goes to your task, not to code the agent didn’t need. Sessions run longer before compacting, and you pay for less.

A map you can explore too.

Open the same graph yourself and trace how your code fits together, from a single function to the whole project.

Less searching. More understanding.

MapThe whole project, grouped by folder
ChangedWhat you touched, and everything linked to it
CallsCallers and callees, with how sure each link is
DataYour tables, beside the code that uses them
01What you can do · With the map
Take in the whole project

Files grouped by folder, with the links between them drawn. Hide a folder to cut the noise.

Focus on what changed

Switch to changed files and see only what you touched, plus everything that depends on it.

Ask who calls this

Pick a function to see its callers and the functions it calls, each marked certain or likely.

Retrace your steps

Every jump you make is kept as a path, so you can walk back to where you started.

Read the database too

Tables, columns and indexes from your SQL migrations or your ORM, each listed with the code that names it. Works with Prisma, Drizzle, TypeORM, Sequelize, Knex, Django, SQLAlchemy, Rails, Diesel, GORM and Entity Framework.

Jump to the source

Open any file or function in the editor, at the line it starts on.

02The database · Schema

Your database, beside your code.

Press d in the code graph and the same screen draws your database. KodaCode reads it from your SQL migrations and from the models your ORM defines, then links every table to the functions that read and write it.

What it reads

Tables, columns, primary and foreign keys from .sql migrations and from Prisma, Drizzle, TypeORM, Diesel and other ORMs, plus MongoDB collections, views and the $lookup joins your code runs.

What you see

A map of every table and how it joins: required, nullable, implied and virtual links drawn apart. Pick a table for its columns, keys and the code that uses it, or find the join path between two.

What the agent gets

Ask the graph join webhook_deliveries accounts and it answers with the shortest paths and the SQL that walks them, so the agent writes the join without opening a single migration.

Text when you need it

Switch the map to Mermaid, DBML or Graphviz to paste the schema into a design doc, a review or another tool.

Open a project.

macOSDesktop appComing soon
WindowsDesktop appComing soon
LinuxDesktop appComing soon