CodeGraphyVisualize relationships Core · TypeScript/JavaScript Plugin · Python Plugin · C# Plugin · GDScript Plugin · MCP · Plugin API CodeGraphy turns repository structure and code relationships into a Relationship Graph inside VS Code. Files start as File Nodes, indexing projects richer Edges into the graph, and the whole repo becomes something you can inspect, filter, and navigate instead of infer. The same Relationship Graph can be used as local agent context through the
Now with Material Icon Theme!
CodeGraphy HistoryI originally came up with CodeGraphy back in college in 2021 after seeing The first iteration was https://github.com/joesobo/CodeGraphy. Its pretty rough, but the core idea is there. V2 was the last published version: https://github.com/joesobo/CodeGraphyV2. This version was a huge upgrade, enabling dynamic physics and a ton more features. But it was largely limited to Javascript So I started working on V3 https://github.com/joesobo/CodeGraphyV3 this time with a broader scope. Instead of limited ourselves to a single language. The goal was to make the core renderer reusable and let plugins teach it new language semantics when needed. Unfortunately I got quite busy and never was able to maintain V2 or finish V3. CodeGraphy V4 is a ground-up for the 4th time. Probably wont be the last time either. This time its been primarily programmed via Codex. Ive followed the same concepts as the previous iterations of CodeGraphy compacted in this monorepo, as a means to test out agentic programming and different methodologies of doing so. This is not a serious project, I am doing this to learn. The project should work but I make no promises. Feel free to fork or look at any of the previous versions if you are interested in the project. Or hell submit an issue or PR. MonorepoCodeGraphy V4 is a pnpm monorepo with one Core Extension, one agent access package, one public Plugin API, optional language plugins, and repo-owned quality tooling. The Core Extension is the source of truth for graph behavior. It discovers files, runs built-in Tree-sitter Analysis and plugin analysis, writes the Graph Cache, projects the Relationship Graph, renders the Graph View, and executes Graph Query requests. The MCP package is the agent access layer. It does not index or parse code by itself; it opens or focuses the repo in VS Code, asks the Core Extension to run Indexing, and forwards Graph Query requests to the active Core Extension window. The optional language plugins add ecosystem-specific filters or enrichment on top of the Core Extension baseline. Markdown ships built in, while TypeScript/JavaScript, C#, Python, and GDScript/Godot are packaged as installable examples of the plugin surface. The quality tooling package owns the local architecture checks used by this repo: organize analysis, boundary checks, reachability, CRAP, scoped mutation, and SCRAP test-shape review. Package Map
The MCP package is an agent companion, not a second indexer. The Core Extension owns Indexing, Graph Cache access, plugin wiring, and Graph Query execution. The MCP server opens/focuses the repo, forwards Indexing and Graph Query requests to the Core Extension, and returns the response to the agent. Core Stack
What you getRelationship Graph Open any project and CodeGraphy shows discovered File Nodes immediately. Index the repo to project richer Edges into the same Graph View. Drag nodes, zoom, search, and filter without switching to a separate built-in view. Core pipeline, plugins for enrichment The Core Extension owns discovery, caching, Graph Projection, repo-local settings, and export flow. Built-in and external Plugins contribute per-file analysis results, richer Relationships, extra Node Types and Edge Types, and UI integrations. Broad Tree-sitter baseline The core now ships native Tree-sitter coverage for JavaScript, TypeScript, TSX, Python, Go, Haskell, Java, Kotlin, Lua, PHP, Ruby, Rust, Swift, Dart, C#, C, and C++. That means many repos produce useful semantic edges before you install any language plugin at all. Explorer-style theming in core The core extension now vendors One graph, configurable scope Use the Git timeline playback Index your repository history, scrub through commits, and watch the Relationship Graph evolve over time.
Repo-local graph settings and cache CodeGraphy stores its Graph Cache and repo-specific Settings under Agent-readable graph memory Install Configurable graph presentation Tune the physics, switch between 2D and 3D, adjust node sizes, color node and edge types, assign glob-based legend rules, and filter out noise. Exports from cached graph data Graph Export the current Visible Graph as JSON/Markdown/image output, and Index Export lightweight symbol JSON from the warmed index without re-scanning the repo.
Actions from the graph Preview, open, rename, delete, favorite, and inspect File Nodes directly from the graph. Single-click previews a File Node, double-click opens it persistently, and non-file nodes can still be selected and focused.
Install
Agent SetupUse this to let an agent open or focus the repo, ask the Core Extension to index when needed, and query the Relationship Graph.
Then start a new agent session and ask something short:
For the full setup flow, Codex config snippets, CLI table, MCP tool table, and verification prompts, see MCP Setup. Legend PrecedenceLegend styling is cumulative and resolves in this order:
Higher layers override lower ones only for the fields they set. DevelopmentWant to build your own language plugin? Start with the Plugin Guide, the plugin lifecycle docs, and Documentation
LicenseMIT |




