Skip to main content
Build a graph first, then export the same saved relationships into the format you need.

Generate a call-flow view

The exporter reads the graph and associated report/labels. Explicit output paths make it easier to include the result in an internal documentation workflow.

Export another graph

Write to an existing Obsidian vault

Review generated content before syncing it to a shared vault. The exporter is designed to preserve your own notes and .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 through NEO4J_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 Local 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 read graph.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. Start with a 14-day Pro trial, then keep up to 3 repositories on Free. No card required.

Share context with your team

Keep one graph for everyone.

Graph files and outputs

What each output file contains.