row_id string | section string | section_slug string | resource_type string | marker string | title string | url string | url_kind string | domain string | annotation string | description string | key_contribution string | novelty string | impact string | signal string | signal_strength string | source_readme string | source_line int64 | source_url string | date_added string | collection string | collection_slug string | user_goal string | lifecycle_stages string | audience string | loop_layer string | scope_fit string | evidence_class string | evidence_tier string | source_status string | canonical_url string | source_title string | source_description string | authors string | publication_date string | publication_year string | publication_venue string | publisher string | doi string | publication_note string | primary_category string | metadata_source string | github_repo string | github_stars string | github_forks string | github_license string | github_created_at string | github_updated_at string | arxiv_id string | audited_at timestamp[ms] |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ale-0501 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | SEAGym: An Evaluation Environment for Self-Evolving LLM Agents | https://arxiv.org/abs/2606.17546 | external | arxiv.org | Evaluation environment that measures whether a self-evolving agent's modifications to prompts, memory, and tools generalize to held-out tasks, using train, validation, and test splits and cost metrics on Terminal-Bench 2.0 and HLE. | Evaluation environment that measures whether a self-evolving agent's modifications to prompts, memory, and tools generalize to held-out tasks, using train, validation, and test splits and cost metrics on Terminal-Bench 2.0 and HLE. | Evaluation environment that measures whether a self-evolving agent's modifications to prompts, memory, and tools generalize to held-out tasks, using train, validation, and test splits and cost metrics on Terminal-Bench 2.0 and HLE. | Evaluation data is used as the feedback signal for improving loop behavior. Evaluation environment that measures whether a self-evolving agent's modifications to prompts, memory, and tools generalize to held-out tasks, using train, validation, and test splits and cost metrics on Terminal-Bench 2.0 and HLE. | Use SEAGym: An Evaluation Environment for Self-Evolving LLM Agents to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,216 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1216 | Verify | verify | Gate progress with tests, evals, and evidence. | workspace;context;verification;budget | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://arxiv.org/abs/2606.17546 | [2606.17546] SEAGym: An Evaluation Environment for Self-Evolving LLM Agents | Self-evolving LLM-based agents improve mainly by changing their agent harness: the structured execution layer around a base model, including prompts, memory, tools, middleware, runtime state, and the model-tool interaction loop. Existing evaluations often reduce this process to isolated task scores or a single sequenti... | Congjie Zheng; Chuanyi Xue; Bin Liang; Jun Yang; Changshui Zhang | 2026-06-16 | 2026 | arXiv | arXiv | cs.AI | arxiv-api | 2606.17546 | 2026-07-20T09:31:57 | |||||||||
ale-0502 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | EvoCode-Bench: Evaluating Coding Agents in Multi-Turn Iterative Interactions | https://arxiv.org/abs/2605.24110 | external | arxiv.org | Benchmark of 26 evolving coding tasks across 227 evaluation rounds using cumulative executable tests to check that agents keep prior requirements working as specifications change, with top agents reaching only about 50% on multi-turn success metrics. | Benchmark of 26 evolving coding tasks across 227 evaluation rounds using cumulative executable tests to check that agents keep prior requirements working as specifications change, with top agents reaching only about 50% on multi-turn success metrics. | Benchmark of 26 evolving coding tasks across 227 evaluation rounds using cumulative executable tests to check that agents keep prior requirements working as specifications change, with top agents reaching only about 50% on multi-turn success metrics. | Evaluation data is used as the feedback signal for improving loop behavior. Benchmark of 26 evolving coding tasks across 227 evaluation rounds using cumulative executable tests to check that agents keep prior requirements working as specifications change, with top agents reaching only about 50% on multi-turn success me... | Use EvoCode-Bench: Evaluating Coding Agents in Multi-Turn Iterative Interactions to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,217 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1217 | Verify | verify | Gate progress with tests, evals, and evidence. | verification | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://arxiv.org/abs/2605.24110 | [2605.24110] EvoCode-Bench: Evaluating Coding Agents in Multi-Turn Iterative Interactions | Coding agents are increasingly used as iterative development partners, but most benchmarks still evaluate one specification followed by one final assessment. This leaves out a basic question: can an agent keep its own codebase working as requirements change? We introduce EvoCode-Bench, a benchmark of 26 stateful coding... | Haiyang Shen; Xuanzhong Chen; Wendong Xu; Yun Ma; Liang Chen; Kuan Li | 2026-05-22 | 2026 | arXiv | arXiv | Work in Progress; 32 pages, 10 figures, preprint | cs.AI | arxiv-api | 2605.24110 | 2026-07-20T09:31:57 | ||||||||
ale-0503 | Benchmarks And Evaluation | benchmarks-and-evaluation | Paper | 📄 | On the Reliability of Computer Use Agents | https://arxiv.org/abs/2604.17849 | external | arxiv.org | Repeated-execution study on OSWorld decomposing why computer-use agents fail tasks they previously completed, separating execution stochasticity, task-specification ambiguity, and behavioral variability as distinct causes of unreliability. | Repeated-execution study on OSWorld decomposing why computer-use agents fail tasks they previously completed, separating execution stochasticity, task-specification ambiguity, and behavioral variability as distinct causes of unreliability. | Repeated-execution study on OSWorld decomposing why computer-use agents fail tasks they previously completed, separating execution stochasticity, task-specification ambiguity, and behavioral variability as distinct causes of unreliability. | Links loop design to measurable tasks where progress and failure can be compared. Repeated-execution study on OSWorld decomposing why computer-use agents fail tasks they previously completed, separating execution stochasticity, task-specification ambiguity, and behavioral variability as distinct causes of unreliability... | Use On the Reliability of Computer Use Agents to measure progress and gate completion with repeatable evidence. | Research source arXiv:2604.17849; inspect its method and evaluation before treating results as production evidence. | medium | README.md | 1,218 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1218 | Verify | verify | Gate progress with tests, evals, and evidence. | verification | researcher;evaluator | evaluation | enabling | research-preprint | A | ok | https://arxiv.org/abs/2604.17849 | [2604.17849] On the Reliability of Computer Use Agents | Computer-use agents have rapidly improved on real-world tasks such as web navigation, desktop automation, and software interaction, in some cases surpassing human performance. Yet even when the task and model are unchanged, an agent that succeeds once may fail on a repeated execution of the same task. This raises a fun... | Gonzalo Gonzalez-Pumariega; Saaket Agashe; Jiachen Yang; Ang Li; Xin Eric Wang | 2026-04-20 | 2026 | arXiv | arXiv | 33 pages, 3 figures, 4 tables | cs.AI | arxiv-api | 2604.17849 | 2026-07-20T09:31:57 | ||||||||
ale-0504 | Benchmarks And Evaluation | benchmarks-and-evaluation | Paper | 📄 | AgentLens: Revealing the Lucky Pass Problem in SWE-Agent Evaluation | https://arxiv.org/abs/2605.12925 | external | arxiv.org | Grades 2,614 SWE-agent trajectories across eight models to show that 10.7% of passing trajectories in its 1,815-trajectory evaluation subset are lucky trial-and-error successes, replacing binary pass/fail with process-quality tiers that shift model rankings. | Grades 2,614 SWE-agent trajectories across eight models to show that 10.7% of passing trajectories in its 1,815-trajectory evaluation subset are lucky trial-and-error successes, replacing binary pass/fail with process-quality tiers that shift model rankings. | Grades 2,614 SWE-agent trajectories across eight models to show that 10.7% of passing trajectories in its 1,815-trajectory evaluation subset are lucky trial-and-error successes, replacing binary pass/fail with process-quality tiers that shift model rankings. | Evaluation data is used as the feedback signal for improving loop behavior. Grades 2,614 SWE-agent trajectories across eight models to show that 10.7% of passing trajectories in its 1,815-trajectory evaluation subset are lucky trial-and-error successes, replacing binary pass/fail with process-quality tiers that shift m... | Use AgentLens: Revealing the Lucky Pass Problem in SWE-Agent Evaluation to measure progress and gate completion with repeatable evidence. | Research source arXiv:2605.12925; inspect its method and evaluation before treating results as production evidence. | medium | README.md | 1,219 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1219 | Verify | verify | Gate progress with tests, evals, and evidence. | verification | researcher;evaluator | evaluation | enabling | research-preprint | A | ok | https://arxiv.org/abs/2605.12925 | [2605.12925] AgentLens: Revealing The Lucky Pass Problem in SWE-Agent Evaluation | Evaluation of software engineering (SWE) agents is dominated by a binary signal: whether the final patch passes the tests. This outcome-only view treats a principled solution and a chaotic trial-and-error process as equivalent. We show that this equivalence is empirically false. We evaluate 2,614 OpenHands trajectories... | Priyam Sahoo; Gaurav Mittal; Xiaomin Li; Shengjie Ma; Benjamin Steenhoek; Pingping Lin; Yu Hu | 2026-05-13 | 2026 | arXiv | arXiv | cs.SE | arxiv-api | 2605.12925 | 2026-07-20T09:31:57 | |||||||||
ale-0505 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | ORLoopBench: Solver-in-the-Loop Benchmarks for Self-Correction | https://arxiv.org/abs/2601.21008 | external | arxiv.org | Formalizes infeasible-model debugging as a solver-in-the-loop process where each action triggers solver re-execution and infeasibility recomputation, giving deterministic verification for iterative repair in operations research. | Formalizes infeasible-model debugging as a solver-in-the-loop process where each action triggers solver re-execution and infeasibility recomputation, giving deterministic verification for iterative repair in operations research. | Formalizes infeasible-model debugging as a solver-in-the-loop process where each action triggers solver re-execution and infeasibility recomputation, giving deterministic verification for iterative repair in operations research. | Verification is promoted from a final check to a loop-control signal. Formalizes infeasible-model debugging as a solver-in-the-loop process where each action triggers solver re-execution and infeasibility recomputation, giving deterministic verification for iterative repair in operations research. | Use ORLoopBench: Solver-in-the-Loop Benchmarks for Self-Correction to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,220 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1220 | Verify | verify | Gate progress with tests, evals, and evidence. | trigger;verification | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://openreview.net/pdf/16a0193aa4e71ffe6c921ac0081a66b525eea017.pdf | [2601.21008] ORLoopBench: Solver-in-the-Loop Benchmarks for Self-Correction and Behavioral Rationality in Operations Research | Operations Research practitioners debug infeasible models through an iterative process: inspecting Irreducible Infeasible Subsystems ( IIS), identifying constraint conflicts, and repairing formulations until feasibility is restored. Existing LLM benchmarks mostly treat OR as one-shot translation from problem descriptio... | Ruicheng Ao; David Simchi-Levi; Xinshang Wang | 2026 | 2026 | Proceedings of the 43rd International Conference on Machine Learning (ICML), PMLR 306 | PMLR | Published in Proceedings of the 43rd International Conference on Machine Learning (ICML), PMLR 306; the linked arXiv record remains available for open access. | cs.LG | PMLR camera-ready record | 2601.21008 | 2026-07-20T09:31:57 | ||||||||
ale-0506 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | LongDS-Bench: On the Failure of Long-Horizon Agentic Data Analysis | https://arxiv.org/abs/2605.30434 | external | arxiv.org | Benchmark of 68 real-world data-analysis tasks built from Kaggle notebooks spanning 2,225 interactive turns, finding that long-horizon errors account for 52-69% of agent failures and that maintaining a correct analytical state is the core bottleneck. | Benchmark of 68 real-world data-analysis tasks built from Kaggle notebooks spanning 2,225 interactive turns, finding that long-horizon errors account for 52-69% of agent failures and that maintaining a correct analytical state is the core bottleneck. | Benchmark of 68 real-world data-analysis tasks built from Kaggle notebooks spanning 2,225 interactive turns, finding that long-horizon errors account for 52-69% of agent failures and that maintaining a correct analytical state is the core bottleneck. | The work turns loop quality into a measurable task or score. Benchmark of 68 real-world data-analysis tasks built from Kaggle notebooks spanning 2,225 interactive turns, finding that long-horizon errors account for 52-69% of agent failures and that maintaining a correct analytical state is the core bottleneck. | Use LongDS-Bench: On the Failure of Long-Horizon Agentic Data Analysis to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,221 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1221 | Verify | verify | Gate progress with tests, evals, and evidence. | verification;state | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://arxiv.org/abs/2605.30434 | [2605.30434] LongDS-Bench: On the Failure of Long-Horizon Agentic Data Analysis | Real-world data analysis is inherently iterative, yet existing benchmarks mostly evaluate isolated or short interactive tasks, leaving agents' ability to track evolving analytical context over long horizons untested. We introduce LongDS, a benchmark for long-horizon, multi-turn data analysis where agents must maintain,... | Kewei Xu; Xiaoben Lu; Shuofei Qiao; Zihan Ding; Haoming Xu; Lei Liang; Ningyu Zhang | 2026-05-28 | 2026 | arXiv | arXiv | Ongoing work | cs.LG | arxiv-api | 2605.30434 | 2026-07-20T09:31:57 | ||||||||
ale-0507 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | MemoryArena: Benchmarking Agent Memory in Interdependent Multi-Session Agentic Tasks | https://arxiv.org/abs/2602.16313 | external | arxiv.org | Multi-session benchmark of interdependent agentic tasks where agents must distill earlier sessions into memory and use it to guide later actions, showing that near-saturated scores on long-context memory benchmarks fail to transfer. | Multi-session benchmark of interdependent agentic tasks where agents must distill earlier sessions into memory and use it to guide later actions, showing that near-saturated scores on long-context memory benchmarks fail to transfer. | Multi-session benchmark of interdependent agentic tasks where agents must distill earlier sessions into memory and use it to guide later actions, showing that near-saturated scores on long-context memory benchmarks fail to transfer. | The work turns loop quality into a measurable task or score. Multi-session benchmark of interdependent agentic tasks where agents must distill earlier sessions into memory and use it to guide later actions, showing that near-saturated scores on long-context memory benchmarks fail to transfer. | Use MemoryArena: Benchmarking Agent Memory in Interdependent Multi-Session Agentic Tasks to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,222 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1222 | Verify | verify | Gate progress with tests, evals, and evidence. | context;verification | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://arxiv.org/abs/2602.16313 | [2602.16313] MemoryArena: Benchmarking Agent Memory in Interdependent Multi-Session Agentic Tasks | Existing evaluations of agents with memory typically assess memorization and action in isolation. One class of benchmarks evaluates memorization by testing recall of past conversations or text but fails to capture how memory is used to guide future decisions. Another class focuses on agents acting in single-session tas... | Zexue He; Yu Wang; Churan Zhi; Yuanzhe Hu; Tzu-Ping Chen; Lang Yin; Ze Chen; Tong Arthur Wu; Siru Ouyang; Zihan Wang; Jiaxin Pei; Julian McAuley; Yejin Choi; Alex Pentland | 2026-02-18 | 2026 | arXiv | arXiv | cs.CL | arxiv-api | 2602.16313 | 2026-07-20T09:31:57 | |||||||||
ale-0508 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | Momento: Evaluating Persistent Memory and Reasoning with Multi-Session Agentic Conversations | https://arxiv.org/abs/2606.00832 | external | arxiv.org | Benchmark for persistent, tool-mediated task completion across multiple sessions, finding that agents fail by treating prior-session history as current context instead of stale state that needs re-validation. | Benchmark for persistent, tool-mediated task completion across multiple sessions, finding that agents fail by treating prior-session history as current context instead of stale state that needs re-validation. | Benchmark for persistent, tool-mediated task completion across multiple sessions, finding that agents fail by treating prior-session history as current context instead of stale state that needs re-validation. | The work turns loop quality into a measurable task or score. Benchmark for persistent, tool-mediated task completion across multiple sessions, finding that agents fail by treating prior-session history as current context instead of stale state that needs re-validation. | Use Momento: Evaluating Persistent Memory and Reasoning with Multi-Session Agentic Conversations to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,223 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1223 | Verify | verify | Gate progress with tests, evals, and evidence. | workspace;context;verification;state;exit | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://arxiv.org/abs/2606.00832 | [2606.00832] Momento: Evaluating Persistent Memory and Reasoning with Multi-Session Agentic Conversations | Recent advances in agentic AI have enabled agents to complete complex tasks through tool use, reasoning, and multi-step planning. Yet existing benchmarks evaluate agents within a single session, ignoring past actions, stated preferences, and prior decisions that agents must integrate to fulfill personalized user goals.... | Adril Putra Merin; David Anugraha; Ayu Purwarianti; Genta Indra Winata | 2026-05-30 | 2026 | arXiv | arXiv | Preprint | cs.CL | arxiv-api | 2606.00832 | 2026-07-20T09:31:57 | ||||||||
ale-0509 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | π-Bench: Evaluating Proactive Personal Assistant Agents in Long-Horizon Workflows | https://arxiv.org/abs/2605.14678 | external | arxiv.org | Benchmark of 100 multi-turn tasks across 5 user personas with hidden intents, inter-task dependencies, and cross-session continuity, measuring agent proactivity separately from task completion in long-horizon trajectories. | Benchmark of 100 multi-turn tasks across 5 user personas with hidden intents, inter-task dependencies, and cross-session continuity, measuring agent proactivity separately from task completion in long-horizon trajectories. | Benchmark of 100 multi-turn tasks across 5 user personas with hidden intents, inter-task dependencies, and cross-session continuity, measuring agent proactivity separately from task completion in long-horizon trajectories. | The work turns loop quality into a measurable task or score. Benchmark of 100 multi-turn tasks across 5 user personas with hidden intents, inter-task dependencies, and cross-session continuity, measuring agent proactivity separately from task completion in long-horizon trajectories. | Use π-Bench: Evaluating Proactive Personal Assistant Agents in Long-Horizon Workflows to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,224 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1224 | Verify | verify | Gate progress with tests, evals, and evidence. | verification;exit | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://arxiv.org/abs/2605.14678 | [2605.14678] $π$-Bench: Evaluating Proactive Personal Assistant Agents in Long-Horizon Workflows | The rise of personal assistant agents, e.g., OpenClaw, highlights the growing potential of large language models to support users across everyday life and work. A core challenge in these settings is proactive assistance, since users often begin with underspecified requests and leave important needs, constraints, or pre... | Haoran Zhang; Luxin Xu; Zhilin Wang; Runquan Gui; Shunkai Zhang; Haodi Lei; Zihao He; Bingsu He; Chicheng Qin; Tong Zhu; Xiaoye Qu; Yang Yang; Yu Cheng; Yafu Li | 2026-05-14 | 2026 | arXiv | arXiv | 44 pages | cs.AI | arxiv-api | 2605.14678 | 2026-07-20T09:31:57 | ||||||||
ale-0510 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | Can LLM Agents Be CFOs? Benchmarking Long-Horizon Resource Allocation | https://arxiv.org/abs/2603.23638 | external | arxiv.org | A 132-month CFO simulation where agents repeat a monthly cycle of liquidity management, financial closings, and financing decisions with compounding state, and only 15.4% of trials survive the full horizon. | A 132-month CFO simulation where agents repeat a monthly cycle of liquidity management, financial closings, and financing decisions with compounding state, and only 15.4% of trials survive the full horizon. | A 132-month CFO simulation where agents repeat a monthly cycle of liquidity management, financial closings, and financing decisions with compounding state, and only 15.4% of trials survive the full horizon. | The work targets tasks that exceed a single context window or prompt session. A 132-month CFO simulation where agents repeat a monthly cycle of liquidity management, financial closings, and financing decisions with compounding state, and only 15.4% of trials survive the full horizon. | Use Can LLM Agents Be CFOs? Benchmarking Long-Horizon Resource Allocation to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,225 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1225 | Verify | verify | Gate progress with tests, evals, and evidence. | state | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://arxiv.org/abs/2603.23638 | [2603.23638] Can LLM Agents Be CFOs? Benchmarking Long-Horizon Resource Allocation in an Uncertain Enterprise Environment | Large language model (LLM) agents are increasingly tested on complex tasks, but their ability to allocate scarce resources over long horizons remains unclear. Unlike reactive tasks with immediate feedback, this setting requires agents to make binding commitments under partial observability, delayed consequences, hard r... | Yi Han; Yan Wang; Lingfei Qian; Haohang Li; Yupeng Cao; Yueru He; Xueqing Peng; Nanhan Shen; Yitao Xu; Yankai Chen; Dongji Feng; Jimin Huang; Xue Liu; Jian-Yun Nie; Sophia Ananiadou | 2026-03-24 | 2026 | arXiv | arXiv | cs.AI | arxiv-api | 2603.23638 | 2026-07-20T09:31:57 | |||||||||
ale-0511 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | EvoAgentBench: Benchmarking Agent Self-Evolution via Ability Transfer | https://arxiv.org/abs/2607.05202 | external | arxiv.org | Benchmark isolating whether agents transfer reusable procedures such as searching, debugging, and verification across episodes in four long-horizon domains linked by ability graphs, finding curated experience transfers but no automatic method yields consistent gains. | Benchmark isolating whether agents transfer reusable procedures such as searching, debugging, and verification across episodes in four long-horizon domains linked by ability graphs, finding curated experience transfers but no automatic method yields consistent gains. | Benchmark isolating whether agents transfer reusable procedures such as searching, debugging, and verification across episodes in four long-horizon domains linked by ability graphs, finding curated experience transfers but no automatic method yields consistent gains. | Control flow is represented as an inspectable graph rather than an opaque prompt loop. Benchmark isolating whether agents transfer reusable procedures such as searching, debugging, and verification across episodes in four long-horizon domains linked by ability graphs, finding curated experience transfers but no automat... | Use EvoAgentBench: Benchmarking Agent Self-Evolution via Ability Transfer to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,226 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1226 | Verify | verify | Gate progress with tests, evals, and evidence. | verification | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://arxiv.org/abs/2607.05202 | [2607.05202] EvoAgentBench: Benchmarking Agent Self-Evolution via Ability Transfer | Agent self-evolution in long-horizon LLM systems is largely procedural: useful experience is not merely stored information, but reusable procedures for searching, debugging, and verification. Yet current evaluations do not isolate this form of transfer. Agent benchmarks test single-episode task solving; memory benchmar... | Xingze Gao; Chuanrui Hu; Hongda Chen; Pengfei Yao; Zhao Wang; Yi Bai; Zhengwei Wu; Yunyun Han; Xiaofeng Cong; Jie Gui; Yafeng Deng; Teng Li | 2026-07-06 | 2026 | arXiv | arXiv | 15 pages, 2 figures, 8 tables | cs.AI | arxiv-api | 2607.05202 | 2026-07-20T09:31:57 | ||||||||
ale-0512 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | AgenticSTS: A Bounded-Memory Testbed for Long-Horizon LLM Agents | https://arxiv.org/abs/2607.02255 | external | arxiv.org | Bounded-memory testbed built on Slay the Spire 2 where every agent decision is made from a fresh prompt assembled by typed retrieval over recorded state, keeping prompt size bounded across runs of any length, with 298 documented trajectories released. | Bounded-memory testbed built on Slay the Spire 2 where every agent decision is made from a fresh prompt assembled by typed retrieval over recorded state, keeping prompt size bounded across runs of any length, with 298 documented trajectories released. | Bounded-memory testbed built on Slay the Spire 2 where every agent decision is made from a fresh prompt assembled by typed retrieval over recorded state, keeping prompt size bounded across runs of any length, with 298 documented trajectories released. | Persistent memory is treated as an external runtime artifact. Bounded-memory testbed built on Slay the Spire 2 where every agent decision is made from a fresh prompt assembled by typed retrieval over recorded state, keeping prompt size bounded across runs of any length, with 298 documented trajectories released. | Use AgenticSTS: A Bounded-Memory Testbed for Long-Horizon LLM Agents to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,227 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1227 | Verify | verify | Gate progress with tests, evals, and evidence. | context;state | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://arxiv.org/abs/2607.02255 | [2607.02255] AgenticSTS: A Bounded-Memory Testbed for Long-Horizon LLM Agents | Memory for a long-horizon LLM agent is a contract about what each future decision is allowed to see. The simplest contract appends past observations, tool calls, and reflections to every prompt, which makes prior context easy to access but also turns it into a jumbled mixture in which the effect of any single memory co... | Xiangchen Cheng; Yunwei Jiang; Jianwen Sun; Zizhen Li; Chuanhao Li; Xiangcheng Cao; Yihao Liu; Fanrui Zhang; Li Jin; Kaipeng Zhang | 2026-07-02 | 2026 | arXiv | arXiv | cs.AI | arxiv-api | 2607.02255 | 2026-07-20T09:31:57 | |||||||||
ale-0513 | Benchmarks And Evaluation | benchmarks-and-evaluation | Paper | 📄 | Is Three the Magic Number? An Empirical Evaluation of LLM-Based Repair Loops | https://arxiv.org/abs/2607.05197 | external | arxiv.org | Empirical evaluation of iteration budgets for generate-validate-repair loops across code generation, test generation, and translation, finding the first three to four iterations capture most gains and that orchestration and feedback design matter more than the model. | Empirical evaluation of iteration budgets for generate-validate-repair loops across code generation, test generation, and translation, finding the first three to four iterations capture most gains and that orchestration and feedback design matter more than the model. | Empirical evaluation of iteration budgets for generate-validate-repair loops across code generation, test generation, and translation, finding the first three to four iterations capture most gains and that orchestration and feedback design matter more than the model. | Evaluation data is used as the feedback signal for improving loop behavior. Empirical evaluation of iteration budgets for generate-validate-repair loops across code generation, test generation, and translation, finding the first three to four iterations capture most gains and that orchestration and feedback design matt... | Use Is Three the Magic Number? An Empirical Evaluation of LLM-Based Repair Loops to measure progress and gate completion with repeatable evidence. | Research source arXiv:2607.05197; inspect its method and evaluation before treating results as production evidence. | medium | README.md | 1,228 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1228 | Verify | verify | Gate progress with tests, evals, and evidence. | delegation;verification;budget | researcher;evaluator | evaluation | enabling | research-preprint | A | ok | https://arxiv.org/abs/2607.05197 | [2607.05197] Is Three the Magic Number? An Empirical Evaluation of LLM-Based Repair Loops | Iterative repair loops have become a core design pattern in LLM-based software engineering systems. These workflows repeatedly generate, validate, and repair artifacts using feedback such as compiler errors or test failures. Despite their widespread use, the impact of repair-loop iteration limits remains poorly underst... | Tobias Kiecker; Eik Reichmann; Hosung Kang; Gabin An; Lars Grunske | 2026-07-06 | 2026 | arXiv | arXiv | 4 Pages (+1 for references), NIER Paper | cs.SE | arxiv-api | 2607.05197 | 2026-07-20T09:31:57 | ||||||||
ale-0514 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | DeepSWE: Measuring Frontier Coding Agents on Original, Long-Horizon Engineering Tasks | https://arxiv.org/abs/2607.07946 | external | arxiv.org | 113 from-scratch, contamination-free long-horizon software-engineering tasks with custom verifiers that accept any correct implementation, built to sidestep SWE-bench-style pretraining recall and better differentiate frontier coding agents. | 113 from-scratch, contamination-free long-horizon software-engineering tasks with custom verifiers that accept any correct implementation, built to sidestep SWE-bench-style pretraining recall and better differentiate frontier coding agents. | 113 from-scratch, contamination-free long-horizon software-engineering tasks with custom verifiers that accept any correct implementation, built to sidestep SWE-bench-style pretraining recall and better differentiate frontier coding agents. | The work targets tasks that exceed a single context window or prompt session. 113 from-scratch, contamination-free long-horizon software-engineering tasks with custom verifiers that accept any correct implementation, built to sidestep SWE-bench-style pretraining recall and better differentiate frontier coding agents. | Use DeepSWE: Measuring Frontier Coding Agents on Original, Long-Horizon Engineering Tasks to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,229 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1229 | Verify | verify | Gate progress with tests, evals, and evidence. | verification | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://arxiv.org/abs/2607.07946 | [2607.07946] DeepSWE: Measuring Frontier Coding Agents on Original, Long-Horizon Engineering Tasks | DeepSWE is a benchmark of 113 original, long-horizon software engineering tasks for evaluating coding agents. Most public agentic coding benchmarks follow SWE-bench in mining merged fixes from public GitHub repositories, which creates two problems: the fixes and their discussion were likely seen during pretraining, so ... | Wenqi Huang; Charley Lee; Leonard Tng; Serena Ge | 2026-07-08 | 2026 | arXiv | arXiv | 32 pages, 10 figures. Code and data: https://github.com/datacurve-ai/deep-swe ; https://deepswe.datacurve.ai/ | cs.SE | arxiv-api | 2607.07946 | 2026-07-20T09:31:57 | ||||||||
ale-0515 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | PERFOPT-Bench: Evaluating Coding Agents on Software Performance Optimization | https://arxiv.org/abs/2607.07744 | external | arxiv.org | Benchmarks the profile-diagnose-edit-verify loop where the verifier is a profiler rather than a test suite: agents must deliver measured, reproducible speedups without breaking correctness, and across seven agent configurations the framework choice shifts results even with identical models. | Benchmarks the profile-diagnose-edit-verify loop where the verifier is a profiler rather than a test suite: agents must deliver measured, reproducible speedups without breaking correctness, and across seven agent configurations the framework choice shifts results even with identical models. | Benchmarks the profile-diagnose-edit-verify loop where the verifier is a profiler rather than a test suite: agents must deliver measured, reproducible speedups without breaking correctness, and across seven agent configurations the framework choice shifts results even with identical models. | Verification is promoted from a final check to a loop-control signal. Benchmarks the profile-diagnose-edit-verify loop where the verifier is a profiler rather than a test suite: agents must deliver measured, reproducible speedups without breaking correctness, and across seven agent configurations the framework choice s... | Use PERFOPT-Bench: Evaluating Coding Agents on Software Performance Optimization to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,230 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1230 | Verify | verify | Gate progress with tests, evals, and evidence. | verification | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://arxiv.org/abs/2607.07744 | [2607.07744] PERFOPT-Bench: Evaluating Coding Agents on Software Performance Optimization | Coding-agent benchmarks have largely measured whether agents can produce functionally correct patches, but production software also demands measurable speedups on real execution targets. Performance optimization is a distinct agentic task: agents must profile executions, diagnose cross-layer bottlenecks, edit code with... | Yingyun Cui; Yi Xie; Piaohong Wang; Jiawei Ma; Bo Liu; Liangliang Cao | 2026-07-08 | 2026 | arXiv | arXiv | cs.SE | arxiv-api | 2607.07744 | 2026-07-20T09:31:57 | |||||||||
ale-0516 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | Benchmarking coding agents on Databricks' multi-million line codebase | https://www.databricks.com/blog/benchmarking-coding-agents-databricks-multi-million-line-codebase | external | www.databricks.com | Databricks engineering post (July 8, 2026, authors including Matei Zaharia and Patrick Wendell) on an internal benchmark built from real merged PRs with test-suite verification, finding that models cluster into three capability tiers, token price is a poor proxy for end-to-end task cost, and harness choice matters, wit... | Databricks engineering post (July 8, 2026, authors including Matei Zaharia and Patrick Wendell) on an internal benchmark built from real merged PRs with test-suite verification, finding that models cluster into three capability tiers, token price is a poor proxy for end-to-end task cost, and harness choice matters, wit... | Databricks engineering post (July 8, 2026, authors including Matei Zaharia and Patrick Wendell) on an internal benchmark built from real merged PRs with test-suite verification, finding that models cluster into three capability tiers, token price is a poor proxy for end-to-end task cost, and harness choice matters, wit... | Verification is promoted from a final check to a loop-control signal. Databricks engineering post (July 8, 2026, authors including Matei Zaharia and Patrick Wendell) on an internal benchmark built from real merged PRs with test-suite verification, finding that models cluster into three capability tiers, token price is ... | Use Benchmarking coding agents on Databricks' multi-million line codebase to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,231 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1231 | Verify | verify | Gate progress with tests, evals, and evidence. | context;verification;budget | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://www.databricks.com/blog/benchmarking-coding-agents-databricks-multi-million-line-codebase | Benchmarking Coding Agents on Databricks’ Multi-Million Line Codebase | Databricks Blog | Databricks shares results from its internal coding benchmark, evaluating coding agents on a multi-million line codebase to optimize engineering cost and performance. | 2026 | 2026 | Databricks | html-meta | 2026-07-20T09:31:57 | |||||||||||||
ale-0517 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | UniClawBench: A Universal Benchmark for Proactive Agents on Real-World Tasks | https://arxiv.org/abs/2607.08768 | external | arxiv.org | Capability-driven benchmark of 400 bilingual tasks for proactive agents operating everyday tools in live Docker environments with step-level checkpoints, decomposed into five foundational capabilities, skill usage, exploration, long-context reasoning, multimodal understanding, and cross-platform coordination, so failur... | Capability-driven benchmark of 400 bilingual tasks for proactive agents operating everyday tools in live Docker environments with step-level checkpoints, decomposed into five foundational capabilities, skill usage, exploration, long-context reasoning, multimodal understanding, and cross-platform coordination, so failur... | Capability-driven benchmark of 400 bilingual tasks for proactive agents operating everyday tools in live Docker environments with step-level checkpoints, decomposed into five foundational capabilities, skill usage, exploration, long-context reasoning, multimodal understanding, and cross-platform coordination, so failur... | Checkpointed state makes long-running agent work recoverable across failures. Capability-driven benchmark of 400 bilingual tasks for proactive agents operating everyday tools in live Docker environments with step-level checkpoints, decomposed into five foundational capabilities, skill usage, exploration, long-context r... | Use UniClawBench: A Universal Benchmark for Proactive Agents on Real-World Tasks to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,232 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1232 | Verify | verify | Gate progress with tests, evals, and evidence. | workspace;context;verification;state;escalation | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://arxiv.org/abs/2607.08768 | [2607.08768] UniClawBench: A Universal Benchmark for Proactive Agents on Real-World Tasks | The rapid development of large language models and multimodal large language models has accelerated the emergence of proactive agents capable of operating everyday tools and assisting users in real-world environments. However, existing benchmarks struggle to evaluate such agents effectively, as they often rely on sandb... | Zhekai Chen; Chengqi Duan; Kaiyue Sun; Bohao Li; Yuqing Wang; Manyuan Zhang; Xihui Liu | 2026-07-09 | 2026 | arXiv | arXiv | Project Page: https://uniclawbench.github.io | GitHub Repo: https://github.com/HKU-MMLab/UniClawBench | cs.CL | arxiv-api | 2607.08768 | 2026-07-20T09:31:57 | ||||||||
ale-0518 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | SLBench: Evaluating How LLM Agents Follow Logical Relations in Skills | https://arxiv.org/abs/2607.09016 | external | arxiv.org | Benchmark for whether agent loops respect the logical relations inside skill files (preconditions, constraints, fallbacks): 70% of 5,000+ public skills contain at least one such relation, and on 86 executable cases leading coding agents show unsafe-behavior rates up to 70%, with an inference-time scaffold cutting viola... | Benchmark for whether agent loops respect the logical relations inside skill files (preconditions, constraints, fallbacks): 70% of 5,000+ public skills contain at least one such relation, and on 86 executable cases leading coding agents show unsafe-behavior rates up to 70%, with an inference-time scaffold cutting viola... | Benchmark for whether agent loops respect the logical relations inside skill files (preconditions, constraints, fallbacks): 70% of 5,000+ public skills contain at least one such relation, and on 86 executable cases leading coding agents show unsafe-behavior rates up to 70%, with an inference-time scaffold cutting viola... | The work turns loop quality into a measurable task or score. Benchmark for whether agent loops respect the logical relations inside skill files (preconditions, constraints, fallbacks): 70% of 5,000+ public skills contain at least one such relation, and on 86 executable cases leading coding agents show unsafe-behavior r... | Use SLBench: Evaluating How LLM Agents Follow Logical Relations in Skills to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,233 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1233 | Verify | verify | Gate progress with tests, evals, and evidence. | verification | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://arxiv.org/abs/2607.09016 | [2607.09016] SLBench: Evaluating How LLM Agents Follow Logical Relations in Skills | Agent skills extend LLM agents with reusable procedures, tools, and domain-specific workflows, but their safety depends on resolving dependencies among interacting instructions. We introduce SkillLogic, a framework for analyzing logical relations in skill files and constructing executable tests from them. Our taxonomy ... | Xuan Chen; Chengpeng Wang; Lu Yan; Xiangyu Zhang | 2026-07-10 | 2026 | arXiv | arXiv | cs.CR | arxiv-api | 2607.09016 | 2026-07-20T09:31:57 | |||||||||
ale-0519 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | SWE-Milestone: Evaluating AI Agents on Continuous Software Evolution | https://arxiv.org/abs/2603.13428 | external | arxiv.org | Commit-history-derived milestone task streams where agents must preserve system integrity across successive runs - frontier-model scores collapse from >80% on isolated tasks to at most 38% in continuous settings, quantifying the error-accumulation gap loop engineering targets. | Commit-history-derived milestone task streams where agents must preserve system integrity across successive runs - frontier-model scores collapse from >80% on isolated tasks to at most 38% in continuous settings, quantifying the error-accumulation gap loop engineering targets. | Commit-history-derived milestone task streams where agents must preserve system integrity across successive runs - frontier-model scores collapse from >80% on isolated tasks to at most 38% in continuous settings, quantifying the error-accumulation gap loop engineering targets. | Links loop design to measurable tasks where progress and failure can be compared. Commit-history-derived milestone task streams where agents must preserve system integrity across successive runs - frontier-model scores collapse from >80% on isolated tasks to at most 38% in continuous settings, quantifying the error-acc... | Use SWE-Milestone: Evaluating AI Agents on Continuous Software Evolution to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,234 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1234 | Verify | verify | Gate progress with tests, evals, and evidence. | verification | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://arxiv.org/abs/2603.13428 | [2603.13428] SWE-Milestone: Evaluating AI Agents on Continuous Software Evolution | Real-world software must continuously evolve to meet ever-changing and open-ended requirements. AI agents, increasingly deployed as long-running systems, are now entrusted to drive this evolution. Yet, existing benchmarks evaluate agents on isolated, one-off coding tasks, neglecting the temporal dependencies and techni... | Gangda Deng; Zhaoling Chen; Zhongming Yu; Haoyang Fan; Yuhong Liu; Yuxin Yang; Dhruv Parikh; Rajgopal Kannan; Le Cong; Mengdi Wang; Qian Zhang; Viktor Prasanna; Xiangru Tang; Xingyao Wang | 2026 | 2026 | Proceedings of the 43rd International Conference on Machine Learning (ICML) | PMLR | Accepted at Proceedings of the 43rd International Conference on Machine Learning (ICML); the linked arXiv record is the available paper version. | cs.SE | Current arXiv acceptance note and official project record | 2603.13428 | 2026-07-20T09:31:57 | ||||||||
ale-0520 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | AgentAbstain: Do LLM Agents Know When Not to Act? | https://arxiv.org/abs/2607.10059 | external | arxiv.org | Benchmark measuring whether agents correctly abstain from acting when a task is underspecified, unsafe, or impossible, rather than proceeding anyway, a capability every unattended loop depends on for safe exits. | Benchmark measuring whether agents correctly abstain from acting when a task is underspecified, unsafe, or impossible, rather than proceeding anyway, a capability every unattended loop depends on for safe exits. | Benchmark measuring whether agents correctly abstain from acting when a task is underspecified, unsafe, or impossible, rather than proceeding anyway, a capability every unattended loop depends on for safe exits. | The work turns loop quality into a measurable task or score. Benchmark measuring whether agents correctly abstain from acting when a task is underspecified, unsafe, or impossible, rather than proceeding anyway, a capability every unattended loop depends on for safe exits. | Use AgentAbstain: Do LLM Agents Know When Not to Act? to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,235 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1235 | 2026-07-15 | Verify | verify | Gate progress with tests, evals, and evidence. | verification | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://arxiv.org/abs/2607.10059 | [2607.10059] AgentAbstain: Do LLM Agents Know When Not to Act? | Agent systems based on large language models (LLMs) are increasingly deployed for autonomous tasks, yet existing evaluations mostly focus on task success rather than whether agents know when to abstain. This gap poses real risks: under ambiguity, conflicting constraints, or tool failures, agents may execute unintended ... | Xun Liu; Yi Evie Zhang; Vira Kasprova; Parisa Rabbani; Pardis Sadat Zahraei; Tianyu Zhang; Ali Ebrahimpour-Boroojeny; Varun Chandrasekaran | 2026-07-11 | 2026 | arXiv | arXiv | 56 pages, 13 figures | cs.AI | arxiv-api | 2607.10059 | 2026-07-20T09:31:57 | |||||||
ale-0521 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | Agents Don't Just Agree, They Remember: Benchmarking Persistent Sycophancy | https://arxiv.org/abs/2607.10526 | external | arxiv.org | Benchmark showing that once a stateful personal agent is nudged into a sycophantic stance, it persists across later sessions through memory, so single-turn sycophancy tests understate the risk in long-running agents. | Benchmark showing that once a stateful personal agent is nudged into a sycophantic stance, it persists across later sessions through memory, so single-turn sycophancy tests understate the risk in long-running agents. | Benchmark showing that once a stateful personal agent is nudged into a sycophantic stance, it persists across later sessions through memory, so single-turn sycophancy tests understate the risk in long-running agents. | The work turns loop quality into a measurable task or score. Benchmark showing that once a stateful personal agent is nudged into a sycophantic stance, it persists across later sessions through memory, so single-turn sycophancy tests understate the risk in long-running agents. | Use Agents Don't Just Agree, They Remember: Benchmarking Persistent Sycophancy to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,236 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1236 | 2026-07-15 | Verify | verify | Gate progress with tests, evals, and evidence. | context;verification;state | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://arxiv.org/abs/2607.10526 | [2607.10526] Agents Don't Just Agree, They Remember: Benchmarking Persistent Sycophancy in Stateful Personal Agents | Stateful personal agents increasingly maintain long-term user profiles, episodic memories, and reusable skills. This persistence turns conversational sycophancy into a state-writing failure: accepted user-centric claims can be committed as lasting preferences, background facts, or workflows and later reused after the o... | Xutao Mao; Liangjie Zhao; Leyao Wang; Rui Qian; Qiang Huang; Wentao Wang; Bo Han; Xiang Zheng; Cong Wang | 2026-07-12 | 2026 | arXiv | arXiv | cs.AI | arxiv-api | 2607.10526 | 2026-07-20T09:31:57 | ||||||||
ale-0522 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | Set-shifting Behavioral Test for Harnessed Agents | https://arxiv.org/abs/2607.13396 | external | arxiv.org | Tests whether harnessed agents adapt when hidden tool reliability changes, paired with no-shift controls that separate genuine adaptation failures from ordinary task errors and expose routine lock-in. | Tests whether harnessed agents adapt when hidden tool reliability changes, paired with no-shift controls that separate genuine adaptation failures from ordinary task errors and expose routine lock-in. | Tests whether harnessed agents adapt when hidden tool reliability changes, paired with no-shift controls that separate genuine adaptation failures from ordinary task errors and expose routine lock-in. | Links loop design to measurable tasks where progress and failure can be compared. Tests whether harnessed agents adapt when hidden tool reliability changes, paired with no-shift controls that separate genuine adaptation failures from ordinary task errors and expose routine lock-in. | Use Set-shifting Behavioral Test for Harnessed Agents to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,237 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1237 | 2026-07-17 | Verify | verify | Gate progress with tests, evals, and evidence. | workspace;verification | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://arxiv.org/abs/2607.13396 | [2607.13396] Set-shifting Behavioral Test for Harnessed Agents | What happens to an LLM agent's tool choice when the reliable tool silently changes within an ongoing session? We borrow set-shifting from cognitive psychology to study how well agents adapt to hidden reliability shifts. Our benchmark mounts tool-skill libraries with redundancies, where many tools solve the same task bu... | Ziwei Ye | 2026-07-15 | 2026 | arXiv | arXiv | cs.AI | arxiv-api | 2607.13396 | 2026-07-20T09:31:57 | ||||||||
ale-0523 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | MCPEvol-Bench: Benchmarking LLM Agent Performance Across Dynamic Evolutions of MCP Servers | https://arxiv.org/abs/2607.14642 | external | arxiv.org | Applies 11 server-evolution mutations to 123 MCP servers and evaluates 12 LLMs; reported performance drops include 13.7% for GPT-5.4 and 14.4% for Claude Sonnet 4.6, quantifying tool-interface drift. | Applies 11 server-evolution mutations to 123 MCP servers and evaluates 12 LLMs; reported performance drops include 13.7% for GPT-5.4 and 14.4% for Claude Sonnet 4.6, quantifying tool-interface drift. | Applies 11 server-evolution mutations to 123 MCP servers and evaluates 12 LLMs; reported performance drops include 13.7% for GPT-5.4 and 14.4% for Claude Sonnet 4.6, quantifying tool-interface drift. | Links loop design to measurable tasks where progress and failure can be compared. Applies 11 server-evolution mutations to 123 MCP servers and evaluates 12 LLMs; reported performance drops include 13.7% for GPT-5.4 and 14.4% for Claude Sonnet 4.6, quantifying tool-interface drift. | Use MCPEvol-Bench: Benchmarking LLM Agent Performance Across Dynamic Evolutions of MCP Servers to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,238 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1238 | 2026-07-17 | Verify | verify | Gate progress with tests, evals, and evidence. | workspace | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://arxiv.org/abs/2607.14642 | [2607.14642] MCPEvol-Bench: Benchmarking LLM Agent Performance Across Dynamic Evolutions of MCP Servers | As Model Context Protocol (MCP) servers emerge as the core infrastructure for connecting LLMs with external tools, existing benchmarks leverage real-world MCP servers to evaluate LLM agents' tool-using capabilities. However, these benchmarks overlook the continuous evolution of tool interfaces and functionalities withi... | Huanxi Liu; Kun Hu; Jiaqi Liao; Qiang Wang; Pengfei Qian; YuanZhao Zhai; Dawei Feng; Bo Ding; Huaimin Wang | 2026-07-16 | 2026 | arXiv | arXiv | cs.AI | arxiv-api | 2607.14642 | 2026-07-20T09:31:57 | ||||||||
ale-0524 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | MM-IssueLoc: A Controlled Benchmark for Evaluating Visual Evidence in Multimodal Repository-Level Issue Localization | https://arxiv.org/abs/2607.15205 | external | arxiv.org | Provides 652 issue-PR instances across 23 languages, seven image categories, and four relevance levels; the strongest evaluated agent reaches 38.96 file Acc@5 and 22.45 function Acc@10, leaving substantial room for visual-evidence-aware repair loops. | Provides 652 issue-PR instances across 23 languages, seven image categories, and four relevance levels; the strongest evaluated agent reaches 38.96 file Acc@5 and 22.45 function Acc@10, leaving substantial room for visual-evidence-aware repair loops. | Provides 652 issue-PR instances across 23 languages, seven image categories, and four relevance levels; the strongest evaluated agent reaches 38.96 file Acc@5 and 22.45 function Acc@10, leaving substantial room for visual-evidence-aware repair loops. | The work turns loop quality into a measurable task or score. Provides 652 issue-PR instances across 23 languages, seven image categories, and four relevance levels; the strongest evaluated agent reaches 38.96 file Acc@5 and 22.45 function Acc@10, leaving substantial room for visual-evidence-aware repair loops. | Use MM-IssueLoc: A Controlled Benchmark for Evaluating Visual Evidence in Multimodal Repository-Level Issue Localization to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,239 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1239 | 2026-07-17 | Verify | verify | Gate progress with tests, evals, and evidence. | intake;verification | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://arxiv.org/abs/2607.15205 | [2607.15205] MM-IssueLoc: A Controlled Benchmark for Evaluating Visual Evidence in Multimodal Repository-Level Issue Localization | Real repository issues routinely include visual evidence such as screenshots, error dialogs, rendered UI states, and logs, yet repository-level issue localization is evaluated mostly as a text-only task. Existing multimodal SE benchmarks evaluate end-to-end repair, entangling localization with patch synthesis and obscu... | Shaoxiong Zhan; Shi Hu; Boyu Feng; Hai Lin; Andrew Gong; Zhengda Zhou; Jiaying Zhou; Yunyun Hou; Hao Su; Hai-Tao Zheng | 2026-07-16 | 2026 | arXiv | arXiv | cs.SE | arxiv-api | 2607.15205 | 2026-07-20T09:31:57 | ||||||||
ale-0525 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | ToolVerse: Unlocking Massive Environments and Long-Horizon Tasks for Agentic Reinforcement Learning | https://arxiv.org/abs/2607.15660 | external | arxiv.org | Builds executable long-horizon training environments from nearly 400 MCP servers and about 4,500 tools, generates tasks from tool-dependency graphs, and introduces turn-aware credit assignment for agentic reinforcement learning in large, dynamic tool spaces. | Builds executable long-horizon training environments from nearly 400 MCP servers and about 4,500 tools, generates tasks from tool-dependency graphs, and introduces turn-aware credit assignment for agentic reinforcement learning in large, dynamic tool spaces. | Builds executable long-horizon training environments from nearly 400 MCP servers and about 4,500 tools, generates tasks from tool-dependency graphs, and introduces turn-aware credit assignment for agentic reinforcement learning in large, dynamic tool spaces. | Control flow is represented as an inspectable graph rather than an opaque prompt loop. Builds executable long-horizon training environments from nearly 400 MCP servers and about 4,500 tools, generates tasks from tool-dependency graphs, and introduces turn-aware credit assignment for agentic reinforcement learning in la... | Use ToolVerse: Unlocking Massive Environments and Long-Horizon Tasks for Agentic Reinforcement Learning to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,240 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1240 | 2026-07-20 | Verify | verify | Gate progress with tests, evals, and evidence. | workspace | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://arxiv.org/abs/2607.15660 | [2607.15660] ToolVerse: Unlocking Massive Environments and Long-Horizon Tasks for Agentic Reinforcement Learning | While LLM agents demonstrate strong reasoning abilities in compact and well-defined scenarios, they struggle to maintain robustness and effectiveness when faced with large-scale, diverse, and dynamic real-world environments that demand seamless tool integration. To address this gap, we introduce ToolVerse, a comprehens... | Shuaiyu Zhou; Fengpeng Yue; Zengjie Hu; Yuanzhe Shen; Chenyang Zhang; feng hong; Cao Liu; Ke Zeng | 2026-07-17 | 2026 | arXiv | arXiv | cs.AI | arxiv-api | 2607.15660 | 2026-07-20T09:31:57 | ||||||||
ale-0526 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | MobileWorld: Benchmarking Autonomous Mobile Agents in Agent-User Interaction and MCP-Augmented Tasks | https://aclanthology.org/2026.acl-long.278/ | external | aclanthology.org | Evaluates long-horizon mobile work that requires clarification and MCP tool use in reproducible self-hosted environments with deterministic backend, storage, and callback verification. | Evaluates long-horizon mobile work that requires clarification and MCP tool use in reproducible self-hosted environments with deterministic backend, storage, and callback verification. | Evaluates long-horizon mobile work that requires clarification and MCP tool use in reproducible self-hosted environments with deterministic backend, storage, and callback verification. | Verification is promoted from a final check to a loop-control signal. Evaluates long-horizon mobile work that requires clarification and MCP tool use in reproducible self-hosted environments with deterministic backend, storage, and callback verification. | Use MobileWorld: Benchmarking Autonomous Mobile Agents in Agent-User Interaction and MCP-Augmented Tasks to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,244 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1244 | 2026-07-18 | Verify | verify | Gate progress with tests, evals, and evidence. | workspace;verification | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://aclanthology.org/2026.acl-long.278/ | MobileWorld: Benchmarking Autonomous Mobile Agents in Agent-User Interactive and MCP-Augmented Environments - ACL Anthology | Quyu Kong, Xu Zhang, Zhenyu Yang, Nolan Gao, Chen Liu, Panrong Tong, Chenglin Cai, Hanzhang Zhou, Jianan Zhang, Liangyu Chen, Zhidan Liu, Steven Hoi, Yue Wang. Proceedings of the 64th Annual Meeting of the Association for Computational Linguistics (Volume 1: Long Papers). 2026. | Quyu Kong; Xu Zhang; Zhenyu Yang; Nolan Gao; Chen Liu; Panrong Tong; Chenglin Cai; Hanzhang Zhou; Jianan Zhang; Liangyu Chen; Zhidan Liu; Steven Hoi; Yue Wang | 2026 | 2026 | Proceedings of the 64th Annual Meeting of the Association for Computational Linguistics (Volume 1: Long Papers) | ACL Anthology | 10.18653/v1/2026.acl-long.278 | html-meta | 2026-07-20T09:31:57 | |||||||||
ale-0527 | Benchmarks And Evaluation | benchmarks-and-evaluation | Benchmark | 🧪 | AGENCYBENCH: Benchmarking the Frontiers of Autonomous Agents | https://aclanthology.org/2026.acl-long.337/ | external | aclanthology.org | Provides 138 high-fidelity tasks across six capabilities whose average rollout exceeds one million tokens and 90 tool calls, exposing context-retention and long-horizon execution limits. | Provides 138 high-fidelity tasks across six capabilities whose average rollout exceeds one million tokens and 90 tool calls, exposing context-retention and long-horizon execution limits. | Provides 138 high-fidelity tasks across six capabilities whose average rollout exceeds one million tokens and 90 tool calls, exposing context-retention and long-horizon execution limits. | Context is managed as durable loop state rather than a single prompt payload. Provides 138 high-fidelity tasks across six capabilities whose average rollout exceeds one million tokens and 90 tool calls, exposing context-retention and long-horizon execution limits. | Use AGENCYBENCH: Benchmarking the Frontiers of Autonomous Agents to measure progress and gate completion with repeatable evidence. | Benchmark or leaderboard source with repeatable tasks or scores; compare systems only after checking setup and scope. | high | README.md | 1,245 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1245 | 2026-07-18 | Verify | verify | Gate progress with tests, evals, and evidence. | workspace;context;budget | researcher;evaluator | evaluation | enabling | benchmark | A | ok | https://aclanthology.org/2026.acl-long.337/ | AgencyBench: Benchmarking the Frontiers of Autonomous Agents in 1M-Token Real-World Contexts - ACL Anthology | Keyu Li, Junhao Shi, Yang Xiao, Mohan Jiang, Jie Sun, Yunze Wu, Dayuan Fu, Shijie Xia, Xiaojie Cai, Tianze Xu, Weiye Si, Wenjie Li, Dequan Wang, Pengfei Liu. Proceedings of the 64th Annual Meeting of the Association for Computational Linguistics (Volume 1: Long Papers). 2026. | Keyu Li; Junhao Shi; Yang Xiao; Mohan Jiang; Jie Sun; Yunze Wu; Dayuan Fu; Shijie Xia; Xiaojie Cai; Tianze Xu; Weiye Si; Wenjie Li; Dequan Wang; Pengfei Liu | 2026 | 2026 | Proceedings of the 64th Annual Meeting of the Association for Computational Linguistics (Volume 1: Long Papers) | ACL Anthology | 10.18653/v1/2026.acl-long.337 | html-meta | 2026-07-20T09:31:57 | |||||||||
ale-0528 | Operations Playbooks | operations-playbooks | Blog | 📝 | Agentic Engineering: The Agent Loop | https://junpingyi.com/books/agentic-engineering/agent-loop/ | external | junpingyi.com | Minimal mental model for the loop underlying agent operation. | Minimal mental model for the loop underlying agent operation. | Minimal mental model for the loop underlying agent operation. | Translates agent-loop ideas into operator-facing workflows for repeated delegated work. Minimal mental model for the loop underlying agent operation. | Use Agentic Engineering: The Agent Loop to bound risk before recurring or unattended execution. | Contextual source from junpingyi.com; useful for practice signals or boundary conditions, not independent validation. | contextual | README.md | 1,253 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1253 | Govern | govern | Bound permissions, cost, failure, and escalation. | trigger;intake;budget;escalation;exit | operator;security | operations | direct | practitioner-analysis | B | ok | https://junpingyi.com/books/agentic-engineering/agent-loop/ | Chapter 1: The Agent Loop — Agentic Engineering: How to Build AI Agents Like Claude Code | Chapter 1: The Agent Loop from Agentic Engineering: How to Build AI Agents Like Claude Code | junpingyi.com | domain-fallback | 2026-07-20T09:31:57 | |||||||||||||||
ale-0529 | Operations Playbooks | operations-playbooks | Blog | 📝 | The agent loop: ReAct, plan-and-execute, reflection | https://www.kunwar.page/chapter/067-the-agent-loop-react-plan-and-execute-reflection | external | www.kunwar.page | Practical walkthrough of the base loop and common variants. | Practical walkthrough of the base loop and common variants. | Practical walkthrough of the base loop and common variants. | Translates agent-loop ideas into operator-facing workflows for repeated delegated work. Practical walkthrough of the base loop and common variants. | Use The agent loop: ReAct, plan-and-execute, reflection to bound risk before recurring or unattended execution. | Contextual source from www.kunwar.page; useful for practice signals or boundary conditions, not independent validation. | contextual | README.md | 1,254 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1254 | Govern | govern | Bound permissions, cost, failure, and escalation. | trigger;intake;budget;escalation;exit | operator;security | operations | direct | practitioner-analysis | B | ok | https://www.kunwar.page/chapter/067-the-agent-loop-react-plan-and-execute-reflection | Chapter 67: The agent loop: ReAct, plan-and-execute, reflection — The Holy Grail Basic agent loop: generate, check for tool calls, execute tools and loop back, or return final answer on no tool call. ReAct interleaves Thought, Action, and Observation triplets; each Thought improves the next Action choice by externalizi... | An agent is a loop of `model.generate()` calls with tool calls in between. The loop is the entire pattern | kunwar.page | domain-fallback | 2026-07-20T09:31:57 | |||||||||||||||
ale-0530 | Operations Playbooks | operations-playbooks | Blog | 📝 | How to Build an Agent | https://ampcode.com/how-to-build-an-agent | external | ampcode.com | Thorsten Ball's demystification of the inner agent loop: a model, a loop, and enough tokens. | Thorsten Ball's demystification of the inner agent loop: a model, a loop, and enough tokens. | Thorsten Ball's demystification of the inner agent loop: a model, a loop, and enough tokens. | Translates agent-loop ideas into operator-facing workflows for repeated delegated work. Thorsten Ball's demystification of the inner agent loop: a model, a loop, and enough tokens. | Use How to Build an Agent to bound risk before recurring or unattended execution. | Contextual source from ampcode.com; useful for practice signals or boundary conditions, not independent validation. | contextual | README.md | 1,255 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1255 | Govern | govern | Bound permissions, cost, failure, and escalation. | budget | operator;security | operations | direct | practitioner-analysis | B | ok | https://ampcode.com/notes/how-to-build-an-agent | How to Build an Agent - Amp | Building a fully functional, code-editing agent in less than 400 lines. | ampcode.com | domain-fallback | 2026-07-20T09:31:57 | |||||||||||||||
ale-0531 | Operations Playbooks | operations-playbooks | Blog | 📝 | Agentic Coding Recommendations | https://lucumr.pocoo.org/2025/6/12/agentic-coding/ | external | lucumr.pocoo.org | Armin Ronacher's field notes on which practices hold up when agents do most of the work. | Armin Ronacher's field notes on which practices hold up when agents do most of the work. | Armin Ronacher's field notes on which practices hold up when agents do most of the work. | Translates agent-loop ideas into operator-facing workflows for repeated delegated work. Armin Ronacher's field notes on which practices hold up when agents do most of the work. | Use Agentic Coding Recommendations to bound risk before recurring or unattended execution. | Contextual source from lucumr.pocoo.org; useful for practice signals or boundary conditions, not independent validation. | contextual | README.md | 1,256 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1256 | Govern | govern | Bound permissions, cost, failure, and escalation. | trigger;intake;budget;escalation;exit | operator;security | operations | direct | practitioner-analysis | B | ok | https://lucumr.pocoo.org/2025/6/12/agentic-coding/ | Agentic Coding Recommendations | Armin Ronacher's Thoughts and Writings | Current recommendations of agentic coding. | 2025-06-12 | 2025 | Armin Ronacher's Thoughts and Writings | html-meta | 2026-07-20T09:31:57 | |||||||||||||
ale-0532 | Operations Playbooks | operations-playbooks | Blog | 📝 | Coding Agents 101: The Art of Actually Getting Things Done | https://devin.ai/agents101 | external | devin.ai | Practical delegation guidance from the Devin team on scoping tasks agents can actually finish. | Practical delegation guidance from the Devin team on scoping tasks agents can actually finish. | Practical delegation guidance from the Devin team on scoping tasks agents can actually finish. | Translates agent-loop ideas into operator-facing workflows for repeated delegated work. Practical delegation guidance from the Devin team on scoping tasks agents can actually finish. | Use Coding Agents 101: The Art of Actually Getting Things Done to bound risk before recurring or unattended execution. | Contextual source from devin.ai; useful for practice signals or boundary conditions, not independent validation. | contextual | README.md | 1,257 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1257 | Govern | govern | Bound permissions, cost, failure, and escalation. | delegation;exit | operator;security | operations | direct | practitioner-analysis | B | ok | https://devin.ai/agents101 | Coding Agents 101: The Art of Actually Getting Things Done | Coding Agents 101: The Art of Actually Getting Things Done | devin.ai | domain-fallback | 2026-07-20T09:31:57 | |||||||||||||||
ale-0533 | Operations Playbooks | operations-playbooks | Blog | 📝 | How Anthropic teams use Claude Code | https://claude.com/blog/how-anthropic-teams-use-claude-code | external | claude.com | Cross-team field report of real recurring agent workflows in engineering, security, and data science. | Cross-team field report of real recurring agent workflows in engineering, security, and data science. | Cross-team field report of real recurring agent workflows in engineering, security, and data science. | Translates agent-loop ideas into operator-facing workflows for repeated delegated work. Cross-team field report of real recurring agent workflows in engineering, security, and data science. | Use How Anthropic teams use Claude Code to bound risk before recurring or unattended execution. | Contextual source from claude.com; useful for practice signals or boundary conditions, not independent validation. | contextual | README.md | 1,258 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1258 | Govern | govern | Bound permissions, cost, failure, and escalation. | trigger;intake;budget;escalation;exit | operator;security | operations | direct | practitioner-analysis | B | ok | https://claude.com/blog/how-anthropic-teams-use-claude-code | How Anthropic teams use Claude Code | Claude by Anthropic | Teams across Anthropic use Claude Code for everything from debugging production issues and navigating unfamiliar codebases to building custom automation tools. Here's how. | Claude | html-meta | 2026-07-20T09:31:57 | |||||||||||||||
ale-0534 | Operations Playbooks | operations-playbooks | Blog | 📝 | How Boris Uses Claude Code | https://howborisusesclaudecode.com/ | external | howborisusesclaudecode.com | Unofficial but concrete compilation of Boris Cherny's autonomous setups: parallel worktrees, auto mode, `/loop`, `/schedule`, dynamic workflows, and `/goal` completion conditions. | Unofficial but concrete compilation of Boris Cherny's autonomous setups: parallel worktrees, auto mode, `/loop`, `/schedule`, dynamic workflows, and `/goal` completion conditions. | Unofficial but concrete compilation of Boris Cherny's autonomous setups: parallel worktrees, auto mode, `/loop`, `/schedule`, dynamic workflows, and `/goal` completion conditions. | Workspace isolation is part of the loop design, not an afterthought. Unofficial but concrete compilation of Boris Cherny's autonomous setups: parallel worktrees, auto mode, `/loop`, `/schedule`, dynamic workflows, and `/goal` completion conditions. | Use How Boris Uses Claude Code to bound risk before recurring or unattended execution. | Contextual source from howborisusesclaudecode.com; useful for practice signals or boundary conditions, not independent validation. | contextual | README.md | 1,259 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1259 | Govern | govern | Bound permissions, cost, failure, and escalation. | objective;trigger;workspace;exit | operator;security | operations | direct | practitioner-analysis | B | ok | https://howborisusesclaudecode.com/ | Boris Cherny's Claude Code Tips — How He Actually Uses It (121+ Tips) | 121+ tips from Boris Cherny, creator of Claude Code, on his daily workflow: CLAUDE.md, worktrees, plan mode, hooks, subagents, and more. | @CarolinaCherry | How Boris Uses Claude Code | html-meta | 2026-07-20T09:31:57 | ||||||||||||||
ale-0535 | Operations Playbooks | operations-playbooks | Blog | 📝 | Agent of the Day: Copilot Agent PR Analysis | https://github.github.com/gh-aw/blog/2026-05-26-agent-of-the-day/ | external | github.github.com | Official walkthrough of a daily scheduled agentic workflow that ingests PR data, analyzes it, and publishes findings to a Discussion, a concrete recurring loop with trigger, intake, analysis, and output. | Official walkthrough of a daily scheduled agentic workflow that ingests PR data, analyzes it, and publishes findings to a Discussion, a concrete recurring loop with trigger, intake, analysis, and output. | Official walkthrough of a daily scheduled agentic workflow that ingests PR data, analyzes it, and publishes findings to a Discussion, a concrete recurring loop with trigger, intake, analysis, and output. | Primary-source operational guidance rather than commentary. Official walkthrough of a daily scheduled agentic workflow that ingests PR data, analyzes it, and publishes findings to a Discussion, a concrete recurring loop with trigger, intake, analysis, and output. | Use Agent of the Day: Copilot Agent PR Analysis to bound risk before recurring or unattended execution. | Contextual source from github.github.com; useful for practice signals or boundary conditions, not independent validation. | contextual | README.md | 1,260 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1260 | Govern | govern | Bound permissions, cost, failure, and escalation. | trigger;intake | operator;security | operations | direct | practitioner-analysis | B | ok | https://github.github.com/gh-aw/blog/2026-05-26-agent-of-the-day/ | Agent of the Day – May 26, 2026 | GitHub Agentic Workflows | Copilot Agent PR Analysis: a daily workflow that monitors GitHub Copilot coding agent performance across pull requests | 2026 | GitHub Agentic Workflows | html-meta | 2026-07-20T09:31:57 | ||||||||||||||
ale-0536 | Operations Playbooks | operations-playbooks | Paper | 📄 | Progressive Crystallization: Turning Agent Exploration into Deterministic, Lower-Cost Workflows | https://arxiv.org/abs/2607.07052 | external | arxiv.org | Production lifecycle in which repeatedly validated agent-loop behaviors are promoted into deterministic workflows and demoted on regression, cutting per-incident agent cost by over 70% across eight months of a cloud AIOps system. | Production lifecycle in which repeatedly validated agent-loop behaviors are promoted into deterministic workflows and demoted on regression, cutting per-incident agent cost by over 70% across eight months of a cloud AIOps system. | Production lifecycle in which repeatedly validated agent-loop behaviors are promoted into deterministic workflows and demoted on regression, cutting per-incident agent cost by over 70% across eight months of a cloud AIOps system. | Translates agent-loop ideas into operator-facing workflows for repeated delegated work. Production lifecycle in which repeatedly validated agent-loop behaviors are promoted into deterministic workflows and demoted on regression, cutting per-incident agent cost by over 70% across eight months of a cloud AIOps system. | Use Progressive Crystallization: Turning Agent Exploration into Deterministic, Lower-Cost Workflows to bound risk before recurring or unattended execution. | Research source arXiv:2607.07052; inspect its method and evaluation before treating results as production evidence. | medium | README.md | 1,261 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1261 | Govern | govern | Bound permissions, cost, failure, and escalation. | budget | researcher;evaluator;operator;security | operations | direct | research-preprint | A | ok | https://arxiv.org/abs/2607.07052 | [2607.07052] Progressive Crystallization: Turning Agent Exploration into Deterministic, Lower-Cost Workflows in Production | AI agents deployed for IT operations are typically permanent cost centers because every execution requires full LLM inference, even for previously solved problems. This paper introduces progressive crystallization, a lifecycle that treats agent exploration as a discovery mechanism rather than a permanent execution mode... | Arun Malik | 2026-07-08 | 2026 | arXiv | arXiv | Conference-style paper; 10 pages (estimated from manuscript formatting if applicable); focuses on agentic AI, AIOps, workflow automation, deterministic execution, and LLM cost optimization | cs.SE | arxiv-api | 2607.07052 | 2026-07-20T09:31:57 | ||||||||
ale-0537 | Operations Playbooks | operations-playbooks | Paper | 📄 | Tool-Making and Self-Evolving LLM Agents in Low-Latency Systems | https://arxiv.org/abs/2607.08010 | external | arxiv.org | Production tool-making pipeline that mines live execution traces to compile recurring SOP steps into validated, versioned tools agents call instead of regenerating code, cutting median latency 42% and errors up to 53% in a fulfillment-center alarm-triage deployment. | Production tool-making pipeline that mines live execution traces to compile recurring SOP steps into validated, versioned tools agents call instead of regenerating code, cutting median latency 42% and errors up to 53% in a fulfillment-center alarm-triage deployment. | Production tool-making pipeline that mines live execution traces to compile recurring SOP steps into validated, versioned tools agents call instead of regenerating code, cutting median latency 42% and errors up to 53% in a fulfillment-center alarm-triage deployment. | Translates agent-loop ideas into operator-facing workflows for repeated delegated work. Production tool-making pipeline that mines live execution traces to compile recurring SOP steps into validated, versioned tools agents call instead of regenerating code, cutting median latency 42% and errors up to 53% in a fulfillme... | Use Tool-Making and Self-Evolving LLM Agents in Low-Latency Systems to bound risk before recurring or unattended execution. | Research source arXiv:2607.08010; inspect its method and evaluation before treating results as production evidence. | medium | README.md | 1,262 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1262 | Govern | govern | Bound permissions, cost, failure, and escalation. | intake;workspace | researcher;evaluator;operator;security | operations | direct | research-preprint | A | ok | https://arxiv.org/abs/2607.08010 | [2607.08010] Tool-Making and Self-Evolving LLM Agents in Low-Latency Systems | Production LLM agents often waste latency and reliability by regenerating code for the same procedural steps on every request. We replace this inference-time coding loop with an agentic tool-making pipeline that compiles repeated SOP steps into validated, versioned tools before deployment. The tool-maker grounds synthe... | Kalle Kujanpää; Ning Liu; Shahnawaz Alam; Yeshwanth Reddy Sura; Tianyu Yang; Kristina Klinkner; Shervin Malmasi | 2026-07-09 | 2026 | arXiv | arXiv | Preprint | cs.CL | arxiv-api | 2607.08010 | 2026-07-20T09:31:57 | ||||||||
ale-0538 | Operations Playbooks | operations-playbooks | Blog | 📝 | AI Loop Engineering: Build Autonomous Agents with Claude Code /goal and Routines | https://www.sabrina.dev/p/loop-engineering-claude-code-goal-routines | external | www.sabrina.dev | Sabrina Ramonov's practitioner walkthrough of building verified loops with Claude Code `/goal` and cloud routines: a six-part loop-engineering framework, five worked examples each with a verifiable end state, and a production daily support-ticket cleanup routine whose independent checker agents illustrate why the check... | Sabrina Ramonov's practitioner walkthrough of building verified loops with Claude Code `/goal` and cloud routines: a six-part loop-engineering framework, five worked examples each with a verifiable end state, and a production daily support-ticket cleanup routine whose independent checker agents illustrate why the check... | Sabrina Ramonov's practitioner walkthrough of building verified loops with Claude Code `/goal` and cloud routines: a six-part loop-engineering framework, five worked examples each with a verifiable end state, and a production daily support-ticket cleanup routine whose independent checker agents illustrate why the check... | Verification is promoted from a final check to a loop-control signal. Sabrina Ramonov's practitioner walkthrough of building verified loops with Claude Code `/goal` and cloud routines: a six-part loop-engineering framework, five worked examples each with a verifiable end state, and a production daily support-ticket cle... | Use AI Loop Engineering: Build Autonomous Agents with Claude Code /goal and Routines to bound risk before recurring or unattended execution. | Contextual source from www.sabrina.dev; useful for practice signals or boundary conditions, not independent validation. | contextual | README.md | 1,263 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1263 | Govern | govern | Bound permissions, cost, failure, and escalation. | objective;verification;state | operator;security | operations | direct | practitioner-analysis | B | ok | https://www.sabrina.dev/p/loop-engineering-claude-code-goal-routines | AI Loop Engineering: Build Autonomous Agents with Claude Code /goal + Routines | What loop engineering means in 2026, how to use the Claude Code /goal command, and how to build your first autonomous AI agent with a routine. | Sabrina Ramonov 🍄 | sabrina.dev | html-meta | 2026-07-20T09:31:57 | ||||||||||||||
ale-0539 | Operations Playbooks | operations-playbooks | Paper | 📄 | Agent Delivery Engineering Predictive Reliability Framework | https://arxiv.org/abs/2607.07689 | external | arxiv.org | Proactive health-trajectory prediction for long-horizon multi-agent systems, aggregating 20 heterogeneous signals across five layers into a trust-margin metric with 8-hour forecasts at 76.8% direction accuracy, detecting degradation concealed by normal surface metrics across 15 days of production traffic. | Proactive health-trajectory prediction for long-horizon multi-agent systems, aggregating 20 heterogeneous signals across five layers into a trust-margin metric with 8-hour forecasts at 76.8% direction accuracy, detecting degradation concealed by normal surface metrics across 15 days of production traffic. | Proactive health-trajectory prediction for long-horizon multi-agent systems, aggregating 20 heterogeneous signals across five layers into a trust-margin metric with 8-hour forecasts at 76.8% direction accuracy, detecting degradation concealed by normal surface metrics across 15 days of production traffic. | The work separates roles across agents, verifiers, or orchestration layers. Proactive health-trajectory prediction for long-horizon multi-agent systems, aggregating 20 heterogeneous signals across five layers into a trust-margin metric with 8-hour forecasts at 76.8% direction accuracy, detecting degradation concealed b... | Use Agent Delivery Engineering Predictive Reliability Framework to bound risk before recurring or unattended execution. | Research source arXiv:2607.07689; inspect its method and evaluation before treating results as production evidence. | medium | README.md | 1,264 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1264 | Govern | govern | Bound permissions, cost, failure, and escalation. | delegation | researcher;evaluator;operator;security | operations | direct | research-preprint | A | ok | https://arxiv.org/abs/2607.07689 | [2607.07689] Agent Delivery Engineering Predictive Reliability Framework | Long-horizon LLM multi-agent systems face reliability risks invisible to infrastructure monitoring. We propose the ADE Predictive Reliability Framework (ADE-PRF), enabling proactive health trajectory prediction from passive degradation detection. ADE-PRF aggregates 20 heterogeneous signals across five layers into a Tru... | Dexing Liu | 2026-07-08 | 2026 | arXiv | arXiv | 117pages,83figures | cs.MA | arxiv-api | 2607.07689 | 2026-07-20T09:31:57 | ||||||||
ale-0540 | Operations Playbooks | operations-playbooks | Paper | 📄 | CADAQUES: A Cost-Aware Dual Architecture for Query-Efficient Autonomous Discovery | https://arxiv.org/abs/2607.16127 | external | arxiv.org | Makes cost part of the loop contract: an Oracle executes queries, a Driver chooses them, a shared vector budget covers wall time, CPU, money, and LLM tokens, and an append-only ledger records declared versus settled cost for every transaction. The Ising-model case study shows how mixed-fidelity scheduling can outperfor... | Makes cost part of the loop contract: an Oracle executes queries, a Driver chooses them, a shared vector budget covers wall time, CPU, money, and LLM tokens, and an append-only ledger records declared versus settled cost for every transaction. The Ising-model case study shows how mixed-fidelity scheduling can outperfor... | Makes cost part of the loop contract: an Oracle executes queries, a Driver chooses them, a shared vector budget covers wall time, CPU, money, and LLM tokens, and an append-only ledger records declared versus settled cost for every transaction. The Ising-model case study shows how mixed-fidelity scheduling can outperfor... | The trigger or cadence is explicit, making the workflow recurring rather than one-off. Makes cost part of the loop contract: an Oracle executes queries, a Driver chooses them, a shared vector budget covers wall time, CPU, money, and LLM tokens, and an append-only ledger records declared versus settled cost for every tr... | Use CADAQUES: A Cost-Aware Dual Architecture for Query-Efficient Autonomous Discovery to bound risk before recurring or unattended execution. | Research source arXiv:2607.16127; inspect its method and evaluation before treating results as production evidence. | medium | README.md | 1,265 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1265 | 2026-07-20 | Govern | govern | Bound permissions, cost, failure, and escalation. | trigger;intake;verification;budget | researcher;evaluator;operator;security | operations | direct | research-preprint | A | ok | https://arxiv.org/abs/2607.16127 | [2607.16127] CADAQUES: A Cost-Aware Dual Architecture for Query-Efficient Autonomous Discovery | Autonomous discovery systems couple a resource that answers queries (a simulator, instrument, or analytic model) to an algorithm that selects what to query next. Most software frameworks for this loop inherit the control structure of numerical optimization: campaigns run for a fixed number of iterations, query costs ar... | Jorge Bravo-Abad | 2026-07-17 | 2026 | arXiv | arXiv | physics.comp-ph | arxiv-api | 2607.16127 | 2026-07-20T09:31:57 | ||||||||
ale-0541 | Operations Playbooks | operations-playbooks | Tool | 🧰 | rocketplaneIO | https://github.com/olemeyer/rocketplaneIO | external | github.com | Self-hosted AI SRE for Kubernetes whose copilot investigates autonomously via eBPF traces, logs, and live service maps, but can only act through named, reversible, risk-graded operations. | Self-hosted AI SRE for Kubernetes whose copilot investigates autonomously via eBPF traces, logs, and live service maps, but can only act through named, reversible, risk-graded operations. | Self-hosted AI SRE for Kubernetes whose copilot investigates autonomously via eBPF traces, logs, and live service maps, but can only act through named, reversible, risk-graded operations. | Translates agent-loop ideas into operator-facing workflows for repeated delegated work. Self-hosted AI SRE for Kubernetes whose copilot investigates autonomously via eBPF traces, logs, and live service maps, but can only act through named, reversible, risk-graded operations. | Use rocketplaneIO to bound risk before recurring or unattended execution. | Inspectable GitHub source (194 stars; 3 forks; Apache-2.0 license; updated 2026-07-20); popularity is context, not proof of reliability. | medium | README.md | 1,266 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1266 | Govern | govern | Bound permissions, cost, failure, and escalation. | trigger;intake;budget;escalation;exit | builder;operator;security | operations | direct | source-implementation | A | ok | https://github.com/olemeyer/rocketplaneIO | GitHub - olemeyer/rocketplaneIO: Self-hosted AI SRE for Kubernetes — zero-instrumentation eBPF observability plus a copilot that fixes issues through guardrailed, self-verifying actions. BYO-LLM, air-gapped capable. · GitHub | Self-hosted AI SRE for Kubernetes — zero-instrumentation eBPF observability plus a copilot that fixes issues through guardrailed, self-verifying actions. BYO-LLM, air-gapped capable. - olemeyer/rocketplaneIO | 2026-07-06 | 2026 | olemeyer/rocketplaneIO | GitHub | github-api | olemeyer/rocketplaneIO | 194 | 3 | Apache-2.0 | 2026-07-06T11:24:01Z | 2026-07-20T09:33:23Z | 2026-07-20T09:31:57 | ||||||
ale-0542 | Operations Playbooks | operations-playbooks | Blog | 📝 | Migrating a Production AI Agent to GPT-5.6 | https://ploy.ai/blog/migrating-a-production-ai-agent-to-gpt-5-6 | external | ploy.ai | Lorenzo Gentile's July 2026 case study of swapping the model inside Ploy's production website-building agent (plans pages, writes components, screenshots its own work, decides when done): roughly a third of initial cross-model eval failures traced to Opus-specific harness assumptions rather than the new model, GPT-5.6 ... | Lorenzo Gentile's July 2026 case study of swapping the model inside Ploy's production website-building agent (plans pages, writes components, screenshots its own work, decides when done): roughly a third of initial cross-model eval failures traced to Opus-specific harness assumptions rather than the new model, GPT-5.6 ... | Lorenzo Gentile's July 2026 case study of swapping the model inside Ploy's production website-building agent (plans pages, writes components, screenshots its own work, decides when done): roughly a third of initial cross-model eval failures traced to Opus-specific harness assumptions rather than the new model, GPT-5.6 ... | Evaluation data is used as the feedback signal for improving loop behavior. Lorenzo Gentile's July 2026 case study of swapping the model inside Ploy's production website-building agent (plans pages, writes components, screenshots its own work, decides when done): roughly a third of initial cross-model eval failures tra... | Use Migrating a Production AI Agent to GPT-5.6 to bound risk before recurring or unattended execution. | Contextual source from ploy.ai; useful for practice signals or boundary conditions, not independent validation. | contextual | README.md | 1,267 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1267 | Govern | govern | Bound permissions, cost, failure, and escalation. | workspace;verification;state;exit | operator;security | operations | direct | practitioner-analysis | B | ok | https://ploy.ai/blog/migrating-a-production-ai-agent-to-gpt-5-6 | Migrating a production AI agent to GPT-5.6 | Ploy | For four months, no frontier model beat Claude Opus in our production evals. GPT-5.6 did. This is what we learned while migrating. | Ploy | html-meta | 2026-07-20T09:31:57 | |||||||||||||||
ale-0543 | Operations Playbooks | operations-playbooks | Paper | 📄 | Coding-agents can replicate scientific machine learning papers | https://arxiv.org/abs/2607.02134 | external | arxiv.org | Runs coding agents independently 12 times across four scientific machine-learning papers; all workspaces satisfy the study's completion criteria, and 158 implementation targets are linked to report evidence, offering a concrete playbook for evidence-backed research replication. | Runs coding agents independently 12 times across four scientific machine-learning papers; all workspaces satisfy the study's completion criteria, and 158 implementation targets are linked to report evidence, offering a concrete playbook for evidence-backed research replication. | Runs coding agents independently 12 times across four scientific machine-learning papers; all workspaces satisfy the study's completion criteria, and 158 implementation targets are linked to report evidence, offering a concrete playbook for evidence-backed research replication. | Translates agent-loop ideas into operator-facing workflows for repeated delegated work. Runs coding agents independently 12 times across four scientific machine-learning papers; all workspaces satisfy the study's completion criteria, and 158 implementation targets are linked to report evidence, offering a concrete play... | Use Coding-agents can replicate scientific machine learning papers to bound risk before recurring or unattended execution. | Research source arXiv:2607.02134; inspect its method and evaluation before treating results as production evidence. | medium | README.md | 1,268 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1268 | 2026-07-17 | Govern | govern | Bound permissions, cost, failure, and escalation. | workspace;exit | researcher;evaluator;operator;security | operations | direct | research-preprint | A | ok | https://arxiv.org/abs/2607.02134 | [2607.02134] Coding-agents can replicate scientific machine learning papers | Scientific machine learning papers typically make computational claims, e.g., that the relative mean square error is less than 5% or that the 95% predictive credible interval covers the test data. A coding agent can be prompted to replicate those claims from paper materials alone, but the prompt does not by itself reli... | Atharva Hans; Ilias Bilionis | 2026-07-02 | 2026 | arXiv | arXiv | cs.AI | arxiv-api | 2607.02134 | 2026-07-20T09:31:57 | ||||||||
ale-0544 | Templates And Patterns | templates-and-patterns | Template | 🧾 | Resource entry template | templates/resource-entry.md | local_path | Format for adding a single resource with evidence quality and category fit. | Format for adding a single resource with evidence quality and category fit. | Format for adding a single resource with evidence quality and category fit. | The resource is directly reusable as a starting artifact. Format for adding a single resource with evidence quality and category fit. | Use Resource entry template to reuse a concrete artifact or connect it to the wider ecosystem. | Repository file; inspect the linked schema, example, guide, or implementation. | medium | README.md | 1,276 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1276 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | whole-loop | builder;operator | workflow | direct | repository-native | A | local_ok | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/templates/resource-entry.md | Resource entry template | 2026 | GitHub | GitHub | repository | 2026-07-20T09:31:57 | |||||||||||||||
ale-0545 | Templates And Patterns | templates-and-patterns | Template | 🧾 | Loop pattern template | templates/loop-pattern.md | local_path | Template for documenting an operational loop such as PR babysitting, CI repair, or feedback clustering. | Template for documenting an operational loop such as PR babysitting, CI repair, or feedback clustering. | Template for documenting an operational loop such as PR babysitting, CI repair, or feedback clustering. | The resource is directly reusable as a starting artifact. Template for documenting an operational loop such as PR babysitting, CI repair, or feedback clustering. | Use Loop pattern template to reuse a concrete artifact or connect it to the wider ecosystem. | Repository file; inspect the linked schema, example, guide, or implementation. | medium | README.md | 1,277 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1277 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | whole-loop | builder;operator | workflow | direct | repository-native | A | local_ok | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/templates/loop-pattern.md | Loop pattern template | 2026 | GitHub | GitHub | repository | 2026-07-20T09:31:57 | |||||||||||||||
ale-0546 | Templates And Patterns | templates-and-patterns | Template | 🧾 | Loop contract schema | schemas/loop-contract.schema.json | local_path | Machine-readable schema for portable loop specs. | Machine-readable schema for portable loop specs. | Machine-readable schema for portable loop specs. | The contribution is machine-readable and validation-friendly. Machine-readable schema for portable loop specs. | Use Loop contract schema to reuse a concrete artifact or connect it to the wider ecosystem. | Repository file; inspect the linked schema, example, guide, or implementation. | medium | README.md | 1,278 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1278 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | whole-loop | builder;operator | workflow | direct | repository-native | A | local_ok | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/schemas/loop-contract.schema.json | Loop contract schema | 2026 | GitHub | GitHub | repository | 2026-07-20T09:31:57 | |||||||||||||||
ale-0547 | Templates And Patterns | templates-and-patterns | Template | 🧾 | Loop contract preview script | scripts/preview_loop_contract.py | local_path | Dependency-free demo that validates and renders a loop contract JSON file. | Dependency-free demo that validates and renders a loop contract JSON file. | Dependency-free demo that validates and renders a loop contract JSON file. | The contribution is machine-readable and validation-friendly. Dependency-free demo that validates and renders a loop contract JSON file. | Use Loop contract preview script to reuse a concrete artifact or connect it to the wider ecosystem. | Repository file; inspect the linked schema, example, guide, or implementation. | medium | README.md | 1,279 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1279 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | whole-loop | builder;operator | workflow | direct | repository-native | A | local_ok | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/scripts/preview_loop_contract.py | Loop contract preview script | 2026 | GitHub | GitHub | repository | 2026-07-20T09:31:57 | |||||||||||||||
ale-0548 | Templates And Patterns | templates-and-patterns | Template | 🧾 | Translation guide | TRANSLATIONS.md | local_path | How to add or maintain a language translation without drifting from the full English guide. | How to add or maintain a language translation without drifting from the full English guide. | How to add or maintain a language translation without drifting from the full English guide. | The resource is directly reusable as a starting artifact. How to add or maintain a language translation without drifting from the full English guide. | Use Translation guide to reuse a concrete artifact or connect it to the wider ecosystem. | Repository file; inspect the linked schema, example, guide, or implementation. | medium | README.md | 1,280 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1280 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | whole-loop | builder;operator | workflow | direct | repository-native | A | local_ok | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/TRANSLATIONS.md | Translation guide | 2026 | GitHub | GitHub | repository | 2026-07-20T09:31:57 | |||||||||||||||
ale-0549 | Templates And Patterns | templates-and-patterns | Template | 🧾 | Pattern library index | patterns/README.md | local_path | Practical loop patterns with triggers, state, verification gates, budgets, and escalation paths. | Practical loop patterns with triggers, state, verification gates, budgets, and escalation paths. | Practical loop patterns with triggers, state, verification gates, budgets, and escalation paths. | Verification is promoted from a final check to a loop-control signal. Practical loop patterns with triggers, state, verification gates, budgets, and escalation paths. | Use Pattern library index to reuse a concrete artifact or connect it to the wider ecosystem. | Repository file; inspect the linked schema, example, guide, or implementation. | medium | README.md | 1,281 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1281 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | trigger;verification;state;budget;escalation | builder;operator | workflow | direct | repository-native | A | local_ok | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/patterns/README.md | Pattern library index | 2026 | GitHub | GitHub | repository | 2026-07-20T09:31:57 | |||||||||||||||
ale-0550 | Examples And Schema | examples-and-schema | Pattern | 🔁 | Loop contract catalog | examples/README.md | local_path | Connects all 20 patterns to schema-valid contracts, deterministic gates, durable receipts, and four worked implementation paths. | Connects all 20 patterns to schema-valid contracts, deterministic gates, durable receipts, and four worked implementation paths. | Connects all 20 patterns to schema-valid contracts, deterministic gates, durable receipts, and four worked implementation paths. | Durable execution and replay are treated as first-class loop infrastructure. Connects all 20 patterns to schema-valid contracts, deterministic gates, durable receipts, and four worked implementation paths. | Use Loop contract catalog to reuse a concrete artifact or connect it to the wider ecosystem. | Repository file; inspect the linked schema, example, guide, or implementation. | medium | README.md | 1,291 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1291 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | state | builder;operator | workflow | direct | repository-native | A | local_ok | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/examples/README.md | Loop contract catalog | 2026 | GitHub | GitHub | repository | 2026-07-20T09:31:57 | |||||||||||||||
ale-0551 | Examples And Schema | examples-and-schema | Template | 🧾 | Loop contract library | examples/README.md#contract-catalog | local_path | Adaptable contracts for build, operate, optimize, and govern loops, checked against the shared schema with explicit permissions, budgets, and handoffs. | Adaptable contracts for build, operate, optimize, and govern loops, checked against the shared schema with explicit permissions, budgets, and handoffs. | Adaptable contracts for build, operate, optimize, and govern loops, checked against the shared schema with explicit permissions, budgets, and handoffs. | The contribution is machine-readable and validation-friendly. Adaptable contracts for build, operate, optimize, and govern loops, checked against the shared schema with explicit permissions, budgets, and handoffs. | Use Loop contract library to reuse a concrete artifact or connect it to the wider ecosystem. | Repository file; inspect the linked schema, example, guide, or implementation. | medium | README.md | 1,292 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1292 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | workspace;delegation;budget | builder;operator | workflow | direct | repository-native | A | local_ok | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/examples/README.md#contract-catalog | Loop contract library | 2026 | GitHub | GitHub | repository | 2026-07-20T09:31:57 | |||||||||||||||
ale-0552 | Examples And Schema | examples-and-schema | Template | 🧾 | Runnable test-repair loop | examples/runnable/test-repair-loop.sh | local_path | Repeats a failing deterministic check with durable progress, duplicate-failure detection, and a hard retry budget. | Repeats a failing deterministic check with durable progress, duplicate-failure detection, and a hard retry budget. | Repeats a failing deterministic check with durable progress, duplicate-failure detection, and a hard retry budget. | Durable execution and replay are treated as first-class loop infrastructure. Repeats a failing deterministic check with durable progress, duplicate-failure detection, and a hard retry budget. | Use Runnable test-repair loop to reuse a concrete artifact or connect it to the wider ecosystem. | Repository file; inspect the linked schema, example, guide, or implementation. | medium | README.md | 1,293 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1293 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | verification;budget | builder;operator | workflow | direct | repository-native | A | local_ok | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/examples/runnable/test-repair-loop.sh | Runnable test-repair loop | 2026 | GitHub | GitHub | repository | 2026-07-20T09:31:57 | |||||||||||||||
ale-0553 | Examples And Schema | examples-and-schema | Template | 🧾 | Runnable loop guide | examples/runnable/README.md | local_path | Compares 8 starters by trigger, state, gate, and runtime, including executable test-repair, threshold-monitor, and queue-worker loops. | Compares 8 starters by trigger, state, gate, and runtime, including executable test-repair, threshold-monitor, and queue-worker loops. | Compares 8 starters by trigger, state, gate, and runtime, including executable test-repair, threshold-monitor, and queue-worker loops. | State persistence is explicit enough for repeated runs and handoff. Compares 8 starters by trigger, state, gate, and runtime, including executable test-repair, threshold-monitor, and queue-worker loops. | Use Runnable loop guide to reuse a concrete artifact or connect it to the wider ecosystem. | Repository file; inspect the linked schema, example, guide, or implementation. | medium | README.md | 1,294 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1294 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | trigger;intake;verification;state | builder;operator | workflow | direct | repository-native | A | local_ok | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/examples/runnable/README.md | Runnable loop guide | 2026 | GitHub | GitHub | repository | 2026-07-20T09:31:57 | |||||||||||||||
ale-0554 | Community Gallery | community-gallery | Template | 🧾 | Loop gallery guide | gallery/README.md | local_path | Quality bar for contributed loop examples with receipts and lessons learned. | Quality bar for contributed loop examples with receipts and lessons learned. | Quality bar for contributed loop examples with receipts and lessons learned. | The resource is directly reusable as a starting artifact. Quality bar for contributed loop examples with receipts and lessons learned. | Use Loop gallery guide to reuse a concrete artifact or connect it to the wider ecosystem. | Repository file; inspect the linked schema, example, guide, or implementation. | medium | README.md | 1,310 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1310 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | state | builder;operator | operations | direct | repository-native | A | local_ok | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/gallery/README.md | Loop gallery guide | 2026 | GitHub | GitHub | repository | 2026-07-20T09:31:57 | |||||||||||||||
ale-0555 | Community Gallery | community-gallery | Template | 🧾 | Loop gallery template | gallery/template.md | local_path | Markdown template for sharing a loop's trigger, intake, state, verification, escalation, and safety notes. | Markdown template for sharing a loop's trigger, intake, state, verification, escalation, and safety notes. | Markdown template for sharing a loop's trigger, intake, state, verification, escalation, and safety notes. | Verification is promoted from a final check to a loop-control signal. Markdown template for sharing a loop's trigger, intake, state, verification, escalation, and safety notes. | Use Loop gallery template to reuse a concrete artifact or connect it to the wider ecosystem. | Repository file; inspect the linked schema, example, guide, or implementation. | medium | README.md | 1,311 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1311 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | trigger;intake;verification;state;escalation | builder;operator | operations | direct | repository-native | A | local_ok | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/gallery/template.md | Loop gallery template | 2026 | GitHub | GitHub | repository | 2026-07-20T09:31:57 | |||||||||||||||
ale-0556 | Community Gallery | community-gallery | Pattern | 🔁 | PR babysitter reference loop | gallery/pr-babysitter-reference.md | local_path | Reference gallery entry for keeping a pull request moving. | Reference gallery entry for keeping a pull request moving. | Reference gallery entry for keeping a pull request moving. | Turns loop adoption into shareable cases with enough structure to compare lessons learned. Reference gallery entry for keeping a pull request moving. | Use PR babysitter reference loop to reuse a concrete artifact or connect it to the wider ecosystem. | Repository file; inspect the linked schema, example, guide, or implementation. | medium | README.md | 1,312 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1312 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | whole-loop | builder;operator | operations | direct | repository-native | A | local_ok | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/gallery/pr-babysitter-reference.md | PR babysitter reference loop | 2026 | GitHub | GitHub | repository | 2026-07-20T09:31:57 | |||||||||||||||
ale-0557 | Community Gallery | community-gallery | Pattern | 🔁 | CI repair reference loop | gallery/ci-repair-reference.md | local_path | Reference gallery entry for turning failing CI into a verified patch or escalation. | Reference gallery entry for turning failing CI into a verified patch or escalation. | Reference gallery entry for turning failing CI into a verified patch or escalation. | Verification is promoted from a final check to a loop-control signal. Reference gallery entry for turning failing CI into a verified patch or escalation. | Use CI repair reference loop to reuse a concrete artifact or connect it to the wider ecosystem. | Repository file; inspect the linked schema, example, guide, or implementation. | medium | README.md | 1,313 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1313 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | verification;escalation | builder;operator | operations | direct | repository-native | A | local_ok | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/gallery/ci-repair-reference.md | CI repair reference loop | 2026 | GitHub | GitHub | repository | 2026-07-20T09:31:57 | |||||||||||||||
ale-0558 | Community Gallery | community-gallery | Pattern | 🔁 | Docs drift reference loop | gallery/docs-drift-reference.md | local_path | Reference gallery entry for recurring docs/code consistency checks. | Reference gallery entry for recurring docs/code consistency checks. | Reference gallery entry for recurring docs/code consistency checks. | Turns loop adoption into shareable cases with enough structure to compare lessons learned. Reference gallery entry for recurring docs/code consistency checks. | Use Docs drift reference loop to reuse a concrete artifact or connect it to the wider ecosystem. | Repository file; inspect the linked schema, example, guide, or implementation. | medium | README.md | 1,314 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1314 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | whole-loop | builder;operator | operations | direct | repository-native | A | local_ok | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/gallery/docs-drift-reference.md | Docs drift reference loop | 2026 | GitHub | GitHub | repository | 2026-07-20T09:31:57 | |||||||||||||||
ale-0559 | Critiques, Risks, And Limitations | critiques-risks-and-limitations | Critique | ⚠️ | Most Developers Do Not Need Agent Loops Yet | https://alphasignalai.substack.com/p/most-developers-do-not-need-agent | external | alphasignalai.substack.com | Useful caution against adopting loops before the task, signal, and economics justify them. | Useful caution against adopting loops before the task, signal, and economics justify them. | Useful caution against adopting loops before the task, signal, and economics justify them. | Keeps adoption grounded in known failure modes, economics, and operational limits. Useful caution against adopting loops before the task, signal, and economics justify them. | Use Most Developers Do Not Need Agent Loops Yet to bound risk before recurring or unattended execution. | Contextual source from alphasignalai.substack.com; useful for practice signals or boundary conditions, not independent validation. | contextual | README.md | 1,322 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1322 | Govern | govern | Bound permissions, cost, failure, and escalation. | budget;escalation;exit | operator;security | cross-layer | enabling | risk-analysis | B | ok | https://alphasignalai.substack.com/p/most-developers-do-not-need-agent | Most Developers Do Not Need Agent Loops Yet | The patterns were documented in 2024. Here’s who it pays off for, and the four conditions that decide. | AlphaSignal AI | Substack | html-meta | 2026-07-20T09:31:57 | ||||||||||||||
ale-0560 | Critiques, Risks, And Limitations | critiques-risks-and-limitations | Critique | ⚠️ | Engineering Agentic Systems for Reliability | https://pruningmypothos.com/systems/engineering-agentic-systems-for-reliability/ | external | pruningmypothos.com | Cautions that agentic systems fail at boundaries when permissions, verification, traceability, and escalation are weak. | Cautions that agentic systems fail at boundaries when permissions, verification, traceability, and escalation are weak. | Cautions that agentic systems fail at boundaries when permissions, verification, traceability, and escalation are weak. | Verification is promoted from a final check to a loop-control signal. Cautions that agentic systems fail at boundaries when permissions, verification, traceability, and escalation are weak. | Use Engineering Agentic Systems for Reliability to bound risk before recurring or unattended execution. | Contextual source from pruningmypothos.com; useful for practice signals or boundary conditions, not independent validation. | contextual | README.md | 1,323 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1323 | Govern | govern | Bound permissions, cost, failure, and escalation. | workspace;verification;escalation | operator;security | cross-layer | enabling | risk-analysis | B | ok | https://pruningmypothos.com/systems/engineering-agentic-systems-for-reliability/ | Engineering Agentic Systems for Reliability | Sans Serif Systems | A practical reliability model for agentic systems built around governed steps, verification, escalation, and observability. | Shailesh Rawat | Sans Serif Systems | html-meta | 2026-07-20T09:31:57 | ||||||||||||||
ale-0561 | Critiques, Risks, And Limitations | critiques-risks-and-limitations | Critique | ⚠️ | Self-Correcting Agents: Reflexion, CRITIC, and ReAct Loops Compared | https://callsphere.ai/blog/self-correcting-agents-reflexion-critic-react-loops-compared-2026 | external | callsphere.ai | Compares self-correction patterns and their cost/failure tradeoffs. | Compares self-correction patterns and their cost/failure tradeoffs. | Compares self-correction patterns and their cost/failure tradeoffs. | Keeps adoption grounded in known failure modes, economics, and operational limits. Compares self-correction patterns and their cost/failure tradeoffs. | Use Self-Correcting Agents: Reflexion, CRITIC, and ReAct Loops Compared to bound risk before recurring or unattended execution. | Contextual source from callsphere.ai; useful for practice signals or boundary conditions, not independent validation. | contextual | README.md | 1,324 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1324 | Govern | govern | Bound permissions, cost, failure, and escalation. | verification;budget | operator;security | cross-layer | enabling | risk-analysis | B | ok | https://callsphere.ai/blog/self-correcting-agents-reflexion-critic-react-loops-compared-2026 | Self-Correcting Agents: Reflexion, CRITIC, and ReAct Loops Compared | CallSphere Blog | Three self-correction patterns dominate 2026 agent design. Side-by-side analysis of where each one wins, where each one fails, and how to combine them. | CallSphere | 2026-04-24 | 2026 | CallSphere | html-meta | 2026-07-20T09:31:57 | ||||||||||||
ale-0562 | Critiques, Risks, And Limitations | critiques-risks-and-limitations | Critique | ⚠️ | How to Build an AI Agent Harness: A 2026 Complete Guide | https://atlan.com/know/how-to-build-ai-agent-harness/ | external | atlan.com | Broad guide with useful warnings on data readiness, permissions, context management, and evaluation. | Broad guide with useful warnings on data readiness, permissions, context management, and evaluation. | Broad guide with useful warnings on data readiness, permissions, context management, and evaluation. | Evaluation data is used as the feedback signal for improving loop behavior. Broad guide with useful warnings on data readiness, permissions, context management, and evaluation. | Use How to Build an AI Agent Harness: A 2026 Complete Guide to bound risk before recurring or unattended execution. | Contextual source from atlan.com; useful for practice signals or boundary conditions, not independent validation. | contextual | README.md | 1,325 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1325 | Govern | govern | Bound permissions, cost, failure, and escalation. | workspace;context;verification | operator;security | cross-layer | enabling | risk-analysis | B | ok | https://atlan.com/know/how-to-build-ai-agent-harness/ | How to Build an AI Agent Harness: Step-by-Step Tutorial (2026) | Most agent harnesses fail at the data layer, not the loop. Build one the right way in 10 steps, with code and a done test for each. Start at Step 0. | atlan.com | domain-fallback | 2026-07-20T09:31:57 | |||||||||||||||
ale-0563 | Critiques, Risks, And Limitations | critiques-risks-and-limitations | Critique | ⚠️ | Harness Engineering vs Prompt Engineering vs Context Engineering Explained | https://medium.com/@visrow/harness-engineering-vs-prompt-engineering-vs-context-engineering-explained-0423b692c87d | external | medium.com | Adjacent framing that helps avoid confusing loop engineering with the surrounding harness discipline. | Adjacent framing that helps avoid confusing loop engineering with the surrounding harness discipline. | Adjacent framing that helps avoid confusing loop engineering with the surrounding harness discipline. | Context is managed as durable loop state rather than a single prompt payload. Adjacent framing that helps avoid confusing loop engineering with the surrounding harness discipline. | Use Harness Engineering vs Prompt Engineering vs Context Engineering Explained to bound risk before recurring or unattended execution. | Contextual source from medium.com; useful for practice signals or boundary conditions, not independent validation. | contextual | README.md | 1,326 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1326 | Govern | govern | Bound permissions, cost, failure, and escalation. | context | operator;security | cross-layer | enabling | risk-analysis | B | ok | https://medium.com/@visrow/harness-engineering-vs-prompt-engineering-vs-context-engineering-explained-0423b692c87d | Medium Harness Engineering vs Prompt Engineering vs Context Engineering Explained | by Vishal Mysore | Medium | Harness Engineering vs Prompt Engineering vs Context Engineering Explained Understanding the evolution from prompts and RAG to reliable AI agent runtime systems. Prompt Engineering tells the model … | Vishal Mysore | 2026-05-19 | 2026 | Medium | html-meta | 2026-07-20T09:31:57 | ||||||||||||
ale-0564 | Critiques, Risks, And Limitations | critiques-risks-and-limitations | Paper | 📄 | Position: Coding Benchmarks Are Misaligned with Agentic Software Engineering | https://arxiv.org/abs/2606.17799 | external | arxiv.org | Argues benchmark scores conflate the model with the harness and penalize valid alternatives, so headline numbers hide which loop and harness choices actually move performance. | Argues benchmark scores conflate the model with the harness and penalize valid alternatives, so headline numbers hide which loop and harness choices actually move performance. | Argues benchmark scores conflate the model with the harness and penalize valid alternatives, so headline numbers hide which loop and harness choices actually move performance. | The work turns loop quality into a measurable task or score. Argues benchmark scores conflate the model with the harness and penalize valid alternatives, so headline numbers hide which loop and harness choices actually move performance. | Use Position: Coding Benchmarks Are Misaligned with Agentic Software Engineering to bound risk before recurring or unattended execution. | Research source arXiv:2606.17799; inspect its method and evaluation before treating results as production evidence. | medium | README.md | 1,327 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1327 | Govern | govern | Bound permissions, cost, failure, and escalation. | verification | researcher;evaluator;operator;security | cross-layer | enabling | research-preprint | A | ok | https://arxiv.org/abs/2606.17799 | [2606.17799] Position: Coding Benchmarks Are Misaligned with Agentic Software Engineering | Coding agents have become a major mode of software engineering, but the benchmarks we use to compare them were designed in a pre-agent era: they collapse model, harness, and environment into a single end-to-end score, typically computed against one reference solution, with no component-level signal for iteration. We ar... | Maria I. Gorinova; Macey Baker; Amy Heineike; Maksim Shaposhnikov; Rob Willoughby; Dru Knox | 2026-06-16 | 2026 | arXiv | arXiv | cs.SE | arxiv-api | 2606.17799 | 2026-07-20T09:31:57 | |||||||||
ale-0565 | Critiques, Risks, And Limitations | critiques-risks-and-limitations | Paper | 📄 | Understanding the Challenges in Iterative Generative Optimization with LLMs | https://arxiv.org/abs/2603.23994 | external | arxiv.org | Empirically isolates three hidden design choices that make self-improving agent loops succeed or fail - starting artifacts, credit horizons over execution traces, and batching strategy - explaining why iterative refinement loops stay brittle in production. | Empirically isolates three hidden design choices that make self-improving agent loops succeed or fail - starting artifacts, credit horizons over execution traces, and batching strategy - explaining why iterative refinement loops stay brittle in production. | Empirically isolates three hidden design choices that make self-improving agent loops succeed or fail - starting artifacts, credit horizons over execution traces, and batching strategy - explaining why iterative refinement loops stay brittle in production. | Keeps adoption grounded in known failure modes, economics, and operational limits. Empirically isolates three hidden design choices that make self-improving agent loops succeed or fail - starting artifacts, credit horizons over execution traces, and batching strategy - explaining why iterative refinement loops stay bri... | Use Understanding the Challenges in Iterative Generative Optimization with LLMs to bound risk before recurring or unattended execution. | Research source arXiv:2603.23994; inspect its method and evaluation before treating results as production evidence. | medium | README.md | 1,328 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1328 | Govern | govern | Bound permissions, cost, failure, and escalation. | budget;escalation;exit | researcher;evaluator;operator;security | cross-layer | enabling | research-preprint | A | ok | https://arxiv.org/abs/2603.23994 | [2603.23994] Understanding the Challenges in Iterative Generative Optimization with LLMs | Generative optimization uses large language models (LLMs) to iteratively improve artifacts (such as code, workflows or prompts) using execution feedback. It is a promising approach to building self-improving agents, yet in practice remains brittle: despite active research, only 9% of surveyed agents used any automated ... | Allen Nie; Xavier Daull; Zhiyi Kuang; Abhinav Akkiraju; Anish Chaudhuri; Max Piasevoli; Ryan Rong; YuCheng Yuan; Prerit Choudhary; Shannon Xiao; Rasool Fakoor; Adith Swaminathan; Ching-An Cheng | 2026-03-25 | 2026 | arXiv | arXiv | 39 pages, 17 figures | cs.LG | arxiv-api | 2603.23994 | 2026-07-20T09:31:57 | ||||||||
ale-0566 | Critiques, Risks, And Limitations | critiques-risks-and-limitations | Paper | 📄 | The Illusion of Multi-Agent Advantage | https://arxiv.org/abs/2606.13003 | external | arxiv.org | Systematic evaluation showing automatically generated multi-agent systems consistently underperform chain-of-thought self-consistency while costing up to 10x more, cautioning that auto-designed orchestration adds complexity without functional benefit. | Systematic evaluation showing automatically generated multi-agent systems consistently underperform chain-of-thought self-consistency while costing up to 10x more, cautioning that auto-designed orchestration adds complexity without functional benefit. | Systematic evaluation showing automatically generated multi-agent systems consistently underperform chain-of-thought self-consistency while costing up to 10x more, cautioning that auto-designed orchestration adds complexity without functional benefit. | Evaluation data is used as the feedback signal for improving loop behavior. Systematic evaluation showing automatically generated multi-agent systems consistently underperform chain-of-thought self-consistency while costing up to 10x more, cautioning that auto-designed orchestration adds complexity without functional b... | Use The Illusion of Multi-Agent Advantage to bound risk before recurring or unattended execution. | Research source arXiv:2606.13003; inspect its method and evaluation before treating results as production evidence. | medium | README.md | 1,329 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1329 | Govern | govern | Bound permissions, cost, failure, and escalation. | delegation;verification | researcher;evaluator;operator;security | cross-layer | enabling | research-preprint | A | ok | https://arxiv.org/abs/2606.13003 | [2606.13003] The Illusion of Multi-Agent Advantage | Prevailing wisdom posits that Multi-Agent Systems (MAS) are superior to Single-Agent Systems (SAS), citing advantages like context protection, parallel processing and distributed decision-making. However, empirical support for this claim relies primarily on comparisons with SAS baselines using benchmarks that prioritiz... | Prathyusha Jwalapuram; Hehai Lin; Chuyuan Li; Fangkai Jiao; Sudong Wang; Yifei Ming; Zixuan Ke; Chengwei Qin; Giuseppe Carenini; Shafiq Joty | 2026-06-11 | 2026 | arXiv | arXiv | cs.AI | arxiv-api | 2606.13003 | 2026-07-20T09:31:57 | |||||||||
ale-0567 | Critiques, Risks, And Limitations | critiques-risks-and-limitations | Critique | ⚠️ | The Coming Loop | https://lucumr.pocoo.org/2026/6/23/the-coming-loop/ | external | lucumr.pocoo.org | Flask creator Armin Ronacher's skeptical essay on harness loops, examining what continuously re-driving agents past their natural stopping points does to code quality, review capacity, and human understanding of the resulting systems. | Flask creator Armin Ronacher's skeptical essay on harness loops, examining what continuously re-driving agents past their natural stopping points does to code quality, review capacity, and human understanding of the resulting systems. | Flask creator Armin Ronacher's skeptical essay on harness loops, examining what continuously re-driving agents past their natural stopping points does to code quality, review capacity, and human understanding of the resulting systems. | Keeps adoption grounded in known failure modes, economics, and operational limits. Flask creator Armin Ronacher's skeptical essay on harness loops, examining what continuously re-driving agents past their natural stopping points does to code quality, review capacity, and human understanding of the resulting systems. | Use The Coming Loop to bound risk before recurring or unattended execution. | Contextual source from lucumr.pocoo.org; useful for practice signals or boundary conditions, not independent validation. | contextual | README.md | 1,330 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1330 | Govern | govern | Bound permissions, cost, failure, and escalation. | escalation;exit | operator;security | cross-layer | enabling | risk-analysis | B | ok | https://lucumr.pocoo.org/2026/6/23/the-coming-loop/ | The Coming Loop | Armin Ronacher's Thoughts and Writings | Loops, harnesses, and why even loop skeptics may end up with them. | 2026-06-23 | 2026 | Armin Ronacher's Thoughts and Writings | html-meta | 2026-07-20T09:31:57 | |||||||||||||
ale-0568 | Critiques, Risks, And Limitations | critiques-risks-and-limitations | Critique | ⚠️ | Loop Engineering, the Latest AI Buzzword, Still Needs Humans in the Loop | https://www.theregister.com/ai-and-ml/2026/06/24/loop-engineering-latest-ai-buzzword-still-needs-humans-in-the-loop/5261735 | external | www.theregister.com | The Register's report on the June 2026 loop-engineering discussion, collecting the Steinberger, Osmani, and Cherny quotes while arguing that vendor token-consumption incentives and model non-determinism keep humans in the loop. | The Register's report on the June 2026 loop-engineering discussion, collecting the Steinberger, Osmani, and Cherny quotes while arguing that vendor token-consumption incentives and model non-determinism keep humans in the loop. | The Register's report on the June 2026 loop-engineering discussion, collecting the Steinberger, Osmani, and Cherny quotes while arguing that vendor token-consumption incentives and model non-determinism keep humans in the loop. | Keeps adoption grounded in known failure modes, economics, and operational limits. The Register's report on the June 2026 loop-engineering discussion, collecting the Steinberger, Osmani, and Cherny quotes while arguing that vendor token-consumption incentives and model non-determinism keep humans in the loop. | Use Loop Engineering, the Latest AI Buzzword, Still Needs Humans in the Loop to bound risk before recurring or unattended execution. | Contextual source from www.theregister.com; useful for practice signals or boundary conditions, not independent validation. | contextual | README.md | 1,331 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1331 | Govern | govern | Bound permissions, cost, failure, and escalation. | budget | operator;security | cross-layer | enabling | risk-analysis | B | ok | https://www.theregister.com/ai-and-ml/2026/06/24/loop-engineering-latest-ai-buzzword-still-needs-humans-in-the-loop/5261735 | Loop engineering, latest AI buzzword, still needs humans in the loop | Prompting less and automating more comes with a price | 2026-06-24 | 2026 | theregister | html-meta | 2026-07-20T09:31:57 | |||||||||||||
ale-0569 | Critiques, Risks, And Limitations | critiques-risks-and-limitations | Paper | 📄 | When Agents Do Not Stop: Uncovering Infinite Agentic Loops in LLM Agents | https://arxiv.org/abs/2607.01641 | external | arxiv.org | Characterizes infinite agentic loops, a failure class where unbounded feedback paths make agents repeat calls, tools, or handoffs forever, and ships IAL-Scan, a static analyzer that confirmed 68 real cases across 47 of 6,549 scanned agent projects at 91.9% precision. | Characterizes infinite agentic loops, a failure class where unbounded feedback paths make agents repeat calls, tools, or handoffs forever, and ships IAL-Scan, a static analyzer that confirmed 68 real cases across 47 of 6,549 scanned agent projects at 91.9% precision. | Characterizes infinite agentic loops, a failure class where unbounded feedback paths make agents repeat calls, tools, or handoffs forever, and ships IAL-Scan, a static analyzer that confirmed 68 real cases across 47 of 6,549 scanned agent projects at 91.9% precision. | Keeps adoption grounded in known failure modes, economics, and operational limits. Characterizes infinite agentic loops, a failure class where unbounded feedback paths make agents repeat calls, tools, or handoffs forever, and ships IAL-Scan, a static analyzer that confirmed 68 real cases across 47 of 6,549 scanned agen... | Use When Agents Do Not Stop: Uncovering Infinite Agentic Loops in LLM Agents to bound risk before recurring or unattended execution. | Research source arXiv:2607.01641; inspect its method and evaluation before treating results as production evidence. | medium | README.md | 1,332 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1332 | Govern | govern | Bound permissions, cost, failure, and escalation. | workspace;delegation;exit | researcher;evaluator;operator;security | cross-layer | enabling | research-preprint | A | ok | https://arxiv.org/abs/2607.01641 | [2607.01641] When Agents Do Not Stop: Uncovering Infinite Agentic Loops in LLM Agents | LLM agents increasingly rely on iterative execution to solve tasks through planning, tool use, state updates, and agent collaboration. While this design enables flexible automation, it also creates a new class of failures: an agent may repeatedly execute model calls, tools, workflow transitions, or agent handoffs when ... | Xinyi Hou; Shenao Wang; Yanjie Zhao; Haoyu Wang | 2026-07-02 | 2026 | arXiv | arXiv | cs.SE | arxiv-api | 2607.01641 | 2026-07-20T09:31:57 | |||||||||
ale-0570 | Critiques, Risks, And Limitations | critiques-risks-and-limitations | Paper | 📄 | The Blind Curator: How a Biased Judge Silently Disables Skill Retirement in Self-Evolving Agents | https://arxiv.org/abs/2607.07436 | external | arxiv.org | Shows via corrupted-reward analysis that false-pass bias in an LLM judge silently disables the skill-retirement mechanism that keeps a self-evolving agent's growing skill library from drifting below the no-skill baseline. | Shows via corrupted-reward analysis that false-pass bias in an LLM judge silently disables the skill-retirement mechanism that keeps a self-evolving agent's growing skill library from drifting below the no-skill baseline. | Shows via corrupted-reward analysis that false-pass bias in an LLM judge silently disables the skill-retirement mechanism that keeps a self-evolving agent's growing skill library from drifting below the no-skill baseline. | Keeps adoption grounded in known failure modes, economics, and operational limits. Shows via corrupted-reward analysis that false-pass bias in an LLM judge silently disables the skill-retirement mechanism that keeps a self-evolving agent's growing skill library from drifting below the no-skill baseline. | Use The Blind Curator: How a Biased Judge Silently Disables Skill Retirement in Self-Evolving Agents to bound risk before recurring or unattended execution. | Research source arXiv:2607.07436; inspect its method and evaluation before treating results as production evidence. | medium | README.md | 1,333 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1333 | Govern | govern | Bound permissions, cost, failure, and escalation. | budget;escalation;exit | researcher;evaluator;operator;security | cross-layer | enabling | research-preprint | A | ok | https://arxiv.org/abs/2607.07436 | [2607.07436] The Blind Curator: How a Biased Judge Silently Disables Skill Retirement in Self-Evolving Agents | A self-evolving agent retires its bad skills by watching them fail, so what happens when the judge cannot see the failures? Skill retirement is the structural constraint that keeps a growing library from drifting below the no-skill baseline, but its guarantee assumes an unbiased reward, which is false for the LLM judge... | Xing Zhang; Yanwei Cui; Guanghui Wang; Ziyuan Li; Wei Qiu; Bing Zhu; Peiyang He | 2026-07-08 | 2026 | arXiv | arXiv | cs.AI | arxiv-api | 2607.07436 | 2026-07-20T09:31:57 | |||||||||
ale-0571 | Critiques, Risks, And Limitations | critiques-risks-and-limitations | Paper | 📄 | Do LLM-Generated Skills Make Better AI Data Scientists? A Component Ablation Across Data-Science Workflows | https://arxiv.org/abs/2607.07504 | external | arxiv.org | Negative result for low-curation skill libraries: across four data-science lifecycle stages (56 tasks), fully LLM-generated skill files show no reliable improvement over plain task prompting, and component ablations find no skill part that helps either (all p > 0.396). Useful counterweight to the skill-generation enthu... | Negative result for low-curation skill libraries: across four data-science lifecycle stages (56 tasks), fully LLM-generated skill files show no reliable improvement over plain task prompting, and component ablations find no skill part that helps either (all p > 0.396). Useful counterweight to the skill-generation enthu... | Negative result for low-curation skill libraries: across four data-science lifecycle stages (56 tasks), fully LLM-generated skill files show no reliable improvement over plain task prompting, and component ablations find no skill part that helps either (all p > 0.396). Useful counterweight to the skill-generation enthu... | Keeps adoption grounded in known failure modes, economics, and operational limits. Negative result for low-curation skill libraries: across four data-science lifecycle stages (56 tasks), fully LLM-generated skill files show no reliable improvement over plain task prompting, and component ablations find no skill part th... | Use Do LLM-Generated Skills Make Better AI Data Scientists? A Component Ablation Across Data-Science Workflows to bound risk before recurring or unattended execution. | Research source arXiv:2607.07504; inspect its method and evaluation before treating results as production evidence. | medium | README.md | 1,334 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1334 | Govern | govern | Bound permissions, cost, failure, and escalation. | budget;escalation;exit | researcher;evaluator;operator;security | cross-layer | enabling | research-paper | A | ok | https://arxiv.org/abs/2607.07504 | [2607.07504] Do LLM-Generated Skills Make Better AI Data Scientists? A Component Ablation Across Data-Science Workflows | Product data scientists often ask LLM-based agents to help with recurring execution tasks such as cleaning data, writing SQL, choosing statistical tests, and formatting results. Reusable skill files are meant to avoid prompting from scratch by packaging guidance for a task family. Expert-written skills can encode high-... | Wei-Jung Huang | 2026 | 2026 | KDD Workshop on AI Data Scientist | ACM SIGKDD | Accepted at KDD Workshop on AI Data Scientist; the linked arXiv record is the available paper version. | cs.AI | Current arXiv acceptance note and official workshop page | 2607.07504 | 2026-07-20T09:31:57 | ||||||||
ale-0572 | Critiques, Risks, And Limitations | critiques-risks-and-limitations | Paper | 📄 | The Verification Horizon: No Silver Bullet for Coding Agent Rewards | https://arxiv.org/abs/2606.26300 | external | arxiv.org | Position paper arguing verification has become harder than generation for coding agents: every verifier is only a proxy for underspecified human intent, so reward design faces a horizon that no single verification mechanism crosses. | Position paper arguing verification has become harder than generation for coding agents: every verifier is only a proxy for underspecified human intent, so reward design faces a horizon that no single verification mechanism crosses. | Position paper arguing verification has become harder than generation for coding agents: every verifier is only a proxy for underspecified human intent, so reward design faces a horizon that no single verification mechanism crosses. | Verification is promoted from a final check to a loop-control signal. Position paper arguing verification has become harder than generation for coding agents: every verifier is only a proxy for underspecified human intent, so reward design faces a horizon that no single verification mechanism crosses. | Use The Verification Horizon: No Silver Bullet for Coding Agent Rewards to bound risk before recurring or unattended execution. | Research source arXiv:2606.26300; inspect its method and evaluation before treating results as production evidence. | medium | README.md | 1,335 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1335 | Govern | govern | Bound permissions, cost, failure, and escalation. | verification;escalation | researcher;evaluator;operator;security | cross-layer | enabling | research-preprint | A | ok | https://arxiv.org/abs/2606.26300 | [2606.26300] The Verification Horizon: No Silver Bullet for Coding Agent Rewards | A classical intuition holds that verifying a solution is easier than producing one. For today's coding agents, this intuition is being inverted: as foundation models develop stronger reasoning capabilities and engineering harnesses grow more sophisticated, generating complex candidate solutions is no longer difficult -... | Binghai Wang; Chenlong Zhang; Dayiheng Liu; Jiajun Zhang; Jiawei Chen; Mingze Li; Mouxiang Chen; Rongyao Fang; Siyuan Zhang; Xuwu Wang; Yuheng Jing; Zeyao Ma; Zeyu Cui | 2026-06-24 | 2026 | arXiv | arXiv | Authors are listed alphabetically by their first names | cs.AI | arxiv-api | 2606.26300 | 2026-07-20T09:31:57 | ||||||||
ale-0573 | Critiques, Risks, And Limitations | critiques-risks-and-limitations | Critique | ⚠️ | Write Code Like a Human Will Maintain It | https://unstack.io/write-code-like-a-human-will-maintain-it | external | unstack.io | Argues that agent-driven codebases create a compounding feedback loop where every merged shortcut becomes training signal for the next generation of changes, so code quality standards matter more, not less, under automation. | Argues that agent-driven codebases create a compounding feedback loop where every merged shortcut becomes training signal for the next generation of changes, so code quality standards matter more, not less, under automation. | Argues that agent-driven codebases create a compounding feedback loop where every merged shortcut becomes training signal for the next generation of changes, so code quality standards matter more, not less, under automation. | Keeps adoption grounded in known failure modes, economics, and operational limits. Argues that agent-driven codebases create a compounding feedback loop where every merged shortcut becomes training signal for the next generation of changes, so code quality standards matter more, not less, under automation. | Use Write Code Like a Human Will Maintain It to bound risk before recurring or unattended execution. | Contextual source from unstack.io; useful for practice signals or boundary conditions, not independent validation. | contextual | README.md | 1,336 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1336 | Govern | govern | Bound permissions, cost, failure, and escalation. | escalation | operator;security | cross-layer | enabling | risk-analysis | B | ok | https://unstack.io/write-code-like-a-human-will-maintain-it | Write code like a human will maintain it | One of the best things about LLMs is that they'll write code for you, all day long. Who cares about DRY? You don't have to be the one updating the same long con... | 2026-07-10 | 2026 | Unstack | html-meta | 2026-07-20T09:31:57 | |||||||||||||
ale-0574 | Critiques, Risks, And Limitations | critiques-risks-and-limitations | Blog | 📝 | Claude Code Sends 33k Tokens Before Reading the Prompt | https://systima.ai/blog/claude-code-vs-opencode-token-overhead | external | systima.ai | July 12, 2026 proxy-interception study of per-turn harness overhead: Claude Code sends ~33k tokens of scaffolding before user input versus OpenCode's ~7k (a 4.7x gap that narrows to 3.3x on newer models), mid-session cache-block rewrites produce up to 54x more cache-write tokens on identical tasks, a 72KB instruction f... | July 12, 2026 proxy-interception study of per-turn harness overhead: Claude Code sends ~33k tokens of scaffolding before user input versus OpenCode's ~7k (a 4.7x gap that narrows to 3.3x on newer models), mid-session cache-block rewrites produce up to 54x more cache-write tokens on identical tasks, a 72KB instruction f... | July 12, 2026 proxy-interception study of per-turn harness overhead: Claude Code sends ~33k tokens of scaffolding before user input versus OpenCode's ~7k (a 4.7x gap that narrows to 3.3x on newer models), mid-session cache-block rewrites produce up to 54x more cache-write tokens on identical tasks, a 72KB instruction f... | The work separates roles across agents, verifiers, or orchestration layers. July 12, 2026 proxy-interception study of per-turn harness overhead: Claude Code sends ~33k tokens of scaffolding before user input versus OpenCode's ~7k (a 4.7x gap that narrows to 3.3x on newer models), mid-session cache-block rewrites produc... | Use Claude Code Sends 33k Tokens Before Reading the Prompt to bound risk before recurring or unattended execution. | Contextual source from systima.ai; useful for practice signals or boundary conditions, not independent validation. | contextual | README.md | 1,337 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1337 | Govern | govern | Bound permissions, cost, failure, and escalation. | delegation;budget | operator;security | cross-layer | enabling | practitioner-analysis | B | ok | https://systima.ai/blog/claude-code-vs-opencode-token-overhead | Claude Code Sends 4.7x More Tokens Than OpenCode Before Reading Your Prompt | Systima Blog | Claude Code vs OpenCode token overhead measured at the API boundary. Out-of-the-box baselines, instruction file weight, MCP schema tax, subagent multipliers, and cache-write behaviour. | Systima | 2026-07-12 | 2026 | Systima | html-meta | 2026-07-20T09:31:57 | ||||||||||||
ale-0575 | Critiques, Risks, And Limitations | critiques-risks-and-limitations | Paper | 📄 | Rethinking the Evaluation of Harness Evolution for Agents | https://arxiv.org/abs/2607.12227 | external | arxiv.org | Re-evaluates harness evolution on Terminal-Bench 2.1 with GPT-5.4 and Claude Opus 4.6, finding that evolved harnesses do not consistently beat budget-matched search and transfer only weakly to held-out tasks. | Re-evaluates harness evolution on Terminal-Bench 2.1 with GPT-5.4 and Claude Opus 4.6, finding that evolved harnesses do not consistently beat budget-matched search and transfer only weakly to held-out tasks. | Re-evaluates harness evolution on Terminal-Bench 2.1 with GPT-5.4 and Claude Opus 4.6, finding that evolved harnesses do not consistently beat budget-matched search and transfer only weakly to held-out tasks. | Evaluation data is used as the feedback signal for improving loop behavior. Re-evaluates harness evolution on Terminal-Bench 2.1 with GPT-5.4 and Claude Opus 4.6, finding that evolved harnesses do not consistently beat budget-matched search and transfer only weakly to held-out tasks. | Use Rethinking the Evaluation of Harness Evolution for Agents to bound risk before recurring or unattended execution. | Research source arXiv:2607.12227; inspect its method and evaluation before treating results as production evidence. | medium | README.md | 1,338 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1338 | 2026-07-17 | Govern | govern | Bound permissions, cost, failure, and escalation. | verification;budget | researcher;evaluator;operator;security | cross-layer | enabling | research-preprint | A | ok | https://arxiv.org/abs/2607.12227 | [2607.12227] Rethinking the Evaluation of Harness Evolution for Agents | We revisit the evaluation of automatic harness evolution for LLM agents. Existing harness evolution methods use unit test cases to search for harness configurations and then report final performance on the same public benchmark. This protocol raises two fundamental concerns. First, harness evolution is itself an iterat... | Yike Wang; Huaisheng Zhu; Zhengyu Hu; Yige Yuan; Zhengyu Chen; Shakti Senthil; Hannaneh Hajishirzi; Yulia Tsvetkov; Pradeep Dasigi; Teng Xiao | 2026-07-14 | 2026 | arXiv | arXiv | cs.AI | arxiv-api | 2607.12227 | 2026-07-20T09:31:57 | ||||||||
ale-0576 | Critiques, Risks, And Limitations | critiques-risks-and-limitations | Paper | 📄 | Compaction as Epistemic Failure: How Agentic LLM Tools Fabricate Confirmed Results from Killed Processes | https://arxiv.org/abs/2607.13071 | external | arxiv.org | Documents a Claude Code failure in which partial output from a process killed with exit 143 becomes a confirmed claim after context compaction, without re-verification, showing why receipts and process status must survive summarization. | Documents a Claude Code failure in which partial output from a process killed with exit 143 becomes a confirmed claim after context compaction, without re-verification, showing why receipts and process status must survive summarization. | Documents a Claude Code failure in which partial output from a process killed with exit 143 becomes a confirmed claim after context compaction, without re-verification, showing why receipts and process status must survive summarization. | Verification is promoted from a final check to a loop-control signal. Documents a Claude Code failure in which partial output from a process killed with exit 143 becomes a confirmed claim after context compaction, without re-verification, showing why receipts and process status must survive summarization. | Use Compaction as Epistemic Failure: How Agentic LLM Tools Fabricate Confirmed Results from Killed Processes to bound risk before recurring or unattended execution. | Research source arXiv:2607.13071; inspect its method and evaluation before treating results as production evidence. | medium | README.md | 1,339 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1339 | 2026-07-17 | Govern | govern | Bound permissions, cost, failure, and escalation. | workspace;context;verification;state;exit | researcher;evaluator;operator;security | cross-layer | enabling | research-preprint | A | ok | https://arxiv.org/abs/2607.13071 | [2607.13071] Compaction as Epistemic Failure: How Agentic LLM Tools Fabricate Confirmed Results from Killed Processes | Agentic LLM coding tools compress long session histories into compaction summaries that subsequent sessions inherit as ground truth. This paper documents a failure mode in Claude Code where partial standard output from timed-out commands (exit code 143) is recorded in compaction summaries as confirmed results, propagat... | Hiroki Tamba | 2026-07-11 | 2026 | arXiv | arXiv | 8 pages, companion to arXiv:2606.26185 | cs.SE | arxiv-api | 2607.13071 | 2026-07-20T09:31:57 | |||||||
ale-0577 | Critiques, Risks, And Limitations | critiques-risks-and-limitations | Paper | 📄 | Do Agent Optimizers Compound? A Continual-Learning Evaluation on Terminal-Bench 2.0 | https://arxiv.org/abs/2607.14004 | external | arxiv.org | Compares GEPA, Meta Harness, and RELAI-VCL under matched continual-learning budgets; only the regression-controlled method keeps improving, reaching 76.4% lifelong performance versus 66.0%, 64.6%, and 58.7% for the reported alternatives. | Compares GEPA, Meta Harness, and RELAI-VCL under matched continual-learning budgets; only the regression-controlled method keeps improving, reaching 76.4% lifelong performance versus 66.0%, 64.6%, and 58.7% for the reported alternatives. | Compares GEPA, Meta Harness, and RELAI-VCL under matched continual-learning budgets; only the regression-controlled method keeps improving, reaching 76.4% lifelong performance versus 66.0%, 64.6%, and 58.7% for the reported alternatives. | Evaluation data is used as the feedback signal for improving loop behavior. Compares GEPA, Meta Harness, and RELAI-VCL under matched continual-learning budgets; only the regression-controlled method keeps improving, reaching 76.4% lifelong performance versus 66.0%, 64.6%, and 58.7% for the reported alternatives. | Use Do Agent Optimizers Compound? A Continual-Learning Evaluation on Terminal-Bench 2.0 to bound risk before recurring or unattended execution. | Research source arXiv:2607.14004; inspect its method and evaluation before treating results as production evidence. | medium | README.md | 1,340 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1340 | 2026-07-17 | Govern | govern | Bound permissions, cost, failure, and escalation. | verification;budget | researcher;evaluator;operator;security | cross-layer | enabling | research-preprint | A | ok | https://arxiv.org/abs/2607.14004 | [2607.14004] Do Agent Optimizers Compound? A Continual-Learning Evaluation on Terminal-Bench 2.0 | Most reported gains from agent-optimization methods are one-shot: an agent is optimized against a fixed benchmark and the resulting improvement is reported as if it were a stable property of the method. This does not test the setting that matters for deployed agents, where optimization is applied recursively as new fai... | Wenxiao Wang; Priyatham Kattakinda; Soheil Feizi | 2026-07-15 | 2026 | arXiv | arXiv | Technical Report by RELAI (relai.ai) | cs.AI | arxiv-api | 2607.14004 | 2026-07-20T09:31:57 | |||||||
ale-0578 | Critiques, Risks, And Limitations | critiques-risks-and-limitations | Paper | 📄 | Does Multi-Agent Debate Improve AI Feedback on Research Papers? | https://arxiv.org/abs/2607.14713 | external | arxiv.org | In a preregistered masked study with authors of 44 meta-analyses, participants prefer single-pass feedback to two multi-agent debate systems, one using about 30x more tokens; AI judges reverse the human preference, warning against self-evaluation alone. | In a preregistered masked study with authors of 44 meta-analyses, participants prefer single-pass feedback to two multi-agent debate systems, one using about 30x more tokens; AI judges reverse the human preference, warning against self-evaluation alone. | In a preregistered masked study with authors of 44 meta-analyses, participants prefer single-pass feedback to two multi-agent debate systems, one using about 30x more tokens; AI judges reverse the human preference, warning against self-evaluation alone. | Evaluation data is used as the feedback signal for improving loop behavior. In a preregistered masked study with authors of 44 meta-analyses, participants prefer single-pass feedback to two multi-agent debate systems, one using about 30x more tokens; AI judges reverse the human preference, warning against self-evaluati... | Use Does Multi-Agent Debate Improve AI Feedback on Research Papers? to bound risk before recurring or unattended execution. | Research source arXiv:2607.14713; inspect its method and evaluation before treating results as production evidence. | medium | README.md | 1,341 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1341 | 2026-07-17 | Govern | govern | Bound permissions, cost, failure, and escalation. | delegation;verification;budget;escalation | researcher;evaluator;operator;security | cross-layer | enabling | research-preprint | A | ok | https://arxiv.org/abs/2607.14713 | [2607.14713] Does Multi-Agent Debate Improve AI Feedback on Research Papers? | Probably not, at least for meta-analyses in economics. In a pre-registered, identity-masked, within-paper experiment, the authors of 44 meta-analyses ranked three AI reports on their own paper by usefulness for improving it: a single pass by a frontier model against two multi-agent debate tools we built and expected to... | Tomas Havranek; Zuzana Irsova | 2026-07-16 | 2026 | arXiv | arXiv | 29 pages, 1 figure, 6 tables. Pre-registered on OSF; data, code, judge prompts, and blinded reports in the replication package on Zenodo. Project page: https://meta-analysis.cz/debate | econ.GN | arxiv-api | 2607.14713 | 2026-07-20T09:31:57 | |||||||
ale-0579 | Adjacent Awesome Lists | adjacent-awesome-lists | List | 🧭 | Awesome Harness Engineering by ai-boost | https://github.com/ai-boost/awesome-harness-engineering | external | github.com | Comprehensive list for the agent harness layer that Loop Engineering builds on. | Comprehensive list for the agent harness layer that Loop Engineering builds on. | Comprehensive list for the agent harness layer that Loop Engineering builds on. | Connects neighboring ecosystems while preserving Loop Engineering as a narrower operating concept. Comprehensive list for the agent harness layer that Loop Engineering builds on. | Use Awesome Harness Engineering by ai-boost to reuse a concrete artifact or connect it to the wider ecosystem. | Inspectable GitHub source (3,153 stars; 336 forks; NOASSERTION license; updated 2026-07-20); popularity is context, not proof of reliability. | medium | README.md | 1,361 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1361 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | whole-loop | builder | cross-layer | adjacent | curated-index | C | ok | https://github.com/ai-boost/awesome-harness-engineering | GitHub - ai-boost/awesome-harness-engineering: Awesome list for AI agent harness engineering: tools, patterns, evals, memory, MCP, permissions, observability, and orchestration. · GitHub | Awesome list for AI agent harness engineering: tools, patterns, evals, memory, MCP, permissions, observability, and orchestration. - ai-boost/awesome-harness-engineering | 2026-03-29 | 2026 | ai-boost/awesome-harness-engineering | GitHub | github-api | ai-boost/awesome-harness-engineering | 3153 | 336 | NOASSERTION | 2026-03-29T15:39:49Z | 2026-07-20T09:04:42Z | 2026-07-20T09:31:57 | ||||||
ale-0580 | Adjacent Awesome Lists | adjacent-awesome-lists | List | 🧭 | Awesome Harness Engineering by walkinglabs | https://github.com/walkinglabs/awesome-harness-engineering | external | github.com | High-signal harness list with strong categories for context, guardrails, specs, evals, runtimes, and benchmarks. | High-signal harness list with strong categories for context, guardrails, specs, evals, runtimes, and benchmarks. | High-signal harness list with strong categories for context, guardrails, specs, evals, runtimes, and benchmarks. | Evaluation data is used as the feedback signal for improving loop behavior. High-signal harness list with strong categories for context, guardrails, specs, evals, runtimes, and benchmarks. | Use Awesome Harness Engineering by walkinglabs to reuse a concrete artifact or connect it to the wider ecosystem. | Inspectable GitHub source (3,655 stars; 297 forks; NOASSERTION license; updated 2026-07-20); popularity is context, not proof of reliability. | medium | README.md | 1,362 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1362 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | context;verification | builder | cross-layer | adjacent | curated-index | C | ok | https://github.com/walkinglabs/awesome-harness-engineering | GitHub - walkinglabs/awesome-harness-engineering: 🛠️ Awesome tools & guides for harness engineering. · GitHub | 🛠️ Awesome tools & guides for harness engineering. - walkinglabs/awesome-harness-engineering | 2026-03-29 | 2026 | walkinglabs/awesome-harness-engineering | GitHub | github-api | walkinglabs/awesome-harness-engineering | 3655 | 297 | NOASSERTION | 2026-03-29T11:29:37Z | 2026-07-20T08:55:26Z | 2026-07-20T09:31:57 | ||||||
ale-0581 | Adjacent Awesome Lists | adjacent-awesome-lists | List | 🧭 | Awesome Agent Harness | https://github.com/AutoJunjie/awesome-agent-harness | external | github.com | Curated tools and resources for environments, constraints, and feedback around coding agents. | Curated tools and resources for environments, constraints, and feedback around coding agents. | Curated tools and resources for environments, constraints, and feedback around coding agents. | Connects neighboring ecosystems while preserving Loop Engineering as a narrower operating concept. Curated tools and resources for environments, constraints, and feedback around coding agents. | Use Awesome Agent Harness to reuse a concrete artifact or connect it to the wider ecosystem. | Inspectable GitHub source (490 stars; 47 forks; updated 2026-07-19); popularity is context, not proof of reliability. | medium | README.md | 1,363 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1363 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | workspace | builder | cross-layer | adjacent | curated-index | C | ok | https://github.com/AutoJunjie/awesome-agent-harness | GitHub - AutoJunjie/awesome-agent-harness · GitHub | Contribute to AutoJunjie/awesome-agent-harness development by creating an account on GitHub. | 2026-03-05 | 2026 | AutoJunjie/awesome-agent-harness | GitHub | github-api | AutoJunjie/awesome-agent-harness | 490 | 47 | 2026-03-05T13:19:10Z | 2026-07-19T05:57:33Z | 2026-07-20T09:31:57 | |||||||
ale-0582 | Adjacent Awesome Lists | adjacent-awesome-lists | List | 🧭 | Awesome Context Engineering | https://github.com/Meirtz/Awesome-Context-Engineering | external | github.com | Survey-style list for context engineering across LLMs and agents. | Survey-style list for context engineering across LLMs and agents. | Survey-style list for context engineering across LLMs and agents. | Context is managed as durable loop state rather than a single prompt payload. Survey-style list for context engineering across LLMs and agents. | Use Awesome Context Engineering to reuse a concrete artifact or connect it to the wider ecosystem. | Inspectable GitHub source (3,240 stars; 259 forks; MIT license; updated 2026-07-20); popularity is context, not proof of reliability. | medium | README.md | 1,364 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1364 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | context | builder | cross-layer | adjacent | curated-index | C | ok | https://github.com/Meirtz/Awesome-Context-Engineering | GitHub - Meirtz/Awesome-Context-Engineering: 🔥 Comprehensive survey on Context Engineering: from prompt engineering to production-grade AI systems. hundreds of papers, frameworks, and implementation guides for LLMs and AI agents. · GitHub | 🔥 Comprehensive survey on Context Engineering: from prompt engineering to production-grade AI systems. hundreds of papers, frameworks, and implementation guides for LLMs and AI agents. - Meirtz/Awesome-Context-Engineering | 2025-07-02 | 2025 | Meirtz/Awesome-Context-Engineering | GitHub | github-api | Meirtz/Awesome-Context-Engineering | 3240 | 259 | MIT | 2025-07-02T17:46:03Z | 2026-07-20T09:24:02Z | 2026-07-20T09:31:57 | ||||||
ale-0583 | Adjacent Awesome Lists | adjacent-awesome-lists | List | 🧭 | Awesome Prompt Engineering | https://github.com/promptslab/Awesome-Prompt-Engineering | external | github.com | Classic adjacent list for prompt techniques and prompting resources. | Classic adjacent list for prompt techniques and prompting resources. | Classic adjacent list for prompt techniques and prompting resources. | Connects neighboring ecosystems while preserving Loop Engineering as a narrower operating concept. Classic adjacent list for prompt techniques and prompting resources. | Use Awesome Prompt Engineering to reuse a concrete artifact or connect it to the wider ecosystem. | Inspectable GitHub source (6,177 stars; 727 forks; Apache-2.0 license; updated 2026-07-20); popularity is context, not proof of reliability. | medium | README.md | 1,365 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1365 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | whole-loop | builder | cross-layer | adjacent | curated-index | C | ok | https://github.com/promptslab/Awesome-Prompt-Engineering | GitHub - promptslab/Awesome-Prompt-Engineering: This repository contains a hand-curated resources for Prompt Engineering with a focus on Generative Pre-trained Transformer (GPT), ChatGPT, PaLM etc · GitHub | This repository contains a hand-curated resources for Prompt Engineering with a focus on Generative Pre-trained Transformer (GPT), ChatGPT, PaLM etc - GitHub - promptslab/Awesome-Prompt-Engineering: This repository contains a hand-curated resources for Prompt Engineering with a focus on Generative Pre-trained Transform... | 2023-02-09 | 2023 | promptslab/Awesome-Prompt-Engineering | GitHub | github-api | promptslab/Awesome-Prompt-Engineering | 6177 | 727 | Apache-2.0 | 2023-02-09T18:22:52Z | 2026-07-20T09:29:06Z | 2026-07-20T09:31:57 | ||||||
ale-0584 | Adjacent Awesome Lists | adjacent-awesome-lists | List | 🧭 | Awesome LLM Agents | https://github.com/kaushikb11/awesome-llm-agents | external | github.com | General list of LLM agent papers, frameworks, and applications. | General list of LLM agent papers, frameworks, and applications. | General list of LLM agent papers, frameworks, and applications. | Connects neighboring ecosystems while preserving Loop Engineering as a narrower operating concept. General list of LLM agent papers, frameworks, and applications. | Use Awesome LLM Agents to reuse a concrete artifact or connect it to the wider ecosystem. | Inspectable GitHub source (1,534 stars; 329 forks; updated 2026-07-19); popularity is context, not proof of reliability. | medium | README.md | 1,366 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1366 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | whole-loop | builder | cross-layer | adjacent | curated-index | C | ok | https://github.com/kaushikb11/awesome-llm-agents | GitHub - kaushikb11/awesome-llm-agents: A curated list of awesome LLM agents frameworks. · GitHub | A curated list of awesome LLM agents frameworks. Contribute to kaushikb11/awesome-llm-agents development by creating an account on GitHub. | 2023-04-04 | 2023 | kaushikb11/awesome-llm-agents | GitHub | github-api | kaushikb11/awesome-llm-agents | 1534 | 329 | 2023-04-04T10:22:43Z | 2026-07-19T03:36:17Z | 2026-07-20T09:31:57 | |||||||
ale-0585 | Adjacent Awesome Lists | adjacent-awesome-lists | List | 🧭 | Awesome AI Agents | https://github.com/e2b-dev/awesome-ai-agents | external | github.com | Broad AI agent ecosystem map. | Broad AI agent ecosystem map. | Broad AI agent ecosystem map. | Connects neighboring ecosystems while preserving Loop Engineering as a narrower operating concept. Broad AI agent ecosystem map. | Use Awesome AI Agents to reuse a concrete artifact or connect it to the wider ecosystem. | Inspectable GitHub source (28,935 stars; 3,198 forks; NOASSERTION license; updated 2026-07-20); popularity is context, not proof of reliability. | medium | README.md | 1,367 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1367 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | whole-loop | builder | cross-layer | adjacent | curated-index | C | ok | https://github.com/e2b-dev/awesome-ai-agents | GitHub - e2b-dev/awesome-ai-agents: A list of AI autonomous agents · GitHub | A list of AI autonomous agents. Contribute to e2b-dev/awesome-ai-agents development by creating an account on GitHub. | 2023-06-19 | 2023 | e2b-dev/awesome-ai-agents | GitHub | github-api | e2b-dev/awesome-ai-agents | 28935 | 3198 | NOASSERTION | 2023-06-19T00:20:06Z | 2026-07-20T09:12:41Z | 2026-07-20T09:31:57 | ||||||
ale-0586 | Adjacent Awesome Lists | adjacent-awesome-lists | List | 🧭 | Awesome CLI Coding Agents | https://github.com/bradAGI/awesome-cli-coding-agents | external | github.com | Directory of terminal-native coding agents, parallel runners, autonomous loops, and the harnesses that orchestrate them. | Directory of terminal-native coding agents, parallel runners, autonomous loops, and the harnesses that orchestrate them. | Directory of terminal-native coding agents, parallel runners, autonomous loops, and the harnesses that orchestrate them. | Orchestration and control flow are made explicit and inspectable. Directory of terminal-native coding agents, parallel runners, autonomous loops, and the harnesses that orchestrate them. | Use Awesome CLI Coding Agents to reuse a concrete artifact or connect it to the wider ecosystem. | Inspectable GitHub source (839 stars; 226 forks; updated 2026-07-20); popularity is context, not proof of reliability. | medium | README.md | 1,368 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1368 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | delegation | builder | cross-layer | adjacent | curated-index | C | ok | https://github.com/bradAGI/awesome-cli-coding-agents | GitHub - bradAGI/awesome-cli-coding-agents: Curated directory of terminal-native AI coding agents and the harnesses that orchestrate them. Covers open-source tools (Pi, OpenCode, Aider, Goose), platform agents (Claude Code, Codex, Gemini CLI), parallel runners, autonomous loops, and agent infrastructure. · GitHub | Curated directory of terminal-native AI coding agents and the harnesses that orchestrate them. Covers open-source tools (Pi, OpenCode, Aider, Goose), platform agents (Claude Code, Codex, Gemini CLI), parallel runners, autonomous loops, and agent infrastructure. - GitHub - bradAGI/awesome-cli-coding-agents: Curated dire... | 2026-02-07 | 2026 | bradAGI/awesome-cli-coding-agents | GitHub | github-api | bradAGI/awesome-cli-coding-agents | 839 | 226 | 2026-02-07T00:53:24Z | 2026-07-20T07:30:00Z | 2026-07-20T09:31:57 | |||||||
ale-0587 | Adjacent Awesome Lists | adjacent-awesome-lists | List | 🧭 | Awesome Self-Evolving Agents | https://github.com/XMUDeepLIT/Awesome-Self-Evolving-Agents | external | github.com | Survey-style list of agents that improve themselves over repeated runs, an adjacent angle on long-running loops with memory and verification. | Survey-style list of agents that improve themselves over repeated runs, an adjacent angle on long-running loops with memory and verification. | Survey-style list of agents that improve themselves over repeated runs, an adjacent angle on long-running loops with memory and verification. | Verification is promoted from a final check to a loop-control signal. Survey-style list of agents that improve themselves over repeated runs, an adjacent angle on long-running loops with memory and verification. | Use Awesome Self-Evolving Agents to reuse a concrete artifact or connect it to the wider ecosystem. | Inspectable GitHub source (338 stars; 20 forks; updated 2026-07-20); popularity is context, not proof of reliability. | medium | README.md | 1,369 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1369 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | context;verification | builder | cross-layer | adjacent | curated-index | C | ok | https://github.com/XMUDeepLIT/Awesome-Self-Evolving-Agents | GitHub - XMUDeepLIT/Awesome-Self-Evolving-Agents: A Survey of Self-Evolving Agents | A curated list of resources (surveys, papers, benchmarks, and opensource projects) on Self-Evolving Agents. · GitHub | A Survey of Self-Evolving Agents | A curated list of resources (surveys, papers, benchmarks, and opensource projects) on Self-Evolving Agents. - XMUDeepLIT/Awesome-Self-Evolving-Agents | 2026-02-09 | 2026 | XMUDeepLIT/Awesome-Self-Evolving-Agents | GitHub | github-api | XMUDeepLIT/Awesome-Self-Evolving-Agents | 338 | 20 | 2026-02-09T10:57:30Z | 2026-07-20T07:30:16Z | 2026-07-20T09:31:57 | |||||||
ale-0588 | Adjacent Awesome Lists | adjacent-awesome-lists | List | 🧭 | Awesome AI Agent Papers | https://github.com/VoltAgent/awesome-ai-agent-papers | external | github.com | Curated 2026 research collection across agent engineering, memory, evaluation, workflows, and autonomous systems, a paper-level feeder for loop-design foundations. | Curated 2026 research collection across agent engineering, memory, evaluation, workflows, and autonomous systems, a paper-level feeder for loop-design foundations. | Curated 2026 research collection across agent engineering, memory, evaluation, workflows, and autonomous systems, a paper-level feeder for loop-design foundations. | Evaluation data is used as the feedback signal for improving loop behavior. Curated 2026 research collection across agent engineering, memory, evaluation, workflows, and autonomous systems, a paper-level feeder for loop-design foundations. | Use Awesome AI Agent Papers to reuse a concrete artifact or connect it to the wider ecosystem. | Inspectable GitHub source (1,599 stars; 166 forks; MIT license; updated 2026-07-20); popularity is context, not proof of reliability. | medium | README.md | 1,370 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1370 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | context;verification | builder | cross-layer | adjacent | curated-index | C | ok | https://github.com/VoltAgent/awesome-ai-agent-papers | GitHub - VoltAgent/awesome-ai-agent-papers: A curated collection of AI agent research papers released in 2026, covering agent engineering, memory, evaluation, workflows, and autonomous systems. · GitHub | A curated collection of AI agent research papers released in 2026, covering agent engineering, memory, evaluation, workflows, and autonomous systems. - VoltAgent/awesome-ai-agent-papers | 2026-02-10 | 2026 | VoltAgent/awesome-ai-agent-papers | GitHub | github-api | VoltAgent/awesome-ai-agent-papers | 1599 | 166 | MIT | 2026-02-10T10:58:31Z | 2026-07-20T07:10:54Z | 2026-07-20T09:31:57 | ||||||
ale-0589 | Adjacent Awesome Lists | adjacent-awesome-lists | List | 🧭 | awesome-ralph | https://github.com/snwfdhmp/awesome-ralph | external | github.com | Curated directory for the Ralph technique, collecting official resources, implementations, playbooks, tutorials, and community channels for running coding agents in automated loops until specifications are fulfilled. | Curated directory for the Ralph technique, collecting official resources, implementations, playbooks, tutorials, and community channels for running coding agents in automated loops until specifications are fulfilled. | Curated directory for the Ralph technique, collecting official resources, implementations, playbooks, tutorials, and community channels for running coding agents in automated loops until specifications are fulfilled. | Primary-source operational guidance rather than commentary. Curated directory for the Ralph technique, collecting official resources, implementations, playbooks, tutorials, and community channels for running coding agents in automated loops until specifications are fulfilled. | Use awesome-ralph to reuse a concrete artifact or connect it to the wider ecosystem. | Inspectable GitHub source (913 stars; 72 forks; updated 2026-07-13); popularity is context, not proof of reliability. | medium | README.md | 1,371 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1371 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | whole-loop | builder | cross-layer | adjacent | curated-index | C | ok | https://github.com/snwfdhmp/awesome-ralph | GitHub - snwfdhmp/awesome-ralph: A curated list of resources about Ralph, the AI coding technique that runs AI coding agents in automated loops until specifications are fulfilled. · GitHub | A curated list of resources about Ralph, the AI coding technique that runs AI coding agents in automated loops until specifications are fulfilled. - snwfdhmp/awesome-ralph | 2026-01-19 | 2026 | snwfdhmp/awesome-ralph | GitHub | github-api | snwfdhmp/awesome-ralph | 913 | 72 | 2026-01-19T08:42:54Z | 2026-07-13T12:09:52Z | 2026-07-20T09:31:57 | |||||||
ale-0590 | Adjacent Awesome Lists | adjacent-awesome-lists | List | 🧭 | Awesome Agent Loops | https://github.com/serenakeyitan/awesome-agent-loops | external | github.com | Curated collection of /loop, /goal, and /schedule commands for Claude Code and Codex sourced from practitioner posts, organized around trigger, condition, and skill structure. | Curated collection of /loop, /goal, and /schedule commands for Claude Code and Codex sourced from practitioner posts, organized around trigger, condition, and skill structure. | Curated collection of /loop, /goal, and /schedule commands for Claude Code and Codex sourced from practitioner posts, organized around trigger, condition, and skill structure. | The trigger or cadence is explicit, making the workflow recurring rather than one-off. Curated collection of /loop, /goal, and /schedule commands for Claude Code and Codex sourced from practitioner posts, organized around trigger, condition, and skill structure. | Use Awesome Agent Loops to reuse a concrete artifact or connect it to the wider ecosystem. | Inspectable GitHub source (195 stars; 16 forks; CC-BY-4.0 license; updated 2026-07-19); popularity is context, not proof of reliability. | medium | README.md | 1,372 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1372 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | objective;trigger | builder | cross-layer | adjacent | curated-index | C | ok | https://github.com/serenakeyitan/awesome-agent-loops | GitHub - serenakeyitan/awesome-agent-loops: A curated collection of the best /loop, /goal, and /schedule uses for Claude Code & Codex — real commands sourced from Twitter/X. The awesome-list of agent loops. · GitHub | A curated collection of the best /loop, /goal, and /schedule uses for Claude Code & Codex — real commands sourced from Twitter/X. The awesome-list of agent loops. - serenakeyitan/awesome-agent-loops | 2026-06-09 | 2026 | serenakeyitan/awesome-agent-loops | GitHub | github-api | serenakeyitan/awesome-agent-loops | 195 | 16 | CC-BY-4.0 | 2026-06-09T01:26:51Z | 2026-07-19T16:20:51Z | 2026-07-20T09:31:57 | ||||||
ale-0591 | Adjacent Awesome Lists | adjacent-awesome-lists | List | 🧭 | Awesome Loop Models | https://github.com/huskydoge/Awesome-Loop-Models | external | github.com | Dedicated catalog of architectures that reuse a learned layer, block, module, or operator within one forward process; use it for deeper model-level coverage while this repository focuses on the bridge to operational agent loops. | Dedicated catalog of architectures that reuse a learned layer, block, module, or operator within one forward process; use it for deeper model-level coverage while this repository focuses on the bridge to operational agent loops. | Dedicated catalog of architectures that reuse a learned layer, block, module, or operator within one forward process; use it for deeper model-level coverage while this repository focuses on the bridge to operational agent loops. | Connects neighboring ecosystems while preserving Loop Engineering as a narrower operating concept. Dedicated catalog of architectures that reuse a learned layer, block, module, or operator within one forward process; use it for deeper model-level coverage while this repository focuses on the bridge to operational agent... | Use Awesome Loop Models to reuse a concrete artifact or connect it to the wider ecosystem. | Inspectable GitHub source (221 stars; 8 forks; MIT license; updated 2026-07-20); popularity is context, not proof of reliability. | medium | README.md | 1,373 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1373 | 2026-07-18 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | whole-loop | builder | model | adjacent | curated-index | C | ok | https://github.com/huskydoge/Awesome-Loop-Models | GitHub - huskydoge/Awesome-Loop-Models: A curated list of papers and selected technical blogs on Loop Models. · GitHub | A curated list of papers and selected technical blogs on Loop Models. - huskydoge/Awesome-Loop-Models | 2026-04-24 | 2026 | huskydoge/Awesome-Loop-Models | GitHub | github-api | huskydoge/Awesome-Loop-Models | 221 | 8 | MIT | 2026-04-24T12:16:55Z | 2026-07-20T06:25:21Z | 2026-07-20T09:31:57 | |||||
ale-0592 | Explore And Reuse | explore-and-reuse | Template | 🧾 | Resource Atlas | https://chaoyue0307.github.io/awesome-loop-engineering/ | external | chaoyue0307.github.io | Filter 601 resources by goal, loop layer, lifecycle stage, artifact type, evidence class, and search query. | Filter 601 resources by goal, loop layer, lifecycle stage, artifact type, evidence class, and search query. | Filter 601 resources by goal, loop layer, lifecycle stage, artifact type, evidence class, and search query. | Turns the evidence into an interactive atlas and structured data. Filter 601 resources by goal, loop layer, lifecycle stage, artifact type, evidence class, and search query. | Use Resource Atlas to reuse a concrete artifact or connect it to the wider ecosystem. | Reusable template, schema, checklist, or guide; signal comes from concrete adaptation and validation. | medium | README.md | 1,381 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1381 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | objective | builder | cross-layer | enabling | reusable-artifact | A | ok | https://chaoyue0307.github.io/awesome-loop-engineering/ | Awesome Loop Engineering | Explore 601 resources from model recurrence to governed agent operations, then build with 20 patterns, 20 contracts, and 8 runtime starters. | Chaoyue He | chaoyue0307.github.io | html-meta | 2026-07-20T09:31:57 | ||||||||||||||
ale-0593 | Explore And Reuse | explore-and-reuse | List | 🧭 | Hugging Face dataset | https://huggingface.co/datasets/cy0307/awesome-loop-engineering | external | huggingface.co | Query the full collection as generated CSV and JSONL tables with publication, evidence, and lifecycle fields. | Query the full collection as generated CSV and JSONL tables with publication, evidence, and lifecycle fields. | Query the full collection as generated CSV and JSONL tables with publication, evidence, and lifecycle fields. | Packages the evidence as queryable CSV and JSONL rather than only a rendered page. Query the full collection as generated CSV and JSONL tables with publication, evidence, and lifecycle fields. | Use Hugging Face dataset to reuse a concrete artifact or connect it to the wider ecosystem. | Contextual source from huggingface.co; useful for practice signals or boundary conditions, not independent validation. | contextual | README.md | 1,382 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1382 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | whole-loop | builder | cross-layer | enabling | curated-index | C | ok | https://huggingface.co/datasets/cy0307/awesome-loop-engineering | cy0307/awesome-loop-engineering · Datasets at Hugging Face | We’re on a journey to advance and democratize artificial intelligence through open source and open science. | Hugging Face | domain-fallback | 2026-07-20T09:31:57 | |||||||||||||||
ale-0594 | Explore And Reuse | explore-and-reuse | Template | 🧾 | Dataset export guide | data/README.md | local_path | Load, query, regenerate, and audit the CSV, JSONL, and Resource Atlas data. | Load, query, regenerate, and audit the CSV, JSONL, and Resource Atlas data. | Load, query, regenerate, and audit the CSV, JSONL, and Resource Atlas data. | Packages the evidence as queryable CSV and JSONL rather than only a rendered page. Load, query, regenerate, and audit the CSV, JSONL, and Resource Atlas data. | Use Dataset export guide to reuse a concrete artifact or connect it to the wider ecosystem. | Repository file; inspect the linked schema, example, guide, or implementation. | medium | README.md | 1,383 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1383 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | whole-loop | builder | cross-layer | enabling | repository-native | A | local_ok | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/data/README.md | Dataset export guide | 2026 | GitHub | GitHub | repository | 2026-07-20T09:31:57 | |||||||||||||||
ale-0595 | Explore And Reuse | explore-and-reuse | Template | 🧾 | Runtime selection guide | meta/RUNTIME_SELECTION.md | local_path | Compare session, scheduled, CI, cron, and durable runtimes by persistence, isolation, permissions, and state. | Compare session, scheduled, CI, cron, and durable runtimes by persistence, isolation, permissions, and state. | Compare session, scheduled, CI, cron, and durable runtimes by persistence, isolation, permissions, and state. | Durable execution and replay are treated as first-class loop infrastructure. Compare session, scheduled, CI, cron, and durable runtimes by persistence, isolation, permissions, and state. | Use Runtime selection guide to reuse a concrete artifact or connect it to the wider ecosystem. | Repository file; inspect the linked schema, example, guide, or implementation. | medium | README.md | 1,384 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1384 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | trigger;workspace;state | builder | cross-layer | enabling | repository-native | A | local_ok | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/meta/RUNTIME_SELECTION.md | Runtime selection guide | 2026 | GitHub | GitHub | repository | 2026-07-20T09:31:57 | |||||||||||||||
ale-0596 | Explore And Reuse | explore-and-reuse | Template | 🧾 | Future Directions agenda | FUTURE-DIRECTIONS.md | local_path | Turn 15 open problems into measurable studies, runtime projects, product pilots, and shared standards. | Turn 15 open problems into measurable studies, runtime projects, product pilots, and shared standards. | Turn 15 open problems into measurable studies, runtime projects, product pilots, and shared standards. | Turns open gaps into measurable research, infrastructure, and product directions. Turn 15 open problems into measurable studies, runtime projects, product pilots, and shared standards. | Use Future Directions agenda to reuse a concrete artifact or connect it to the wider ecosystem. | Repository file; inspect the linked schema, example, guide, or implementation. | medium | README.md | 1,385 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1385 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | whole-loop | builder | cross-layer | enabling | repository-native | A | local_ok | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/FUTURE-DIRECTIONS.md | Future Directions agenda | 2026 | GitHub | GitHub | repository | 2026-07-20T09:31:57 | |||||||||||||||
ale-0597 | Shape What Comes Next | shape-what-comes-next | Template | 🧾 | Release notes | https://github.com/ChaoYue0307/awesome-loop-engineering/releases | external | github.com | Versioned changelog of new resources, patterns, and repository changes. | Versioned changelog of new resources, patterns, and repository changes. | Versioned changelog of new resources, patterns, and repository changes. | Turns open questions and operating lessons into visible next work. Versioned changelog of new resources, patterns, and repository changes. | Use Release notes to reuse a concrete artifact or connect it to the wider ecosystem. | Inspectable GitHub source (35 stars; 7 forks; CC0-1.0 license; updated 2026-07-20); popularity is context, not proof of reliability. | medium | README.md | 1,400 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1400 | 2026-07-15 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | whole-loop | builder | cross-layer | enabling | reusable-artifact | A | ok | https://github.com/ChaoYue0307/awesome-loop-engineering/releases | Releases · ChaoYue0307/awesome-loop-engineering · GitHub | 🔁 Build reliable recurring AI-agent systems: 601 resources, 20 operational patterns, 20 loop contracts, 8 runtime starters, an interactive atlas, and a structured dataset. - Releases · ChaoYue0307/awesome-loop-engineering | 2026-06-09 | 2026 | GitHub Releases | GitHub | github-api | ChaoYue0307/awesome-loop-engineering | 35 | 7 | CC0-1.0 | 2026-06-09T16:17:27Z | 2026-07-20T09:11:11Z | 2026-07-20T09:31:57 | |||||
ale-0598 | Shape What Comes Next | shape-what-comes-next | Template | 🧾 | Roadmap | ROADMAP.md | local_path | Near-term work, pattern priorities, gallery goals, and open questions. | Near-term work, pattern priorities, gallery goals, and open questions. | Near-term work, pattern priorities, gallery goals, and open questions. | Turns open questions and operating lessons into visible next work. Near-term work, pattern priorities, gallery goals, and open questions. | Use Roadmap to reuse a concrete artifact or connect it to the wider ecosystem. | Repository file; inspect the linked schema, example, guide, or implementation. | medium | README.md | 1,401 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1401 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | objective | builder | cross-layer | enabling | repository-native | A | local_ok | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/ROADMAP.md | Roadmap | 2026 | GitHub | GitHub | repository | 2026-07-20T09:31:57 | |||||||||||||||
ale-0599 | Shape What Comes Next | shape-what-comes-next | Template | 🧾 | Launch article | posts/launch.md | local_path | Concise explanation of the concept, implementation kit, and evidence base. | Concise explanation of the concept, implementation kit, and evidence base. | Concise explanation of the concept, implementation kit, and evidence base. | Turns open questions and operating lessons into visible next work. Concise explanation of the concept, implementation kit, and evidence base. | Use Launch article to reuse a concrete artifact or connect it to the wider ecosystem. | Repository file; inspect the linked schema, example, guide, or implementation. | medium | README.md | 1,402 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1402 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | whole-loop | builder | cross-layer | enabling | repository-native | A | local_ok | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/posts/launch.md | Launch article | 2026 | GitHub | GitHub | repository | 2026-07-20T09:31:57 | |||||||||||||||
ale-0600 | Shape What Comes Next | shape-what-comes-next | Template | 🧾 | Discussion guide | meta/DISCUSSIONS.md | local_path | Suggested discussion categories, starter prompts, and moderation standard. | Suggested discussion categories, starter prompts, and moderation standard. | Suggested discussion categories, starter prompts, and moderation standard. | The resource is directly reusable as a starting artifact. Suggested discussion categories, starter prompts, and moderation standard. | Use Discussion guide to reuse a concrete artifact or connect it to the wider ecosystem. | Repository file; inspect the linked schema, example, guide, or implementation. | medium | README.md | 1,403 | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/README.md#L1403 | Apply | apply | Reuse, adapt, and contribute concrete loop artifacts. | whole-loop | builder | cross-layer | enabling | repository-native | A | local_ok | https://github.com/ChaoYue0307/awesome-loop-engineering/blob/main/meta/DISCUSSIONS.md | Discussion guide | 2026 | GitHub | GitHub | repository | 2026-07-20T09:31:57 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.