Explore the Code Graph

Code GraphBeginner4 min

Code Graph is CodeZero's organisation-wide view of how the engineering system is connected. It uses indexed relationships to connect modules, files, data and cross-repository dependencies without treating every repository as an isolated project.

Open Code Graph

Open Graph from the CodeZero tool strip. Start from the organisation view or select a repository you already recognise.

Code Graph in Modules view showing colour-coded repositories, dependency arrows and the repository legend — Graph · Modules across all repositories. Dashed edges are inferred service calls.

Choose the level of detail

Code Graph provides two related controls:

Modules / Files: Switch between directory-level and file-level views.
Grouping: While viewing Modules, control how much directory structure is rolled up.

A shallower grouping keeps the system compact. Moving deeper reveals more specific directories. Switch to Files when you need the graph at individual file level.

Filter the system

Use All repositories to keep the organisation-wide view, or isolate one repository when you need a narrower investigation.

You can also include third-party packages and the data layer. Data nodes show collections, tables and other storage relationships alongside the code that reads or writes them.

Explore a relationship

Select a node to inspect the relationships around it.

The detail panel separates the relationship in both directions:

Depended on by — what points into the selected component
Depends on — what the selected component points to

Some relationships remain inside one repository. Others continue into another indexed repository, which is where the organisation-wide view becomes especially useful.

Direct and inferred relationships

Code Graph distinguishes relationships resolved directly from source from service calls that are inferred from indexed evidence.

Inferred edges keep their uncertainty visible. When an inferred relationship matters to an investigation, use Verify to ask your agent to check the relevant call site. Verified verdicts are kept for the organisation.

When to use Code Graph

Code Graph is most useful when you begin with an engineering question:

What consumes this service?
Which components depend on this package?
Where is this capability implemented?
Does this flow cross into another repository?
What could be affected by changing this component?

The graph is not only a diagram. The same indexed relationships support Feature Mapping, Chat and change planning throughout CodeZero.