graphify extract runs the pipeline without an assistant skill. It is useful for repeatable local scripts and CI jobs.
Code-only extraction
Semantic extraction
Install the extra for your backend, configure its credentials outside the repository, then select it:Tune resource use
--max-workers controls structural extraction parallelism. --max-concurrency controls model requests. --api-timeout changes the request timeout. Smaller chunks and less concurrency can help a local model fit its available memory.
CI pattern
Install a pinned package version in the CI environment, run extraction from the repository root, and retain the reviewed graph or report as an artifact. Use the same ignore rules and output location on every run. Supply provider credentials through the CI secret store only when semantic extraction is part of the job. No provider key is necessary for--code-only. Do not make CI publication of the graph public unless the underlying source can be public too.
Run it 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. A code-only run finished in about 2.6 seconds of wall time:cluster-only to write the report:
Flags
For a self-hosted OpenAI-compatible server (llama.cpp, vLLM or LM Studio), use
--backend openai and set OPENAI_BASE_URL and OPENAI_MODEL. For an Anthropic-compatible gateway, use --backend claude and set ANTHROPIC_BASE_URL and ANTHROPIC_MODEL.
FAQ
Why is.netrc skipped? Credential files are never indexed. The run lists them as “skipped as potentially sensitive”.
Can CI fail when the graph shrinks? graph.json reports the node count, so you can compare it in a script step. See the incremental updates page for --force.
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.
Keep the graph current
Update only what changed.
graphify extract
Every flag for the extract command.