This exists though. Cline, Aider, Cursor, etc. all hook into the diagnostics of the IDE and can run arbitrary commands (including compilers) and feed outouts back to the LLM. Take Cline, it has a planning mode that you can plug a reasoning model into and that will outline the best path to implementation. Then you switch to action mode where a (usually) completion model takes over, implements in multiple steps and validated diagnostics (or compilation output) as it implements the plan.
Correct, same with windsurf, you can ask it to first generate unit tests, then the code, and it will run the test, analyze the results, comment where and why it made mistakes, improve its own code, and repeat the tests until it works.
What I’ve also found very useful in windsurf is to have it analyze existing code bases, you can ask it to generate markdown documentation for specific functionality, including mermaid diagrams.
Also helps to have it first generate design documents, improve the designs until satisfactory, and then have it generate the tests and code accordingly.
I've had cursor suggest changes for debugging (like prints), you do have to copy paste the results though.
I've also had cursor generate a CURL request to test an endpoint and determine what responses it had so it could generate a struct to store the result.
