You vibe-code three projects a day with Claude Code. Fast, fluid, shipping. Then two weeks in, you open that codebase and hit a wall: which instructions are still active, which got silently overridden, and what does this function actually do now?
Yesterday, a developer named Nir shipped claude-watch, an open source graphical semantic visualization layer built for exactly this problem. It analyzes your project in a nested, zoomable structure so you can drill into specific logic flows and see exactly what Claude built inside.
The twist is not the visualization. It is the AI search layer baked on top. Ask a natural language question about your project and it surfaces every relevant piece of logic across the entire codebase. Semantic understanding, not keyword matching. “Where does the auth flow start?” Get an answer.
How to use it:
- 🔍 Clone the repo at github.com/NirDiamant/claude-watch
- Point it at your project directory
- Let it generate the visual graph of your codebase
- Zoom into complex logic areas to audit what is actually there
- 💬 Use AI search to ask specific questions about behavior, flows, and edge cases
Pro tip: Run this after every major Claude Code session before moving to the next project. Treat it as a five-minute checkpoint that keeps you oriented in your own work. It is especially useful when you hand a project back to Claude after a break and need to re-anchor the context.
If you are building with AI assistants daily, visibility into what actually got built is the layer that has been missing. ⭐ Star the repo now so you have it ready when things get complex.
Claude Code writes your code, but do you actually know what’s in it? I built a tool for that
by u/Nir777 in ChatGPTPromptGenius