4 ms·
Looks polished but I must ask - what's the point? Why build another coding agent given the crowded space of coding agents? We have soooo many already. You coul
by mimo25 4mo ago
Looks polished but I must ask - what's the point? Why build another coding agent given the crowded space of coding agents? We have soooo many already. You could spend your time something more innovative.
- mochow13 4mo agoThanks for your feedback! The greatest motivation behind building yet another coding agent it to try two things: - Experimenting with the "new way of working" where I only drive the development instead of actively writing code and creating implementation plans or design docs. But yes, I have been thoroughly reviewing every line of code, design docs, and plans. - Context efficiency. As I have shared in the comment above, Keen takes different approach for context handling. The first one is conservative: don't keep tool i/o beyond a single agent turn. This is why you will see that context window percentage goes down every time you send a new message in Keen. Secondly, MCP server full schemas are never loaded preemptively. In fact, only specific tool's schema in an MCP server is loaded only when needed. This process is driven by Agent Skills. So the bottom line, the reason for building another CLI coding agent is to try out some ideas and experimenting with them, and also to build something substantial from scratch using agents.