u/ivan_m21

Hi everyone, I am new to cline. I have been switiching tools around, CC/Codex/Amp/Kiro-CLI/OpenCode.

And along my way, I noticed that it is hard to track what the heck is my agent doing with the codebase. It feels like I cannot keep up either way so I give up and cave in to the blindness.

My friends and I were working on an onboarding tool and later on realized that it can be used to track the blast radius of agent changes. We believe for such thing to be useful it has to be super accurate (otherwise it is just slop over slop) and so made it based on static analysis and CFGs.

It is opensource as well: https://github.com/CodeBoarding/CodeBoarding

I would love to hear what you guys are thinking of it and how would it fit into your cline workflow, do you use something else to manage the overwhelming amount and size of changes introduced by agents?

I think Windsurf, ClaudeCode, Codex and so on are amazing, however very hard to track what exactly has been changed without having to look through a 10k line diff on git.

My friends and I started this open-source proejct to visualize software architectures. We found out that we are also curious how big of an effect does each agent change have, this way we can stop Windsurf early as soon as we notice it messed up, without having to read every line (saving also on tokens and time).

Our project is based on static analysis alongside LLMS and you can find it on github:
https://github.com/CodeBoarding/CodeBoarding

If you have any suggestions, please open an issue there.

I am also super curious to hear how do you guys know if windsurf messed up, do you always wait till it is fully done, I feel like I don't have the patience anymore :D (neither the tokens...)

Would love to answer questions in the comments and hear how do you guys use windsurf effectively.

I think Antigravity, ClaudeCode, Codex and so on are amazing, however very hard to track what exactly has been changed without having to look through a 10k line diff on git.

My friends and I started this open-source proejct to visualize software architectures. We found out that we are also curious how big of an effect does each agent change have, this way we can stop Antigravity early as soon as we notice it messed up, without having to read every line (saving also on tokens and time).

Our project is based on static analysis alongside LLMS and you can find it on github:
https://github.com/CodeBoarding/CodeBoarding

If you have any suggestions, please open an issue there.

I am also super curious to hear how do you guys know if Antigravity messed up, do you always wait till it is fully done, I feel like I don't have the patience anymore :D (neither the tokens...)

Would love to answer questions in the comments and hear how do you guys use Antigravity effectively.

I love tools like ClaudeCode and Codex, they are amazing. However it is very hard to track what exactly has been changed without having to look through a 10k line diff on git.

My friends and I started this open-source proejct to visualize software architectures. We found out that we are also curious how big of an effect does each agent change have, this way we can stop ClaudeCode early as soon as we notice it messed up, without having to read every line (saving also on tokens and time).

Our project is based on static analysis alongside LLMS and you can find it on github:
https://github.com/CodeBoarding/CodeBoarding

If you have any suggestions, please open an issue there.

I am also super curious to hear how do you guys know if Claude Code messed up, do you always wait till it is fully done, I feel like I don't have the patience anymore :D (neither the tokens...).

Also would love to answer any questions in the comments!

I have found tools like Codex and CC amazing, however very hard to track what exactly has been changed without having to look through a 10k line diff on git.

My friends and I started this open-source proejct to visualize software architectures. We found out that we are also curious how big of an effect does each agent change have, this way we can stop codex early as soon as we notice it messed up, without having to read every line (saving also on tokens and time).

Our project is based on static analysis alongside LLMS and you can find it on github:
https://github.com/CodeBoarding/CodeBoarding

If you have any suggestions, please open an issue there.

I am also super curious to hear how do you guys know if codex messed up, do you always wait till it is fully done, I feel like I don't have the patience anymore :D.

Also would love to answer any questions in the comments!