kgraph-plugin

Stepping into an unfamiliar codebase with hundreds of files, no clear module boundaries, and tangled dependencies can feel overwhelming. kgraph-plugin addresses exactly that friction: it performs a read-only scan of any project directory and automatically assembles a module-level and file-level knowledge graph, so you can grasp the overall architecture and design intent in minutes, with a solid basis for subsequent evolution and optimization.

Under the hood it recognizes manifests such as pom.xml, package.json, go.mod, and requirements.txt to split modules, resolves cross-references for Java/Kotlin, TypeScript/Vue, Python, and Go, and classifies files into roles like controller, service, mapper, entity, dto, config, pages, components, router, store, api, and util. The output covers a module dependency graph, a file-level layered graph, detected tech stack, entry points, key files, and architectural observations, all built exclusively with DSH fs services so the scanned project is never modified.

Usage is straightforward: a floating project knowledge graph panel appears in the lower-right corner of the page. Type a path, hit Scan, and drill from module cards and the overview graph into the file-level layered view, clicking any node to inspect code in fullscreen if needed. On the Agent side, the project_kgraph tool returns the same cached full-graph JSON for follow-up Q&A or refactoring analysis. Whether you are onboarding to a new project, walking a team through its architecture, or letting an Agent drive optimization, kgraph-plugin has a natural place in your workflow.