arXiv AI

Chronicle: Cut-Point Replay for Regression Testing of LLM Agents

Chronicle introduces a method called cut‑point replay to make regression testing of large language model (LLM) agents reproducible. It records an agent’s run at non‑deterministic boundaries as immutable envelopes and then replays selected boundaries while executing the rest live, enabling continuous‑integration tests that detect faulty code changes. Benchmarks show minimal overhead, perfect bit‑stability, and effective detection of unsafe actions in a mutation study.

Hugging Face Trending Papers
Sep 17

Chronicle: Cut-Point Replay for Regression Testing of LLM Agents

Chronicle introduces a method called cut‑point replay to make regression testing of large language model (LLM) agents reproducible. It records an agent run at non‑deterministic boundaries as immutable envelopes and replays selected boundaries while executing the rest live, turning recorded failures into continuous‑integration tests. Benchmarks show minimal overhead, bit‑stable full replay, and effective detection of faulty code changes in a mutation study.

arXiv AI
Oct 9

TestJack: Should you trust the results in coding benchmarks? Agentic Coding Benchmarks Auditing via Evaluator Evolution

TestJack is a scalable framework that audits large language model (LLM) coding agents by generating new tests for each trial, focusing on prompt requirements that may be violated. It keeps only the tests passed by the ground‑truth patch and re‑examines failures, providing replayable evidence for each confirmed error. In experiments across six model backends and five benchmarks, TestJack found that 34.4% of trials deemed correct actually violated task requirements, reducing the overall resolution rate from 50.6% to 33.2%.

By Shuangjie Yao, Hao Wang, Koushik Sen, Simin Chen, Baishakhi Ray, Dawn Song
arXiv AI
Sep 30

Boundary-State Control for Tool-Using Language-Model Agents: Commit-Time Consistency under State Drift

The paper introduces BSC‑R, a deterministic effect‑boundary mechanism that ties a single‑use commit authorization to the specific action and the semantic state that justified it, aiming to close the proposal‑to‑commit gap in tool‑using language‑model agents. Experiments on 2,847 AgentDojo episodes and 10,302 frozen proposals show that BSC‑R preserves the agent’s original behavior while rejecting unauthorized changes, and further tests on a boundary‑drift experiment and the CONTINUITY suite demonstrate high success rates in valid contexts and robust handling of replay and ambiguous cases. However, broader testing reveals that BSC‑R still allows a 25% invalid‑effect commit rate in a larger attack set, indicating that it provides scoped, not universal, safety.

By Wesley Shu
arXiv AI
Nov 5

Attributing Agent Failures to Their History Needs an Executed Counterfactual: Toward a Reporting Standard

The paper proposes a new reporting standard for attributing agent failures to their history, insisting on intervention‑verified evidence rather than post‑hoc taxonomies. It outlines a method to freeze an executable mid‑trajectory state, alter only the agent’s perceived history, and continue execution to obtain a measured replay certificate. The authors review existing manipulation classes and highlight that while several methods perform interventions, none currently report a quantified replay certificate, and they provide two cautionary examples illustrating the pitfalls of lacking such verification.

By Egor Pakhomov, Erik Nijkamp
arXiv AI
Oct 16

Independent Data-Integrity Verification for LLM-Driven Functional Coverage Closure in Hardware Design

The paper presents a small coverage‑closure agent that verifies data integrity for LLM‑generated functional tests in hardware design. It reads coverage from simulation reports (cocotb‑coverage YAML) and uses separate scoreboards to check data, rather than relying on the model’s account. Applied to three different RTL designs—a FIFO, a UART transmitter, and an AHB2APB bridge—the agent increased coverage from 91.7%, 88.9%, and 67.4% to 100% within eight iterations, and also uncovered a clock‑domain‑crossing bug in a manual testbench.

By Venkata Krishna Kumar Vedantam
arXiv AI
Aug 26

Rebuild Dossier: Mechanically-Enforced Specs for Agentic App Rebuilds, and What Model-Tier Failures Reveal

The paper introduces rebuild‑dossier, an open‑source tool that locks an application’s real interface before code is written and enforces one‑test‑at‑a‑time building through automated checks. In experiments, a compliant agent failed a held‑back test while a rule‑breaking agent passed, showing that a passing test suite can be gamed. The study also demonstrates that the automated check mechanism, rather than interface‑locking alone, is crucial for reliable rebuilds, and that multi‑level verification catches errors that single‑level checks miss.

By Parker Fawcett