Skip to main content
Graph queries read the saved graph. Update it after changing the source to keep answers relevant.

​
Refresh code

For an assistant-driven incremental refresh that also considers document context:
The code and semantic paths have separate work and caching behavior. A code-only refresh does not replace a semantic refresh for changed documents.

​
Watch the project

Install the watch extra, then:
Or install git hooks:
The hooks refresh after commits and branch switches. They run in the background, so a query immediately after a commit can briefly see the old graph. After git pull or a merge, run graphify update . explicitly.

​
Exclude unhelpful files

Graphify respects ignore files. Add a .graphifyignore at the repository root for project-specific exclusions:
.graphifyignore
graphify extract --no-gitignore opts out of Git’s ignore rules while retaining .graphifyignore. Use it only when ignored source belongs in the graph.

​
After a large refactor

Graphify has guards against accidentally replacing a graph with a smaller incomplete result. If you intentionally removed substantial source, inspect the warning, then explicitly allow the smaller graph:
Keep a copy of the old graph if you need to compare it. Regenerate visualizations with graphify export html after a refresh when necessary.

​
See the cache at work

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. The first run of update re-extracted only the files that weren’t already cached:
After a one-line edit, the next run extracted a single file:
When communities shift, Graphify renames them after their hub node. Run graphify label if you want an LLM to name them again. graphify extract without --force is incremental too:

​
Flags

​
Troubleshooting

error: watchdog not installed. Run: pip install watchdog. graphify watch needs the watch extra:
error: path not found. The path you passed doesn’t exist. Run update from the project root, or pass the root path. The node count dropped after a refactor. If the rebuild has fewer nodes, update won’t overwrite graph.json unless you pass --force. That stops a partial checkout from wiping the graph.

​
FAQ

Does update re-read documents? No. It re-extracts code without an LLM. For document, paper and image changes, run /graphify --update in your assistant.

​
Next steps

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.

Repositories and builds

How Cloud indexes and rebuilds repositories.

Record useful findings

Save what you learn next to the graph.