Hey Product Hunt! 👋 I’m Derek, founder of Tonkotsu.
We believe developers need a fundamentally new tool for this moment, not another IDE or CLI. Tonkotsu elevates you as the manager of a team of coding agents: you make the key decisions and delegate the rest. It’s a calm, modern workflow without endless knobs and config, but a lot more leverage.
We’re so excited to share Tonkotsu today with the Product Hunt community 🚀
Ask us anything, give us feedback, or share how your AI-powered development workflow is changing. We’ll be around to chat all day.
Well done on the launch — this is a genuinely interesting project, and the workflow aligns closely with how I approach agentic development myself. I also noticed the SOC 2 audit and the emphasis on keeping everything within the local development environment, which is reassuring.
One question I had relates to data handling during LLM processing: what information, if any, leaves the local machine, and which providers are involved? Are there guarantees that this data is not retained or used for future model training by the underlying LLM vendors?
This is an area I often struggle to fully square from an enterprise adoption perspective, though it feels much less problematic for personal or side projects.
TBH I love the name Tonkotsu! Reading docs is always easier than managing workflows!
This looks great. I've been using Claude Code with a small army of focused agents recently and have been really happy with the results - but having something like this where it can help manage them all is exciting.
I have an old project which is severely deprecated. Interested to see how this would handle a major refactor!
I love the clean GUI approach, but I wonder how much control we actually have over the 'team' through that doc. Is it mostly for giving high-level commands, or can we jump in and micro-manage the specific logic if an agent starts heading in the wrong direction?
Your UI centers on a single doc that plans, delegates, and reviews. How do you translate that doc into enforceable task boundaries (dependencies, ownership, conflict avoidance) so multiple agents can move in parallel without stepping on each other?
It is the first tool that treats AI like a team, not a trick. How do you keep things transparent when agents make decisions?
Great job @derekattonkotsu and @fmerian exiting to test it! I like a new way of linear and confluence, I like this approach!
Congrats on the launch! I get the positioning of this being fundamentally for developers (I am not a dev lol) but keen to try it out and see what results I get!
Doc-as-control panel for coding agents feels right. I’m tired of juggling prompts in five places. How do you keep context clean with a few agents at once? I’ll try it after standup. Free early access helps. Also, the name makes me want ramen.
Am I upvoting because I am craving ramen. yes.
Is this super cool and looking a lot better than antigravity, yes.
Do I have to bring my own API keys? Do you manage that? How is usage billed?
What's the biggest project you have built with this?
Opinionated, primarily designed for professional engineers. You don't start from scratch here, you start from an existing repo. You don't play around with models, it defaults to Sonnet 4.5. You don't chat with agents, you manage them.
Tonkotsu provides a different approach to coding with agents, spec-driven, from prompt engineering to context engineering. Love this direction!
Hey Product Hunt! 👋 I’m Derek, founder of Tonkotsu.
We believe developers need a fundamentally new tool for this moment, not another IDE or CLI. Tonkotsu elevates you as the manager of a team of coding agents: you make the key decisions and delegate the rest. It’s a calm, modern workflow without endless knobs and config, but a lot more leverage.
We’re so excited to share Tonkotsu today with the Product Hunt community 🚀
Ask us anything, give us feedback, or share how your AI-powered development workflow is changing. We’ll be around to chat all day.