Visualize your LLM workflows as interactive & shareable graphs. Point Codag at your codebase ā it maps every LLM call, branch, and data flow. Click any node to jump to source. Live updates as you code. Self-hosted, open source.
Intercom ā Startups get 90% off Intercom + 1 year of Fin AI Agent free
Startups get 90% off Intercom + 1 year of Fin AI Agent free
Promoted
Maker
š
Hey ProductHunt!
I'm Michael, Founder of Codag, prev @Shopify and @Okta. I've been building startups for the past couple months and and I keep running into the same problem.
I built Codag because I couldn't keep up with my own AI code anymore.
The problem: You vibe code an agentic workflow with Cursor or Claude. It works. But now there's 5 files, 3 LLM calls, branching logic everywhere. Your teammate asks "how does it work?" and you're like... let me ask my agent...
Other workflow tools need you to instrument your code, deploy it, send traces to their cloud. That's fine for prod monitoring, but terrible for understanding code you just wrote, and horrendous if you need to migrate to use someone else's infrastructure š±š±š±
Codag is different: ā Point it at your repo ā that's it ā Instant workflow graph from static & LLM analysis ā Live updates as you edit (tree-sitter + AST diffing) ā Click node ā jump to source ā Export PNG to share in PRs, docs, Slack
No SDK. No traces. No cloud. Just your code.
Works with OpenAI, Anthropic, Gemini, LangChain, CrewAI, Mastra, and 20+ more providers/frameworks.
Fully open source (MIT) and free, host the backend yourself! Would love feedback ā what should we build next?
Report
Let me ask why agent problem is so relatable. Iāve been there too with complex agentic workflow that became impossible to explain to teammates. Love that itās local and you donāt need to add any dependencies.
How does Codag handle workflows that span multiple repos or include external API calls? Does graph visualization captures those dependencies too?
Congrats on the launch!
Report
Maker
@ruhao_lou1Ā Hi! Thanks for the thoughtful question. Similarly with @seoyunyang31's question, external API calls will be captured if its within the providers we use, and you'll see it on the visualization as such. If you want to capture the whole workflow, you'll have to analyze all the directories/repos together (we support that!).
This is really cool! Gonna try it on my codebase soon! Good luck with the launch @michaelzixizhou !
Report
Maker
@miro_kĀ Thanks Myro! Still got Orchestra installed, beautiful app. I'm sure the visualization would be stunning too.
Report
Hi Michael! This looks very cool. I was wondering if this also works for polyrepo? If not, are you planning to expand its coverage?
Report
Maker
@seoyunyang31Ā Thanks! Codag can visualize the connection to repos outside of your current one, as long as you're using APIs to communicate! But if you want to visualize the whole polyrepo you're going to have to up one parent directory to include all of them.
Hey ProductHunt!
I'm Michael, Founder of Codag, prev @Shopify and @Okta. I've been building startups for the past couple months and and I keep running into the same problem.
I built Codag because I couldn't keep up with my own AI code anymore.
The problem: You vibe code an agentic workflow with Cursor or Claude. It works. But now there's 5 files, 3 LLM calls, branching logic everywhere. Your teammate asks "how does it work?" and you're like... let me ask my agent...
Other workflow tools need you to instrument your code, deploy it, send traces to their cloud. That's fine for prod monitoring, but terrible for understanding code you just wrote, and horrendous if you need to migrate to use someone else's infrastructure š±š±š±
Codag is different:
ā Point it at your repo ā that's it
ā Instant workflow graph from static & LLM analysis
ā Live updates as you edit (tree-sitter + AST diffing)
ā Click node ā jump to source
ā Export PNG to share in PRs, docs, Slack
No SDK. No traces. No cloud. Just your code.
Works with OpenAI, Anthropic, Gemini, LangChain, CrewAI, Mastra, and 20+ more providers/frameworks.
Fully open source (MIT) and free, host the backend yourself! Would love feedback ā what should we build next?
@ruhao_lou1Ā Hi! Thanks for the thoughtful question. Similarly with @seoyunyang31's question, external API calls will be captured if its within the providers we use, and you'll see it on the visualization as such. If you want to capture the whole workflow, you'll have to analyze all the directories/repos together (we support that!).
Orchestra
This is really cool! Gonna try it on my codebase soon!
Good luck with the launch @michaelzixizhou !
@miro_kĀ Thanks Myro! Still got Orchestra installed, beautiful app. I'm sure the visualization would be stunning too.
Hi Michael! This looks very cool. I was wondering if this also works for polyrepo? If not, are you planning to expand its coverage?
@seoyunyang31Ā Thanks! Codag can visualize the connection to repos outside of your current one, as long as you're using APIs to communicate! But if you want to visualize the whole polyrepo you're going to have to up one parent directory to include all of them.