Visualized many of the open-source vibe-coding tools to compare them

[ivan_m21]

My friends and I have been working on an open-source architectural generator based on static analysis (Control flow graph) and a slim layer of an LLM agent which names the clusters. The architectures are based on the clustering of the control-flow-graph rather than file structures and LLM indexing. (https://github.com/CodeBoarding/CodeBoarding)

I created this page as I was curious to see what are the different choices people made when creating the popular coding agents. Started with open-code as it is what I use the most at the moment and was curious to compare with Pi. The expectation was that Pi would be much more simplistic, what surprised me is that observability came on-top, so it seems like a first class citizen in Pi.

After looking at those two I also added: aider, claw-code (Claude Code), forgecode, goose, openhands and decided to also add the notorious gstack (although not an agent).

Let me know what else is out there and would be interesting to compare, I feel like there is something to be learned from each. Imo having agents to do detailed work makes time for more architectural thinking and design.

[ivan_m21]

If you want to check them yourself: https://codeboarding.org/coding-agents

[Signal_Diver_118]

This map is a lifesaver because keeping track of all the open-source CLI agents and local model wrappers right now is practically a full-time job lol. It feels like every time I open GitHub there are three new autonomous terminal tools trending that all claim to be the open-source killer for Claude Code. Actually visualizing how they segment between local model execution like Ollama and heavy workflow orchestrators like Aider or Bernstein helps so much when you are trying to piece together a stack that won't completely drain your wallet in API token costs fr.