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.