boleary-gl
Joined 9 years ago
Joined 9 years ago
The answer is discoverability. which is pretty critical for any business
What makes it different:
- 500+ models (including everyone’s favorites from Claude, Gemini, OpenAI). Switch anytime - 5 specialized modes: Code, Ask, Debug, Architect, and Orchestrator (breaks down tasks and delegates to the others) - Parallel agents: spin up multiple instances on the same repo, each on its own branch - Session continuity: start in CLI, pick up in Kilo VS Code or cloud. Context travels with you
--parallel --auto for running multiple autonomous agents simultaneously is a favorite. It’s the same engine as our IDE extensions, not a stripped-down version.
Install: npm install -g @kilocode/cli
Also: open source, and contributions are welcome. Would love feedback on what's missing from your terminal workflow.
Does it take effort to work with them and get them to be effective in your code base? Yes. But is there a way to lead them in such a way that your "team" (you in this case) gets more done? Yes.
But it does take effort. That's why I love "vibe engineering" as a term because the engineering (or "senior" or "lead" engineering) is STILL what we are doing.
I would love to know if and how you disagree. I am (I thought obviously) making a jump here from her desire to make FLOW-MATIC human-readable. Also, I don't believe that AI will take developers's jobs, but I do believe a developer using AI will replace ones not using it...so I'm intentionally provocative there, yes.
This will be another abstraction layer that MANY people will use and be able to accomplish things that would have been impossible to do in a reasonable amount of time in machine code.