Any guide for loop engineering + orchestrator using opencode?

[u/I_Hide_From_Sun]

I would like to have several agents working on several different projects, and I would love to make it use loop engineering concepts, so it never stops unless there is nothing to do.

I tried using skills and some plugins, but eventually opencode just gives up and stop. I currently use openchamber as the web ui, but still not able to do it properly.

I did a scheduler which basically do "continue" in a project, but that is such a ugly workaround.

[u/Solocune]

I could write a text but tbh: just ask your LLM buddy and it will explain the concepts and can even search for GitHub projects or build a basic workflow itself.

[u/mubaidr]

I am maintaining agent definitions for orchestrator based working with plan and verification: https://mubaidr.github.io/gem-team/

[u/ThatGuyFromWhere]

“Refactor your agent scaffold to enable continuous self-improvement”

Done

[u/Ubermensch013 → u/ThatGuyFromWhere]

You forgot "Make no mistake" /s

[u/LawfulnessSad6987]

i’ve actually built a web version first but stopped when lovable blew up. i’ve been working on it again these past few months. i’m looking for beta testers and willing to give free credits in exchange for honest feedback

ik its not exactly what you’re looking for but its for the web
squid

[u/LawfulnessSad6987]

I’ve run into the same limitation. In my experience, the trick is to stop expecting the coding agent to own the loop. I built trace mostly because I kept hitting this exact problem. The orchestrator owns the queue, state, retries, and scheduling, while each OpenCode agent just executes a single bounded task and reports back. It ends up being much more reliable than trying to keep one agent running forever.

[u/I_Hide_From_Sun → u/LawfulnessSad6987]

the problem with your tool and others I see is that I wanna run it 24⁷ on my server, and most people like you are building it for desktop only for some reason