Collaboration invite — benchmark your repair loop on LoopBench
Hi @OpenAutoCoder maintainers — Agentless solves software repair with a closed locate → patch → verify loop, which maps cleanly to our public LB-CR-1 (code repair) task.
We run a fixed-seed, no-API-key scoreboard for comparable loop engineering:
pip install "le-loopforge>=0.2.0" "le-loopctl>=0.1.0" "loopbench>=0.1.1" "loopgym>=0.1.2"
loopbench run --task LB-CR-1 --spec your-agentless-loop.yaml --seeds 0,1,2,3,4 -o results.json
loopbench validate results.json
# → PR to KanakMalpani/LoopBench leaderboard/entries.json
What we need: one maintainer or contributor PR with your loop mapped to LSS YAML + observed LES. First non-maintainer row gets permanent leaderboard credit and a shout-out on Loop Engineering.
Happy to pair on the LSS mapping (workers / evaluators / termination_conditions) if useful. Playground hub: https://github.com/KanakMalpani/Loop-Engineering/blob/main/contributions/LOOP_PLAYGROUND.md
— Loop Engineering community (issue #4)
Posted 2026-06-25 UTC via adoption_wave11.py
Collaboration invite — benchmark your repair loop on LoopBench
Hi @OpenAutoCoder maintainers — Agentless solves software repair with a closed locate → patch → verify loop, which maps cleanly to our public LB-CR-1 (code repair) task.
We run a fixed-seed, no-API-key scoreboard for comparable loop engineering:
What we need: one maintainer or contributor PR with your loop mapped to LSS YAML + observed LES. First non-maintainer row gets permanent leaderboard credit and a shout-out on Loop Engineering.
Happy to pair on the LSS mapping (
workers/evaluators/termination_conditions) if useful. Playground hub: https://github.com/KanakMalpani/Loop-Engineering/blob/main/contributions/LOOP_PLAYGROUND.md— Loop Engineering community (issue #4)
Posted 2026-06-25 UTC via adoption_wave11.py