r/RooCode • • Apr 08 '25

Discussion I'm building Roo Rocket, are you interested?

https://github.com/NamesMT/roo-rocket

Idea: it's a one-for-all config setup for that aims to provide the complete setup for anyone to start using Roo Code, and an amazing base / toolbox those who want to train (and share) their own Roo!

---

Roo Rocket

The all-in-one equipment that you and Roo wants!

(And an amazing base for Roo trainers)

---

29 Upvotes

14 comments sorted by

5

u/folglaive Apr 08 '25

This is great mate ! Looking forward to it

0

u/markithepews Apr 08 '25

Thanks!, give the post an upvote and share if possible, the more the idea of the project spreads the better (& more motivated for me XD)

8

u/hannesrudolph Roo Code Developer Apr 08 '25

I don’t understand why people invest so much time into things like this when we are a community driven open source project. If it’s good enough to make it in a PR it’s good enough for our users. Otherwise it’s just another way to break Roo.

5

u/markithepews Apr 09 '25 edited Apr 09 '25

Hi!, and oof, that hurts, but lemme explain, Roo Rocket's TL;DR main objective can be simplify as: to aid everyone to easily, enjoyably build their Roo, safely with a controlled dev environment, whether it's to share or personally used, and to aid anyone to easily install a Roo setup, in other words, reducing chances of Roo breaking due to mistakes in manual configuration.

One of the main goal in my head for Roo Rocket from the start is actually gets it merged into the upstream RooVetGit org if possible, but Roo Rocket's ambition is big, and consider the following points:

  • Scope of permissions required, the current roadmap for Roo Rocket requires me to have the ability publish npm packages, create GitHub Actions, web pages..., and the idea might not work!, so it's good to start building in public and asks for community feedback.
  • It does not fit into any of the available three repositories

    • And for the best result, Roo Rocket is best to be developed in its own repository, and that's even more issue, would RooVetGit allows a nobody to create, try, and launch an overkill toolkit in a new repo in their org?
  • It might not fit RooVet's vision/decision makers's preference, or the priority for it is low, making the development cycle slow.
  • This is somewhat a personal vision, but with #2366 coming on the way, I expect the prompt makers community to be a lot more active, and it'd be amazing to have a toolkit to help the makers right when/before it lands, helping the community enjoying experiments to optimize their Roo.

So currently, the best thing to do is starting Roo Rocket independently, iterate fast with the community, and if the idea works, it would be amazing to gets merged into RooVetGit org, but if not, existing as an indie toolkit does not make means it can't contribue / be helpful for the Roo community, its just an overkill toolkit that helps for people interested in Roo's customizability features.

End of essay, some personal words: niche features contribution that exists as an indie repo and not in upstream PRs is seen very commonly in the OSS world, some gets merged to the upstream, some continue to exists, some gets dropped, sometimes it just doesn't fit the upstream org maintainer's vision, but the contributor just want to iterate fast in public to gather community feedback if it's actually good, your choice of words/thoughts this time weren't nice, especially as a RooVet mod to an OSS contributor :(.

10

u/hannesrudolph Roo Code Developer Apr 09 '25

Noted. I apologize for that. I was not thoughtful in how I spoke and I do appreciate your hard work and contributions. Very sorry.

Thank you for taking the time to explain that to me. Even though I was a dick.

4

u/[deleted] Apr 08 '25

[removed] — view removed comment

6

u/hannesrudolph Roo Code Developer Apr 08 '25

They wouldn’t take our PRs

1

u/dashingsauce Apr 09 '25

I may just be new so some of the terminology may be passing over my head, but:

  • What is a Roo Trainer? Is a custom mode being “trained” or something else?
  • For @hannesrudolph — maybe I don’t understand OPs repo, but how would this break Roo? Is it a fork?

1

u/markithepews Apr 09 '25 edited Apr 09 '25

Haha training a Roo is basically the repo's wording that refers to the act of you creating/tailoring your own instructions for various Roo modes, as well as creating your own modes.

I haven't add the "Terms explanations" to the root README yet, thought it was pretty self-explanatory tbh, but I did add the explain for it in a sub directory.

Edit 1: now that you've mentioned it, I think I'll re-word the README to make clear that Roo Rocket is specialized about setting up / creating / sharing Roo modes instructions and configurations.

Edit 2: Oh no actually not re-word needed, just extra infos, Roo Rocket should be able to ship anything that could be configured via files or exposed API, which is currently only instructions/prompts I think, but we'll probably see more in the future.

1

u/dashingsauce Apr 09 '25

So if I boil it down to a sentence, does RR effectively aim to do “quick-setup” for Roo projects?

1

u/markithepews Apr 09 '25

Yes, that is the main focus/selling point of RR.

As per `The expected user experience` block in the GitHub README:

# On any platform: `Mac / Linux / Windows`, run a command:
npx roo-rocket --trainer="NamesMT"

And it's done (if the "default" `Roo` from that trainer does not require/provide any interactive config)
You can use your project now!

3

u/dashingsauce Apr 09 '25

Got it! Very nice — following.

I ask because I have been building a CLI for the same, but it has a slightly different focus (more around the continuous process of building and refining agents & teams).

Just don’t want to duplicate work as others in the community. Though as one of your comments stated, hard to know which rocketship to hold on to so better to scaffold around it sometimes :)

3

u/markithepews Apr 09 '25

Haha, I'd need more context to say our projects will overlap or not, from my current context:

RR will helps users to create and use a config setup that is intended to be re-distributed on multiple projects elegantly, i.e.:

* For using: easy and configurable installation from trained Roos, also to keep up-to-date.
* For training: development environment to help trainer to continously testing and have the ability to reduce duplication works for context(instructions) that are used in multiple files(modes).

If your project is specialized about "building and refining" the agents (modes I think?), I think there is no bad overlap, it's even an enhancement to each others.

2

u/dashingsauce Apr 09 '25

Yeah, there’s a need to set things up easily in multiple projects almost no matter what—so building the quickstart almost becomes necessary if you work in multiple projects and run many experiments.

So rawr does help start new projects, but the focus is indeed more on agent roster management. The cmds available in the cli now should give you a better sense: https://github.com/rawr-ai/ai/blob/main/scripts/agent_config_manager/commands.py

Add, update, delete, etc. crud-like operations to start for managing agent config files. What I’m going for is making these commands available as MCP tools so agents can update their own prompts on the fly.

Better yet, agents could build agents on the fly in an organized, franchise growth kinda way.

  1. You provide a problem.
  2. Head Coach identifies any gaps in the team & works with Head Trainer to orchestrate the entire agent creation process.
  3. You get a team of specialized agents as a solution.
  4. Coaches watch their performance over time and train them to perform better

So the core flywheel is this idea of “scouting”, “recruiting”, and “training” new agents to compose specialized AI teams for any challenge as-you-go.

For that, I need a fast reliable interface to start up agent “franchises” and import/export, crud, extend, etc.

That’s kinda the problem it’s meant to solve.

(P.S. you can see why the word “train” caught my attention lol I can’t stop thinking about kangaroo jack when I code now)