Roo code shuts down, Team will focus on roomote agent

twitter.com

28 pointsbuster2 comments

The risk of forking an actively maintained OSS repo for commercial purposes is that you have to compete with the source repo and in this particular industry where business moats are weak/nonexistent, it's tough to differentiate.

That said, pivoting to a cloud-hosted agent might be even more difficult to differentiate.

It's a bit odd, since RooCode was genuinely great (those various agent modes, vs just plan/act).

At the same time, something like KiloCode (which is a further fork) seems to be doing well at the project level!

Then again, I almost expected this to hit the front page of HN but it wasn't even close, despite it being one of the better AI plugins for VSC (I didn't really use it in any other way).

Reply on news.ycombinator.com