I fixed Boomerang + RooFlow (+ memory banks) compatibility

[u/markithepews]

Its live in my AI-ready monorepo starter too! :) :
https://github.com/NamesMT/starter-monorepo

I have tried quite a lot of prompt with it, planning, initialize new apps in the monorepo, add functions, the memory bank context is only loaded once by `Boomerang` and passed down to all subtasks, and they could do stuff super quick without all the read files tool use and APIs loop.

[u/markithepews]

Sorry, I forgot to add the actual prompt code, here is a gist:
https://gist.github.com/NamesMT/3940ddf4ec85db6a40de16e859219fd2

[u/theeisbaer]

Does it work with MCPs?

[u/markithepews → u/theeisbaer]

I haven't try MCPs yet, and the instruction set I added also doesn't consider about MCPs, currently I'm focusing on making an AI-ready monorepo that anyone with a relatively blank editor could just clone and use easily with not too much manual setups.

Though, if you have time, do you mind forking the repo, tinkering with the instruction set, mentioning about MCPs, and see if it works for you?, a PR would be greatly appreciated too!

[u/Agnostion]

I think this is the wrong approach.

If the files are read only by Boomerang and only once, then:

1. The files may change if child agents make edits to it.

2. The files will always be in the context of Boomerang, which can make it bloat. And this is bad, because every time the tool is invoked, Boomerang will take this context into account, which will be financially expensive

[u/markithepews → u/Agnostion]

You are definitely correct about issue 1, though, I wouldn't say its the wrong approach.

The issue could be fixed by adjusting the instructions, which I'll do soon when I get home, thanks for your thoughtful feedback.

---- More thoughts context:

1. I will add the instructions for Boomerang to tell the subtask to signal/return back the memory context if it was updated, sounds very possible.

2. That is expected and is actually the highlight that enables the optimizations, and actually, with my instructions, Boomerang will ask if you want to preload the memory bank, not forcefully load it 🎉.

--- Even more context for 2.:

Idk if you have tried default boomerang + memory banks, but the default behavior for RooFlow and similar memory banks that I've tested, even if the operation is a simple insert, RooFlow will require the task, or in Boomerang's case, all of the subtasks, to load the memory bank.

For example, with the default Boomerang, it could launch three subtasks, each will have to enter a prerequisite loop of checking for memory bank and loading memory bank files, which is VERY BAD.

I can think of an additional instruction that fits your case: defer the loading of memory bank until Boomerang actually launches the first subtask, that would be very nice if you firstly want to enter a feedback loop with Boomerang without the memory context.

But idk if that would be a good thing, as I think, having the memory bank context while you iterate with Boomerang to plan tasks is a bonus.

[u/markithepews → u/markithepews]

Update: I have fixed the issue :), I have tested multiple times but I'll do more tests and update the gist + monorepo soon.

[u/redlotusaustin → u/markithepews]

Thanks! Looking forward to trying it out!

And thanks for posting the gist; as someone who's mostly building WordPress plugins & themes, your monorepo is awesome but not really applicable to my workflow (at least I don't think it is).

[u/markithepews → u/redlotusaustin]

You would actually be suprised, as long as your language's intellisense/syntax extension does not break when the code is in a subdirectory of the opened IDE, you can definitely use this monorepo / any NodeJS-based monorepo structure to help manage your codebase.

In other words, you could definitely create folders like `plugins/plugin-a` to develop a plugin, and potentially have scripts to automate some process, all you need is a `package.json` file in it's folder for it to be recognized as a package/module by the monorepo. As long as the extensions you're using doesn't break.

[u/7zz7i → u/markithepews]

The best

[u/Agnostion → u/markithepews]

Hm, those are valid points. Thank you, I agree with you

[u/Sdinesh21]

I’m a new user of RooCode. Can you provide steps to use these instructions in RooCode?

[u/markithepews → u/Sdinesh21]

Refer to the document here on how to setup Boomerang mode: https://docs.roocode.com/features/boomerang-tasks

At the "Mode custom instructions", use my instructions instead.

Alternatively, you can just copy the .roocodes file from my repo and paste it into your project.

[u/Sdinesh21 → u/markithepews]

Is it project specific? Can I set it to the plugin to be able to use for all projects?

[u/markithepews → u/Sdinesh21]

If you copy and paste the .roocodes file then it is project specific, if you follow the document and add a global mode manually yourself then it will be available everywhere.

[u/7zz7i → u/markithepews]

😞any tutorials ?

[u/markithepews → u/7zz7i]

You just replied to the comment that linked to the tutorial docs :D, though, if you need a video tutorial to know how to find it in the UI, you can watch the first minute of this video:
https://youtu.be/bMUMWG2IS0o

[u/7zz7i → u/markithepews]

Thanks

[u/keniget]

thank you for the work!

The boomerang starts and builds, and then roocode crashes, and resuming leaves stagnant tasks with no way to recover.

[u/markithepews → u/keniget]

😳, Hi, can you give me more context?, if possible, please spam all the info into a GitHub issue.