kilocode VS llmehelp

Amp Code is also very good, they released about 2 weeks ago their Oracle feature which leverages o3 to do reviews (https://ampcode.com/news/oracle). Amp leans the closer to Claude Code more than other solutions I’ve seen so far, the team there is really leaning into the agentic approach.

I watch the changes on Kilo Code as well (https://github.com/Kilo-Org/kilocode). Their goal is to merge the best from Cline & Roo Code then sprinkle their own improvements on top.

I've been a software developer for over 8 years and recently started using AI to help me code.

The OSS project I'm currently working on (Kilo Code [1]) basically also attracts the same type of people: People with software dev. experience who like to use AI to help them do things they already know, just faster.

They also don't want to be called "vibe coders". A few days ago, I created a question on a subreddit called "ChatGPTCoding" (which you'd expect to be filled with "vibe coders")[2], asking people if they do "vibe coding" or "AI assisted coding".

Surprisingly, almost NOBODY replies that they do "vibe coding". One guy described vibe coding as "using AI while not having a clue what you're doing."

Am I the only one who wants to be using AI to help me code/design/etc., but I don't want to put under the umbrella of a "vibe coder"?

If yes, is there a better phrase to distinguish ourselves from the "vibe" folks out there?

[1] https://github.com/Kilo-Org/kilocode

I learned about your project from your comment on the Windsurf post but wanted to suggest that you plug your URL anytime you plug the project since it can make the difference between someone "adding it to their eventual list" versus "open in new tab, read, enjoy, engage"

https://github.com/Kilo-Org/kilocode#-kilo-code (Apache 2)

It's open source: https://github.com/Kilo-Org/kilocode, so they are giving back.

my screen-query tool does this: https://github.com/kristopolous/llmehelp?tab=readme-ov-file#...

You can install it in a few seconds.

I'm doing something similar over here https://github.com/kristopolous/llmehelp

The latest approach I'm working on is composable semantic routing.

Essentially what I'd like to do is have a way to seamlessly go in between different tools and have things like saved outputs and conversational fragments (not code fragments).

Essentially my current plans are to have routing similar to pipewire, conversation chains similar to git, and URI addressable conversations similar to xpath.

the proper timeline is

cline -> roo -> kilo

There's also things like goose, plandex, and aider.

The real problem is what to do after all those bugs are written by the AI.

That's what my latest effort, https://github.com/kristopolous/llmehelp is trying to address.