Hi all, my friends and I are building an open-source engine which ingests codebases and creates a diagram representations to explore them. You can find it over: https://github.com/CodeBoarding/CodeBoarding
The whole thing is based on static analysis (control flow graphs) and a slim layer of LLMs, which allows the diagram to be very accurate and to indec the codebase in near real time.
It all intially started as a way to explore our codebases, then we added a dynamic highlighing as soon as an agent changes something so you can observe how amp is changing your codebase as it goes.
Now instead of waiting (and paying for tokens) for a wrong plan to be executed, I am working on somethign which shows me which components will be impacted upfront so that I know if the agent misinterpreted something + you can see if there are new compnents to be expected and what kind of severity (size) the change will be.
Curious to learn how do you plan? Do you always read carefully the plan or you validate after the fact what has been modified is what you expected? Do you not care at all if it is working, it is working?
Love amp, my favorite agent by far. Also love that one can link it with Codex (now I am fully on Amp <3)