Multiple repositories

Real systems rarely live in one repository. A frontend calls an API, the API imports a shared client library, and a worker reads the same tables. Graphify Local can join separate graphs so your agent can follow a path from one repository into another. There are two ways to do it:

Approach	Use it for	Output
`merge-graphs`	A fixed set of repositories, such as one product’s services	A merged `graph.json` you choose the path for
`global`	Every project you work on, kept up to date over time	`~/.graphify/global-graph.json`

Use this when a change in one repository can break another, or when your agent keeps asking where a shared type is defined.

How it works

Build each repository

Run graphify extract . (or your usual build) in each repository so each has its own graphify-out/graph.json.

Combine

Nodes are tagged with their repository. Unresolved calls saved during each build are matched against definitions in the other repositories, so cross-repo member calls become real edges.

Re-cluster

The combined graph is clustered as a whole, so communities can span repositories.

See it in action

merge-graphs
global

graphify merge-graphs ../web/graphify-out/graph.json ../api/graphify-out/graph.json \
  --out graphify-out/merged-graph.json
graphify path "LoginForm" "create_session" --graph graphify-out/merged-graph.json

The default output is graphify-out/merged-graph.json. Pass --previous <path> to keep the community IDs from an earlier merge.

graphify global add graphify-out/graph.json --as api
graphify global list

Added 'api' to global graph: +3872 nodes, -0 pruned. Global: ~/.graphify/global-graph.json
Global graph: ~/.graphify/global-graph.json
  api: 3872 nodes, added 2026-10-28

Running global add again with the same tag replaces that repository’s nodes. --as defaults to the parent folder’s name.

Query the global graph by passing its path:

graphify query "where is the auth token validated" --graph "$(graphify global path)"

To pull in a public repository first, graphify clone <github-url> clones it locally and prints its path.

Manage the global graph

Command	Does
`graphify global add <graph.json> --as <tag>`	Add or update a repository
`graphify global remove <tag>`	Remove a repository’s nodes
`graphify global list`	List repositories with node counts and dates
`graphify global path`	Print the global graph’s location

Point your agent at it

The MCP server reads any graph file, so you can serve a merged graph:

graphify-mcp --graph graphify-out/merged-graph.json

See MCP tools for the tools it exposes.

Verify and troubleshoot

Symptom	Fix
No edges between repositories	Rebuild each repository with the current version so unresolved calls are saved, then merge again.
Duplicate nodes for a shared library	Build the library once and include its graph in the merge, instead of vendoring it.
Stale repository in the global graph	Run `global add` again with the same `--as` tag, or `global remove` it.
Community IDs change after each merge	Pass `--previous` with the last merged graph.

Does merging change each repository's graph?

No. Inputs are read, not modified.

Is the global graph shared?

No. It’s a file in your home folder.

Run it on a second repository

These examples come from a code-only graph of the open-source httpx repository, built with Graphify Local 0.9.97. Your counts will differ.

$ graphify global add graphify-out/graph.json --as httpx
Added 'httpx' to global graph: +2315 nodes, -0 pruned. Global: /home/box/.graphify/global-graph.json
$ graphify global list
  httpx: 2315 nodes, added 2026-10-28
$ graphify global remove httpx
Removed 'httpx' from global graph (2278 nodes pruned).

To combine graphs into one file without the global graph, use merge-graphs:

$ graphify merge-graphs a/graphify-out/graph.json b/graphify-out/graph.json --out merged.json
Merged 2 graphs -> 4629 nodes, 9082 edges

Pass --previous <path> to keep the earlier merged community IDs. Then a later cluster-only run can reuse the labels.

Add a repository while you extract

extract can write a project graph and merge it into the global graph in one step:

graphify extract . --code-only --global --as sqldemo
graphify global path

/home/box/.graphify/global-graph.json

--as sets the tag. Without it, the tag is the target directory’s name. Use the same tag later to update or remove that repository:

$ graphify global remove sqldemo
Removed 'sqldemo' from global graph (4 nodes pruned).

Command	What it does
`global add <graph.json> [--as TAG]`	Adds or updates a project graph.
`global remove <tag>`	Removes that repository’s nodes.
`global list`	Lists the repositories in the global graph.
`global path`	Prints the global graph’s path.
`merge-graphs <g1> <g2> ... [--out PATH] [--previous PATH]`	Writes a merged file. The default is `graphify-out/merged-graph.json`.

FAQ

Where is the global graph? Run graphify global path to print it. By default it’s ~/.graphify/global-graph.json.

What’s next

PR impact

Check what a change touches.

Deduplication and resolution

How calls are resolved.

Try it in Graphify

We build and host the graph for you. Start with a 14-day Pro trial, then keep up to 3 repositories on Free. No card required.

Get started

Features

Configuration

Support

Multiple repositories

How it works

See it in action

Manage the global graph

Point your agent at it

Verify and troubleshoot

Run it on a second repository

Add a repository while you extract

FAQ

What’s next

PR impact

Deduplication and resolution

Try it in Graphify

​How it works

​See it in action

​Manage the global graph

​Point your agent at it

​Verify and troubleshoot

​Run it on a second repository

​Add a repository while you extract

​FAQ

​What’s next

PR impact

Deduplication and resolution

Try it in Graphify

How it works

See it in action

Manage the global graph

Point your agent at it

Verify and troubleshoot

Run it on a second repository

Add a repository while you extract

FAQ

What’s next