Reminds me a lot of omnigent (which I am a huge fan of) with a persistent memory layer. Unlike omnigent's subagent threads, the DAG it uses to coordinate other harnesses doesn't look to be durable; I am curious as to whether this is by design or is a forthcoming feature, as this essentially makes or breaks my use case of long-running project-sized implementation sessions.<p>In any event, it's great to see competition in this meta-harness space, which is likely one that none of the frontier labs will touch since it, by definition, would utilize their competitors' products.
RSI here is for "recursive self-improvement", instead of a harness being built to help users with repetitive strain injury like I first thought when reading the post title
A very popular yoga kata called <i>sun salutations</i> (available in various versions depending on your fitness/advancement level) helped me get rid of wrist and thumb RSI. It stretches and gently stresses these load bearing ;) joints, thus strengthening them.<p>Hope this helps the last few folk before searching for RSI will be impossible due to the term being taken over.<p>For those afraid of Satanism in yoga, there's also non satanic variants where you don't greet each other saying <i>Namaste</i> or say <i>Shanti</i> anywhere during the practice.
We gotta do something about these clashing TLAs.
A register is the obvious choice, but of course then you get a gold rush and people squatting on XPZ and stuff without even having invented an opaque term behind it.
Perhaps modelling acronyms in TLA+ will help?
This looks similar to <a href="https://paseo.sh/" rel="nofollow">https://paseo.sh/</a>, if I understand correctly. I’ve recently tried it and liked it a lot. Would be nice to see a comparison. When’s the harness of harnesses of harnesses coming?
I'm using paseo heavily too. The main differences here seem to be around how opinionated Raven's orchestration is. They're providing agents, workflows, memory, skills, etc. Paseo gives you some orchestration tools but it's mostly letting the 'native' harnesses do the work. For my workflow, I'm interested in some of what they're doing here but I'm not in buying into their whole system (markdown for memory and calling it RSI, as someone else called out, is not doing it for me). The follow up actions and meta-harness tuning look pretty cool.<p>They also don't ship an app which is one of the best parts of paseo. Then again Paseo's perf leaves a lot to be desired.
Interesting. Only thing, from someone who has built something similar, is that it moght tend to duplicate certain capabilities that those harnesses handle on their own. Some overlap is bound to happen.
This, and also they have to chase changes in model tuning and capabilities. I have a nice little meta-harness focused on product development (requiremwnts, acceptance criteria) for Claude code, and when major new models come it it’s weeks before I can find and fix constraints that are no longer necessary + constraints that have become necessary.
I wish they had also compared it to omp and dsh, I’m curious how it stacks up
Recursion has started. Here we go!
Agents editing their prompts and writing memory to markdown files is not and will never be RSI.
[dead]