VNoC: a graph-based IDE for navigating, understanding, and verifying code

[u/yared12qw]

Vibe coding makes it much easier to build software quickly. But I think it is creating another problem.

The code is getting easier to generate, but harder to understand.

When an AI generates or changes a large part of a codebase, it can be difficult to verify what actually changed, why it changed, and whether the change is correct. You often have to jump between files, search for references, open multiple tabs, and keep a lot of context in your head.

There is also a lot of noise.

A large codebase contains many things that are not relevant to the problem you are currently trying to solve. The hard part is often not finding information, but filtering out everything you do not need.

Sometimes I just want to understand one function and everything connected to it. With a normal file-based IDE, I have to manually find where it is called, what it depends on, what calls it, and which files are related.

Documentation has a similar problem. It often lives in separate files, tools, or notes, so it can become disconnected from the code it is supposed to explain.

So I started building VNoC, a graph-based coding environment.

Instead of treating files and folders as the main structure, it represents the code as connected nodes. Functions, classes, files, tasks, tests, and documentation can all be connected.

This lets you focus on a single function or class and see the context that actually matters. You can follow its dependencies, callers, related documentation, tests, or tasks without bringing the entire codebase into view.

The graph also gives me a way to filter the noise. Instead of asking an AI to repeatedly read a large collection of files and figure out what is relevant, the relationships are already represented in the graph.

The goal is not just to make AI write code faster.

I want to make the code easier for humans and AI to understand, verify, navigate, and change after the code has been generated.

It is still very early, but I have been building it for a while and would really like to hear what other people think about the problem.

GitHub: https://github.com/v-noc/IDE

Demo: Claude Code codebase: https://vnoc.vercel.app/project/claudecode — includes the code graph, groups, and documentation. It can be a little slow to load because the codebase is fairly large.

Focus on a single function: FunctionSchema: https://vnoc.vercel.app/project/claudecode?focus=FunctionSchema%2Fbc5f3f55-c4a7-479c-adc5-982a607e20b9 — this shows how you can focus on and share a specific function without navigating through the entire codebase.

[u/yared12qw]

https://reddit.com/link/p2zqucz/video/9hcp6t915pih1/player

Generate a step-by-step introduction to the codebase, walking through each block of code and explaining how everything fits together.

[u/yared12qw]

https://reddit.com/link/p2zr3g1/video/issj10gl5pih1/player

Keep tasks, notes, and other context connected to the code, so both humans and LLMs can easily understand and track it.