GraphRAG eyes whole-PC indexing

The idea is technically viable, but “graph RAG for an entire PC” sounds cleaner than it is. Once you move beyond a curated codebase or document set, the hard part becomes trust, freshness, and scope control rather than retrieval.

• –Microsoft’s open-source GraphRAG is designed to extract structured knowledge from unstructured text, but its own docs warn that indexing is expensive and prompt tuning matters.
• –Graphify’s pitch is closer to “turn a project folder into a persistent knowledge graph” than “index every file on a live machine,” which is a much narrower and more practical problem.
• –A whole-PC graph would mix source code, docs, configs, binaries, logs, screenshots, browser data, and personal files, so schema quality and access controls quickly become the real bottlenecks.
• –Snapshot-based indexing also goes stale fast on an active machine; incremental updates, deduping, and provenance tracking are mandatory if you want answers you can trust.
• –The best use case is usually scoped knowledge infrastructure for a repo, team drive, or research corpus, not a universal memory layer over everything on disk.