Comment by kristopolous
9 hours ago
It seems wildly trivial. Chat completion loop with toolcalling over a universal chat gateway.
What's the innovation here? Local model? That was always possible. Toolcalling? Been around a couple years now...
It's like 5 minutes of vibe coding at most. There's likely 1,000s of similar projects already on GitHub
And when you can use claude-code from basically any device (termux on phone via ssh), Why even bother?
I had 3 friends ping me yesterday to tell me how this is going to eat their job....
but i don't see how this is different from claude-code + some chat interface + mcp servers
> termux on phone via ssh
I agree, but it also rhymes a lot with the infamous “why use Dropbox when you can just use rsync” comment. Convenience can be a game changer.
Not exactly. This isn't substantive work. Do we really need to find a bunch of identical projects on GitHub?
This is the kind of project I saw at hackathons in 2023 by teams that didn't win anything
The whole world is about bundling (and unbundling).
Not saying it really is useful, but there are values bundling an easier interface to CC with battery included.
When someone is pushing 500 commits a day, i don't think they have time to review any code, and it was likely written in full YOLO mode.
So it's not just batteries-included, it's probably 100-vulnerabilities-included as well
3 replies →
> Why even bother?
Claude-code is closed-source. That is a good enough reason to look at alternatives.