I ve been vibe-coding tools to automate chunks of my consulting work, fell down a rabbit hole, and started building actual products. Suddenly I m in a world of unknown-unknowns and known-unknowns. One of the bigger things to solve was understanding code the LLM generated that I didn t fully grasp. What does it touch? What reads and writes where? Is the auth path where I think it is?So I built codeflowmap. Point it at a repo and it maps the dependency and call graph, then surfaces the read / write / auth paths between files and functions.Connect a local model (Ollama) or any OpenAI-compatible API and it annotates each file with what it does and the data it touches. It all runs locally unless you connect to a remote/hosted API, and the output links straight into an Obsidian vault.bunx codeflowmap serve · MIT · built for meKeen for thoughts on what would make it more useful or sharpen it up.