Just launched Loop Library - a curated list of agent loops you can use right now.
Find loops, submit your own, tokenmaxx!!
https://signals.forwardfuture.ai/loop-library/
Forward Future founder Matthew Berman has released Loop Library, a public directory of AI agent workflows that bundle prompts with explicit checks, proof steps, and stopping conditions so agents can execute repeatable tasks without drifting.
Just launched Loop Library - a curated list of agent loops you can use right now.
Find loops, submit your own, tokenmaxx!!
https://signals.forwardfuture.ai/loop-library/
The collection currently features 22 entries, including a ticket-to-PR workflow, a sub-50 ms page-load optimizer, and an architecture refactoring loop that runs live tests and checkpoints before committing.
Everything is freely accessible at signals.forwardfuture.ai/loop-library; users can submit their own loops for review, though adoption numbers and long-term maintenance plans remain unstated.
Many users praised Matthew Berman's Loop Library launch as a powerful and timely collection of AI agent loops, while some called the approach token-wasting slop or a cute toy.
No Digg Deeper questions have been answered for this story yet.
One of my new favorite loops from Peter Steinberger (@steipete):
“Refactor until you are happy with the architecture. After each significant step, live-test the system, run autoreview, and commit. Track progress in /tmp/refactor-{projectname}.md.”
https://signals.forwardfuture.ai/loop-library/loops/architecture-satisfaction-loop/
Just launched Loop Library - a curated list of agent loops you can use right now.
Find loops, submit your own, tokenmaxx!!
https://signals.forwardfuture.ai/loop-library/
My favorite loop: "Continue optimizing the code for speed. After each significant change, measure page-load performance across every page under the same repeatable test conditions. Continue until every page loads in under 50 ms."
https://signals.forwardfuture.ai/loop-library/loops/sub-50ms-page-load-loop/
Just launched Loop Library - a curated list of agent loops you can use right now.
Find loops, submit your own, tokenmaxx!!
https://signals.forwardfuture.ai/loop-library/
New Loop submitted!!
By my friend @hnshah - A workflow that turns a ticket, failing behavior, or customer complaint into a proven root cause, minimal patch, and reviewer-ready handoff.
Full prompt here:
https://signals.forwardfuture.ai/loop-library/loops/ticket-to-pr-ready-loop/
Just launched Loop Library - a curated list of agent loops you can use right now.
Find loops, submit your own, tokenmaxx!!
https://signals.forwardfuture.ai/loop-library/
There are two kinds of loops: > deterministic (ex: when site speed less than 50ms) > LLM as judge (ex: when the website is fast enough)
LLMs are becoming fantastic judges. This opens up significantly more knowledge work to be looped.
Just launched Loop Library - a curated list of agent loops you can use right now.
Find loops, submit your own, tokenmaxx!!
https://signals.forwardfuture.ai/loop-library/
Shout out to http://here.now for hosting and partnering!
Just launched Loop Library - a curated list of agent loops you can use right now.
Find loops, submit your own, tokenmaxx!!
https://signals.forwardfuture.ai/loop-library/

Very cool, will check it out. Looks like you have 1 builder and 1 reviewer and they don’t directly communicate is that right? Does that ever get stuck for you? Or maybe I’m misunderstanding but I’m my experiments I’ve seen the reviewer and builder go back and forth in perpetuity without a third vote. Found real time context sharing to be useful in that regard as well as opposed to one builder going down a path too deeply before getting feedback.

yeah you read it right, they coordinate through committed git state, not direct chat. the back-and-forth-forever thing is real for pure two-party loops, but two things stop it here. the reviewer isn’t just voting, it runs a mechanized gate (revert the fix and confirm the test goes red, coverage ratchet, patch coverage) so the verdict is pass/fail against real code, not an opinion that can ping-pong. and there’s a no-progress breaker: consecutive waves with no tree change park the loop to me instead of looping forever.
your “going too deep before feedback” point is fair though. i’ve actually watched the reviewer pull the builder back from a bad path a few times, so commit-then-review catches more than you’d think. real-time sharing getting feedback earlier is a real edge, i won’t pretend otherwise. 0.6.0 (live now) already adds a planner that grills the spec before the builder builds, basically the third perspective you’re describing, just upstream instead of a runtime vote. the coordination stuff you’re hitting is exactly what i’m building next, more coming tonight !

@MatthewBerman @steipete Loops are prompts..prompts to loop..that prompt the loop to loop... I still don't get how loops aren't just prompts to "check your work before you are done" 😵💫 am I missing something?

@RohithThakurwar @MatthewBerman dang this is a cool visualization. Can you drag things around and add from this screen?

@RyanTanaka thanks got any loops you use?

@MatthewBerman Smart

@MatthewBerman congratulations with another great launch
let me check this Loop Library

@alphabatcher please submit your loops :)

@willwashburn say more

@MatthewBerman Nice! will submit autonomy-loop

@MatthewBerman I don't see how "The overnight docs sweep" is a loop. Are you calling it a loop because it runs every night?

@MatthewBerman Not yet!

@MatthewBerman i did a loop with video yesterday in CC and worked great. even if youve created a template, sometimes it drifts...and nailed the first one. try it!

@gauthampai The goal of the loop is documentation completeness

@bradshannon @steipete yes!