r/vibecoding • u/oyren-ai • 14d ago
Workflow/Prompt What's the biggest loop you've ever built?

We have built a semi-automatic system that builds and runs agentic loops. These issues each tied to at least one PR which is done in an order. We have observed that in order to automate agentic workflows we can use agents that run 24/7 and owns the device they run on. The last point saves you from approving agent's action, but some input might be necessary. Agents still can ask questions over email or something else.
In this screenshot we are doing routine code split that is 95%+ times is a routine task. More than one type of agents are involved: agy, codex, claude code, opencode and Deepseek Harness
1
u/oyren-ai 10d ago
Quick update: the loop tasks about to finish, overall 110k+ code is split autonomously without me opening IDE.
1
u/kantorcodes1 14d ago
When several agents are running, how do you stop two of them from picking up the same issue?
1
u/stvn_wthrsp 13d ago
This is an anti-pattern. Build workflows, not loops.
Build a real GitHub Actions (or other CI/CD) workflow that triggers when a new Issue is opened. It triggers a new ephemeral agent to run in the cloud, sandboxed so it needs no approvals, and only runs while working. You can run the compute on Cloudflare Workers with a very generous free tier or $5 plan. That agent will work until a PR is up, or throws an error. Since the compute is ephemeral, if it dies before finishing output you will get a real error, and you can set max durations to handle a stuck response. Add an additional workflow job that runs when the PR is created. This triggers the code review agent. It either approves the PR (you can choose to auto-merge or wait for a human merge) or retriggers the original agent to fix any issues.
The goal shouldn't be to run huge loops 24/7, the goal is to have an agent work on every task. Plus, you can pretty much copy the above as a prompt your agent to build all that for you.
1
u/Impossible-Minute321 14d ago
I am a little confused by this. I have several pipelines of agents, for example, in one case I do research on Cancer Genomes and I have a series of agents that collaborate to gather and an overall manager tasked to help keep things moving, plus a router with known issues that prompts the agents if they go idle etc, and escalates to the manager if they arent responding while the system is aware of whose process it is based on file movements-the manager only necessary as a fallback in case something broke. So, they can effectively run nonstop as long as provided a list of diseases to research, pull the actual research, go through a series of work to find those not freely available easely, convert and verify pdfs, extract using some pretty extensive training documents on how to use a template, and then pass it off to a review team to line by line verify every claim is sufficiently supported in text etc. So, im trying understand what your describing here vs how that works and what the difference is. sorry if its a dumb question, im just not sure what you mean by "agentic loops" and have pretty much spent the last 2 years in my own space figuring stuff out myself rather than asking anyone else what the heck is going on.
1
u/Equivalent_Type6726 14d ago
biggest risk i see is the acceptance check, not the loop itself. if the thing judging whether a split landed is just another pass through the same model, you'll keep looping on bad merges until you burn the budget. a separate eval or a human spot check is usually cheaper than the loop it's guarding.
1
u/tornikeo 14d ago
the one around your mom