Model -> brain cells' conections
Harness -> everything else
I've been working with different setups in parallel for months (openclaw, pi, cursor per project harnesses and codex) and, even though using the same model most of the time, I can clearly see how the behave in very different ways deppending on the setup.
As a language model, language is our way to communicate and build everything around the models, which makes my younger self (who loved writing stories) very very happy :)
This honestly applies to current society, not just work.
Even the fun bits of life have been infected with the "speed" thing. We want things, and we want them NOW!
But movements like this come and go, what actually stays are the real things, the ones made with time, passion and love. The rest is just waiting to be forever forgotten.
Just recently started playing with the idea of an agent that has multiple agents as subordinates. My main agent has the context of the system, controls api keys, tokens, etc. and has a high level overview of each project. Then I have an agent per project and some general "experts" (such as db expert, devops expert, etc.). My main agent (the captain) takes my inputs and then splits the tasks and reports back when the subagents have done the work.
I wonder if this idea of having a queue may or may not benefit someone with my setup (running on openclaw).
Have you tried this kind of setup yourself and, if so, what are the benefits of using a queue system?
I've been working with different setups in parallel for months (openclaw, pi, cursor per project harnesses and codex) and, even though using the same model most of the time, I can clearly see how the behave in very different ways deppending on the setup.
As a language model, language is our way to communicate and build everything around the models, which makes my younger self (who loved writing stories) very very happy :)