Graphify’s code graph is local; document processing has different boundaries
The maintainer distinguishes deterministic code extraction from semantic processing of documents and media through an assistant or configured backend.
Graphify represents project relationships as a queryable graph and integrates with coding assistants. For code-only ingestion, the maintainer describes deterministic local tree-sitter extraction without an LLM. This is a specific processing lane, not a blanket property of every supported file type.
Documents, PDFs and media use semantic processing through an assistant or configured backend. Consequently, a mixed code/document corpus may send content to that backend. The original article wrongly extended the local AST/no-external-model claim to these files. Its September 12 first-release claim was not backed by an exact release receipt and is omitted here.
Before indexing sensitive material, choose the intended lane and verify backend configuration, data egress and permissions. The repository’s capabilities do not establish measured onboarding speed or production accuracy for every architecture.
Editorial correction (2026-10-13 UTC): Corrected the code-only locality boundary and document/media processing.