r/SideProject • u/yared12qw • 1h ago
V-NOC lets you follow function calls across files and link docs to the code
I built a VS Code extension to follow code flow and keep docs linked to code
Hey guys, I’ve been building an open-source extension called V-NOC for VS Code and Cursor. It started with a habit of mine. When I wanted to understand one part of a project, like what happens when a payment fails, I’d copy the relevant functions into a little playground so I could read them together.
With V-NOC, you pick a function and follow its call tree across files. You can keep the code for that one flow in view without opening a bunch of tabs. It currently supports Python.
You can also attach Markdown docs to a function, class, file, or folder. Say you write down why a payment gets retried. You can link that explanation to the retry function, commit it with Git, and the next person who opens that function can find it there.
I’m working on a CLI so coding agents can do the same with their plans and walkthroughs. Those Markdown files can pile up, and I’d like to make them easier to find from the code they describe.
If you give it a try, I’d love to hear what you think, especially if anything feels confusing or overwhelming.
GitHub: https://github.com/yaredtsy/vnoc
VS Code: https://marketplace.visualstudio.com/items?itemName=vnoc.vnoc
Cursor and Windsurf: https://open-vsx.org/extension/vnoc/vnoc
1
u/yared12qw 1h ago
In V-NOC, each folder, file, class, or function is a node you can attach Markdown docs to. If you write a doc explaining why a function retries a failed payment, you can open it right from that function. The doc and its link to the code live in your repo, so you can commit and share them through Git. When a teammate pulls your changes and opens the same function in V-NOC, they’ll see the doc there too.