Generate a call-flow view
Export another graph
Write to an existing Obsidian vault
.obsidian configuration.
Push to a graph database
Neo4j and FalkorDB exports support optional push connections. Install the matching extra, use the appropriate connection URL, and supply passwords throughNEO4J_PASSWORD or FALKORDB_PASSWORD rather than putting secrets on the command line.
Run every export on a real repository
These examples come from a code-only graph of the open-source httpx repository, built with Graphify CLI 0.9.97. Your counts will differ.Outputs
To push to a database, set
NEO4J_PASSWORD or FALKORDB_PASSWORD instead of passing --password, so the secret stays out of your shell history.
Troubleshooting
ImportError: matplotlib not installed. Run: pip install matplotlib. SVG export needs the svg extra:
warning: graphify-out/.graphify_analysis.json is stale (1883 node(s) recorded vs 2341 in graph.json). The graph changed after the last clustering. The export still runs, rebuilding communities from graph.json. To refresh community data, run:
Flags
FAQ
Do exports call an LLM? No. They readgraph.json and the label files.
Which export should an agent read? wiki/index.md is marked as the agent entry point.
Next steps
Try it in Graphify
We build and host the graph for you, and review your pull requests with it. The Free plan (up to 3 repositories) needs no card. Pro and Teams start with a 14-day trial, card required.
Share context with your team
Keep one graph for everyone.
Graph files and outputs
What each output file contains.