Stop paying your agents to search your code

A live map of your code, with your team's lessons attached. Agents start in the right place.

Add my repository
A chalkboard sketch of one file in the middle, the files that import it on the left and the files it imports on the right.
The Graph view: pick a file and see what it works with.

What the code index does for you

Agents start in the right place

An agent asks the map where things are and what connects to the file it is changing, then goes straight there instead of searching folder by folder.

Less duplicate code

Before writing something new, an agent asks whether it already exists. If it does, the agent uses it instead of writing another copy.

More of your subscriptions do real work

Big models find their way around a large project. Smaller ones get lost. With the same clear map, cheaper models can take on more of the work.

Lessons that follow the code

Link a lesson to a file, a function or a folder. When the code moves, the lesson moves with it. When the code is deleted, the lesson is flagged.

The right lessons, not the whole rulebook

Before an agent changes a file, it gets the lessons for that file and the files around it. A small change no longer means reading every rule.

See it for yourself

Open a project's Code index and choose Graph. You see your folders, how they connect, and what each file works with.

How a lesson follows your code

Take an example repository, acme/shop.

  1. Your team records a lesson on checkout/payment.py: refunds go through issue_refund, never straight to the payment provider.
  2. Someone moves the file to billing/payment.py. The next index sees the move, and the lesson moves with it. Nobody edits anything.
  3. Later, the file is deleted. The lesson is marked stale and shows up in its author's list, so a person decides whether it still matters.

And an agent about to change checkout/cart.py gets the refund lesson, because cart.py uses billing/payment.py. It does not get the lessons about the admin panel. Those are not about this change.

What we promise

The map is built from your code by a parser on your workspace's build machine, so it shows what is really there, not a guess. Nothing is sent to an AI model to build it. It keeps itself up to date as your team merges changes.

Your lessons stay attached to the code they are about. And a missing map never stops a build: your agents simply carry on.

Read the whole story on the blog: Stop paying your agents to search your code. Developers can find the methods in the code index docs.

Give your agents a map

Connect a GitHub repository under Project, Settings, Repository. With a build machine in your workspace, the map builds itself.

Add my repository