Skip to main content
Graph shows the code knowledge graph of a repository: its modules, files, classes, and functions, and how they connect. Every relationship carries a confidence tag, so you can tell what was read from the code and what was worked out by analysis.
Use the graph when you want to see the shape of a system, find its most connected code, or check what a change could affect.

Before you start

  • A Graphify account at app.graphify.com.
  • A repository with the status Indexed. To combine graphs, you need at least two.

Read the canvas

Select a code area to see its connections, or use Filter the canvas by code area. Most connected lists the nodes that much of the code depends on. Graph totals shows the size of what you’re looking at. New to reading a graph this size? Read your code graph and clean up your repos walks through each view in order.

Explore a node

1

Find it

Use Find a node to search by name, path, or repository. Prefix with a kind, such as repo:, to narrow results.
2

Read its connections

The panel shows the node’s repository, path and code area, then lists its Outgoing and Incoming connections. In a combined graph, a Cross-repo list appears when the node has edges to another repository.
3

Check impact

What a change could affect counts the Possible dependents of the node. Choose a Depth of 1, 2 or 3 to widen or narrow it.
4

Ask about it

Explain this code gives a plain-language explanation of the selected node. For a broader question, use Ask.
Use Fit graph to view, Zoom out, full screen, and Reset layout (which returns dragged nodes to the computed layout) to move around. Export the graph downloads it.

Combine repositories

Real systems span repositories. A combined graph links entities in different repositories so you can trace a change across them.
1

Open Combine graphs

Go to the cross-repository view and select Combine graphs.
2

Pick repositories

Select two or more repositories.
3

Name it

Enter a name, or leave it blank to use the suggested one.
The combined graph is listed under Combined graphs in the graph view’s right panel, and you can pick it from the graph selector. When you select a node, its Cross-repo list shows edges to other repositories, and What a change could affect adds a Cross-repo dependents list when dependents are in other repositories.

Combined graph limits and states

  • A name is 2 to 120 characters.
  • A combined graph holds 1 to 100 repositories from your workspace.
  • Rebuilding with the same repositories and unchanged graphs doesn’t start new work.
A combined graph moves through not_started, queued, running, then ready or failed. If it fails, select Retry build.

Query the graph

The console, Ask, and your hosted MCP agent all query the same graph. Each query targets one repository, by ID, full name such as acme/api, or short name such as api. A combined graph is targeted by its name. See Troubleshooting. The graph reads its URL, so you can share an exact view. Selecting a combined graph sets ?group= and ?title=. Turning on Show on canvas for an impact check sets ?impact= and ?depth=. Links can also open a node with ?node=, or specific repositories with ?repo= or ?repos=.

Read the legend

Use Search nodes by name, path, or repository. You can narrow a search with kind: and repo:. Press F to open the focus lens. Use Fit graph to view, Show the minimap and Maximize the graph to full screen to move around large graphs, and Reset layout to put dragged nodes back.

What a change could affect

Select a node and find What a change could affect in its details. Under Depth, choose 1, 2 or 3 connections. The default is 2. Possible dependents counts everything that calls, imports, cites or implements the node within that range. Select Show on canvas to highlight them, and Clear overlay to remove the highlight. This is a structural over-estimate. It’s not a prediction that anything will break, and it doesn’t verify anything. No dependents found in this view means nothing in the loaded graph depends on the node within that depth. Dynamic and external callers may not be represented.

Plan limits

Combining graphs needs an active plan. The Free plan (up to 3 repositories) needs no card. Pro and Teams start with a 14-day trial, card required.

Verify and troubleshoot

Relationships are tagged as read directly from the code or inferred by analysis. See provenance.
Yes. Open-source Graphify writes graph.html for a local build. See Exports.
No. The impact view is a dependency estimate. Use reviews and your tests to check a real change.

What’s next

Ask

Question the graph in plain language.

Pull request reviews

See what a pull request changes.

Connect your agent

Add the hosted MCP at api.graphify.com/mcp. Sign in with OAuth, no API key.